On 22/02/11 22:28, sync wrote: > > > On Tue, Feb 22, 2011 at 4:42 PM, Cameron Kerr <cameron at humbledown.org > <mailto:cameron at humbledown.org>> wrote: > > On 22/02/11 19:25, sync wrote: > > > Jan 11 07:56:00 kernel: [17179663.076000] atkbd.c: Unknown key > released > > (translated set 2, code 0x81 on isa0060/serio0). > > Jan 11 07:56:00 kernel: [17179663.076000] atkbd.c: Use 'setkeycodes > > e001 <keycode>' to make it known. > > Jan 11 07:56:00 kernel: [17179663.084000] atkbd.c: Unknown key > pressed > > (translated set 2, code 0xd9 on isa0060/serio0). > > Jan 11 07:56:00 kernel: [17179663.084000] atkbd.c: Use > 'setkeycodes e059 > > <keycode>' to make it known. > > You might find this document has useful information on scancodes: > > http://www.win.tue.nl/~aeb/linux/kbd/scancodes-10.html#ss10.1 > <http://www.win.tue.nl/%7Eaeb/linux/kbd/scancodes-10.html#ss10.1> > > It seems that perhaps you have pressed a key that emits an unknown > scancode. I have seen this before on older laptops when typing the Fn > key. You might also see it when using extended keys on multimedia > keyboards. > > Can you determine if these are generated while using the text console or > instead inside X11? > > What keyboard mapping are you using? > > > > Thanks for your reply on this . > > Em.. it generated on the text console .Maybe it is caused by my keyboard. > But I don't remember what I type . > > > By the way, I sent that bug to the redhat bugzilla system, hope it > would be solved > soon. Exactly what type of keyboard do you have? (eg. what does lsusb say?) What about the kernel log at startup? Here's mine (on an Ubuntu laptop) -- the -Cn argument gives the surrounding n lines of context. $ grep -C2 keyboard /var/log/dmesg [ 0.595625] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 0.595631] EDD information not available. [ 0.638265] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5 [ 0.642953] Freeing initrd memory: 7784k freed [ 0.688496] ata1.00: ATA-8: A-DATA_SSD_16GB, 081210, max UDMA/100 Note that my example, the "i8042" driver (standard PC Keyboard) is being used. In your case, the isa0060 driver is being used. Do you have an embedded trackpad or pointing device in the keyboard? Where is your mouse plugged in? This post discusses a very similar issue (albeit on Debian) http://www.linux-archive.org/debian-user/276835-atkbd-c-unknown-key-pressed-translated-set-2-code-0x88-isa0060-serio0.html Hope it helps. Cameron