I've finally gotten my ParadisePlus board to display properly, but
I still haven't figured out what I need to do to tell X386 about my
mouse... Can someone help me?
Rick, the following may help you. It's probably findable as a previous
post in this newsgroup.
---------------the following article that posted may help ----------------
Article: 6134 of comp.os.linuxQuote:>From gatech!prism!gt7080a Tue Jul 21 17:52:17 EDT 1992
THE 0.96c-patchlevel2 KERNEL SUPPORTS LOGITECH AND COMPATABLE BUS MICEQuote:>Forgot to mention last time another problem. Trying to get my
>bus mouse to work. Have a logitech trackman, and linux kernel finds
>it correctly and init's it. However, I don't seem to have a /dev/mouse
>to correspond to it. Any suggestions? I RTFFAQ but didn't see anything
>on the bus mouse.
(you can find a patched kernel as /pub/Linux/Incoming/linux-0.96c-pl2.tar.Z
If you are unsure that you have a bus mouse or not, check to see if your
mouse card has a selection for a sample rate switchable between 30Hz
and 60Hz (or possibly 25/50Hz), if it does not, then it is NOT a true
bus mouse (InPort mice for example will not work with this driver).
To create a bus mouse device:
mknod /dev/mouse c 10 0
What do I use in my Xconfig file to use the bus mouse? Logitech doesn't
Here are the mouse lines from my Xconfig:
You may add a sample rate if you want, but chances are, unless the model
number on your mouse matches mine: PC-93-9MD it probably will cause your
machine to lock up, as I've gotten several reports saying that.
According to the X386 documentation, non-logitech mice do not support
a sample rate.
How do I make mgr use my bus mouse?
Well you don't have to. Once you've created /dev/mouse you're set.
Now you've got something that resembles a piece of a faq... maybe
it will make its way into the real faq...
(sorry to have to waste so much space)
Anguna V. Ynerqb
Trbetvn Vafgvghgr bs Grpuabybtl, Ngynagn Trbetvn, 30332
I'm having difficulties getting an inport mouse to work with X386....it works
fine with WinDoze, and I managed to get the kernel to see it (I had to use IRQ4
as I have a scsi card at IRQ5). The server now sees the mouse but it behaves as
though the protocol is wrong. Movement is erratic and uncoordinted...
Any ideas? I'll summarise to the group ....