Bug#532237: marked as done (Failure to both enable proto=exps and detect ALPS touchpad on ThinkPad X301)
Your message dated Mon, 8 Jun 2009 09:29:10 -0400
with message-id <20090608132910.GA5556@eep.dnsalias.org>
and subject line Re: Bug#532237: Failure to both enable proto=exps and detect ALPS touchpad on ThinkPad X301
has caused the Debian Bug report #532237,
regarding Failure to both enable proto=exps and detect ALPS touchpad on ThinkPad X301
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
532237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532237
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.29-5
Severity: normal
I have a ThinkPad X301 that has an ALPS touchpad. I've found that
tap-to-drag (a double tap on the touchpad, but without releasing the
finger from the touchpad after the second tap, which lets you drag using
just the touchpad and not any physical buttons) works only if the
psmouse module is loaded with the option "proto=exps".
Unfortunately, if I place "options psmouse proto=exps" into
/etc/modprobe.d/psmouse.conf so that this option is automatically
enabled when the module is initially loaded, HAL fails to recognize the
touchpad as a touchpad anymore, making X.Org fail to load the Synaptics
input driver to enable more specialized features like edge scrolling.
(Tap to click and tap-to-drag work even with just the X.Org generic PS/2
input driver, though.)
Thus, there are two things I'd expect: 1) the kernel should
automatically recognize that my touchpad deserves proto=exps, and
2) with proto=exps, the kernel shouldn't confuse HAL into not
recognizing that my touchpad is a touchpad.
Please let me know if there's any hardware information that you need in
order to fix this.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Sun, Jun 07, 2009 at 10:44:09PM +0100, Ben Hutchings wrote:
> On Sun, 2009-06-07 at 15:06 -0400, EspeonEefi wrote:
> [...]
> > Thus, there are two things I'd expect: 1) the kernel should
> > automatically recognize that my touchpad deserves proto=exps,
>
> If you have an ALPS touchpad then I believe the psmouse driver should
> use the "alps" protocol variant, not "exps". Please try using "options
> proto=alps" instead.
Actually, proto=alps is not a legal option, but I've figured out that
the problem is with the X.Org Synaptics driver, not the kernel
(probably). Playing with the MaxTapTime and MaxDoubleTapTime settings of
the X.Org Synaptics driver brought back dragging.
Unfortunately, it looks like the model that the X.Org Synaptics driver
is using to process taps and taps and drags is worse than whatever the
hardware does on its own; there's a delay in response time to taps from
X.Org Synaptics that using proto=exps doesn't have. (Also, the defaults
for the X.Org Synaptics driver make tap-and-drag really, really hard to
trigger.) But these are bugs for xserver-xorg-input-synaptics, not
linux-2.6.
Thanks for the prompting to investigate this more closely myself. Hopefully
this will show up higher on Google (I got the mistaken impression that
proto=exps was the correct fix from Googling for alps and tap to drag.)
Closing the bug now.
--- End Message ---
Reply to: