From: Ian Justman (ianj@citrus.SAC.CA.US)
Date: 02/06/93


From: ianj@citrus.SAC.CA.US ( Ian Justman )
Subject: Re: MS Busmouse problem solved!!!
Date: 7 Feb 1993 00:08:42 GMT

chiang@cs.uiuc.edu (Sam. H.K. Chiang) writes:
: wgcho@cair.kaist.ac.kr (Cho Wongyu) writes:
:
: >I realized that the kernel uses IRQ5 for Microsoft Busmouse and examined my
: >interface board. Guess what? There are jumpers for setting the IRQ!
: >After changing the jumpers from IRQ2 to IRQ5, my mouse works as a miracle
: >under X. Although the mouse test program which is bundled with SLS doesn't
: >work, now I am *very* happy with my Linux and my mouse.
:
: It happens to my MouseSystem bus mouse, too. After setting up IRQ to 3 (4?),
: I can use /dev/ttys0 (com 1) to drive my bus mouse.
:
: >Well, after all, it was quite a simple problem. However, I think that this
: >should be *definitely* included in the FAQs.
:
: Definitely should be included in linux.faq about how to setting up the jumpers
: on bus mouse to select IRQ.

However, what should also be included in the FAQ is that if you jumper a card
so that it uses IRQ2, like I did with MY mouse, also a Microsoft, YOU CANNOT
TELL THE KERNEL TO MONITOR IRQ2!!!!! IT WILL BE FELT AS IRQ9. IRQ2 is the
cascade interrupt and is, for very good reason, shunted to a black-hole rou-
tine within the interrupt code.

-- 
Born to void warranties!        ianj@ijpc.UUCP