bloody

I've been using the mouse for well...forever, and everything had been okay up until a few weeks ago. I'm not sure why it's happening, but it's actually a pretty annoying problem. I've no idea where the problem lies(KDE, X, kernel...I've no idea). The one place where this gets really annoying is when I'm using my image viewer. I'd like to be able to scroll through them without skipping half of them(and without using my keyboard), for the sake of convenience. If anyone has any bright ideas, please do speak up, because I'm quite frustrated by this point. (I know I mentioned only one place where it's an issue, but it also seems to scroll twice as many text lines in text-ish programs (id est kate))

Thanks danleff... It seems that was right on the mark. 'tis a PS/2 Mouse, and the problem was fairly easy to fix. All I had to do was change the device from '/dev/psaux' to '/dev/input/mice' and voila, problem fixed.

Yeah, I switched to kernel 2.6, although I'm not sure if that's where the problem started or not. I think it'd be a good place to look though...

Debian (testing)

I've been having yet another feud with linux over my disk drives, a nd it has finally managed to get on my nerves. It seems Linux has a grudge against me, and doesn't want to eject cds, that, or something must be wrong(Oh my!) Whether I try to eject using KDE, a terminal of some sort, or whatever, it simply won't let me do it, it tells me that the umount has failed because the device is busy.....and it's not, the device isn't busy at all! How annoying...

Erm, I'm not sure, I'm using a fairly up-to-date Debian Sarge... snapshot from sometime in early May, but I've updated a reasonable bit of it since then, not all of it because I'm forced into using dialup, if you know what I mean. It couldn't be the kernel version could it? I do recall that it's using the 2.4 kernel instead of 2.6, if that could do it. Hmm, the idea of that shell script sounds like an intriguing idea, I think I just might have to try that out. [an hour or so later] Ah,yes,k a little help in writing one may come of use... Any good ideas on getting the script to execute something (more specifically - fuser) as root in the script? So far what I have is #!/bin/bash clear screen echo echo "Attempting to kill all processes using the Drive..." echo fuser -kvi /media/cdrom0 echo echo "Attempting to unmount and eject cdrom device 0..." echo #umount /media/cdrom0 eject /media/cdrom0 echo; echo It probably should work if I find myself a way to do that one line as root, though, half the time it gives me an error when I go to the eject(when doing it in terminal as root), something about an invalid argument... eject: unable to eject, last error: Invalid argument Then I run the same script from out of terminal, as myself, afterwards and it ejects it... crazyness, I need help indeed, though, this was an excellent excuse to [attempt to] write my first shell script. Whoa, d***.... 9:30 already, time flies... well, off to bed, need to be up at 3:30.

Originally posted by egorgry: Quote: Did Danleff reply to this thread or are you refering to me? anyway famd is the file allocation manager daemon. It is the daemon that scans your filesystems looking for changes and such. Sorry about that, I was kinda reading a couple posts at once, and mixed myself up, so yeah, I meant you... Crap, that's embarrassing, I really need more caffeine around here. Dapper Dan: That's more or less exactly what I was doing, just I wasn't having near as much luck, so I'm pretty much stuck using egorgry's method, which seems to be working pretty consistently.

Mr.iamroot, not even the godly powers of root would free my disks from their prisons, sad ne? Okay, thank you danleff, that was much easier than logging out just to take out a disk I must say. I still though, have no idea why famd was using the drives, then again, I really have no idea what famd is in the first place. After killing famd it seems konqueror was still using the drives as well, strange. Have any ideas on a permanent fix for this?

Wow, my inability to cope with a painful reality has brought me back here yet again. This painful reality is the fact that I have switched to a fairly recent snapshot of Debian Sarge... and I'm rather lacking in the decent graphical support department. I'm not really sure what to do, currently I have it set up with the generic ATI driver (being as I have a Radeon 9700). I'm not really sure what to do to get everything back to smoothness again, any ideas... I think I'll have to shoot myself in the foot if I have to stay at a 800x600 resolution for more than about another five minutes...

It was detecting the monitor fine, and gave me no bigger options for resolutions(I never knew 400 x 300 existed...yeesh, tiny!). I'm not sure if it's neccessarily the best way I could have went about it, but I went ahead and added the resolution I wanted to use to the xf86 config file manually(1280 x 1024), and well, it worked. As for xvidtune, it scared me away with some sort of warning message... the big meanie!(I've killed a monitor before somehow or another...no desire to ruin another) I suppose this problem is as good as solved ne?

No, that shouldn't misdirect the shortcut, that's not the path, the actual path the shortcut is pointing to is probably something like /mnt/camera.

Not so long ago I finally got myself Linux, and bounced around distrobutions and am now using Mandrake. Unfortunately I'm forced into using dialup, yet, my modem that I got seems to be is connecting at a pathetic speed. It's an external Actiontec 56k(serial)... For some odd reason it's only connecting at about 30kbps, whereas back before I switched to Linux I was getting about 50kbps out of this line. Does anyone have any bright ideas on why it's connecting at such a slow rate?

Erm, I think I have it set to somewhere around 128kbps(ish) in the KPPP settings ... One weird thing I noticed when it was connecting is that I think it said it was using V42BIS (unless my eyes decieve me in some way shape or form, or if I'm an idiot, I hope neither are the case) ..... Which is rather old if my memory serves me correctly, why would it do that? Hmm, tried playing with the speed settings, didn't make any difference ...

I recently decided it wouldn't be a bad idea to switch to linux, and as such downloaded something that someone recommended to me, suse 9.1 personal. Seeing as I have dialup and I knew I had a winmodem I expected trouble, and that's exactly what I got. I'm supposing I need some sort of driver to get this working, but I'm not really sure what to do about it. I have all the settings configured, and yes, it is connected properly(I'm posting this right?). I checked the connection log and it says - [tt]SuSE Meta pppd (smpppd-ifcfg), Version 1.16 on linux. Status is: disconnected trying to connect to smpppd connect to smpppd Status is: disconnected Status is: connecting pppd[0]: Plugin passwordfd.so loaded. pppd[0]: --> WvDial: Internet dialer version 1.54.0 pppd[0]: --> Initializing modem. pppd[0]: --> Sending: ATM1 pppd[0]: --> Sending: ATQ0 pppd[0]: --> Re-Sending: ATM1 pppd[0]: --> Modem not responding. pppd[0]: Connect script failed Status is: disconnected pppd[0] died: Connect script failed (exit code 8)[/tt] OS: Suse 9.1 personal Modem: Broadcom Corporation BCM4212 v.90 56k modem (rev 02) Anyone have any ideas?

This site has links to dells download for it, http://www.modemsite.com/56k/bcm.asp

LinuxCrusader: I indeed already tried it without much chance for success. danleff: It's still there ... the red hat rpm for it anyway(it actually started downloading after around the 20th time I tried), which isn't of much use to me. So I would need the kernel source to get it up you say, and I'm guessing gcc also, from the looks of other info I've seen floating around.(neither of which were included sadly) I don't really have the money to go out and buy one(or I probably would have done it already), and even if I did - I wouldn't really be sure what to get. could you point me in the right direction with that?(Maybe I'll get the money later, I hope) I agree It's probably not worth the effort...but it's all I've got at the moment.