Did you mean i8042.dumbkbd instead of i8042.direct? To me it happens that i8042.direct causes no apparent side effects, and the sporious events are triggered once after pressing CAPS LOCK or NUM LOCK; i8042.dumbkbd instead causes the CAPS LOCK keyboard led not to blink (and this is expected), but there are no sporious events after pressing CAPS LOCK or NUM LOCK.
I analyzed a bit the debug messages sent by the i8042 controller and the kernel module, and the sporious messages are sent from the i8042 controller to the kernel module after the kernel module send the 0xED messages, which is the message used to turn on and off the keyboard leds. To enable the i8042 module debug log into dmesg you can use this command: echo Y > /sys/module/i8042/parameters/debug This logs both the keyboard and touchpad events. Anyway since i8042.direct flag changes the behaviour of the i8042 controller leads me to think the controller is initialized with a wrong capability bitmask or sort of. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532746 Title: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
