1. Find the keyboard device.
- Run /usr/share/udev-extras/findkeyboards. This should always give you an "AT
+ Run /lib/udev/findkeyboards. This should always give you an "AT
keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and
Acers) have multimedia/function keys on a separate input device instead of the
primary keyboard. The keyboard device should have a name like "input/event3".
- In the following commands, the name will be written as "input/eventX".
+ In the following commands, the name will be written as "input/eventX" (replace
+ X with the appropriate number).
2. Dump current mapping:
/lib/udev/keymaps/ for existing key map files and make sure that you use the
same structure.
+ If the key only ever works once and then your keyboard (or the entire desktop)
+ gets stuck for a long time, then it is likely that the BIOS fails to send a
+ corresponding "key release" event after the key press event. Please note down
+ this case as well, as it can be worked around in
+ /lib/udev/keymaps/95-keyboard-force-release.rules .
+
4. Find out your system vendor and product:
cat /sys/class/dmi/id/sys_vendor
/tmp/orig-map.txt from step 2, and /tmp/udev-db.txt from step 5
to the bug tracker, so that they can be included in the next release:
- https://bugs.launchpad.net/udev-extras/+bugs
+ https://bugs.launchpad.net/udev/+bugs
For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate
name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules: