Bug#224909: xlibs: still need more infos ?
Some more info to these bugs: (forwarded from lkml)
(search lkml archives for more info)
From: Vojtech Pavlik [email blocked]
To: linux-kernel, [email blocked]
Subject: 2.6 input drivers FAQ
Date: Sun, 1 Feb 2004 11:06:44 +0100
Common problems and solutions with 2.6 input drivers:
[...]
Problem:
~~~~~~~~
Kernel reports:
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Solution:
~~~~~~~~~
Well, the kernel means what it says. XFree86 boldly goes and accesses the
keyboard controller registers when it starts up. This is a bad thing to do,
as it can conflict with the kernel using these registers at the same time.
The kernel spots this and complains, and in most cases is not affected by
the problem.
So, unless you are an XFree86 developer and can fix X, ignore this message.
[...]
Problem:
~~~~~~~~
My multimedia keys don't work at all and instead emit a message like this:
atkbd.c: Unknown key pressed (translated set 2, code 0x83 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e003 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0x83 on
isa0060/serio0).
atkbd.c: Use 'setkeycodes e003 <keycode>' to make it known.
Solution:
~~~~~~~~~
Do what the kernel says. Use the setkeycodes utility with the suggested
scncode value. For the keycode value, look into /usr/include/linux/input.h,
where is a list of all defined Linux keycodes.
Then you can verify that the keyboard works correctly by using the evtest
program:
evtest /dev/input/event#
Where # is the number of the input device that is your keyboard.
Reply to: