From owner-freebsd-current@FreeBSD.ORG Thu Oct 1 19:44:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B107106566B for ; Thu, 1 Oct 2009 19:44:02 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 478A58FC1D for ; Thu, 1 Oct 2009 19:44:01 +0000 (UTC) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id n91Ji0eH001577; Thu, 1 Oct 2009 14:44:01 -0500 (CDT) (envelope-from stephen@missouri.edu) Message-ID: <4AC50680.7070608@missouri.edu> Date: Thu, 01 Oct 2009 14:44:00 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.23) Gecko/20090905 SeaMonkey/1.1.18 MIME-Version: 1.0 To: David Horn References: <25ff90d60910010138l24e83470v390e8c0271f332f7@mail.gmail.com> <4AC4A26A.6040101@missouri.edu> <25ff90d60910010907la9f8227oecee2aec0b492572@mail.gmail.com> In-Reply-To: <25ff90d60910010907la9f8227oecee2aec0b492572@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" Subject: Re: synaptics touchpad + mouse taps = trouble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2009 19:44:02 -0000 David Horn wrote: > On Thu, Oct 1, 2009 at 8:36 AM, Stephen Montgomery-Smith > wrote: >> David Horn wrote: >>> I currently have a laptop running FreeBSD 8/Stable RC1 r197621 (amd64) >>> that happens to have a synaptics touchpad. On this particular >>> laptop(Inspiron 1520), the placement of the touchpad means that I will >>> inevitably accidentally hit it while typing, and I have found that I >>> always need to disable the "mouse taps" in order to have the touchpad >>> usable for me. >> I have an Inspiron 1525. After struggling with this for a long time, I >> found that the following entry in /etc/rc.conf did the trick >> >> moused_flags="-3 -m 11=4 -A 2" > > Interesting. This maps physical button #4 to buttton #11. I will > take a look again, but in my psm device, I never saw button 4 events, > just button #1 and button #3 under generic psm mode. Mouse taps always > showed up as button #1 so it was impossible to differentiate between > tap #1 and real #1. (unless something like moused was mapping #4 to > #1, hmm something to investigate) > > Were you running psm/generic or psm/Extended Synaptics or using ums0 ? > Does your ums0 mouse show up as Broadcom 4503 ? OK, I have a "Glidepoint." Probably your situation is completely different than mine. psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model GlidePoint, device ID 0 > >> It is the "-m 11=4" that did it. On my computer, it isn't really a >> "synaptics" touchpad, but some other brand. >> >> Hopefully it will work for you. >> >> Stephen >> > > Here is the hw.usb.ums.debug=99 data after a usbconfig -u 0 -a 5 reset > > Oct 1 11:33:43 dhorn-1520 kernel: ums0: 0x4503, class 0/0, rev 2.00/1.00, addr 5> on usbus0 > Oct 1 11:33:43 dhorn-1520 kernel: ums0: 3 buttons and [XY] coordinates ID=2 > Oct 1 11:44:56 dhorn-1520 kernel: ums0: at uhub7, port 3, addr 5 (disconnected) > Oct 1 11:44:56 dhorn-1520 kernel: ums_detach:661: sc=0xffffff0001feb000 > Oct 1 11:44:57 dhorn-1520 kernel: ums_probe:365: > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:503: sc=0xffffff00041d1000 > Oct 1 11:44:57 dhorn-1520 kernel: ums0: 0x4503, class 0/0, rev 2.00/1.00, addr 5> on usbus0 > Oct 1 11:44:57 dhorn-1520 kernel: ums0: 3 buttons and [XY] coordinates ID=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:599: > sc=0xffffff00041d1000, index=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:601: X 8/8 id=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:603: Y 16/8 id=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:605: Z 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:607: T 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:609: W 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:614: B1 0/1 id=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:614: B2 1/1 id=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:614: B3 2/1 id=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:599: > sc=0xffffff00041d1000, index=1 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:601: X 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:603: Y 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:605: Z 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:607: T 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:609: W 0/0 id=0 > Oct 1 11:44:57 dhorn-1520 kernel: ums_attach:617: size=4, id=2 > Oct 1 11:44:57 dhorn-1520 kernel: ums_open:771: > Oct 1 11:44:57 dhorn-1520 kernel: ums_open:771: > Oct 1 11:44:57 dhorn-1520 kernel: ums_ioctl:808: > > No additional events on mouse movement/buttons, but on moused startup I get > > Oct 1 12:01:23 dhorn-1520 kernel: ums_open:771: > Oct 1 12:01:23 dhorn-1520 kernel: ums_open:771: > Oct 1 12:01:23 dhorn-1520 kernel: ums_ioctl:808: > > > running moused -df -p /dev/ums0 -t auto gives no mouse events to > movement/buttons at all. > > --Dave H > >