Re: Curious keyboard behaviour.

Dylan Griffiths wrote:
> I've been experiencing weird keyboard behaviour since the recent
> Feisty upgrade which I assumed was related to the network card badness
> and lockups (since they both seemed to occur at the same time).
> However, now that I'm running a friendly Edgy kernel, I've still run
> into these periodic keyboard snafus -- even though everything else works
> as advertised.
> What happens is that, while using the keyboard, my metakey status
> will get into an inconsistent state. For example, if I'm typing on the
> alphanumeric section of the keyboard ctrl, alt, or shift will become
> stuck "on" until I press the keys again. If I'm using the arrow keys or
> insert/delete/etc, even though I leave numlock ON and use the dedicated
> arrow keys, I will have 4/8/6/2 pop into my text as if I were using the
> number pad and had temporarily toggled on the numlock.
> I've tried two different PS/2 keyboards, and it seems unlikely that
> it's a single dead keyboard. The keyboards otherwise seem to function
> entirely normally. A USB keyboard seems unaffected by the behaviour,
> though, so I've been using that more often than my main one. I'll
> probably try out more keyboards as time permits.
> Whenever this behaviour occurs, I get a friendly dmesg entry:
>
> [17183431.224000] atkbd.c: Unknown key pressed (translated set 2, code
> 0x8e on isa0060/serio0).
> [17183431.224000] atkbd.c: Use 'setkeycodes e00e <keycode>' to make it
> known.
>
> [17183443.632000] atkbd.c: Unknown key released (translated set 2, code
> 0xe0 on isa0060/serio0).
> [17183443.632000] atkbd.c: Use 'setkeycodes e060 <keycode>' to make it
> known.
>
> [17183686.936000] atkbd.c: Unknown key released (translated set 2, code
> 0xff on isa0060/serio0).
> [17183686.936000] atkbd.c: Use 'setkeycodes e07f <keycode>' to make it
> known.

Do you have 2 keyboards plugged in? I've had similar oddness when using
an external keyboard plugged into my Lappy. As I understand from
google, Linux is (was?) not entirely happy with having more than one
keyboard plugged in.

In my case it would very occasionally but entirely randomly send
keypresses, resulting in similar messages to those above as well as
sometimes corrupting what I was typing.

I haven't checked if it's been fixed since about 2.6.12 though, so it
may work now and your problem might be something different.
Received on Wed May 2 12:03:56 2007