From: rafetmad@cheshire.oxy.edu (David Giller) Subject: Re: Bus Mouse Tester > not working Date: Tue, 18 Aug 1992 08:33:36 GMT
viggo@diku.dk (Allan Kim Schougaard) wrote:
>gt6698a@prism.gatech.EDU (Andrew Hobson) writes:
>
>>I have a bus mouse, but linux 97 patch 1 does not recognize it.
>
>Me too also not working. ;-(
>
>I have tried :
>
># cat /dev/bm
>cat: bm: Try again
Actually, this is the proper behaviour.
>And:
>
># mouse Microsoft /dev/bm
>Play with mouse. Press Ctrl-c to ...
>{nothing happens}
>Finished
I've never tried it like that, but you might want to try it with
'mouse MouseSystems /dev/bm' or 'mouse BusMouse /dev/bm' although the
mouse program really isn't written to recognize bus mice. I think I
patched it once to get it to work with BusMouse (the code was there,
just commented out). And you might run into the 'Try Again' problem.
This is normal. The mouse isn't meant to be read by normal programs.
You are supposed to read it 3 bytes at a time.
>During boot Linux displays the message:
>
>Busmouse detected and installed.
>
>The jumpers are installed at IRQ3 port 02c8 (not sure about the port)
>and the mouse workes perfectly in dos.
Ah, here's a problem. Most mice are configured on IRQ5, and so
the mouse driver assumes that. If you can recompile the kernel, you
can change this (it is trivial, but you must recompile the kernel).
I don't have any idea how to autodetect what IRQ the mouse is on.
Another {ossibility is that you have one of the newer bus mice that
are really hacked serial ports. I don't know what to say about
this, except that using the setserial program may get you going.
Also, Xconfig must say that the mouse is mousesystems or busmouse.
microsoft and logitech won't work.
-Dave
-- David Giller, Box 134 | Q: How many Oregonians does it take to screw in a light Occidental College | bulb? A: Three. One to replace the bulb, and two to 1600 Campus Road | fend off all the Californians trying to share the Los Angeles, CA 90041 | experience. ---------------------------rafetmad@oxy.edu