Well, firstly 'udevadm trigger' also does not work. I really have to
physically reconnect or unbind and rebind via sysfs to get the mapping
working. Just for the record.
As for your other question: It's a relatively normal system
- Intel Core i5-4570 (Haswell)
- 8 GB RAM
- Asrock H87 Pro4 (Intel H
Malte Wetz [2014-08-26 9:56 -]:
> The last sentence seems to indicate that compiling the hwdb is the only
> thing you have to do to make changes take effect.
Yes, that's indeed the intended mode. It works like that just fine
here. Of course you have to either unplug/replug the keyboard, or se
I figured out what the problem was myself: The manpage of udevadm is
incorrect. Or at least misleading. It says:
<- snip ->
udevadm hwdb [options]
Maintain the hardware database index in /lib/udev/hwdb.bin.
--update
Compile the hardware database information lo
