From owner-freebsd-questions Thu Oct 7 21: 9: 9 1999 Delivered-To: freebsd-questions@freebsd.org Received: from earth.wnm.net (earth.wnm.net [208.246.240.243]) by hub.freebsd.org (Postfix) with ESMTP id 77AAD153C4 for ; Thu, 7 Oct 1999 21:08:46 -0700 (PDT) (envelope-from alex@wnm.net) Received: from localhost (alex@localhost) by earth.wnm.net (8.8.8/8.8.8) with ESMTP id XAA29416; Thu, 7 Oct 1999 23:12:16 -0500 (CDT) Date: Thu, 7 Oct 1999 23:12:15 -0500 (CDT) From: Alex Charalabidis To: J McKitrick Cc: freebsd-questions@FreeBSD.ORG Subject: Re: mouse lockup in X In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Oct 1999, J McKitrick wrote: > Sometimes when i start FBSD, the mouse won't work in windowmaker. Other > times it is fine. Starting X again or logging out and back in don't work. > Only a reboot cures it. ANy ideas? > FBSD 3.2 > Toshiba Satellite laptop with PS/2 mouse I first encountered this immediately after upgrading to 3.3-RC. It would very rarely work when starting X and WM. The mouse (PS/2 to 9-pin adaptor on sio0 using the mousesystems protocol) would not work in console either. Both moused and X would detect it and identify it correctly but it would refuse to move. Initially I got it to work in Microsoft (two-button) mode only until I tried a more sophisticated approach... Try twiddling the mouse connector or dis- and reconnecting it - oddly enough, this is what fixes it for me. Since I'm pretty sure I don't have a hardware/connector problem and it only started doing it right after installing 3.3-RC, this behaviour strikes me as strange. -ac -- Alex Charalabidis WebNet Memphis (901) 432-6000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message