I'm experiencing this problem on a Sony Vaio vpcsb, which has a
"AlpsPS/2 ALPS GlidePoint".
What I've understood so far is that the kernel creates two input devices
for the touchpad. In `/proc/bus/input/devices` I have two devices with
the same Bus, Vendor, an Product: a PS/2 mouse and the touchpad.
I: Bus=0011 Vendor=0002 Product=0008 Version=0000
N: Name="PS/2 Mouse"
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/platform/i8042/serio1/input/input8
U: Uniq=
H: Handlers=mouse1 event8
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3
I: Bus=0011 Vendor=0002 Product=0008 Version=7326
N: Name="AlpsPS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input9
U: Uniq=
H: Handlers=mouse2 event9
B: PROP=0
B: EV=b
B: KEY=420 70000 0 0 0 0
B: ABS=1000003
Xorg sees both of them. `xinput -list` gives:
⎡ Virtual core pointer id=2 [master pointer
(3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer
(2)]
⎜ ↳ PS/2 Mouse id=12 [slave pointer
(2)]
⎜ ↳ AlpsPS/2 ALPS GlidePoint id=13 [slave pointer
(2)]
*But*, and herein lies the problem, only the PS/2 mouse generates
events. Using `xinput -test` with device 12
motion a[0]=326 a[1]=224
motion a[0]=322 a[1]=219
motion a[0]=314 a[1]=205
Device 13 (the touchpad) on the other hand doesn't generate any events.
Xorg loads the synaptics module, I can configure its properties with
synclient, the KDE synaptiks application shows me that it sees the
touchpad and can configured it. Its events however get re-routed to the
mouse device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737051
Title:
[regression] Alps touchpad detected, but scrolling not working
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
