Return to BSD News archive
Xref: sserve comp.os.386bsd.development:1279 comp.os.386bsd.bugs:1538 Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!uwm.edu!rutgers!utcsri!newsflash.concordia.ca!sifon!homer.cs.mcgill.ca!storm From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER) Newsgroups: comp.os.386bsd.development,comp.os.386bsd.bugs Subject: Re: Microsoft Mouse driver for XFree [NetBSD 0.9] Message-ID: <28n4cf$ce9@homer.cs.mcgill.ca> Date: 3 Oct 93 18:07:11 GMT References: <1993Sep30.172025.8306@dfw.paranet.com> <28lt7o$77t@werple.apana.org.au> Organization: SOCS, McGill University, Montreal, Canada Lines: 30 NNTP-Posting-Host: mnementh.cs.mcgill.ca In article <28lt7o$77t@werple.apana.org.au>, Andrew Herbert <andrew@werple.apana.org.au> wrote: >lacoursj@dfw.paranet.com (Jeff Studman) writes: > >It sounds like your kernel config file (in /sys/arch/i386/conf) is slightly >broken. It should include a line similar to the following: > >device mms0 at isa? port "IO_BMS1" tty irq 5 vector mmsintr > > >Jumpy mice are symptomatic of a mouse device with a minor number of 0 rather >than the 1 that is required for X servers. Using MAKEDEV avoids this >problem. The problem might very well lie in XFree86, which supposedly assumed that Microsoft Mouse=="com?". David Dawes noted this yesterday, and was kind enough to send me a patch that might very well take care of the problem. As soon as I am finished building NetBSD-current, I will start another build of XFree86, and see what happens Toodlepip! Marc 'em. -- ---------------------------------------------------------------------------- Marc Wandschneider Seattle, WA "Satan has a stranglehold on my toilet and he won't let go!" - frm the Weekly World News