Tag Info

New answers tagged

0

Try rename it to 99-hdmi_sound.rules (with 2 digits only) & use RUN instead and omit ACTION SUBSYSTEM=="drm", RUN+="/lib/udev/hdmi_sound_toggle.sh"


0

I taught of same cause as @dmd, PCI uevents come before filesystem re-mount as rw. (But sometimes, some of PCI uevents come after, race condition, working in parallel) dmesg | grep -i -e mount -e pci @Sparhawk sleep idea seems good to me. I think this why it doesn't work (Ref: man udev): This can only be used for very short-running foreground tasks. ...


0

Rename it to 99-my.rules Use absolute paths: SUBSYSTEM=="block", ACTION=="add", RUN+="/bin/touch /tmp/my_udev_rule_matched_OK"


0

Actually, I couldn't get a reference for this; But It's something got by Try & Error. udev requires the full path of script/program/file used either in PROGRAM, TEST, RUN or IMPORT. udev doesn't support redirection operations. udev can handle command with arguments. udev has variable substitution. So you can write multifunction script (not just ...


0

It is possible that your rule is overridden by a late rule. ~$ /lib/udev/rules.d/40-flashrom.rules # Olimex ARM-USB-TINY-H # http://olimex.com/dev/arm-usb-tiny-h.html ATTRS{idVendor}=="15ba", ATTRS{idProduct}=="002a", MODE="664", GROUP="plugdev" Try rename your rule to start with number higher then 90-*


0

Have you tried reloading udev? It should recognise new rules automatically, but maybe it didn't... sudo udevadm control --reload-rules ; sudo udevadm trigger


1

Remove the line sudo su. It starts a new root shell that never returns and that is why any command after that is not being executed. On top of that granting yourself a permission to do sudo su without password is a serious security risk and should not be done in a real world environment.


0

You can use inequality for exceptions: ACTION=="add", DRIVERS=="usb-storage", ATTRS{idVendor}!="054c", RUN+="/bin/sh -c 'echo 0 >/sys%p/authorized'"


0

%k (variables) are not to be used in matching condition. Use directly same add condition (you have chosen a long path): ATTRS{manufacturer}=="Zebra Technologies", ACTION=="remove", RUN+="/usr/local/bin/reinitZebra.sh"


11

It seems to work for me in Ubuntu 14.04 with 2 flash keys & android phone as storage and usb network adapter & webcam as other type. (I couldn't test placing a usb hub) Check USB port (which is a parent device for the plugged device) $ udevadm info --name=/dev/sdc --attribute-walk looking at parent device ...


0

This problem has been solved in the latest update for udev in trusty, so just run the Software Updater or open a Terminal and enter sudo apt-get update sudo apt-get upgrade


0

Keyboards use event device files. You can find them in /dev/input/event*. To find the exact path you can egrep -i "keyboard.+\/dev" /var/log/Xorg.0.log



Top 50 recent answers are included