Thanks for making me notice the fact I am using X.org 7.1
The evdev implementation, as far as i know, changed from 6.9 to 7.0. I don't know about 7.0 to 7.1.
Basically, if you read the recent addition to the howto describing how the evdev X driver generates keycodes, just now that kbd and keyboard generate different keycodes than evdev, therefore the kbd-generated keycode for Down Arrow is different than the evdev-generated keycode for Favorites, so in your case they do not overlap. On the other hand the key number 1 and the Print key are both managed by the same evdev-driven InputDevice, so they still have the same keycode. The problem is at kernel level, or rather in the fact that X and console do not accept keycodes higher than 255 (1 byte integers), so the right keycodes in the kernel driver for the six keys I mentioned in the howto cannot be used (the X evdev driver alter them truncating their values to 8 bits and causing those annoying overlaps, while the kbd driver and the console simply ignores them).
I've written to liyu about using lower keycodes for those keys, even if they would not be the proper ones listed by /usr/include/linux/input.h (being KEY_FAVORITES, KEY_FN_F1, KEY_FN_F2, KEY_FN_F3, KEY_FN_F4, KEY_FN_F5).
A good advice would also be to customise your xkb files with keycodes and symbols files adapted for this keyboard (the geometry file is not strictly necessary, even if quite complicate to write) and update then the rules file.
Code: Select all
# setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+nek4k(nek4k)+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc(pc105)+it+inet(microsoftnek4k)" };
xkb_geometry { include "microsoft(nek4k)" };
};
You can also do the same, in a less standard way, with the old xmodmap (except setting the geometry).
XKB can be a little complicated thing sometimes.
Stay tuned to howto and related talk for changes. It's still a work in progress. (gento-wiki is up again).
P.S. The reason why I didn't use symlinks whas that the evdev X driver accept only /dev/input/event* names for the devices (man 4x evdev, one of the most obscure and frustrating man pages I've ever read, especially in the part regarding the capabilities bits).
DON'T USE event0 or 1, as a rule. They might be already existing if you plug in your mouse before your keyboard os samething like that. Using a higher number (event20 and 21 or similar) as in my howto should prevent nasty, even if occasional, surprises.
) doing wonders for your wrists, at least it did for me, and the multimedia keys works great with lineak
)
