Marcelo Magno T. Sales wrote:
Em Sáb 12 Mai 2007, dragoran escreveu:
> Marcelo Magno T. Sales wrote:
>
>> Em Qua 09 Mai 2007, Matthias Clasen escreveu:
>>
>>> On Wed, 2007-05-09 at 07:29 +0200, Nicolas Mailhot wrote:
>>>
>>>> Le mardi 08 mai 2007 à 17:51 -0400, Matthias Clasen a écrit :
>>>>
>>>>> For these, I had the crazy idea today that maybe you could have a
tool
>>>>> that asks you to press a key, and if no key event is coming forward,
>>>>> parse the dmesg output for the keyboard driver warning...
>>>>>
>>>> You won't get a keyboard warning : most enhanced keys do not
generate
>>>> anything today because they're attached to a different device than
the
>>>> main keyboard, and there's no driver for this device (yet)
>>>>
>>> I do get warnings for all of the nonworking keys on this laptop, at
>>> least.
>>>
>> Lucky you :) On mine, none of them are detected by the kernel.
>>
> I also get this kind of warings:
> atkbd.c: Unknown key pressed (translated set 2, code 0xd8 on
> isa0060/serio0).
> atkbd.c: Use 'setkeycodes e058 <keycode>' to make it known.
> atkbd.c: Unknown key released (translated set 2, code 0xd8 on
> isa0060/serio0).
> atkbd.c: Use 'setkeycodes e058 <keycode>' to make it known.
>
These are easier to solve. Use the setkeycodes command to map ths scancodes
listed to unused keycodes. Then you'll be able to use these keys even in X
and map shortcuts to them.
You may add the setkeycodes lines in /etc/rc.d/rc.local so that they are
always executed when you boot.
thats what I do now ;)
but I don't think this is a user friendly way ....