dmesg broken

[David Gonzalez Rivera]

Thilo Six wrote:

>David Gonzalez Rivera schrieb am 18.12.2005 09:09:
>  
>
>>everytime i type dmesg i get this
>>
>>[4414765.991000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it
>>known.
>>[4414884.872000] atkbd.c: Unknown key pressed (translated set 2, code
>>0xaa on isa0060/serio0).
>>[4414884.872000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it
>>known.
>>[4414885.005000] atkbd.c: Unknown key released (translated set 2, code
>>0xaa on isa0060/serio0).
>>[4414885.005000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it
>>known.
>>[4414984.348000] atkbd.c: Unknown key pressed (translated set 2, code
>>0xaa on isa0060/serio0).
>>[4414984.348000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it
>>known.
>>[4414984.496000] atkbd.c: Unknown key released (translated set 2, code
>>0xaa on isa0060/serio0).
>>[4414984.496000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it
>>known.
>>
>>
>>    
>>
>
>
>I´m resending a mail from this list:
>
>
>John Nicholls schrieb am 08.12.2005 02:26:
>
>  
>
>>>In Breezy pressing and releasing the up arrow key produces these errors
>>>in the system log:
>>>
>>>Dec  6 17:00:56 localhost kernel: [4310260.318000] atkbd.c: Unknown key
>>>pressed (translated set 2, code 0xaa on isa0060/serio0).
>>>Dec  6 17:00:56 localhost kernel: [4310260.318000] atkbd.c: Use
>>>'setkeycodes e02a <keycode>' to make it known.
>>>Dec  6 17:00:56 localhost kernel: [4310260.435000] atkbd.c: Unknown key
>>>released (translated set 2, code 0xaa on isa0060/serio0).
>>>Dec  6 17:00:56 localhost kernel: [4310260.435000] atkbd.c: Use
>>>'setkeycodes e02a <keycode>' to make it known.
>>>
>>>The key works as it should but these error messages clutter up the
>>>syslog. The keyboard is a standard 104-key US English. This does not
>>>occur on the same computer with Warty or Hoary.
>>>
>>>Any suggestions?
>>>John
>>>
>>>
>>>      
>>>
>
>
>sudo update-rc.d -f hotkey-setup remove
>
>This script tries to setup laptop keys, and causes this Problem.
>search in forums and bugzilla you will find it there also.
>
>bye Thilo
>
>
>
>  
>
thanks, that fixed it :D, had to give it a restart :)