Messages in this thread | | | Date | Thu, 3 Oct 2002 10:47:50 +0200 | From | Vojtech Pavlik <> | Subject | Re: 2.5.40: AT keyboard input problem |
| |
On Thu, Oct 03, 2002 at 08:59:30AM +0200, Tobias Ringstrom wrote: > While 2.5 has worked better than I hoped for so far, I do have a problem > with the new input layer (I think) that is easily reproducible, and quite > irritating. > > If I press and hold my left Alt key, press and release the right AltGr > key, and then release the left Alt key, I get one of the following > messages in dmesg: > > atkbd.c: Unknown key (set 2, scancode 0x1b8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x1b8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x1b8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x1b8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x1b8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0xb8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x1b8, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed. > atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed. > > The left Alt key is now stuck until I press and release it again. > > The same thing happens for a few other combinations as well. I happens > both in X and in the console. > > Please let me know if you need more info.
Yes, please try with #I8042_DEBUG_IO enabled, try all the suspicious key combinations and add comments to the log file which is which. This will allow me to fix it properly.
Thanks in advance. :)
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |