Date: Mon, 26 Jan 1998 08:30:04 -0600 (CST) From: "Richard M. Neswold" <rneswold@mcs.net> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/5568: Problems with 'moused'. Message-ID: <Pine.BSF.3.96.980126082726.1430L-100000@drmemory.cohorts.org>
next in thread | raw e-mail | index | archive | help
>Number: 5568 >Category: bin >Synopsis: Problems with 'moused'. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 26 06:40:02 PST 1998 >Last-Modified: >Originator: Richard M. Neswold >Organization: >Release: FreeBSD 2.2.5-STABLE i386 >Environment: I have a Mouse Systems three-button mouse connected to /dev/cuaa0. My /etc/rc.conf sets up 'moused' to use the mousesystems protocol and use -D as an extra command line option. My X configuration uses the mousesystems protocol on /dev/sysmouse. This setup has worked flawlessly for the past six months. >Description: After applying the latest moused patches (merged from -current, I believe) I recompiled the kernel and did a make world. Now 'moused' doesn't recognize my mouse. I invoked 'moused' with the "show info" option and it couldn't determine what my mouse type was. Removing 'moused' and having X talk directly to cuaa0 works. The mouse operates fine with just X. It appears that something got broken in the moused upgrade. >How-To-Repeat: Get the latest moused sources in RELENG_2_2 and connect a MouseSystems mouse (model 403972-001, in case that's significant). >Fix: Don't use 'moused' with MouseSystems mice (?) >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980126082726.1430L-100000>