Synaptics touchpad doesn't work fully after upgrading from edgy to feisty

dmesg edgy

lspci edgy

xorg log edgy

dmesg feisty

lspci feisty

xorg log feisty

me again...

Actually, from looking at the bug #89603 more closely I'm pretty confident, that what I'm seeing is in fact the same bug, but the symptoms may be a bit different. This is because just like in the afore mentioned bug, when I boot my *current feisty installation* with the *kernel from edgy*, the touchpad functions normally, ie. the scrolling functionality works perfect This is the edgy kernel:

Linux laptop 2.6.17-11-generic #2 SMP Tue Mar 13 23:32:38 UTC 2007 i686 GNU/Linux

So this seems to be a kernel bug. I'm attaching the dmesg output in here. If you need more information, again, please tell me.

juhis

juhis, I have the same problems on a Fuijtsu Amilo Pi1505. When you cat /proc/bus/input/devices in feisty, is your touchpad detected as a touchpad or as a "PS/2 Logitech Wheel Mouse" like it happens for me?

Could be, don't know which one of the below devices is the touchpad:

juhis@laptop:~$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0008 Version=0000
N: Name="PS/2 Mouse"
P: Phys=isa0060/serio1/input1
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1 ts0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0002 Product=0008 Version=7321
N: Name="AlpsPS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input2
H: Handlers=mouse1 event2 ts1
B: EV=f
B: KEY=420 0 70000 0 0 0 0 0 0 0 0
B: REL=3
B: ABS=1000003

I: Bus=0010 Vendor=104d Product=0000 Version=0000
N: Name="Sony Vaio Jogdial"
P: Phys=
S: Sysfs=/class/input/input3
H: Handlers=mouse2 event3
B: EV=7
B: KEY=40000 0 0 0 0 0 0 0 0
B: REL=100

I: Bus=0010 Vendor=104d Product=0000 Version=0000
N: Name="Sony Vaio Keys"
P: Phys=
S: Sysfs=/class/input/input4
H: Handlers=kbd event4
B: EV=3
B: KEY=1f ffff0000 0 20000 100000 0 2 0 0 100400 0 40300400 0 0 0 0

Yours is detected properly, it's the "Alps PS/2 Glidepoint". Mine isn't even detected as a touchpad:

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/class/input/input0
H: Handlers=mouse0 event0 ts0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input1
H: Handlers=kbd event1
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0001 Version=0063
N: Name="PS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio4/input0
S: Sysfs=/class/input/input4
H: Handlers=mouse2 event3 ts2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=046d Product=c50a Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/class/input/input9
H: Handlers=mouse1 event2 ts1
B: EV=20007
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=103
B: LED=ff00

I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=ACPI_FPB/button/input0
S: Sysfs=/class/input/input10
H: Handlers=kbd event8
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/class/input/input11
H: Handlers=event9
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/class/input/input12
H: Handlers=kbd event10
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button (CM)"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/class/input/input13
H: Handlers=kbd event11
B: EV=3
B: KEY=4000 0 0 0 0

Whoops, never mind my previous entry, I wasn't thinking clearly. See, I'm running the kernel from edgy now until the bug (hopefully) gets fixed. So that command was issued with the edgy kernel. I'll post the proper listing soon, when I reboot to the feisty kernel.

sorry for mixing things up..... juhis

There's a thread in ubuntuforums about this right now - http://ubuntuforums.org/showthread.php?t=417492 . It seems that most people that have the touchpad problems have them because the touchpad is detected as a ordinary mouse by the kernel psmouse driver, even though tpconfig detects it as a touchpad.

Hello,

First of all I tried the "reload psmouse" trick as suggested on the above thread, but it didn't work for me, so I'm still running edgy kernel. Today I however was feeling adventurous and tried the latest gutsy kernel in order to see how I could lower my power usage with the help of powertop... got down from around 20W to around 17W easily, quite substantial, really looking forward to being able to run a tickless kernel.

But, long story short, this same bug with the synaptics touchpad is still present in gutsy. It's actually the only problem I discovered during my short test period of the kernel.

I hate to be whining here, but just being curious, are there really no patches lying around that I could try and see if they'd fix the bug? Is anybody looking at this bug, hopefully it isn't forgotten, seems to me there are quite a few people with the same problem.

Thanks, juhis

My bad, sorry. Described in the thread.

So, I fixed the problem, here's the description. The bottom line, this wasn't a kernel bug (for me).

It seems to be, there were at least two bugs that I kept mixing up. The other was, that the kernel psmouse driver didn't recognize the Alps touchpad, so synaptics in xorg didn't work. It turns out this was not my problem.

My problem was probably more related to udev rules or the upgrade process or something. The problem was, that kernel changed the 'Handler' identification of the alps device in /proc/bus/input/devices between 2.6.17 (edgy) and 2.6.20 (feisty). This change, however, wasn't propagated through to the upgrade process so that my xorg.conf file would've been updated. So the end result was, that I had the wrong device listed the in xorg.conf file in the InputDevice section for the synaptics driver. I might've had some issues in the upgrade from edgy to feisty, I have a vague recollection, so maybe the upgrade process just didn't run cleanly for me, and the xorg.conf file wasn't updated properly.

The bottom line is however, that both the feisty and the gutsy kernel work for me now in my feisty installation, so this bug can be closed.

br, juhis

On a Dell Latitude D620 I get:

$ cat /proc/bus/input/devices
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

[snipped keyboard/power buttons/lid switch]

I: Bus=0011 Vendor=0002 Product=0008 Version=0000
N: Name="PS/2 Mouse"
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/virtual/input/input10
U: Uniq=
H: Handlers=mouse1 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0002 Product=0008 Version=6337
N: Name="AlpsPS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input11
U: Uniq=
H: Handlers=mouse2 event3
B: EV=f
B: KEY=420 0 70000 0 0 0 0 0 0 0 0
B: REL=3
B: ABS=1000003

The laptop has a trackpad and a trackpoint (one of those nipple-mouse things). I think the GlidePoint mentioned above is the latter. Not sure what the other two are. (There's no mouse plugged in right now.)

Note that gsynaptics (I think I installed it by hand) has a "disable" option that works only on the trackpad (the nipple keeps working), it can enable tapping (and change tapping speed), and can enable/disable vertical scrolling on the trackpad's edge. So it can do some detection. However, the sensitivity setting does nothing whatsoever.

(Note that I think it's preferable that the sensitivity settings for a mouse/trackpad/trackpoint be separated. So the mouse settings applet shouldn't do anything with the trackpad unless it presents it as a separate option.)

The sensitivity setting in the mouse applet doesn't affect the trackpoint, either. However, the acceleration setting affects _all_ of them (mouse, trackpad, trackpoint). So it's impossible to balance them out.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.