Arch Linux

UnwillingFirehose

Member

From: UK

Registered: 2014-12-09

Posts: 17

udev failing to act on USB device being inserted

Hi,

I'd like udev to print an onscreen message when I plug in a specific USB device. However, before I even start making "notify-send" work ( I'm ready to use the proposed solution on https://wiki.archlinux.org/index.php/De … tions#Bash ), I'm facing a couple of issues:

The device looks like this in the output of lsusb:

Bus 008 Device 037: ID 10d6:1101 Actions Semiconductor Co., Ltd D-Wave 2GB MP4 Player / AK1025 MP3/MP4 Player

I write up a file in /etc/udev/rules.d called "00-personal-rules", consisting of one of these three lines:

ACTION=="add", SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", ENV{ID_MODEL_ID}=="1101", RUN+="/usr/bin/touch /tmp/udevffs"
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="10d6", ATTRS{idProduct}=="1101", RUN+="/usr/bin/touch /tmp/udevffs"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="10d6", ATTR{idProduct}=="1101", RUN+="/usr/bin/touch /tmp/udevffs"

Each of ENV or ATTR or ATTRS appears in the wiki and examples online, so I've tried each one.

However, when I plug in the device, nothing happens. The device is detected, and is available to be mounted as a disk drive, but I can't RUN anything.

Beyond that, trying to diagnose this by executing "udevadm test /dev/bus/usb/008/037 --action=add" gives me two further issues. The output is listed below, but as you can see...

• The file I've added to /etc/udev/rules.d isn't listed amongst all the files being read.

• The command seems to be looking in /sys/dev/... , and so doesn't find the device anyway .

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.

Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/01-md-raid-creating.rules
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
[b]Reading rules file: /etc/udev/rules.d/10-network.rules[/b]
Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
Reading rules file: /usr/lib/udev/rules.d/40-gphoto.rules
Reading rules file: /usr/lib/udev/rules.d/49-sane.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/51-android.rules
Reading rules file: /usr/lib/udev/rules.d/56-hpmud.rules
Reading rules file: /usr/lib/udev/rules.d/60-block.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules
Reading rules file: /usr/lib/udev/rules.d/60-input-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /usr/lib/udev/rules.d/60-rfkill.rules
Reading rules file: /usr/lib/udev/rules.d/60-sensor.rules
Reading rules file: /usr/lib/udev/rules.d/60-serial.rules
Reading rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
Reading rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs-dm.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
Reading rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
Reading rules file: /usr/lib/udev/rules.d/65-kvm.rules
Reading rules file: /usr/lib/udev/rules.d/65-libwacom.rules
Reading rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
Reading rules file: /usr/lib/udev/rules.d/69-libftdi.rules
Reading rules file: /usr/lib/udev/rules.d/69-libmtp.rules
Reading rules file: /usr/lib/udev/rules.d/69-md-clustered-confirm-device.rules
Reading rules file: /usr/lib/udev/rules.d/69-yubikey.rules
Reading rules file: /usr/lib/udev/rules.d/70-infrared.rules
Reading rules file: /usr/lib/udev/rules.d/70-joystick.rules
Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
Reading rules file: /usr/lib/udev/rules.d/70-spice-webdavd.rules
Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/80-libinput-device-groups.rules
Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks2.rules
Reading rules file: /usr/lib/udev/rules.d/89-alsa-ucm.rules
Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
Reading rules file: /usr/lib/udev/rules.d/90-libinput-model-quirks.rules
Reading rules file: /usr/lib/udev/rules.d/90-vconsole.rules
Reading rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
Reading rules file: /usr/lib/udev/rules.d/96-e2scrub.rules
Reading rules file: /usr/lib/udev/rules.d/99-fuse3.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
Reading rules file: /usr/lib/udev/rules.d/99-vmware-scsi-udev.rules
Rules contain 405480 bytes tokens (33790 * 12 bytes), 31767 bytes strings
26784 strings (206641 bytes), 23385 de-duplicated (178274 bytes), 3400 trie nodes used
[b]Failed to open device '/sys/dev/bus/usb/008/037': No such device[/b]
Unload module index
Unloaded link configuration context.

Last edited by UnwillingFirehose (2019-05-26 10:21:03)

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,645

Re: udev failing to act on USB device being inserted

Please edit your post and use [ code ] tags (not quote tags) when posting output.

https://wiki.archlinux.org/index.php/Co … s_and_code
https://bbs.archlinux.org/help.php#bbcode

loqs

Member

Registered: 2014-03-06

Posts: 17,377

Re: udev failing to act on USB device being inserted

Rule files must have the
       extension .rules; other extensions are ignored.

UnwillingFirehose

Member

From: UK

Registered: 2014-12-09

Posts: 17

Re: udev failing to act on USB device being inserted

Please edit your post and use [ code ] tags (not quote tags) when posting output.

https://wiki.archlinux.org/index.php/Co … s_and_code
https://bbs.archlinux.org/help.php#bbcode

Thanks for this   When I looked at https://bbs.archlinux.org/help.php#bbcode it shows the output of using the "code" in bbcode as white characters with a black background, which I don't think I've seen in the forum. So I assumed that page was incorrect and everyone used "quote" instead.

UnwillingFirehose

Member

From: UK

Registered: 2014-12-09

Posts: 17

Re: udev failing to act on USB device being inserted

Rule files must have the
       extension .rules; other extensions are ignored.

Thank you! I knew I was missing something simple, and I genuinely didn't "see" the crucial difference between my use of "rules" and the required ".rules".

I've got a couple of issues to solve, such as the command I want to run actually running, and figuring out why

udevadm test /dev/bus/usb/008/038 --action=add

doesn't actually work, so I won't mark this as s-o-l-v-e-d just yet.

Last edited by UnwillingFirehose (2019-05-26 10:39:07)