Are /etc/udev/rules.d/86-hpmud* files obsolete?

For a while now, I keep getting the following errors during boot:
Sat Jan 21 14:25:13 2012: udevd[148]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1102w.rules:9
Sat Jan 21 14:25:13 2012: udevd[148]: invalid rule '/etc/udev/rules.d/86-hpmud-hp_laserjet_professional_p1102w.rules:9'
... (repeat for every 86-hpmud-* file in that folder)
I found an (ancient) bug report from 2009 with the subject "hplip: obsolete udev rules files are not removed on upgrades", so I assume they're obsolete, but I've only recently starting seeing this problem, which wouldn't jive with a 3-year old issue.
Can I safely delete these files, assuming that their contents has been replaced with entries in the /lib/udev/rules.d tree? I am not that well-versed in udev, unfortunately....

OK - I backed them up and moved them out of /etc/udev/rules.d.
Confirming nothing broke is a bit of a problem right now. Printing is hit & miss from my laptop to my wireless HP P1102w printer at the best of times. I haven't figured out what the real issue is there, but since printing to other HPs works fine, I'll probably have to blame the printer or HPLIP. I wish HP would simplify their software and made simple drivers. I just need to print, I don't need all that hp-toolbox junk. I'll confirm this when I have a chance to print to a different HP printer.

Similar Messages

  • 3 unable to open '/etc/udev/rules.d/':m error during booting

    After a recent upgrade to the kernel26-2.6.28.5-1-i686, I got the above error during booting in one of the laptop.
    My search did not give any positive solution for this till now. I read that now udev gets its rules from /lib/udev/rules.d.
    But still rules files in /etc/udev/rules.d and /lib/udev/rules.d are different. I know that any symllink work around will not work in this case, I tried but as  expected the error message appears again.
    So, I roll back to kernel26-2.6.28.4-1-i686 and everything back to normal.
    Any Idea to resolve this? (package is not broken as I use the same mirror for another PC and in that I am not getting any error)
    Last edited by kgas (2009-02-19 16:10:23)

    This issue got resolved on its own with the latest kernel (kernel26-2.6.28.6-1-i686) update. I will leave this topic for some more time to see others response...

  • [solved] /etc/udev/rules.d/10-network.rules ignored

    Hi.
    I have 4 nics (eth0, eth1, eth2, eth3) mapped to MAC addresses in  /etc/udev/rules.d/10-network.rules.
    Some months ago, I had to symlink /etc/udev/rules.d/80-net-name-slot.rules to /dev/null in order to use these static names.
    Now it doesn't work anymore (again and again and again) after a full update (kernel and I assume systemd).  The "nic-names" are completely wrong.  You call this "predictable". I call this "unpredictable". The only thing which is predictable is that after a kernel update, the network will stop working. It has been that way for months and months ... fortunately I don't update other machines anymore.
    Was this non sense really necessary?
    Anyway, if you could tell me what to do now to get my network rules applied again, I would really appreciate.
    Right now all ethX/MAC are wrong and none of them gets an IP (had to set an IP manually to post here).
    * I know what "predictable Network Interface Names" is about. I don't want this bullshit. It's much worse as it used to be. Keep it simple, folks!
    Last edited by Agnelo de la Crotche (2013-03-27 07:14:05)

    tomegun wrote:To narrow down the problem you are experiencing: What do you mean when you say that the names are "wrong"? Are they still eth0, eth1,... just in the wrong order, or are you actually seeing the "weird" new names given by udev?
    To answer this question more precisely.
    * with  /etc/udev/rules.d/80-net-name-slot.rules => /dev/nul and /etc/udev/rules.d/10-network.rules posted earlier  (in #4)
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
    link/ether 66:64:b3:6a:26:61 brd ff:ff:ff:ff:ff:ff
    The rules are ignored.
    * after deleting   /etc/udev/rules.d/80-net-name-slot.rules
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    3: enp6s1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    4: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
    link/ether a2:ee:ec:d1:65:2d brd ff:ff:ff:ff:ff:ff
    The rules don't apply.
    * with  /etc/udev/rules.d/80-net-name-slot.rules => /dev/nul and after replacing eth0, eth1, eth2, eth3 with arbitrary names net0, net1, net2, net3 in  /etc/udev/rules.d/10-network.rules
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: net1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    3: net3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    4: net2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    5: net0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
    link/ether ea:63:09:b7:1b:1b brd ff:ff:ff:ff:ff:ff
    But the rules were applied in this case!
    It solved the problem described originally.  I think I was hit by the race condition after upgrating to kernel 3.8.4-1. This was actually my first 3.8 kernel.
    With kernel 3.7, the rules were working even if the devices were named eth0, eth1, etc.
    Those names don't work anymore, at least in my case.
    Further I  created this file for static ips:
    # cat /etc/systemd/system/network.service
    [Unit]
    Description=Wired Static IP Connectivity
    Wants=network.target
    Before=network.target
    BindsTo=sys-subsystem-net-devices-net0.device
    After=sys-subsystem-net-devices-net0.device
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/sbin/ip link set dev net0 up
    ExecStart=/sbin/ip addr add 192.168.101.9/24 dev net0
    ExecStart=/sbin/ip link set dev net1 up
    ExecStart=/sbin/ip addr add 192.168.102.9/24 dev net1
    ExecStart=/sbin/ip link set dev net2 up
    ExecStart=/sbin/ip addr add 192.168.104.9/24 dev net2
    ExecStart=/sbin/ip link set dev net3 up
    ExecStart=/sbin/ip addr add 192.168.105.9/24 dev net3
    ExecStart=/sbin/ip route add default via 192.168.101.1
    ExecStop=/sbin/ip addr flush dev net0
    ExecStop=/sbin/ip link set dev net0 down
    ExecStop=/sbin/ip addr flush dev net1
    ExecStop=/sbin/ip link set dev net1 down
    ExecStop=/sbin/ip addr flush dev net2
    ExecStop=/sbin/ip link set dev net2 down
    ExecStop=/sbin/ip addr flush dev net3
    ExecStop=/sbin/ip link set dev net3 down
    [Install]
    WantedBy=multi-user.target
    I disabled netcfg and enabled network.service.
    Problem is solved now.

  • Oh god I overwrote /etc/udev/rules.d/90-hal.rules

    I accidentally sudo overwrote this file with garbage. I haven't rebooted yet. What was in here? Is it important? How do I get it back?
    Thanks!

    If it was something in that directory, the sizes should be different than mine. This is what I have:
    ls -l /etc/udev/rules.d/
    total 52
    -rw-r--r-- 1 root root 1071 2008-09-24 07:07 60-pcmcia.rules
    -rw-r--r-- 1 root root 390 2009-03-07 15:42 75-cd-aliases-generator.rules.optional
    -rw-r--r-- 1 root root 2403 2009-03-07 15:42 75-persistent-net-generator.rules.optional
    -rw-r--r-- 1 root root 8039 2009-03-07 15:42 81-arch.rules
    -rw-r--r-- 1 root root 82 2008-11-30 08:51 90-hal.rules
    -rw-r--r-- 1 root root 28 2008-10-19 06:35 99-fuse.rules

  • My /etc/udev/rules.d is empty? [SOLVED]

    The other week i installed a virtal inviroment in QEMU, i read a little bit about writing udev-rules, in order to work with USB. but for some reason.. the folder in mentioned in the topic happends to be empty.. and it just strikes me, because when gogling the problem it seems that the people it happend to before, it also ment that the system didnt work, or worked really bad, but my system works fine.. Now, as i allready mentioned, i bumped in to this problem the other week. i have been searching for some obvious noskillmistake, but.. i gave up and just turned to you guys instead.
    Last edited by kimbo (2014-11-13 18:02:04)

    That folder is empty for me too, because I haven't put anything there.  Have you created files there that disappeared?  If not, what's the issue?  You say everything is working ... so what's the question?

  • Udev rules or buggy hardware driver?

    hello out there,
    here's my situation, after setting this rule for my graphics tablet...
    KERNEL=="event*", SYSFS{manufacturer}="AIPTEK International Inc.",
    NAME="input/aiptektablet", MODE="0644"
    i revieve the following on next boot...
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt and you might try running e2fsck with an alternate superblock
    E2fsck -b 8193 <device>
    after removing the rule and rebooting the drive check goes fine and everything runs smooth again.
    note:The idea to remove the aiptek udev rule came when I noticed all udev events in /dev/disk/* pointed to the aiptek tablet instead of their usual sda sdb sdc sdd hda1 hda2 etc.
    I would still like a consistent input point for my tablet someday, but this situation seems over my head.
    any ideas?
    thanks

    Thanks for your answer Rexilion.
    The author of the module, and the rule, suggest to put the rule in /etc/udev/rules.d under the file name 90-logitech-g710-plus.rules. So that is what I have tried up to now, along with putting the file in /usr/lib/udev/rules.d and changing the preceding number to 10 instead of 90. The only thing that my tinkering has done is that changing ACTION=="add" to ACTION=="add|change" has allowed udevadm trigger to apply the rule. Of course, I could use that to generate some real ugly workaround, but I would rather not. Otherwise, from what I have seen, you are probably right about a race condition, but I have been in the dark as to how to resolve it.
    At this point, I have put the rule in /usr/lib/udev/rules.d and used "mkinitcpio -p linux" to rebuild the image, but it doesn't make a difference as to what default rules are in the image. In mkinitcpio.conf, I have the udev hook, but I figure that is kind of defautl, am I to modify that hook? What am I missing? I have read and reread the wiki about udev, and mkinitcpio, but I'm very unclear as to how to add the rule for the keyboard to the default set.
    @jasonwryan: Perhaps I'm being stupid, but is loading a module and binding it to the keyboard considered a long running process? I would have thought it is an event which is very short and needs no further attention or resources once it is done.

  • Udev update: udev.rules file contains errors [was: dbus+hal update]

    I am aware of the fact that there are already a few topics and a bug report (http://bugs.archlinux.org/task/6351) concerning the recent dbus & hal upgrades. However, my case seems different and more complex. I am not even sure if this is directly related to the others' issues.
    Since the update to dbus-1.0.2-2 my system does not follow some dbus rules any more. The recent follow-up update to dbus-1.0.2-3 did not remedy my problems, either.
    I think that this is due to the /etc/udev/rules.d/udev.rules file having become corrupted with the recent updates. Under the sections
    #pty and tty legacy devices
    and
    #vc devices
    several KERNEL=[...] lines have errors, at least the final double quotation marks are missing!
    So far my problems are as follows:
    - Intel i810 video driver fails to load: "No matching device [...] found".
    - Thinkpad's nvram is not get created in /dev
    - no pty devices / no ttyp devices are created in /dev. Therefore, none of my X-based consoles will start. Konsole, for example, exits with "Konsole is unable to open a PTY [...]".
    I will investigate further and report. Anyone eslse experiencing similar problems?
    Btw., contrary to the experience of others, removable devices are recognized and mounted.
    Last edited by mutlu_inek (2007-02-07 02:52:34)

    Those errors I found were actually introduced a few days ago by udev-105-1! The /etc/udev/rules.d/udev.rules provided by that package has errors!
    Correcting those errors brought back my beloved pseudo teletypes in /dev/pts/X. But the nvram device is still not created.
    Update:
    Here is the diff output of udev-105-1's udev.rules compared with what it should be:
    --- udev.rules 2007-02-06 21:20:06.000000000 -0500
    +++ udev.rules_corrected 2007-02-06 21:16:36.000000000 -0500
    @@ -143,8 +143,8 @@
    SUBSYSTEMS=="scsi", KERNEL=="sg[0-9]*", ATTRS{type}=="6", GROUP="scanner"
    # pty and tty legacy devices
    -KERNEL=="pty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule
    -KERNEL=="tty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule
    +KERNEL=="pty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule"
    +KERNEL=="tty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule"
    # md block devices
    KERNEL=="md[0-9]*", NAME="md%n", SYMLINK+="md/%n"
    @@ -166,8 +166,8 @@
    KERNEL=="vcs[0-9]*", NAME="vcc/%n", OPTIONS="last_rule"
    KERNEL=="vcsa", NAME="vcc/a0", OPTIONS="last_rule"
    KERNEL=="vcsa[0-9]*", NAME="vcc/a%n", OPTIONS="last_rule"
    -KERNEL=="ptmx", MODE="0666", OPTIONS="last_rule
    -KERNEL=="tty", MODE="0666", OPTIONS="last_rule
    +KERNEL=="ptmx", MODE="0666", OPTIONS="last_rule"
    +KERNEL=="tty", MODE="0666", OPTIONS="last_rule"
    # video devices
    SUBSYSTEM=="video4linux", GROUP="video"
    Last edited by mutlu_inek (2007-02-07 02:44:24)

  • [Solved] Auto-open a file manager after mounting with udev rules

    Hellooooo,
    I followed the udev Wiki for auto mounting USBs and it now works great.
    The only problem is: how can I automatically open a file manager of the mounted directory? I tried putting this at the end of the "ACTION=="add"," section in "/etc/udev/rules.d/11-media-by-label-auto-mount.rules" but for some reason nothing happens:
    , RUN+="/usr/bin/dolphin /media/%E{dir_name}"
    Even if I just try to open dolphin with the "ACTION=="add"," section nothing happens either way.
    So what am I doing wrong?
    Last edited by algorythm (2011-05-05 12:35:56)

    In that case, the best choice in my opinion is to use Automounting UDisks Wrappers :
    devmon is a script developed by IgnorantGuru. He left Arch Linux, but the package in AUR is still there and is the last version. For a future new release, it should be available at his blog site. The script is distro independent.
    My udisksvm script, in its default state, doesn't launch a file manager after automounting, but it is not a big thing to let the automounting be done and then manually open a file manager (a new entry in the traydevice right-click menu can also be added for that).
    If you can do without automounting, there is also the bashmount script from jnguyen.
    All these scripts don't require writing any udev rules, they use udisks instead.
    I hope you could find something you like and which will suit your wishes.

  • [RESOLVED] udev rules are always ignored.

    #/etc/udev/rules.d/powersave.rules
    ACTION=="add", SUBSYSTEM=="net", KERNEL=="wlp4s0", RUN+="/usr/sbin/iw dev %k set power_save on"
    I have a simple udev rule like the above, but it's always ignored. Any ideas?
    btw, udevadm test can pass.
    Thanks.
    Last edited by enihcam (2013-07-14 03:55:51)

    brebs wrote:
    enihcam wrote:KERNEL=="wlp4s0"
    I would be suspicious of that. That's a name created by udev rules AIUI, so I would recommend using 91-blah.rules to ensure that the normal rules are processed *first*.
    Just match on something easy, like ATTR{address}.
    I changed it to KERNEL="wl*", and it works. Thanks!

  • [SOLVED] udev rule no longer working

    I have a udev rule set up to automatically mount an ext4 filesystem when I plug a certain thumb drive in.  It was working fine until yesterday (probably due to updates).  Here is the rule, in file /etc/udev/rules.d/99-gfk.rules:
    KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", SYMLINK+="gfshare"
    ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mkdir /media/gfshare"
    ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mount -t ext4 -o ro,nosuid,nodev,noexec,noatime /dev/gfshare /media/gfshare"
    The symlink and the mkdir command are both working fine, but the mount command is not being run for some reason.  If I manually run the mount command it works fine.  Some possibly helpful output:
    # pacman -Qo $(which udevadm)
    /usr/bin/udevadm is owned by systemd 212-1
    # dmesg |tail -16
    [26458.120628] usb 7-1.3: new high-speed USB device number 7 using ehci-pci
    [26458.223059] usb-storage 7-1.3:1.0: USB Mass Storage device detected
    [26458.223825] scsi10 : usb-storage 7-1.3:1.0
    [26459.311607] scsi 10:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4
    [26460.834081] sd 10:0:0:0: [sdd] 15240576 512-byte logical blocks: (7.80 GB/7.26 GiB)
    [26460.834931] sd 10:0:0:0: [sdd] Write Protect is off
    [26460.834935] sd 10:0:0:0: [sdd] Mode Sense: 23 00 00 00
    [26460.835617] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.835621] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.839455] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.839460] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.860579] sdd: sdd1 sdd2
    [26460.867111] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.867115] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.867118] sd 10:0:0:0: [sdd] Attached SCSI removable disk
    [26461.041982] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null)
    # udevadm test /sys/bus/usb/devices/7-1.3
    calling: test
    version 212
    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
    timestamp of '/etc/systemd/network' changed
    timestamp of '/usr/lib/systemd/network' changed
    Parsed configuration file /usr/lib/systemd/network/99-default.link
    Created link configuration context
    timestamp of '/etc/udev/rules.d' changed
    Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
    read rules file: /usr/lib/udev/rules.d/10-dm.rules
    read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    read rules file: /etc/udev/rules.d/12-android.rules
    read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
    read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
    read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
    read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
    read rules file: /usr/lib/udev/rules.d/50-firmware.rules
    read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    read rules file: /usr/lib/udev/rules.d/51-android.rules
    read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
    read rules file: /usr/lib/udev/rules.d/60-drm.rules
    read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
    read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
    read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
    read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
    read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
    read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
    read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
    read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
    read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
    read rules file: /usr/lib/udev/rules.d/70-infrared.rules
    read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
    read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
    read rules file: /usr/lib/udev/rules.d/71-seat.rules
    read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
    read rules file: /usr/lib/udev/rules.d/75-net-description.rules
    read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
    read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
    read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
    read rules file: /usr/lib/udev/rules.d/80-drivers.rules
    read rules file: /etc/udev/rules.d/80-net-setup-link.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
    read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
    read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
    read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
    read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
    read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
    read rules file: /etc/udev/rules.d/99-gfk.rules
    read rules file: /usr/lib/udev/rules.d/99-systemd.rules
    read rules file: /usr/lib/udev/rules.d/kino.rules
    rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
    10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
    IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/50-udev-default.rules:9
    IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:9
    MODE 0664 /usr/lib/udev/rules.d/50-udev-default.rules:37
    GROUP 1002 /usr/lib/udev/rules.d/51-android.rules:387
    MODE 0660 /usr/lib/udev/rules.d/51-android.rules:387
    RUN '/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers' /usr/lib/udev/rules.d/60-vboxdrv.rules:6
    PROGRAM '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' /usr/lib/udev/rules.d/69-libmtp.rules:1204
    starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'
    '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'(out) '0'
    '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' [24644] exit with return code 0
    IMPORT builtin 'path_id' /usr/lib/udev/rules.d/71-seat.rules:43
    RUN 'uaccess' /usr/lib/udev/rules.d/73-seat-late.rules:15
    handling device node '/dev/bus/usb/007/007', devnum=c189:774, mode=0660, uid=0, gid=1002
    preserve permissions /dev/bus/usb/007/007, 020660, uid=0, gid=1002
    preserve already existing symlink '/dev/char/189:774' to '../bus/usb/007/007'
    ACTION=add
    BUSNUM=007
    DEVNAME=/dev/bus/usb/007/007
    DEVNUM=007
    DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3
    DEVTYPE=usb_device
    DRIVER=usb
    ID_BUS=usb
    ID_DRIVE_THUMB=1
    ID_FOR_SEAT=usb-pci-0000_00_1a_7-usb-0_1_3
    ID_MODEL=DataTraveler_2.0
    ID_MODEL_ENC=DataTraveler\x202.0
    ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    ID_MODEL_ID=6545
    ID_PATH=pci-0000:00:1a.7-usb-0:1.3
    ID_PATH_TAG=pci-0000_00_1a_7-usb-0_1_3
    ID_REVISION=0100
    ID_SERIAL=Kingston_DataTraveler_2.0_1C6F654E4041ED601910053F
    ID_SERIAL_SHORT=1C6F654E4041ED601910053F
    ID_USB_INTERFACES=:080650:
    ID_VENDOR=Kingston
    ID_VENDOR_ENC=Kingston
    ID_VENDOR_FROM_DATABASE=Toshiba Corp.
    ID_VENDOR_ID=0930
    MAJOR=189
    MINOR=774
    PRODUCT=930/6545/100
    SUBSYSTEM=usb
    TAGS=:seat:uaccess:
    TYPE=0/0/0
    USEC_INITIALIZED=26452326568
    adb_user=yes
    run: '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 774 00 vboxusers'
    run: 'uaccess'
    unload module index
    Unloaded link configuration context
    # udevadm test /sys/bus/usb/devices/7-1.3:1.0
    calling: test
    version 212
    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
    timestamp of '/etc/systemd/network' changed
    timestamp of '/usr/lib/systemd/network' changed
    Parsed configuration file /usr/lib/systemd/network/99-default.link
    Created link configuration context
    timestamp of '/etc/udev/rules.d' changed
    Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
    read rules file: /usr/lib/udev/rules.d/10-dm.rules
    read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    read rules file: /etc/udev/rules.d/12-android.rules
    read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
    read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
    read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
    read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
    read rules file: /usr/lib/udev/rules.d/50-firmware.rules
    read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    read rules file: /usr/lib/udev/rules.d/51-android.rules
    read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
    read rules file: /usr/lib/udev/rules.d/60-drm.rules
    read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
    read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
    read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
    read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
    read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
    read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
    read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
    read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
    read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
    read rules file: /usr/lib/udev/rules.d/70-infrared.rules
    read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
    read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
    read rules file: /usr/lib/udev/rules.d/71-seat.rules
    read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
    read rules file: /usr/lib/udev/rules.d/75-net-description.rules
    read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
    read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
    read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
    read rules file: /usr/lib/udev/rules.d/80-drivers.rules
    read rules file: /etc/udev/rules.d/80-net-setup-link.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
    read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
    read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
    read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
    read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
    read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
    read rules file: /etc/udev/rules.d/99-gfk.rules
    read rules file: /usr/lib/udev/rules.d/99-systemd.rules
    read rules file: /usr/lib/udev/rules.d/kino.rules
    rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
    10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
    IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11
    RUN 'kmod load $env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3/7-1.3:1.0
    DEVTYPE=usb_interface
    DRIVER=usb-storage
    ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    ID_VENDOR_FROM_DATABASE=Toshiba Corp.
    INTERFACE=8/6/80
    MODALIAS=usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00
    PRODUCT=930/6545/100
    SUBSYSTEM=usb
    TYPE=0/0/0
    USEC_INITIALIZED=452326811
    run: 'kmod load usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00'
    unload module index
    Unloaded link configuration context
    Last edited by bentglasstube (2014-04-03 20:51:36)

    I see.  That is somewhat aggravating but I will find another way to achieve what I wanted I suppose.
    Thank you.  Should I mark this is solved or unsolvable or something?  Sorry, I'm new to posting on these forums.
    Edit:  I was able to achieve what I wanted with udevil as recommended by the wiki.
    Last edited by bentglasstube (2014-04-03 20:55:45)

  • [SOLVED]Udevd fails to recognize rules in /lib/udev/rules.d

    I've been having a few crashes since the update of udev earlier this week (so far only on my laptop where the Xserver hangs and requires a hard reboot to get anything working again).  While investigating the logs, I ran across the following errors:
    Oct 26 04:39:54 lswest-CULV [ 0.836513] udevd[74]: starting version 173
    Oct 26 04:39:54 lswest-CULV [ 17.450369] udevd[260]: starting version 174
    Oct 26 04:46:04 lswest-CULV [ 0.839752] udevd[74]: starting version 173
    Oct 26 04:46:04 lswest-CULV [ 8.778232] udevd[259]: starting version 174
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/42-qemu-usb.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/50-firmware.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/50-udev-default.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-cdrom_id.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-alsa.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-input.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-serial.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-storage-tape.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-storage.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-v4l.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/61-accelerometer.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/70-udev-acl.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/75-net-description.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/75-probe_mtd.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/75-tty-description.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/78-sound-card.rules': No such file or directory
    Oct 26 11:00:48 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/80-drivers.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/42-qemu-usb.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/50-firmware.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/50-udev-default.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-cdrom_id.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-alsa.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-input.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-serial.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-storage-tape.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-storage.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/60-persistent-v4l.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/61-accelerometer.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/70-udev-acl.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/75-net-description.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/75-probe_mtd.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/75-tty-description.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/78-sound-card.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/80-drivers.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/81-arch.rules': No such file or directory
    Oct 26 11:01:16 lswest-CULV udevd[259]: can not find '/lib/udev/rules.d/95-keyboard-force-release.rules': No such file or directory
    These errors have appeared since the 24th of October (the last marked update day for the udev package).  I'm also slightly concerned about the first 4 lines, where udevd "starts" version 173 and then version 174.  According to pacman -Q udev, only version 174 is installed.
    Upon investigating the folder, I find that all the "missing" files are present:
    [lswest@lswest-CULV: rules.d]% ls
    total 652K
    drwxr-xr-x 2 root root 4.0K Oct 26 11:01 ./
    drwxr-xr-x 5 root root 4.0K Oct 26 11:01 ../
    -r--r--r-- 1 root root 6.4K Aug 20 02:32 10-dm.rules
    -rw-r--r-- 1 root root 505 Aug 16 19:06 10-vboxdrv.rules
    -r--r--r-- 1 root root 1.3K Jul 7 2010 11-dm-lvm.rules
    -r--r--r-- 1 root root 1011 Nov 13 2009 13-dm-disk.rules
    -rw-r--r-- 1 root root 159K Nov 28 2010 40-gphoto.rules
    -rw-r--r-- 1 root root 26K Oct 4 11:56 40-usb-media-players.rules
    -rw-r--r-- 1 root root 764 Oct 19 23:43 42-qemu-usb.rules
    -rw-r--r-- 1 root root 1.8K Jul 30 18:31 45-libnjb.rules
    -rw-r--r-- 1 root root 219 Oct 19 23:43 50-firmware.rules
    -rw-r--r-- 1 root root 3.5K Oct 19 23:43 50-udev-default.rules
    -rw-r--r-- 1 root root 52K Jun 13 13:04 52-libmtp.rules
    -rw-r--r-- 1 root root 104K Oct 5 23:42 53-sane.rules
    -rw-r--r-- 1 root root 584 Oct 19 23:43 60-cdrom_id.rules
    -rw-r--r-- 1 root root 1.1K Aug 3 18:54 60-pcmcia.rules
    -rw-r--r-- 1 root root 616 Oct 19 23:43 60-persistent-alsa.rules
    -rw-r--r-- 1 root root 2.4K Oct 19 23:43 60-persistent-input.rules
    -rw-r--r-- 1 root root 947 Oct 19 23:43 60-persistent-serial.rules
    -rw-r--r-- 1 root root 6.0K Oct 19 23:43 60-persistent-storage.rules
    -rw-r--r-- 1 root root 1.4K Oct 19 23:43 60-persistent-storage-tape.rules
    -rw-r--r-- 1 root root 770 Oct 19 23:43 60-persistent-v4l.rules
    -rw-r--r-- 1 root root 46 Feb 9 2011 60-rfkill.rules
    -rw-r--r-- 1 root root 166 Oct 19 23:43 61-accelerometer.rules
    -rw-r--r-- 1 root root 369 Oct 17 15:34 61-gnome-bluetooth-rfkill.rules
    -rw-r--r-- 1 root root 2.2K Sep 14 09:07 64-md-raid.rules
    -rw-r--r-- 1 root root 40 Aug 12 18:32 65-kvm.rules
    -rw-r--r-- 1 root root 4.0K Oct 4 09:34 69-cd-sensors.rules
    -rw-r--r-- 1 root root 233 Jul 17 18:06 70-infrared.rules
    -rw-r--r-- 1 root root 2.6K Oct 19 23:43 70-udev-acl.rules
    -rw-r--r-- 1 root root 642 Oct 19 23:43 75-net-description.rules
    -rw-r--r-- 1 root root 254 Oct 19 23:43 75-probe_mtd.rules
    -rw-r--r-- 1 root root 642 Oct 19 23:43 75-tty-description.rules
    -rw-r--r-- 1 root root 3.3K Aug 3 10:00 77-mm-ericsson-mbm.rules
    -rw-r--r-- 1 root root 11K Aug 3 10:00 77-mm-longcheer-port-types.rules
    -rw-r--r-- 1 root root 379 Aug 3 10:00 77-mm-pcmcia-device-blacklist.rules
    -rw-r--r-- 1 root root 510 Aug 3 10:00 77-mm-platform-serial-whitelist.rules
    -rw-r--r-- 1 root root 1.6K Aug 3 10:00 77-mm-simtech-port-types.rules
    -rw-r--r-- 1 root root 3.0K Aug 3 10:00 77-mm-usb-device-blacklist.rules
    -rw-r--r-- 1 root root 1.6K Aug 3 10:00 77-mm-x22x-port-types.rules
    -rw-r--r-- 1 root root 9.3K Aug 3 10:00 77-mm-zte-port-types.rules
    -rw-r--r-- 1 root root 284 Sep 20 09:26 77-nm-olpc-mesh.rules
    -rw-r--r-- 1 root root 4.2K Oct 19 23:43 78-sound-card.rules
    -rw-r--r-- 1 root root 559 Oct 19 23:43 80-drivers.rules
    -rw-r--r-- 1 root root 667 Aug 3 10:00 80-mm-candidate.rules
    -rw-r--r-- 1 root root 9.3K Aug 26 18:47 80-udisks.rules
    -rw-r--r-- 1 root root 372 Oct 19 23:43 81-arch.rules
    -rw-r--r-- 1 root root 335 Apr 4 2011 85-regulatory.rules
    -rw-r--r-- 1 root root 602 Aug 4 17:39 85-usbmuxd.rules
    -rw-r--r-- 1 root root 131 Aug 17 09:43 90-alsa-restore.rules
    -rw-r--r-- 1 root root 83 Jan 10 2011 90-hal.rules
    -rw-r--r-- 1 root root 1.9K Aug 9 15:18 90-libgpod.rules
    -rw-r--r-- 1 root root 2.0K Oct 20 17:26 90-pulseaudio.rules
    -rw-r--r-- 1 root root 847 Oct 4 09:34 95-cd-devices.rules
    -r--r--r-- 1 root root 492 Nov 1 2009 95-dm-notify.rules
    -rw-r--r-- 1 root root 3.0K Oct 19 23:43 95-keyboard-force-release.rules
    -rw-r--r-- 1 root root 11K Oct 19 23:43 95-keymap.rules
    -rw-r--r-- 1 root root 155 Oct 19 23:43 95-udev-late.rules
    -rw-r--r-- 1 root root 2.8K Oct 3 13:17 95-upower-battery-recall-dell.rules
    -rw-r--r-- 1 root root 1.2K Oct 3 13:17 95-upower-battery-recall-fujitsu.rules
    -rw-r--r-- 1 root root 1020 Oct 3 13:17 95-upower-battery-recall-gateway.rules
    -rw-r--r-- 1 root root 1.6K Oct 3 13:17 95-upower-battery-recall-ibm.rules
    -rw-r--r-- 1 root root 774 Oct 3 13:17 95-upower-battery-recall-lenovo.rules
    -rw-r--r-- 1 root root 1.1K Oct 3 13:17 95-upower-battery-recall-toshiba.rules
    -rw-r--r-- 1 root root 1.6K Oct 3 13:17 95-upower-csr.rules
    -rw-r--r-- 1 root root 6.0K Oct 3 13:17 95-upower-hid.rules
    -rw-r--r-- 1 root root 354 Oct 3 13:17 95-upower-wup.rules
    -rw-r--r-- 1 root root 1.4K Aug 1 12:20 97-bluetooth-hid2hci.rules
    -rw-r--r-- 1 root root 28 Oct 7 2010 99-fuse.rules
    Can anyone confirm this?  If I get confirmation that this is indeed present for other users (and a bug, not a "feature"), I'll open a bug report for the udev package.
    Also, semi-related, in the post-install message from the udev package they refer you to the folder /etc/udev.d/rules, however, that directory structure doesn't exist on my system, and the old /etc/udev/rules.d is still present.
    I'd appreciate any information or input.  If any further information is required, I'll gladly supply it.
    Last edited by lswest (2011-10-26 09:54:58)

    Since the upgrade to 174, thunar doesn't mount anymore external hdd or usb. I removed my user from storage group.
    Searching for solutions I find out that I have the same errors in the logs that lswest has.
    /var/log/messages.log:
    Oct 29 10:29:46 localhost udevd[75]: starting version 174
    while /var/log/errors.log:
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/42-qemu-usb.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/50-firmware.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/50-udev-default.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-cdrom_id.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-persistent-alsa.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-persistent-input.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-persistent-serial.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-persistent-storage-tape.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-persistent-storage.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/60-persistent-v4l.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/61-accelerometer.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/70-udev-acl.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/75-net-description.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/75-probe_mtd.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/75-tty-description.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/78-sound-card.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/80-drivers.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/81-arch.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/95-keyboard-force-release.rules': No such file or directory
    Oct 29 11:42:14 localhost udevd[75]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory
    Edit: a fresh installation of udev seems stopping error message flooding in errors.log, but I still can't automount drives and reboot/shutdown with dbus-send method.
    Last edited by oceans11 (2011-10-29 10:29:48)

  • [SOLVED] udev rules: cannot run command

    I want to run a scipt everytime I plug in my external harddrive. I read the documentation and create a file called /etc/udev/rules.d/extern_hd.rules:
    SUBSYSTEMS=="usb", SYSFS{serial}=="33504D315647585A", SYMLINK+="ExternHD", RUN+="/root/scripts/test.sh"
    The symlink "ExternHD" gets created. The permissions of test.sh are rwxr-xr-x root root, but it never gets executed. What am I doing wrong?
    Last edited by Kei (2007-09-18 11:30:35)

    Solution was easy... Udev doesn't want to start anything from within /root, so I put a hardlink to /usr/local/bin/ and now everything works fine.

  • Trying to disable a Udev rule. Deleting it is not working.

    I am trying to configure my sound. I have a usb sound card I want it to be default.
    I followed the procedure as described here .
    So, my default soundcard was my usb soundcard!
    But, did this,
    Hot-plugging a USB sound card
    The following udev rule can be used to automatically make a USB sound card the primary output device when the card is plugged in. To do so, create the following file with the specified contents and.
    /etc/udev/rules.d/00-local.rules
    KERNEL=="pcmC[D0-9cp]*", ACTION=="add", PROGRAM="/usr/bin/sh -c 'K=%k; K=$${K#pcmC}; K=$${K%%D*}; echo defaults.ctl.card $$K > /etc/asound.conf; echo defaults.pcm.card $$K >>/etc/asound.conf'"
    KERNEL=="pcmC[D0-9cp]*", ACTION=="remove", PROGRAM="/usr/bin/sh -c 'echo defaults.ctl.card 0 > /etc/asound.conf; echo defaults.pcm.card 0 >>/etc/asound.conf'"
    For information regarding loading udev rules see the following: Udev#Loading_new_rules
    But it was a mistake.. So, I wanted to correct this. I deleted this file.
    rm -rf /etc/udev/rules.d/00-local.rules
    after that, as mentioned here
    udevadm control --reload
    udevadm trigger
    After reboot, I was having again the file
    /etc/asound.conf
    which is created after the rule is triggered.
    So, what can i Do ?

    MoonSwan wrote:
    I may be mis-understanding your problem, zabrielza, so please correct me if I am off base here.
    You have 2 soundcards, yes?  One is a HDA Intel on-board and the other is your USB card.  You want the USB card to be the default all the time, correct?  If that is true then I suggest using this little part of the Alsa Wiki article to set your default card: https://wiki.archlinux.org/index.php/Ad … sound_card  I have used that part of the wiki successfully to set my default card, as I also have two sound cards, and I've had few issues since then. 
    As I said when I began this post, I may be wrong here so please say so if I am.  You might also want to start over and re-state exactly what your goal is because I see some posters are confused about what it is you're trying to accomplish.
    Yes you are right. You described my situation perfectly.  Firstly I started this topic to learn/know How should i disable correctly udev rules. It turns out that my udev rule is disabled. I have this file
    /etc/modprobe.d/alsa-base.conf
    configured correctly. Before I create the rule I had sound correctly but I never followed this.
    Select the default PCM via environment variable
    In your configuration file, preferably global, add:
    pcm.!default {
        type plug
        slave.pcm {
            @func getenv
            vars [ ALSAPCM ]
            default "hw:Audigy2"
    You need to replace the default line with the name of your card (in the example is Audigy2). You can get the names with aplay -l or you can also use PCMs like surround51. But if you need to use the microphone it is a good idea to select full-duplex PCM as default.
    Now you can start programs selecting the sound card just changing the environment variable ALSAPCM. It works fine for all program that do not allow to select the card, for the others ensure you keep the default card. For example, assuming you wrote a downmix PCM called mix51to20 you can use it with mplayer using the commandline ALSAPCM=mix51to20 mplayer example_6_channel.wav
    Instead of using new variables, you could set one of those mentioned in default global configuration.
    /usr/share/alsa/alsa.conf
    Variable name # Definition
    ALSA_CARD # pcm.default pcm.hw pcm.plughw ctl.sysdefault ctl.hw rawmidi.default rawmidi.hw hwdep.hw
    ALSA_CTL_CARD # ctl.sysdefault ctl.hw
    ALSA_HWDEP_CARD # hwdep.default hwdep.hw
    ALSA_HWDEP_DEVICE # hwdep.default hwdep.hw
    ALSA_PCM_CARD # pcm.default pcm.hw pcm.plughw
    ALSA_PCM_DEVICE # pcm.hw pcm.plughw
    ALSA_RAWMIDI_CARD # rawmidi.default rawmidi.hw
    ALSA_RAWMIDI_DEVICE # rawmidi.default rawmidi.hw
    Note: Pay attention to default addressing type.
    So, Should I try it now? Do I have to reset alsa-installation first ( I do not know how to do this ) or not?

  • UDEV rules for Xilinx FPGA devices

    I recently purchased a Digilent Nexys3 FPGA board with a Xilinx Spartan 5 FPGA on it. I finally got around to finding some time to using it, and setting up the development environment under Arch linux.
    After spending ages reading around about various problems and workarounds, I finally managed to get Xilinx ISE Webpack installed and working, as well as Digilent Adept software for downloading the designs to the development board. One issue still remains though. I am unable to download the designs to the FPGA as a normal user, but only as root.
    I'm pretty sure this is a udev rules problem. Digilent supplies a rules file (attached below) which is supposed to grant permissions to all users to access the FPGA devices over USB. I placed this rule file under /etc/udev/rules.d, but I am still unable to access the devices as normal user due to the following error:
    $ djtgcfg enum
    libusb couldn't open USB device /dev/bus/usb/001/003: Permission Denied.
    libusb requires write access to USB device nodes.
    $
    I believe that udev rules syntax changed since the last time I had a look at it, so maybe the supplied rules file still uses the old syntax? Any suggestions to fixing this rules file (attached below)?
    # 52-digilent-usb.rules -- UDEV rules for Digilent USB Devices #
    # Author: MTA #
    # Copyright 2010 Digilent Inc. #
    # File Description: #
    # This file contains the rules used by UDEV when creating entries for #
    # Digilent USB devices. In order for Digilent's shared libraries and #
    # applications to access these devices without root privalages it is #
    # necessary for UDEV to create entries for which all users have read #
    # and write permission. #
    # Usage: #
    # Copy this file to "/etc/udev/rules.d/" and execute #
    # "/sbin/udevcontrol reload_rules" as root. This only needs to be done #
    # immediately after installation. Each time you reboot your system the #
    # rules are automatically loaded by UDEV. #
    # Revision History: #
    # 04/15/2010(MTA): created #
    # 02/28/2011(MTA): modified to support FTDI based devices #
    # Create "/dev" entries for Digilent device's with read and write
    # permission granted to all users.
    SYSFS{idVendor}=="1443", MODE="666"
    ACTION=="add", SYSFS{idVendor}=="0403", SYSFS{manufacturer}=="Digilent", MODE="666", RUN+="/usr/local/sbin/dftdrvdtch %s{busnum} %s{devnum}"
    # The following rules (if present) cause UDEV to ignore all UEVENTS for
    # which the subsystem is "usb_endpoint" and the action is "add" or
    # "remove". These rules are necessary to work around what appears to be a
    # bug in the Kernel used by Red Hat Enterprise Linux 5/CentOS 5. The Kernel
    # sends UEVENTS to remove and then add entries for the endpoints of a USB
    # device in "/dev" each time a process releases an interface. This occurs
    # each time a data transaction occurs. When an FPGA is configured or flash
    # device is written a large number of transactions take place. If the
    # following lines are commented out then UDEV will be overloaded for a long
    # period of time while it tries to process the massive number of UEVENTS it
    # receives from the kernel. Please note that this work around only applies
    # to systems running RHEL5 or CentOS 5 and as a result the rules will only
    # be present on those systems.
    Thanks!
    -Igor
    Last edited by UQ-igor (2011-12-24 03:56:10)

    Try this
    Use ATTR or ATTRS.
    -SYSFS{idVendor}=="1443", MODE="666"
    -ACTION=="add", SYSFS{idVendor}=="0403", SYSFS{manufacturer}=="Digilent", MODE="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"
    +ATTRS{idVendor}=="1443", MODE="666"
    +ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{manufacturer}=="Digilent", MODE="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"
    +ATTR{idVendor}=="1443", MODE="666"
    +ACTION=="add", ATTR{idVendor}=="0403", ATTR{manufacturer}=="Digilent", MODE="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"

  • Stranger udev.rules error

    I am trying to use my pda (Palm Tungsten E, but that should be irrelevant) under KDE.  Well, I do not get that far!
    According to the standard udev.rules the PDA should be seen as a tty device with the rule
    KERNEL=="ttyUSB[0-9]*", NAME="tts/USB%n"
    Later there is a rule specifically for Palm Pilots
    BUS=="usb", KERNEL=="ttyUSB[0-9]*", SYSFS{product}="Palm Handheld... ", SYMLINK+=pilot
    (Should not the later rule be disregarded since a valid rule has already been encountered?)
    However, I get nothing.  The messages.log tells
    usb 3-2: new full speed USB device using uhci_hcd and address 2
    usb 3-2: configuration #1 chosen from 1 choice
    That's all. No devices (not even /dev/tts/USB1), no module loaded, nothing (that I can detect).
    Connections etc are ok - in Slackware the PDA is connected at /dev/tts/USB1 (later rule disregarded!) and can be used as root. So no positive clue there.
    So, what is different in Arch? HAL? and most important, what should I do?

    Ok. Add usbserial and visor modules to the MODULES in /etc/rc.conf (as it seems they are not loaded automatically). Restart machine or run /etc/udevstart and replug your palm. Can you see /dev/tts/USBx now at least? (x might be different number each time you plug in your palm).
    Note that the second standard rule that should create /dev/pilot link will not work for you because SYSFS{product} is different than yours and will not match with the rule.
    Now create /etc/udev/rules.d/010.udev.rules file and put these rules inside (there are two lines only! watch out for forum line wraps):
    KERNEL=="ttyUSB[0-9]*", NAME:="tts/USB%n", GROUP:="users"
    BUS=="usb", KERNEL=="ttyUSB[0-9]*", SYSFS{idVendor}=="0830", SYSFS{idProduct}=="0060", SYMLINK:="pilot"
    Restart machine or start /etc/udevstart and replug your palm. It should create /dev/tts/USBx and /dev/pilot (which you should use in palm applications). The owner for /dev/tts/USBx should be root:users. If it needs special write permissions you can add
    , MODE:="0660"
    to the first rule in /etc/010.udev.rules file. You can of course change "users" to any group you like just remember to add your user to this group.
    BTW If you have too many modules loaded you can customize /etc/mkinitrd.conf - check wiki for details.

Maybe you are looking for

  • Is there a way to have the effect in a panel ???

    Using the effect in the property panel is very powerfull, but very annoying when you use more than 4 filters. So is there an extension to have the effects list ( or as you call "Live filters" area) out of the property panel ... in it's own panel ? Ca

  • Dynamic Link issues between Pr and Ae

    Hey Guys - We have had issues with our dynamic link since the last update to Premiere CC 45 days ago. Two different iMacs, one 2010 and the other late 2012 are both having these issues. Regardless of system, we weren't having the issue before the mos

  • Updated Adobe AIR and now Adobe reader crashes when trying to open PDFs created by Livescribe

    Adobe AIR auto-updated earlier this afternoon, and now every time I try to open a PDF created by Livescribe, Adobe Reader crashes. Adobe Reader XI ver. 11.0.0.379 Adobe AIR ver. 3.5.0.1060 Windows 7 Pro, SP1 I have tried uninstalling/reinstalling bot

  • Error conection to fpt      R3 - XI  - FILE FTP

    In message monitorin the following error is registered - Attempt to process file failed with java.net.SocketException: Connection reset - Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com

  • CS6 InDesign does not launch, gives a series of issue messages.

    I faced an issue to launch InDesign when opening an earlier file. Then as a fresh launch also it gives the same errors. It finally crashes, sometimes with a message that appears it could recover, by the time one can respond to it, it crashes! The seq