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.

Similar Messages

  • 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)

  • 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...

  • Udev rules and group / permission errors [solved] [outdated]

    Latest udev is a miracle to me. It ignores every group ore permission settings. Anyone else having same experiences?
    Last edited by Moo-Crumpus (2008-09-29 05:17:40)

    Let's assume that you have two files with udev rules. The basic udev.rules and 00.udev.rules (with custom rules).
    Udev first reads all rules from 00 file and then rules from the basic file.
    This means that if you have a custom rule for a given device you should copy all rules that apply to it from the basic file to the 00 file (not only lines with GROUP). This is because with OPTIONS="last_rule" udev will stop processing rules for this device.
    All rules are read and then applied in the order from the top to bottom except SUBSYTEM which is applied as the last rule (kind of held in a buffer). This is the reason why my cd burner /dev/hdc had permissions for disk group and not optical.
    This is my 00.udev.rules (it still needs some cosmetic changes but it works and of course I don't have all the devices):
    SUBSYSTEM="video4linux", GROUP="users"
    SUBSYSTEM="sound", GROUP="users"
    SUBSYSTEM="printer", GROUP="users"
    SUBSYSTEM="block", GROUP="disk"
    BUS="ide", KERNEL="hd[a-z]", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
    BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
    BUS="ide", KERNEL="hdc", SYSFS{removable}="1", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom*", NAME="%k", GROUP="users", SYMLINK="nagrywarka dvd cdrw", OPTIONS="last_rule"
    BUS="ide", KERNEL="hd[a-z]", SYSFS{removable}="1", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom*", NAME="%k", GROUP="users", OPTIONS="last_rule"
    BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-floppy.sh %k", RESULT="floppy", NAME{all_partitions}="%k", GROUP="users", OPTIONS="last_rule"
    BUS="scsi", KERNEL="sr[0-9]*", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
    BUS="scsi", KERNEL="scd[0-9]*", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
    BUS="scsi", KERNEL="sr[0-9]*", SYSFS{type}="5", NAME="scd%n", GROUP="users", OPTIONS="last_rule"
    BUS="scsi", KERNEL="sg[0-9]*", SYSFS{type}="5", NAME="%k", GROUP="users", OPTIONS="last_rule"
    KERNEL="fd[0-9]*", NAME="fd%n", GROUP="users", SYMLINK="floppy/%n fd%nu1440 fd%nu720 fd%nh1200 fd%nu360", OPTIONS="last_rule"
    BUS="usb", SYSFS{serial}="CN16J1Q3HWSX", KERNEL="lp[0-9]*", NAME="usb/%k", GROUP="users", SYMLINK="drukarka_hp_845c drukarka", OPTIONS="last_rule"
    BUS="usb", KERNEL="sd*", PROGRAM="/etc/udev/usb-storage.sh %k", RESULT="1", NAME="%k", GROUP="users", OPTIONS="last_rule"
    KERNEL="rtc", NAME="misc/%k", SYMLINK="%k", GROUP="users", MODE="0664", OPTIONS="last_rule"
    KERNEL="agpgart", NAME="misc/%k", SYMLINK="%k" GROUP="users", OPTIONS="last_rule"
    KERNEL="nvidia*", GROUP="users", OPTIONS="last_rule"
    KERNEL="fb[0-9]*", NAME="fb/%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="card[0-9]*", NAME="dri/%k", GROUP="users", OPTIONS="last_rule"
    KERNEL="3dfx*", NAME="%k", GROUP="users", OPTIONS="last_rule"
    KERNEL="dvb*", PROGRAM="/etc/udev/dvb.sh %k", NAME="%c", GROUP="users", OPTIONS="last_rule"
    KERNEL="video[0-9]*", NAME="v4l/video%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="radio[0-9]*", NAME="v4l/radio%n", GROUP="users", SYMLINK="radio%e", OPTIONS="last_rule"
    KERNEL="vbi[0-9]*", NAME="v4l/vbi%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="vtx[0-9]*", NAME="v4l/vtx%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="controlC[0-9]*", NAME="snd/%k", OPTIONS="last_rule"
    KERNEL="hw[CD0-9]*", NAME="snd/%k", OPTIONS="last_rule"
    KERNEL="pcm[CD0-9cp]*", NAME="snd/%k", OPTIONS="last_rule"
    KERNEL="midi[CD0-9]*", NAME="snd/%k", OPTIONS="last_rule"
    KERNEL="timer", NAME="snd/%k", OPTIONS="last_rule"
    KERNEL="seq", NAME="snd/%k", OPTIONS="last_rule"
    KERNEL="audio*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="dmmidi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="admmidi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="dsp*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="adsp*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="midi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="amidi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="sequencer*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
    KERNEL="pktcdvd", NAME="pktcdvd/control", GROUP="users", MODE="0660", OPTIONS="last_rule"
    KERNEL="pktcdvd[0-9]*", NAME="pktcdvd/pktcdvd%n", GROUP="users", MODE="0660", OPTIONS="last_rule"
    The problem with /dev/hdc was that first udev (version 057) was reading a rule from my 00 file (BUS="ide", KERNEL="hdc"...) with GROUP=users. Then it was reading SUBSYSTEM="block", GROUP="disk" rule from the basic file (but it wasn't executed at that time). And then it was reading BUS="ide", KERNEL="hd[a-z]", SYSFS{removable}="1"... with GROUP=optical. Then it was executing SUBSYTEM rule (hdc is a block device). That's why only disk group had an access to /dev/hdc (with OPTIONS="last_rule" in the basic file in the GROUP="optical" line it would ignore SUBSYSTEM rule).
    There are also other rules that you should add (IMO) to your custom rules if  you are changing something. In my case it's for example BUS="ide", KERNEL="hd[a-z]", PROGRAM="/etc/udev/cdsymlinks.sh %k"... which creates symlinks for cd drives. This rule must be above other rules (the number of the symlinks is now unlimited - previously it was 5 IIRC).
    So now the rules are mixed together in the lexical order (except SUBSYTEM rules which are executed at the end) unless OPTIONS="last_rule" is used or second (and other) rule has a NAME filed (only one rule for a given device can have NAME filed. Every other rule for the same device with NAME field is ignored IIRC). It also means you can now split rules for a device into several rules - only one of them can have NAME filed and the last should have OPTIONS="last_rule".
    Since in your case you have custom rules only for a well defined usb devices (not /dev/sd*) IMO it should work as you think (only add OPTIONS="last_rule").
    I hope it's now perfectly clear  8) 

  • Udev rules for a modem

    The following udev rule was given to me last February to get a friends dial-up working:
    KERNEL=="ttyS[0-9]", NAME=="%k", MODE=="0660", GROUP=="tty", SYMLINK+="modem"
    I have just updated the system and I am aware that the udev rules have changed. It is not an area that I usually venture into. What is now needed to achieve a suitable device creation at boot-up to have the modem recognised?
    Thanks.

    Thanks byte. This got rid of the messages but didn't solve the connection problem    I have now reverted back to the orginal options file as this does match the old one. This is really strange. I created a separate partition and rsynced the original Arch install across and updated grub. I then updated one installation and left the other alone just in case I ran into problems. As it happened the upgrade went fine and both old and new installations run fine except the dial-up on neither works    I am now beginning to think it might be a problem with the ISP (uklinux.net), but their website does not suggest any status issues.
    I went back through the errors.log on the old installation and found that the:
    Dec 28 18:27:51 hollowood pppd[3498]: Cannot determine ethernet address for proxy ARP
    always occurs and does not stop the connection. I have checked the /etc/rc.conf as I had to make some changes in connecting and disconnecting to my network and have got rid of the other messages that way.  There are no other error messages and wvdial runs through the connection and disconnection process perfectly. Is there anything else I could have overlooked or could this be problems with the ISP?

  • [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)

  • 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.

  • Writing udev rules [SOLVED]

    Hi guys.
    I'm on a mission to run win7 on QEMU, and I also want to be able to use my USB-ports. Now, archwiki tells me to do this:
    $ qemu-system-i386 -usbdevice host:vendor_id:product_id disk_image
    You can find vendor_id and product_id of your device with lsusb command.
    Note: If you encounter permission errors when running QEMU, see Udev#Writing udev rules for information on how to set permissions of the device.
    I then made a file called 10-adm.rules both in, /etc/udev/rules.d and /usr/lib/udev/rules.d
    In it I wrote:
    KERNEL=="sdc[0-9]*",  GROUP="storage"
    My user with wich i lauch QEMU is in the group storage, and my usb always turns out as sdc*.
    But it still gives me the permission erros.
    Last edited by kimbo (2014-11-28 14:06:24)

    now I renamed the files to 99 instead of 10, and I even overkilled it with the GROUP:= instead of GROUP=
    tried:
    udevadm control --reload-rules
    udevadm trigger
    But it still doesnt work
    lsusb gives me:
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 004: ID 18a5:0302 Verbatim, Ltd Flash Drive
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 002: ID 04f2:b23b Chicony Electronics Co., Ltd
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 002: ID 04ca:3002 Lite-On Technology Corp.
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    And my qemu-launch-commad it:
    qemu-system-x86_64 -m 1G -enable-kvm -cpu host -usbdevice host:18a5:0302 win7
    oh, I dont really undestand what you by ' the group that /dev/sdc* ends up having'
    Last edited by kimbo (2014-11-13 23:04:47)

  • 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}"

  • [SOLVED] automatic usb-backup with udev-rules + script

    I would like to have my usb-harddrive automatically start a backup as soon as it is plugged in.  And finally a bell is supposed to ring.
    I've created an udev-rule and a backup-script as shown below.
    However, instead of creating /dev/backup-drive first something strange is happening:
    The bell rings 3 times, followed by the backup, followed by a 4th ring.
    What's going on?
    Here's may udev-rule:
    ## /etc/udev/rules.d/95-backup.rules
    SUBSYSTEMS=="usb", ATTRS {serial}=="100", SYMLINK=="backup-drive", RUN+="/usr/local/bin/backup-thumb.sh"
    fstab:
    /dev/backup-drive    /media/backup   ext3     rw,user    0 0
    and my script:
    #!/bin/bash
    sleep 10
    rsync -vrtolgh --exclude '/.VirtualBox/' --delete /home/myhome /media/backup-drive
    aplay /usr/share/sounds/phone.wav
    Last edited by mehldutt (2007-07-03 20:28:27)

    The syntax of your udev rule is all wrong - for example after SYMLINK you should use "+=" or ":=". "==" is for comparing to some value.
    I think in rsync command line you want -H not -h (help) option. Also -v (verbose) is useless since you'll never see the output.
    Another thing which will prevent running rsync properly is /media/backup-drive while you use /media/backup in fstab.
    I suggest that you first try running rsync command from the command line "manually" and try if it works at all. After you'll make it work try the below suggestions.
    Another problem: what makes the backup drive mounted under /media/backup directory when you plug it into usb slot ? Are you doing it somehow "manually" in the 10 second period after plugging ? Do you use automounter of some kind ?
    If you intend to use ext3 as the backup drive filesystem you should also add sync command after rsync to make sure no data stays in RAM cache.
    I think you need to read udev manpage first.
    I can also advice you to read my udev rules for automounting usb devices (it's for any type of filesystem and any number of partitions):
    KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/ln -s /media/usbhd-%k /mnt/usbhd-%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", PROGRAM=="/lib/udev/vol_id -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/
    usbhd-%k", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rm -f /mnt/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    I think it could be simplified and modified for your backup device like this:
    SUBSYSTEMS=="usb", ATTRS(idVendor)=="XXXX", ATTRS(idProduct)=="YYYY", KERNEL=="sd[a-z]", NAME:="%k", SYMLINK:="backupdevice", OPTIONS="last_rule"
    SUBSYSTEMS=="usb", ATTRS(idVendor)=="XXXX", ATTRS(idProduct)=="YYYY", ACTION=="add", KERNEL=="sd[a-z]1", SYMLINK:="backuppartition", GROUP:="users", NAME:="%k"
    SUBSYSTEMS=="usb", ATTRS(idVendor)=="XXXX", ATTRS(idProduct)=="YYYY", ACTION=="add", KERNEL=="sd[a-z]1", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/backup-drive"
    SUBSYSTEMS=="usb", ATTRS(idVendor)=="XXXX", ATTRS(idProduct)=="YYYY", ACTION=="add", KERNEL=="sd[a-z]1", RUN+="/usr/local/bin/backup-thumb.sh", OPTIONS="last_rule"
    SUBSYSTEMS=="usb", ATTRS(idVendor)=="XXXX", ATTRS(idProduct)=="YYYY", ACTION=="remove", KERNEL=="sd[a-z]1", RUN+="/bin/umount -l /media/backup-drive", OPTIONS="last_rule"
    assuming that you have a single partition backup drive formatted as ext3 (or at least it's the first partition).
    Also another assumption is that idVendor and idProduct are unique to your backup drive. If not you should add some extra ATTRS parameters that will ensure this combination is unique.
    The directory /media/backup-drive must already exist (remove your fstab line - it's not needed in this case because mount command is run directly from the udev rule).
    Replace all XXXX and YYYY with the values from lsusb for your backup device - plug it in, run lsusb and copy values which look like XXXX:YYYY near to the name of your backup device.
    Anyway, you can play with different options and try to modify it yourself. The automounting rules work for me very well for some time (including flush option). The backup rules you need to test yourself :-)
    Last edited by lanrat (2007-05-05 17:20:51)

  • [Solved] udev rules: serial for persistent device naming disappeared

    Hello,
    since the latest upgrade of udev and kmod I cant't mount my external e-SATA hard disk with my working udev rules.
    This is my udev rule:
    $ cat /etc/udev/rules.d/66-persistent_esata.rules
    KERNEL=="sd?1", SUBSYSTEMS=="block", ENV{ID_SERIAL_SHORT}=="S1VSJ1LS301247", NAME="aluguard"
    When plugged in, I could decrypt and mount it with "sudo cryptsetup luksOpen /dev/aluguard aluguard && mount /mnt/aluguard".
    Since the update above I get "Device /dev/aluguard doesn't exist or access denied."
    While I re-checked https://wiki.archlinux.org/index.php/Ma … _with_udev, I discovered, that the serial entry in the output of udevadm has vanished:
    $ udevadm info -a -p $(udevadm info -q path -n /dev/sdg)
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    looking at device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg':
    KERNEL=="sdg"
    SUBSYSTEM=="block"
    DRIVER==""
    ATTR{range}=="16"
    ATTR{ext_range}=="256"
    ATTR{removable}=="0"
    ATTR{ro}=="0"
    ATTR{size}=="1953525168"
    ATTR{alignment_offset}=="0"
    ATTR{discard_alignment}=="0"
    ATTR{capability}=="50"
    ATTR{stat}==" 96 24 762 780 0 0 0 0 0 780 780"
    ATTR{inflight}==" 0 0"
    ATTR{events}==""
    ATTR{events_async}==""
    ATTR{events_poll_msecs}=="-1"
    looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0':
    KERNELS=="3:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
    ATTRS{type}=="0"
    ATTRS{scsi_level}=="6"
    ATTRS{vendor}=="ATA "
    ATTRS{model}=="SAMSUNG HD103SI "
    ATTRS{rev}=="1AG0"
    ATTRS{state}=="running"
    ATTRS{timeout}=="30"
    ATTRS{iocounterbits}=="32"
    ATTRS{iorequest_cnt}=="0xa2"
    ATTRS{iodone_cnt}=="0x98"
    ATTRS{ioerr_cnt}=="0xc"
    ATTRS{evt_media_change}=="0"
    ATTRS{queue_depth}=="31"
    ATTRS{queue_ramp_up_period}=="120000"
    ATTRS{queue_type}=="simple"
    looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0':
    KERNELS=="target3:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    looking at parent device '/devices/pci0000:00/0000:00:09.0/host3':
    KERNELS=="host3"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    looking at parent device '/devices/pci0000:00/0000:00:09.0':
    KERNELS=="0000:00:09.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ahci"
    ATTRS{vendor}=="0x10de"
    ATTRS{device}=="0x0554"
    ATTRS{subsystem_vendor}=="0x1849"
    ATTRS{subsystem_device}=="0x0554"
    ATTRS{class}=="0x010601"
    ATTRS{irq}=="23"
    ATTRS{local_cpus}=="00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{numa_node}=="0"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""
    looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""
    What is the reason for this strange behaviour, and how can I get back the serial entry?
    Thank in advance!
    Last edited by indianahorst (2012-01-31 13:03:20)

    $ udevadm info -q all -n /dev/sdg1
    P: /devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
    N: sdg1
    S: disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1
    S: disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1
    S: disk/by-id/wwn-0x50024e900136a03e-part1
    S: disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1
    S: disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: DEVLINKS=/dev/disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1 /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1 /dev/disk/by-id/wwn-0x50024e900136a03e-part1 /dev/disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1 /dev/disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: DEVNAME=/dev/sdg1
    E: DEVPATH=/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
    E: DEVTYPE=partition
    E: ID_ATA=1
    E: ID_ATA_DOWNLOAD_MICROCODE=1
    E: ID_ATA_FEATURE_SET_AAM=1
    E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254
    E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
    E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
    E: ID_ATA_FEATURE_SET_APM=1
    E: ID_ATA_FEATURE_SET_APM_ENABLED=0
    E: ID_ATA_FEATURE_SET_HPA=1
    E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
    E: ID_ATA_FEATURE_SET_PM=1
    E: ID_ATA_FEATURE_SET_PM_ENABLED=1
    E: ID_ATA_FEATURE_SET_PUIS=1
    E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
    E: ID_ATA_FEATURE_SET_SECURITY=1
    E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
    E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=194
    E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=194
    E: ID_ATA_FEATURE_SET_SMART=1
    E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
    E: ID_ATA_SATA=1
    E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
    E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
    E: ID_ATA_WRITE_CACHE=1
    E: ID_ATA_WRITE_CACHE_ENABLED=1
    E: ID_BUS=ata
    E: ID_FS_TYPE=crypto_LUKS
    E: ID_FS_USAGE=crypto
    E: ID_FS_UUID=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: ID_FS_UUID_ENC=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
    E: ID_FS_VERSION=1
    E: ID_MODEL=SAMSUNG_HD103SI
    E: ID_MODEL_ENC=SAMSUNG\x20HD103SI\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
    E: ID_PART_ENTRY_TYPE=0x83
    E: ID_PART_TABLE_TYPE=dos
    E: ID_PATH=pci-0000:00:09.0-scsi-3:0:0:0
    E: ID_PATH_TAG=pci-0000_00_09_0-scsi-3_0_0_0
    E: ID_REVISION=1AG01131
    E: ID_SCSI_COMPAT=SATA_SAMSUNG_HD103SIS1VSJ1LS301247
    E: ID_SERIAL=SAMSUNG_HD103SI_S1VSJ1LS301247
    E: ID_SERIAL_SHORT=S1VSJ1LS301247
    E: ID_TYPE=disk
    E: ID_WWN=0x50024e900136a03e
    E: ID_WWN_WITH_EXTENSION=0x50024e900136a03e
    E: MAJOR=8
    E: MINOR=97
    E: PART_ENTRY_DISK=8:96
    E: PART_ENTRY_NUMBER=1
    E: PART_ENTRY_OFFSET=63
    E: PART_ENTRY_SCHEME=dos
    E: PART_ENTRY_SIZE=1953520002
    E: SUBSYSTEM=block
    E: UDEV_LOG=3
    E: UDISKS_PARTITION=1
    E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
    E: UDISKS_PARTITION_NUMBER=1
    E: UDISKS_PARTITION_OFFSET=32256
    E: UDISKS_PARTITION_SCHEME=mbr
    E: UDISKS_PARTITION_SIZE=1000202241024
    E: UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg
    E: UDISKS_PARTITION_TYPE=0x83
    E: UDISKS_PRESENTATION_NOPOLICY=0
    E: USEC_INITIALIZED=6897248001
    OK, there is the serial.... but the problem persists - udev doesn't execute the rule and doesn't create /dev/aluguard.

  • Problem with udev rule to disable touchpad when USB mouse connects

    Hi, I've been running Arch on this laptop, but I can't get this udev rule to work properly.
    What I want to happen is: when I plug in my usb mouse, the laptop touchpad is disabled, and the left and right buttons are reversed (I'm left handed)
    After following several tutorials, both from the arch wiki and other sites, I've come up with this udev rule:
    ACTION=="add", SUBSYSTEM=="input", RUN+="/usr/local/bin/USBMouse.sh"
    ACTION=="remove", SUBSYSTEM=="input", RUN+="/usr/local/bin/USBMouse.sh"
    And here's the script it links to (USBMouse.sh):
    #!/bin/bash
    export DISPLAY=:0.0
    synclient TouchPadOff=$(/usr/bin/lsusb | grep "Microsoft Corp.\
    Nano Transceiver v1.0 for Bluetooth" | wc -l)
    if [[ $(/usr/bin/lsusb | grep "Microsoft Corp.\
    Nano Transceiver v1.0 for Bluetooth" | wc -l) == 1 ]]
    then
    xmodmap -e 'pointer = 3 2 1'
    fi
    if [[ $(/usr/bin/lsusb | grep "Microsoft Corp.\
    Nano Transceiver v1.0 for Bluetooth" | wc -l) == 0 ]]
    then
    xmodmap -e 'pointer = 1 2 3'
    fi
    Running the script from a terminal returns no errors and works as expected. The problem is when I plug/unplug the mouse from the usb port, nothing happens.
    I appreciate any insight you might have about how to fix this, and thank you in advance

    This has already been done. And another relevant thread.

  • Udev rule breaking my machine

    My machine boots as far as the "Loading UDev uevents" point then stops and I see the following error:
    iTCO_wdt: Unexpected close, not stopping watchdog!
    At this point I have about 10 seconds before my machine does a hard reboot.  From what I can tell udev is getting hung on a rule I have under /etc/udev/rules.d/00-myrules.rules.  The rule is:
    IMPORT{program}="vol_id --export $tempnode"
    When I comment out this line my machine boots fine.  Digging into rc.sysinit, the exact command that is triggering this hang is /sbin/udevadm trigger.
    The full listing of said rule file is:
    IMPORT{program}="vol_id --export $tempnode"
    ENV{ID_FS_UUID}!="aa068b0a-456f-4a76-9ab7-d076d540b5a7", GOTO="not_data2"
    ACTION=="add", RUN+="/bin/start-stop-daemon --start --background --pidfile=/var/run/daemons/cryptsetup --startas /usr/sbin/cryptsetup -S -- -d /etc/data2.key luksOpen /dev/%k data2"
    ACTION=="remove", RUN+="/usr/sbin/cryptsetup luksClose data2"
    LABEL="not_data2"
    My machine is a Dell Latitude D830 running Arch 64.  Kernel 2.6.27.7-1 and udev 130-1.
    Last edited by zosodk69 (2008-12-04 14:15:30)

    [dave@hendrix ~]$> yaourt -Ss start-stop-daemon
    aur/start-stop-daemon 1.13.25-1 [installed]
    A Debian program for starting daemons from initscripts
    The rule works fine for me if I uncomment the IMPORT line and run:
    sudo udevadm control --reload-rules

  • Matching udev rules

    sda4 is the partition luks encrypted as home (/dev/home/mapper  |  /dev/dm-1)
    it's opened at boot using /etc/crypttab
    ID_FS_LABEL=home in /dev/dm-1
    udevadm info /dev/dm-1 --query=all  doesn't tell the parent (physical partition sda4). how can I output it so I can use it in udev rule?
    or is there any way to match dm-1 with sda4 without hardcoding paths?
    I want to write a rule for sda4 but as a condition that it is the parent partition for dm-1 (without hardcoding sda4 and dm-1)
    thank you.

    Sure, a loop that waits up to a certain number of seconds for you to mount the device is far more preferrable. Something like...
    #!/bin/bash
    # max time to wait
    timeout=60
    # label of device to wait for
    devlabel=blackhole
    # where to look for it
    devmount=/mnt/backup
    dev_mounted() {
    mountpoint -q "$devmount" &&
    [[ $(findmnt -runo LABEL "$devmount") = "$devlabel" ]]
    if ! dev_mounted; then
    printf "==> Waiting %s seconds for %s to be mounted on %s" "$devlabel" "$devmount"
    until dev_mounted; do
    sleep 1
    if (( --timeout == 0 )); then
    print "==> ERROR: device didn't show up after %s seconds!\n" "$timeout"
    exit 1
    fi
    done
    fi
    # do backup stuff here...

  • [SOLVED]system fails to boot since adding udev rules for automounting

    Hello
    I have recently been trying to use udev rules to automount, and putting together stuff from the wiki, forums and general googling around have produced the following set of rules:
    # automounts usb hdd and pendrives as usbhd-sdx; no messing around with
    # volume labels or other confusing stuff
    # matches all sdx devices except the internal hdd, sda
    KERNEL=="sd[b-z]", NAME="%k", SYMLINK+="usbhd-%k", GROUP="users", OPTIONS="last_rule"
    # imports filesystem information
    ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
    # creates mount points and sets up symlinks
    ACTION=="add", KERNEL=="sd[b-z][0-9]", SYMLINK+="usbhd-%k", GROUP="users", NAME="%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/ln -s /media/usbhd-%k /mnt/usbhd-%k"
    # global mount options
    ACTION=="add", ENV{mount_options}="relatime"
    # filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
    ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
    # automount ntfs filesystem with ntfs-3g driver
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_r$
    # automount all other file systems
    ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    # unmounts and removes the mount points
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rm -f /mnt/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    This seemed to be working very well unitl I tried to boot this morning and the boot process stopped at "processing UDev events" with the following message:
    iTCO_wdt: Unexpected close, not stopping watchdog!
    It pauses at this point for 10-15 seconds and then reboots.
    Having searched a bit, I found the following similar post on the forums:  http://bbs.archlinux.org/viewtopic.php?pid=459375
    Which suggests that the problem might lie with this line:
    ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
    I have renamed the file so that it no longer has the udev .rules extension and now the system boots fine.  Does anyone have any suggestions as to why the above rules might be causing this behaviour and how I might go about fixing it?
    Thanks
    Last edited by useradded (2010-07-02 22:58:14)

    Hey falconindy
    That was the final kick up the logical a$$ that I needed to get some kind of grip on udev rules.  I now have a fully functional rule that applies only to /dev/sdxy and not to everything else as well, so no more boot trauma, THANK YOU.
    I will mark this thread as solved and post my new rule for the benefit of anyone who might read this.
    New rule (no boot problems):
    # automounts usb hdd and pendrives as label or as usbhd-sdxy if no label present
    # ensures the following is _only_ run for sdxy devices excluding internal hdd, sda
    KERNEL!="sd[b-z][0-9]", GOTO="personal_usb_automount_settings_end"
    # imports filesystem information
    # provides access to following variables:
    # ID_FS_UUID; ID_FS_UUID_ENC; ID_FS_VERSION; ID_FS_TYPE; ID_FS_VERSION; ID_FS_LABEL
    # accessible via ENV{variable}; $env{variable}|%E{variable}
    IMPORT{program}="/sbin/blkid -o udev -p %N"
    # Get a label if present, otherwise name usbhd-%k
    ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
    ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
    # creates mount points and sets up symlinks
    ACTION=="add", SYMLINK+="%E{dir_name}", GROUP="users", NAME="%k"
    ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}"
    ACTION=="add", RUN+="/bin/ln -s /media/%E{dir_name} /mnt/%E{dir_name}"
    # global mount options
    ACTION=="add", ENV{mount_options}="relatime"
    # filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
    ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
    # automount ntfs filesystem with ntfs-3g driver
    ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
    # automount all other file systems
    ACTION=="add",ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
    # unmounts and removes the mount points
    ACTION=="remove", RUN+="/bin/rm -f /mnt/%E{dir_name}"
    ACTION=="remove", RUN+="/bin/umount -l /media/%E{dir_name}"
    ACTION=="remove", RUN+="/bin/rmdir /media/%E{dir_name}", OPTIONS="last_rule"
    # exit
    LABEL=="personal_usb_automount_settings_end"
    Last edited by useradded (2010-07-02 22:59:20)

Maybe you are looking for

  • 3D Rotating on it's own center axis problem...

    Need some help here. This is my first time using 3D in flash. I have a movieclip (picture 80 x 80 pix) that I am tweening to look like it is rotating like face of a cube. What I did: 1. I transformed the z-axis to "raise" the picture off of the y axi

  • How do I export from QT into "motion jpeg" / mjpeg?

    Hello, my digitale frame does only accept "motion jpeg" as a video format. How do I export from QT? I read in various notes in the Web, that QT does support MJPEG-A and MJPEG-B Please advise

  • BIll of Material (BOM)

    Hi All, I would like to know how BOM(IDNRK - Material No.) available in (STPO table) is linked with Operation/Activity Number(VORNR) and Group Counter(PLNAL). Transaction Code IA07 Thanks, Pratibha

  • Forms 10.1.2 release date

    Hi, Grant can you tell when the relase will be out and what news features are included. ThankS Jean-Yves

  • Error on selecting object in ILLUSTRATOR CC

    Hi everyone, i have problem with selecting object in illustrator CC, when i select the current object it will also select the other object, i cannot select the object i want, not on the group or clipping mask.. always highlight it both. it often time