On Tue, May 7, 2013 at 7:25 AM, H. Peter Anvin <hpa@xxxxxxxxx> wrote: > Hello, > > The touchpad on Lenovo Yoga 13 seems to have broken some time between 3.4 > and the current kernel. The dmesg is full of spewage: > > [ 256.246481] atkbd serio0: Use 'setkeycodes e03e <keycode>' to make it > known. > [ 256.251473] atkbd serio0: Unknown key released (translated set 2, code > 0xbe on isa0060/serio0 > > ... about once per second; I am wondering if the touchpad is spewing output > onto the keyboard channel or if there is something else wrong. > > I have tried i8042.nomux and i8042.noloop to no effect. > > Unless someone has a better idea I'll try to do a bisect. On top of Kevin's answer: I already saw that with Yoga 13 laptops. The touchpad went into this mode, and Linux was not able to recognize it anymore. What "solves" the pb was to stop the machine, then go to the bios (or UEFI), then the touchpad was back alive when the guy rebooted under Linux. I bet the bios managed to set the touchpad in the right mode where Linux can then handle it correctly. This is not an ideal solution, but at least this may help restoring your touchpad to a functional state while the correct driver is being developed. Anyway, if you are able to do a real bisect (instead of my dirty trick), that would be great because it would help fixing the problem. Cheers, Benjamin -- 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
