Date: Sun, 06 May 2001 04:35:06 -0500 From: John Baxter <jbaxter@mmcable.com> To: freebsd-mobile@freebsd.org, yokota@freebsd.org, freebsd-bugs@freebsd.org Subject: psm0 touch pad bug Message-ID: <3AF51ACA.44D9B292@mmcable.com>
next in thread | raw e-mail | index | archive | help
i am having problems with my touchpad. i found the following posting in an archive of freebsd-bugs. i too have a prostar laptop. the workaround suggests adding '0x400' as a flag fr freebsd 3.3. the freebsd 2.8 version of moused does not have a valid flag of 0x400. would someone direct me as what i can/should do to fix this problem. thanks, john baxter >Number: 14892 >Category: kern >Synopsis: Laptop PS/2 mouse (touch pad) not detected by kernel, moused does not load >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Nov 14 23:20:01 PST 1999 >Closed-Date: >Last-Modified: >Originator: Michael Lindsay >Release: 3.3 >Organization: Personal use >Environment: FreeBSD 3.3-RELEASE (GENERIC)#0 >Description: Kernel does not detect PS/2 mouse. /var/log/messages shows "psm0 not found". As a result moused does not load. Manually running "moused -i all -p /dev/psm0" returns "device not configured" message. Linux and OpenBSD detect mouse as PS/2 device and load mouse daemon ok so I know hardware device is fuctional. (Note diagnostic clue: OpenBSD /var/log/messages shows mouse at "psm0 at vt0 IRQ12") Laptop is a Sager 6500 (aka ProStar 3203T, Kapok 1100, FOSA 1100). AMD K6-2 300Mhz Processor, 128MB RAM >How-To-Repeat: Attempt FreeBSD load on referenced type system. >Fix: >Release-Note: >Audit-Trail: >Unformatted: Synopsis: Laptop PS/2 mouse (touch pad) not detected by kernel, moused does not load State-Changed-From-To: open->closed State-Changed-By: yokota State-Changed-When: Sat Nov 27 23:54:28 PST 1999 State-Changed-Why: Workaround has been found. It appears that the device is not returning expected value when probed. Adding 'flags 0x400' forced the psm driver to recognize the device. The PR originator reported this works. 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?3AF51ACA.44D9B292>