With udev / systemd version 241 and similar, as root:
udevadm control --log-priority=debug
journalctl -f
Or to make it permanent, again as root:
vi /etc/udev/udevd.conf
systemctl restart systemd-udevd
journalctl -f
PS: the most frequent answer looks like:
udevadm -d test /devices/where/is/my/device |& less
... but this has a number of issues. The main ones:
where/is/my/device
? Tedious, complicated and error-prone.
Comparing old answers to recent udev version 241 output, udevadm test
seems to show less information that it used to.
It's only a simulation!
Every time it warns:
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.
udevadm test
is for developing a new rule, it's not for troubleshooting broken, missing or overridden rules.
2I think you mean
SUBSYSTEMS=="usb"
. I.e. double==
which tests for equality rather than single=
which assigns a value to a key. – Lqueryvg – 2015-09-26T13:31:44.900