Ok.. maybe I did it... I was experiencing the same bug and it sucked me
a lot(#96596, cursor out of sync).
this is the relevant part of dmesg
...
[ 794.450212] psmouse.c: GlidePoint at isa0060/serio1/input0 - driver
resynched.
[ 794.451978] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte
1
[ 794.455045] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte
1
[ 794.456556] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte
1
[ 794.458622] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte
1
[ 794.464386] psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte
1
[ 794.464392] psmouse.c: issuing reconnect request
[ 795.676077] input: PS/2 Mouse as /devices/virtual/input/input15
[ 795.740513] input: AlpsPS/2 ALPS GlidePoint as
/devices/platform/i8042/serio1/input/input16
So I did this:
sudo echo 1 > /sys/module/psmouse/parameters/resetafter
Now it works well, however, when I type "cat
/sys/module/psmouse/parameters/resetafter", there's still number 5.
The trick is, that after "issuing reconnect request" the bug instantly
dissappears. So I wanted to reset the device immediatelly. Changing to
number 1 solve it.
This is the part of the driver, which I believe resets the device
psmouse->pktcnt = 0;
if (psmouse_resetafter > 0 && priv->out_of_sync == psmouse_resetafter) {
psmouse->state = PSMOUSE_IGNORE;
- serio_rescan(psmouse->serio);
+ printk(KERN_NOTICE "synaptics: issuing reconnect request\n");
+ serio_reconnect(psmouse->serio);
}
I don't know, if it works for you, but if yes, write some feedback. If
no, write it too :)
--
touchpad lockup/drag
https://bugs.launchpad.net/bugs/34501
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
