dmesg - odd response

[Tom]

On Wed, 2005-09-21 at 16:58 -0400, Michael Gordon wrote:
> Carthik Sharma wrote:
> 
> >
> >
> > On 9/20/05, *Tom* <sett at iinet.net.au <mailto:sett at iinet.net.au>> wrote:
> >
> >     I have just used the dmesg command with no additional options and it
> >     completed the output I expected but at the end it gave a series of
> >     line-pairs all identical ....
> >
> >
> >     atkbd.c: Unknown key released (translated set 2, code 0x81 on
> >     isa0060/serio0).
> >     atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
snip

> > I suspect you have a dell laptop, or a microsoft keyboard, with 
> > special keys, some of which are not mapped.
> >
> > Search for "setkeycodes e001 <keycode>" on google and you'll find a 
> > few people talking about it. Since I don't know more about your 
> > laptop/desktop I can't be of any more help :)
> >
> > Carthik.
> 
> I personally wouldn't worry about it. It could also be pushing the 
> Function key on a laptop keyboard (it's blue on my Dell Latitude D505). 
> Perhaps turning on your wireless card requires it? I think that's 
> actually not OS-dependent, as I've seen Fn+F2 turn on and off my 
> wireless card in linux and Windows.
> 
> You could, of course, map those keys to do something like Carthik says, 
> but the question is, do you actually use those buttons?
> 
> 
> Michael
> 
> 

Thanks for the replies .....

Carthik yes, i have an m$ wireless keyboard and mouse (and a KVM switch
to make things even more iteresting) ....

BUT ...

I am getting those messages without pressing any keys other than the
necessary spaces, and <enter> of course, in a terinal window.

So even if the cause is the keyboard i am using how come linux sees a
keystroke that is not be pressed?

Chris