On Tue, Feb 22, 2011 at 4:42 PM, Cameron Kerr <cameron@xxxxxxxxxxxxxx> wrote:
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.
On 22/02/11 19:25, sync wrote:You might find this document has useful information on scancodes:
> 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.
http://www.win.tue.nl/~aeb/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.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
