<<I don't understand why you had to do this. Did you try it without doing
<<this first? Also, the header file states the MOUSE_IRQ defaults to 5, not
<<2 as you stated.
BTW, I have RH5.0 and my bus mouse neither auto-detected nor worked when I configured
it this way, does RH5.0 also have interrupt 5 as default, if it does I'll change my
mouse card to Int 5 ???
Mike
Michael Hatzakis, Jr MD
Resident Physiatrist - R3
Thomas Jefferson University Hospital
Department of Rehabilitation Medicine
Philadelphia, PA, 19026
E-Mail Address: [EMAIL PROTECTED]
-----Original Message-----
From: Dave Wreski [SMTP:[EMAIL PROTECTED]]
Sent: Monday, April 27, 1998 10:01 PM
To: M. Neidorff
Cc: [EMAIL PROTECTED]
Subject: Re: Inport busmouse woes. Please help.
> I don't know why configuring a mouse has always given me so much trouble. I
> have a MS Inport BusMouse (It says so on the bottom of the mouse)which makes
> it a busmouse. I have it set to IRQ 2. From experience in 4.0, 4.1, 4.2 I
> learned that I had to change the mouse header file (busmouse.h??) to change
> the IRQ value for the mouse from 2 to 9. I did that and built a new kernel.
I don't understand why you had to do this. Did you try it without doing
this first? Also, the header file states the MOUSE_IRQ defaults to 5, not
2 as you stated.
> I then installed the new kernel and ran mouseconfig. Everything autodetected
> properly (so it seemed). In the /dev directory, /dev/mouse is linked to
> /dev/inportbm which is what I recall is correct for this silly beast. In
> 4.2 using this setup had the mouse working in terminals. Now gpm won't
> recognize my mouse on startup. On shutdown it complains saying that "you
> shouldn't be seeing this error"(that's really helpful :-( ). Does anyone
> have a clue as to what is going on here?
Make sure gpm is using the correct device. "ps ax | grep gpm" should
report something like "gpm -t ps2".
You can run a simple test by making sure gpm nor X are running, and doing
something like:
# cat < /dev/inportbm
which should produce some garbage as you move the mouse. Kill it using
ctrl-c. If you don't seen anything printed, you are using the wrong
device. If you do, then perhaps you are using the wrong protocol, and try
something other than 'ps2'.
And /var/log/dmesg should contain information about your mouse. Be sure
you have compiled the proper mouse support into the kernel as well.
Dave
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
application/ms-tnef
