Am Sonntag, den 02.08.2009, 20:56 +0000 schrieb Martin Pitt:
> > Is there a way to trace the whole sequence done during boot-up?
>
> Something like this. "udevadm test /devices/.../" (the sysfs path) will
> show the matches and commands run.
# udevadm
test /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.1/input/input7
run_command: calling: test
udevadm_test: version 145
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
...
parse_file: reading '/lib/udev/rules.d/95-keymap.rules' as rules file
add_rule: unknown key 'ID_CLASS' in /lib/udev/rules.d/95-keymap.rules:14
...
Line 14 of 95-keymap.rules is:
ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
ID_CLASS=="kbd", RUN=+"keymap $name usb-mosart-0102"
After modifying it to:
ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
ENV{ID_CLASS}=="kbd", RUN=+"keymap $name usb-mosart-0102"
The udevadm output looks better. But still no luck.
Cheers,
Dominik
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
