Originally Posted by zamboni
Thanks for the reply. The problem is: When I am in X, 7 of the 9 keys are not assimilated(...sorry couldn't resist).
xev does not show a thing for 7 of the extra keys, so I'm stumped as to how to wake up the keyboard. I figure it has to be something to do with how X and maybe gnome see the keyboard. No X event is generated for these seven keys.
How do I get these keys to generate a code? Nothing in the syslogs in the way of error messages: i.e no atkbd.c error messages.
And as I said in the first message the codes are different when I boot into text/console mode. This fact gives me a small clue. Small indeed.
Some keys have unknown scancodes for the AT driver and they don't get keycodes. The X server uses its own mapping but
when it starts it reads the kernel mapping and then it maps it to its own. Because the kernel doesn't "see" these
keycodes the keys don't work in X either.
Press a key and then run "dmesg". You will read a message like the following
atkbd.c: Unknown key released (translated set 2, code 0xaa on isa0060/serio0).
atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
Run setkeycodes to set a keycode to the specified scancode. The syntax is very simple and it is shown in the above
example. To see which keycodes are free to use run "dumpkeys"
Put these commands in a initscript so that when you reboot they will work and you are ok. You will have one
setkeycodes command for every uknown key.
After that the keys will be reported in xev and xbindkeys will see them
Another program that you can use instead of xbindkeys is keytouch (keytouch.sf.net). That is after you have done
the setkeycodes thing described above. Keytouch also have plugins for many commands so that you don't need to run them
like with xbindkeys.