[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#622231: psmouse module doesn't reliably detect Synaptics touchpad



This report is for an Acer Aspire One touchpad rather than a  
Dell latitude.

When the kernel detects the pad correctly, /proc/bus/input/devices
includes:-
-----------------------------------------------------
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio2/input0
S: Sysfs=/devices/platform/i8042/serio2/input/input11
U: Uniq=
H: Handlers=mouse0 event11 
B: PROP=9
B: EV=b
B: KEY=6420 0 30000 0 0 0 0 0 0 0 0
B: ABS=2608000 11000003
-----------------------------------------------------

Nondeterministically, the kernel, 3.2.0-3-686-pae on testing today,
will only report Name="PS/2 Synaptics TouchPad", and the xserver-xorg-
input-synaptics then fails to work (I presume is not loaded) as
described in /usr/share/doc/xserver-xorg-input-synaptics/trouble-shooting.txt.gz which says:

"If you are using a 2.6 linux kernel, check the
/proc/bus/input/devices
file. The touchpad must be identified a "SynPS/2 Synaptics TouchPad"
or an "AlpsPS/2 ALPS TouchPad". If it is identified as a "PS/2 Generic
Mouse" or "PS/2 Synaptics TouchPad", something is wrong.
"
Reloading the psmouse module does *not* fix the problem: it seems to
be necessary to reboot.

This is relatively rare, but has shown up as a regression from
linux-image-3.2.0-2-686-pae to linux-image-3.2.0-3-686-pae.
 
A long standing and perhaps related problem also results in the
xorg synaptics driver not working, but that *is* resolved
by reloading the psmouse module. That happens on perhaps half
the time on fresh boots. Smells like a race condition somewhere
in psmouse? ISTR that I had bug reported this last problem long
ago, with no result. Reloading psmouse wasn't much of a burden
(although it did smell of Windoze), so I didn't bother to chase that up.

As it happens, while I was composing this message, the touchpad
(well the pointer) froze. I reloaded psmouse and the pad worked again.

I have just found in /var/log/Xorg.log:
-----------------------------------------------------------------
[  2362.471] (II) config/udev: removing device SynPS/2 Synaptics TouchPad
[  2362.477] (II) UnloadModule: "synaptics"
[  2363.669] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event11)
[  2363.669] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[  2363.669] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[  2363.669] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[  2363.669] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Synaptics TouchPad"
[  2363.669] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[  2363.670] (**) SynPS/2 Synaptics TouchPad: always reports core events
[  2363.670] (**) Option "Device" "/dev/input/event11"
[  2363.712] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[  2363.712] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis 8
[  2363.712] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis 8
[  2363.712] (--) synaptics: SynPS/2 Synaptics TouchPad: pressur
[  2363.712] (--) synaptics: SynPS/2 Synaptics TouchPad: finger 15
[  2363.712] (--) synaptics: SynPS/2 Synaptics TouchPad: buttonsble triple
[  2363.713] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 
[  2363.713] (**) Option "LeftEdge" "1700"
[  2363.713] (**) Option "BottomEdge" "5100"
[  2363.713] (**) Option "FingerLow" "25"
[  2363.713] (**) Option "FingerHigh" "30"
[  2363.713] (**) Option "MaxTapTime" "180"
[  2363.713] (**) Option "MaxDoubleTapTime" "140"
[  2363.714] (**) Option "VertScrollDelta" "100"
[  2363.714] (**) Option "VertEdgeScroll" "true"
[  2363.714] (**) Option "HorizEdgeScroll" "true"
[  2363.714] (**) Option "VertTwoFingerScroll" "true"
[  2363.714] (**) Option "HorizTwoFingerScroll" "true"
[  2363.715] (**) Option "RTCornerButton" "2"
[  2363.715] (**) Option "TapButton1" "1"
[  2363.715] (**) Option "TapButton2" "2"
[  2363.715] (**) Option "MinSpeed" "0.5"
[  2363.715] (**) Option "MaxSpeed" "20"
[  2363.715] (**) Option "AccelFactor" "0.02"
[  2363.716] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[  2363.716] (**) SynPS/2 Synaptics TouchPad: always reports core events
[  2363.720] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input13/event11"
[  2363.720] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
[  2363.720] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.0
[  2363.720] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 40.00
[  2363.720] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.020
[  2363.722] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[  2363.722] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[  2363.722] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[  2363.722] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[  2363.725] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[  2363.725] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
-------------------------------------------------------------------------
So it looks as if the kernel passed some sort of disconnect event to
udev, but as there are no time stamps, I am not sure how this fits with
the other symptoms.

I realize this isn't a lot of help, but if this reaches 
Vojtech Pavlik's eyes, maybe he can spot what might be happening...

ael


Reply to: