Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!umn.edu!csus.edu!netcom.com!netcom!ceb From: ceb@netcom6.Netcom.COM (Buckley) Subject: Re: Mouse problem...XFree86-1.3 on NetBSD 0.9 In-Reply-To: rkb55989@uxa.cso.uiuc.edu's message of 7 Oct 1993 18:43:36 GMT Message-ID: <CEB.93Oct8032151@netcom6.Netcom.COM> Sender: ceb@netcom.com (Buckley) Organization: Netcom Online Communications Service References: <5OCT93.04385139@tifrvax.tifr.res.in> <MYCROFT.93Oct6062234@duality.gnu.ai.mit.edu> <291o0o$h37@vixen.cso.uiuc.edu> Date: Fri, 8 Oct 1993 11:21:51 GMT Lines: 45 In article <291o0o$h37@vixen.cso.uiuc.edu> rkb55989@uxa.cso.uiuc.edu (Rafal Boni) writes: From: rkb55989@uxa.cso.uiuc.edu (Rafal Boni) Newsgroups: comp.os.386bsd.questions mycroft@duality.gnu.ai.mit.edu (Charles Hannum) writes: >In article <5OCT93.04385139@tifrvax.tifr.res.in> >bhiksha@tifrvax.tifr.res.in writes: > When i use a logitech 3-button mouse, (with the default XConfig), > i get very odd response: the cursor movements are staccatto and > dont seem to correlate to the mouse motions very much. Also, the > machine seems to be receiving a lot of button-clicks, even though i > dont touch the buttons and the screen goes haywire. >This is odd. These are symptoms of two things: >* Using the wrong minor device number number. The mouse should have >minor number 1, not 0. The MAKEDEV script gets this right. >* There is a bug in XFree86 related to the boundary condition of Hmm... I don't mean to start stakes burning or anything of that nature, but.... The result: same problems as described above, BUT it's a serial mouse on the same port as the old mouse [hence minor/major versions should be OK, since the old mouse worked...], and even small movements suffered Look, guys, don't go off the deep end. I had the same problems when I installed XFree with my brand new Logitech First mouse. They disappeared entirely when I changed the mouse typ in the configuration from "Logitech" to "MouseMan", even though the documentaiton leads you to do otherwise. I got the tipoff from a faxback document available from Logitech telling you how to determine what kind of mouse your mouse is if you don't know. Once you change that, it runs right out of the box, modulo dinking around with the display parameters to compensate for the latest in non-VESA monitor "excitement" from Taiwan. -- --