Comment 13 for bug 250732

Revision history for this message
John Tait (johntait1-waitrose) wrote :

Hi,
 I have finally got a copy of 9.10 installed and will follow this with information as requested

meanwhile here is the info from showkeys when the wireless key is pressed

[411.988162] atkbd.c unknown key pressed translated set2, code 0xd6 on isa0060/serio0
[411.988246] atkbd.c use setkeycodes e056 <keycode> to make it known

[412.397977] atkbd.c use setkeycodes e056 <keycode>to make it known

a few tips on how to collect the necessary info would be welcome if anyone can help I had to write this down and type it into this window (hopefully accurately)

On a version of 8.04 with wireless button working (after using the script ) which I have also installed reports two different keycodes for the same wireless button depending on whether you use xev or showkeys -k to monitor the key press

root@amilo:/home/john# showkey -k
kb mode was RAW
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...
keycode 147 press
keycode 147 release

root@amilo:/home/john# xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
keycode 36 = (keysym 0xff0d, Return), state = 0x0
keycode 155 = (keysym 0x1008ff8a, XF86Xfer), state = 0x0
keycode 155 = (keysym 0x1008ff8a, XF86Xfer), state = 0x0
keycode 155 = (keysym 0x1008ff8a, XF86Xfer), state = 0x0
keycode 155 = (keysym 0x1008ff8a, XF86Xfer), state = 0x0