From owner-freebsd-current Sat Sep 23 11:50:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 02D2F37B422 for ; Sat, 23 Sep 2000 11:50:48 -0700 (PDT) Received: (qmail 70077 invoked by uid 1040); 23 Sep 2000 18:50:43 -0000 Date: Sat, 23 Sep 2000 20:50:43 +0200 From: =?iso-8859-1?Q?David_Sieb=F6rger?= To: freebsd-current@freebsd.org Subject: Re: -Current + X 4.0.1 = mouse problems Message-ID: <20000923205043.A63108@rucus.ru.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8qi4d2$2c9q$1@ganerc.mips.inka.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG naddy@mips.inka.de (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. Switching from "Auto" to "MouseSystems" is no panacea, however. I've experienced the (apparently common) problem of switching from X to console and back to X and getting an unresponsive mouse pointer in X. This occurs when I use protocol "Auto", or don't specify a protocol. Switching to "MouseSystems" protocol fixes the above problem, but it introduces a problem: the wheels on my mice no longer work in X. While there may be a way to get the wheel working under MouseSystems protocol, I've not found it. I experience this problem with both my FreeBSD workstations: one running 5.0-CURRENT (circa end-of-August) with a Microsoft IntelliMouse 1.1A for PS/2, and a second running 4.1-STABLE (of 19th September) with a Mitsumi PS/2 Scroll Mouse. Both run XFree86 4.0.1. -drs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message