atkbd.c: Unknown key pressed

callendorph · n00b Joined: 21 Feb 2006 Posts: 3

Hello,

I am working on installing Gentoo AMD64. I am not new to linux, but I am having some problems with my microsoft keyboard :-P

Microsoft Wireless Desktop Elite

I get the following message after booting from the CD :

kernel: atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
kernel: atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.
kernel: atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on isa0060/serio0).
kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.

I am not pressing any keys at this point. Also when I start typing, the console shows what I am typing and gives these message more often.

For most of the install I just used the following command

setkeycodes e059 112

which sets that scancode to something that won't get in my way too much. However, when i try to passwd and reset my root password, it won't lock my password because there are these extra 112 keys being interspersed in my typing.

I have tried reducing the keyboard scan rate, I have tried changing the keycode to something different with no success. I have run showkey and it will show me that I am typing keys and then randomly when I am typing introduce 112 keys.

Does anyone have any other ideas? I am mostly interested in a way that I can just assign this scancode to do nothing. I just want it to not register these two scancodes at all.

Thanks,
Carl

dadodrake · n00b Joined: 19 Mar 2005 Posts: 55 Location: Slovakia

I have the same problem with Microsoft Wireless Multimedia Keyboard

Deathwing00 · Posted: Fri Apr 07, 2006 2:46 pm Post subject:

Moved from Installing Gentoo to Kernel & Hardware. Hardware specific problem.

gerard27 · Posted: Fri Apr 07, 2006 2:58 pm Post subject:

Have you tried a keyboard that is wire connected?
It might be RF interference.

niick · Tux's lil' helper Joined: 09 Mar 2006 Posts: 93

Hello,

I use a Microsoft Wireless Multimedia Keyboard as well, so far I've been unable to sort this out.

I have read that these codes (e001 and e059) are the keyboard reporting its status i.e. battery life and signal level.
In Windows the Intellitype software can deal with this, but unfortunatly this is not supported in linux

I have tried assigning them via setkeycodes but nothing seems to work.

garlik42 · Posted: Mon Aug 28, 2006 1:53 pm Post subject:

I have seen this particular error in a couple of different forums for more than one linux.
I tracked it down in /usr/src/linux/drivers/input/keyboard/atkbd.c
The functions that are producing the message look like this: