On Sat, Jan 26, 2013 at 3:53 AM, Peter Korsgaard <jacmet@xxxxxxxxxx> wrote: > Thanks. I've tested it here on a e6230 (bios rev 08), and it gets > correctly detected (but twice?): > > input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input14 > input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input16 It should show one input device for the trackstick, and one input device for the touchpad: [397682.041027] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input17 [397682.054959] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input18 I'm not sure what would cause it to register two identical touchpads; I don't see that on either E6230 or E6430. Did you build psmouse.ko from my DKMS sources, or apply the patches on top of some other baseline? > But the input events seem very noisy (E.G. the cursor jumps up and down > if I keep my finger pressed on the touchpad). Especially the Y > coordinate seems unstable: OK - I do see this on E6230 but not E6430. Normal usage is fine but the "pressed finger" test fails on E6230. I'll do some digging and try to figure out why. In another thread [1] it was mentioned that the ALPS_BITMAP_* constants needed to be tweaked for the Rushmore touchpads. This might be related. I also saw some "lost sync" errors in the kernel log on E6430 after running for a few days, but I don't know how to reproduce the issue. They did not seem to be associated with any obvious touchpad misbehavior. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html