Date: Wed, 20 Jun 2001 02:54:15 -0700 (PDT) From: Sam Habash <the@llama.com> To: freebsd-gnats-submit@FreeBSD.org Subject: conf/28290: Mouse refuses to run Message-ID: <200106200954.f5K9sFC39391@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 28290 >Category: conf >Synopsis: Mouse refuses to run >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: Wed Jun 20 03:00:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Sam Habash >Release: 5.0-CURRENT >Organization: >Environment: FreeBSD hal 5.0-CURRENT-20010618-JPSNAP FreeBSD 5.0-CURRENT-20010618-JPSNAP #8: Wed Jun 20 02:20:17 PDT 2001 root@hal:/usr/src/sys/compile/HAL i386 >Description: Mouse isn't detected, either under X, or in console running moused. This is on an IBM Thinkpad 570 with an 'eraser' keyboard pointer. (PS/2) >How-To-Repeat: /stand/sysinstall...configure moused, as well as starting X. >Fix: Commenting out the "hint.psm.0.at" and "hint.psm.0.irq" lines gets things working again. With these in place, a bogus psm1 interface appeared in dmesg. When I added entries for hint.psm.1.*, a bogus psm2 entry appeared. Haven't looked to see what causes this "off-by-one". >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106200954.f5K9sFC39391>