/dev/mouse: Device or resource busy
From: Charlie Gibbs (cgibbs_at_kltpzyxm.invalid)
Date: 09/17/04
- Next message: ANTant_at_zimage.com: "Any known issues with an Asus K8V SE Deluxe?"
- Previous message: Clive Dove: "Re: mandrake 10 installed OK w/out inserting UN & PW, but now insists I login USING them.... :-( WTF?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 17 Sep 04 00:16:05 -0800
First, a bit of rambling...
I was given an old box for parts, but I realized that it wouldn't
take much to get it going again. All it was missing was the hard
drive and floppy drive; it still had a 200-MHz PII, 224MB RAM,
onboard serial, parallel, and USB ports, ATI Rage 128 video card,
CD-ROM drive, CD burner, PCI parallel card, and three ISA cards:
a Sound Blaster, a 3Com EtherLink III (3C509B), and a USR 33.6
modem.
This was far too much hardware to not try to get it going again.
A niece of ours wants a machine, and doesn't mind being a guinea pig
for my best efforts to put together a user-friendly Linux machine.
My local computer surplus store didn't have any hard drives in the
5 to 10GB range, but I picked up two smaller drives - 1.28 and 1.08
GB - for $15 each, plus a secondhand floppy drive. I allocated 80MB
on /dev/hda for swap and left the remaining 1.2G for /, and put two
partitions on /dev/hdb: half for /opt and half for /home. By dropping
the development tools I was able to fit Slackware 9.1 quite comfortably
on this setup - complete with Gnome and KDE, which took up 70% of
the 500MB /opt partition. (I did say I wanted to give my nice a
user-friendly setup, right?)
Now comes the interesting part. I've been gradually getting the
peripherals going. The Ethernet card wasn't that much trouble,
and neither was the Sound Blaster. But when I tried firing up X,
it kept failing with the messages:
(EE) xf86OpenSerial: Cannot open device /dev/mouse
Device or resouce busy.
(EE) Mouse1: cannot open input device
(EE) PreInit failed for input device "Mouse1"
No core pointer
I tried googling for this error, and came up with lots of hits.
Most of them suggested getting rid of gpm - but ps showed that
gpm wasn't running. In fact, the last messages that came up while
booting were:
Starting gpm: /usr/sbin/gpm -m /dev/mouse -t ps2
gpm: oops() invoked from gpm.c(977)
/dev/mouse: Device or resource busy
So who the heck is using the mouse? fuser was silent. I couldn't
understand it, especially since I had X working (KDE in all its glory,
mouse and all) before I started messing around with the Sound Blaster.
Yup, you guessed it, the Sound Blaster and the EtherLink III don't
play well together. Either one works fine on its own, and the
Sound Blaster works regardless, but if I put them both in together,
the "Device or resource busy" message comes up for the mouse. Just
one more cause for that ubiquitous error, I suppose.
Meanwhile, the Sound Blaster makes the EtherLink III fail to
receive. Pings from elsewhere on the network get no response.
Pinging from this machine gets "Destination Host Unreachable",
although the activity lights blink on the network.
Any hints as to how to make these two cards work together without
messing up the mouse? Or should I just get a cheap PCI NIC and
forget about it? (After all, I still have that modem card to
fiddle with...)
-- /~\ cgibbs@kltpzyxm.invalid (Charlie Gibbs) \ / I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
- Next message: ANTant_at_zimage.com: "Any known issues with an Asus K8V SE Deluxe?"
- Previous message: Clive Dove: "Re: mandrake 10 installed OK w/out inserting UN & PW, but now insists I login USING them.... :-( WTF?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|