From owner-freebsd-current Tue Sep 26 8:50: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [203.2.75.115]) by hub.freebsd.org (Postfix) with ESMTP id 2799737B42C for ; Tue, 26 Sep 2000 08:49:52 -0700 (PDT) Received: from echidna.stu.cowan.edu.au (perax4-081.dialup.optusnet.com.au [198.142.81.81]) by mail05.syd.optusnet.com.au (8.9.3/8.9.3) with ESMTP id CAA10008; Wed, 27 Sep 2000 02:48:47 +1100 Message-ID: <39C5C99D.5C43EB32@echidna.stu.cowan.edu.au> Date: Mon, 18 Sep 2000 15:51:57 +0800 From: Trent Nelson X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christian Weisgerber Cc: freebsd-current@FreeBSD.ORG Subject: Re: -Current + X 4.0.1 = mouse problems References: <8qi4d2$2c9q$1@ganerc.mips.inka.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > > Doug Barton wrote: > > > Previously I had X + moused working just fine, so I had the best > > of both worlds. With X 4.0.1 if I use moused I get no response from the > > mouse in X at all. > > Make sure you use > > Option "Protocol" "MouseSystems" > > Protocol "Auto" is not reliable. I had XFree86 4.0.1 lock my system up completely if the options "auto" & "/dev/sysmouse" were present - the screen would go blank, no keyboard or mouse response, and a hard reboot was required to get out of it. This is running a reasonably recent 5.0-CURRENT and I actually thought it may have something to do with resource locks as X worked fine if I used "auto" & "/dev/psm0" without `moused' present. Your suggestion has everything working fine now, though. Much appreciated. Regards, Trent. > > -- > Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message