Comment 7 for bug 407940

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 407940] Re: Acer 6920: Some scancodes not/wrong registered

Hello Alex,

Alexander Hartl [2009-08-07 16:05 -0000]:
> > OK, that means that these keys are on a different input device.
> > Apparently you have something called a "Logitech USB receiver".
>
> That's my Logitech wireless mouse.

Ah, then the input devices I mentioned are not related to the missing
keys.

> > Can you please try whether you see these keys on input/event6
> > (unlikely, but possible) or input/event7 (more likely)?
>
> No, they appear on none of them.

Can you check "sudo lsinput" and check if there's any other device
which isn't obviously something else (such as the power button), and
you didn't try yet?

> > EUR, $, and the other keys are already correct, except for 0xD9 which
> should be "bluetooth", not "brightnessup".
>
> Yes, € and $ are correct but they don't work anyway...

They can't work in X.org because they have a key code > 255, that's a
known limitation of X (there's a bug report for it, but I'm offline
right now and can't find it). Nothing we can fix in udev and the
keymaps, unfortunately.

> > Where do these come from? You did not mention them in your testing above?
>
> From syslog. For each unknown key pressed it throws messages like (e.g.
> Acer Arcade-key)
>
> Aug 7 18:00:35 alex-note kernel: [ 305.874799] atkbd.c: Unknown key pressed (translated set 2, code 0x92 on isa0060/serio0).
> Aug 7 18:00:35 alex-note kernel: [ 305.874807] atkbd.c: Use 'setkeycodes e012 <keycode>' to make it known.
> Aug 7 18:00:35 alex-note kernel: [ 305.885437] atkbd.c: Unknown key released (translated set 2, code 0x92 on isa0060/serio0).
> Aug 7 18:00:35 alex-note kernel: [ 305.885445] atkbd.c: Use 'setkeycodes e012 <keycode>' to make it known.

Ah, this at least proves that they should appear on _some_ input
device, and that it doesn't need a kernel fix. Did adding these keys
to above map actually make these keys work? If so, this would prove
that they are indeed normal keys on the input/event5 device (as I
would expect).

FYI, I'll be on holidays the next two weeks, so my next response will
be delayed a little.

Thanks!