From owner-freebsd-stable Mon Jul 24 8:25:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id 1BE2D37BB2C for ; Mon, 24 Jul 2000 08:25:08 -0700 (PDT) (envelope-from steve@sse0691.bri.hp.com) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id F09F21292D; Mon, 24 Jul 2000 17:24:10 +0200 (METDST) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id QAA09055; Mon, 24 Jul 2000 16:24:10 +0100 (BST) Received: (from steve@localhost) by sse0691.bri.hp.com (8.9.3/8.9.3) id QAA11850; Mon, 24 Jul 2000 16:26:39 +0100 (BST) (envelope-from steve) Date: Mon, 24 Jul 2000 16:26:39 +0100 From: Steve Roome To: Graham Wheeler Cc: stable@freebsd.org Subject: Re: psmintr: out of sync (0080 != 0000). ARGH! Message-ID: <20000724162639.A11618@moose.bri.hp.com> References: <6390.964219824@localhost> <397BF8E3.878462E6@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <397BF8E3.878462E6@cequrux.com>; from gram@cequrux.com on Mon, Jul 24, 2000 at 10:05:55AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 24, 2000 at 10:05:55AM +0200, Graham Wheeler wrote: > "Jordan K. Hubbard" wrote: > > > > I'm almost tempted to declare this a show-stopper for FreeBSD 4.1. > > Is anyone else even able to reproduce this? > > As you know, Jordan, I have had this problem in a bad way since 4.0-R > (currently running a 3 week old stablesnapshot). I made those terrible > kludges to the driver that I sent you, which are definitely not a real > solution. However, my mouse is now completely usable with these hacks. I > suspect though, that the problem may be in the kbd driver, if only > because I sometimes (quite infrequently, but even so) have my keyboard > going screwy too, usually manifesting as the Enter key being remapped to > (for example) backspace or scroll lock. In case this is useful info ? I've got two perfectly okay systems with ps/2 logitech mice. So, is there any chance it's X related. (i.e. PS/2 protocol instead of sysmouse) or maybe it is limited to four or more button devices ? Both systems run "moused -p /dev/psm0 -t auto". Work system : 4.1-RC (from last Thursday/Friday) with logitech mouseman (Model M-S43) (from dmesg) psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 (from XF86Config) Section "Pointer" Protocol "SysMouse" Device "/dev/mouse" Resolution 200 Buttons 3 EndSection Home system : 4.0-RELEASE with logitech mouseman (quite old - don't know model) psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 Section "Pointer" Protocol "SysMouse" Device "/dev/mouse" Resolution 100 Buttons 3 EndSection On both systems /dev/mouse is a symlink to /dev/sysmouse, and both work fine, with X 3.3.6, and I didn't have problems witht the mouse with XF86 4.0 either, but I didn't stick with that for other reasons. Don't know if this information is of any help though. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message