atkbd.c not recognising key on logitech cordless keyboard
Hi, I have a Logitech Cordless Desktop with those funny extra buttons at the top. However, one particular button no longer works when running development kernels (it worked in 2.4 kernels). The first development kernel I tested with was 2.5.75; it hasn't worked from then up until 2.6.0-test6, which I am running now.
The key in question is labelled "Messenger / SMS". When tailing /var/log/kern.log, and I press the key in question, I get this (I switched on debug in i8042.c and atkbd.c in case it helped):
Sep 30 21:55:32 fastpc kernel: drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, kbd, 1) [187205] Sep 30 21:55:32 fastpc kernel: atkbd.c: Received e0 flags 00 Sep 30 21:55:32 fastpc kernel: drivers/input/serio/i8042.c: 11 <- i8042 (interrupt, kbd, 1) [187208] Sep 30 21:55:32 fastpc kernel: atkbd.c: Received 11 flags 00 Sep 30 21:55:32 fastpc kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x11d, data 0x11, on isa0060/serio0). Sep 30 21:55:32 fastpc kernel: drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, kbd, 1) [187383] Sep 30 21:55:32 fastpc kernel: atkbd.c: Received e0 flags 00 Sep 30 21:55:32 fastpc kernel: drivers/input/serio/i8042.c: 91 <- i8042 (interrupt, kbd, 1) [187387] Sep 30 21:55:32 fastpc kernel: atkbd.c: Received 91 flags 00 Sep 30 21:55:32 fastpc kernel: atkbd.c: Unknown key released (translated set
2, code 0x11d, data 0x91, on isa0060/serio0).
cat'ing /proc/bus/input/devices gave this for the keyboard
I: Bus=0011 Vendor=0001 Product=0002 Version=ab02
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd evbug
B: EV=120003
B: KEY=4 2200000 c061f9 fbc9d621 efdfffdf ffefffff ffffffff fffffffe
B: LED=7
Is there anyway I can make this key work again?
Thanks for any help.
Paul
Quoted 10 lines · Paul Symons
Hi, I have a Logitech Cordless Desktop with those funny extra buttons at the top. However, one particular button no longer works when running development kernels (it worked in 2.4 kernels). The first development kernel I tested with was 2.5.75; it hasn't worked from then up until 2.6.0-test6, which I am running now.
The key in question is labelled "Messenger / SMS" and gives scancode e0 11.
Sep 30 21:55:32 fastpc kernel: atkbd.c: Unknown key pressed (translated set 2,code
0x11d, data0x11, on isa0060/serio0).
I do not think that scancode was associated to a keycode in a vanilla 2.4 kernel. So, maybe you used setkeycodes(8) or used a patched kernel?
Patching also works today. The setkeycodes command is a bit broken these days.
Andries
Quoted 2 lines
I do not think that scancode was associated to a keycode in a vanilla 2.4 kernel. So, maybe you used setkeycodes(8) or used a patched kernel?
I've had the keyboard for around a year, and I've been mostly using gentoo-sources kernels from Gentoo, which are certainly not vanilla kernels. Perhaps they had some patch applied. Though, I think I used 2.4.21 vanilla previous to development kernels.
Quoted 2 lines
Patching also works today. The setkeycodes command is a bit broken these days.
I only saw the message from earlier in the day about multimedia keyboards after I posted, so sorry for the repetition. I think I need to do some reading on keycodes and scancodes. Thanks very much for your help.
Paul