Udev rules not applied during bootup

I don't know if this problem is associated with the lates kernel-upgrade to 2.6.21 but I didn't have it before.
My problem:
I have an external USB-harddrive that gets mounted everytime I boot because it is listed in my fstab. To avoid confusion with other external storages (such as USB-sticks etc.) I worte an udev rule for it:
# Externe USB-Festplatte von TrekStor
BUS=="usb", KERNEL=="sd?1" SYSFS{serial}=="307541703010",SYMLINK+="externe"
As I've said this worked well before but now I get a message during the booting process saying that /dev/externe couldn't be found. But it actually IS recognised by udev. I just have to do a
mount -a
after the booting process and everything works again.
Does anyone have an idea what the problem could be? It seems to me that all the devices listed in fstab get mounted before the udev rules are applied.

Ok, I solved my problem: I'm not mounting my USB-HD through fstab anymore. I'm using udev-rules as described here.
Still I'd be interesting to know what went wrong.
Last edited by mata_svada (2007-05-21 05:11:06)

Similar Messages

[Solved] udev rule not working

Hi!
I'm trying to set my trackpoint sensitivity and speed using an udev rule:
[jeroen@zechs ~]$ ls -l /etc/udev/rules.d/
total 4
-rw-r--r-- 1 root root 113 Sep 14 01:54 10-trackpoint.rules
[jeroen@zechs ~]$ cat /etc/udev/rules.d/10-trackpoint.rules
# Set trackpoint option
KERNEL=="serio2", ATTR{speed}="180", ATTR{sensitivity}="255", RUN+="touch /tmp/udevtest"
When I test the rule, everything seems to be working as planned:
[jeroen@zechs ~]$ cat /sys/devices/platform/i8042/serio1/serio2/speed
97
[jeroen@zechs ~]$ cat /sys/devices/platform/i8042/serio1/serio2/sensitivity
128
[jeroen@zechs ~]$ sudo udevadm test /sys/devices/platform/i8042/serio1/serio2/
calling: test
version 216
timestamp of '/etc/udev/rules.d' changed
Reading rules file: /etc/udev/rules.d/10-trackpoint.rules
ATTR '/sys/devices/platform/i8042/serio1/serio2/speed' writing '180' /etc/udev/rules.d/10-trackpoint.rules:2
ATTR '/sys/devices/platform/i8042/serio1/serio2/sensitivity' writing '255' /etc/udev/rules.d/10-trackpoint.rules:2
RUN 'touch /tmp/udevtest' /etc/udev/rules.d/10-trackpoint.rules:2
ACTION=add
DEVPATH=/devices/platform/i8042/serio1/serio2
DRIVER=psmouse
MODALIAS=serio:ty05pr00id00ex00
SERIO_EXTRA=00
SERIO_ID=00
SERIO_PROTO=00
SERIO_TYPE=05
SUBSYSTEM=serio
USEC_INITIALIZED=284056746
run: 'touch /tmp/udevtest'
run: 'kmod load serio:ty05pr00id00ex00'
unload module index
Unloaded link configuration context.
[jeroen@zechs ~]$ cat /sys/devices/platform/i8042/serio1/serio2/sensitivity
255
[jeroen@zechs ~]$ cat /sys/devices/platform/i8042/serio1/serio2/speed
180
But when I boot the system, the rule has not been applied
[BOOT]
[jeroen@zechs ~]$ cat /sys/devices/platform/i8042/serio1/serio2/speed
97
[jeroen@zechs ~]$ cat /sys/devices/platform/i8042/serio1/serio2/sensitivity
128
[jeroen@zechs ~]$ sudo udevadm trigger
[jeroen@zechs ~]$ ls -l /tmp/udevtest
ls: cannot access /tmp/udevtest: No such file or directory
So the rule runs fine when I do `udevadm test` but fails to run on boot or `udevadm trigger`
Any hints or ideas, or probably some basic stuff I missed, to get this working?
Thank you for reading this far!
Last edited by jeroentbt (2014-10-07 11:42:58)

There is not much to go with.
I'll try adding the 'description' attribute maybe.
$ udevadm info -a -p /sys/devices/platform/i8042/serio1/serio2
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/platform/i8042/serio1/serio2':
KERNEL=="serio2"
SUBSYSTEM=="serio"
DRIVER=="psmouse"
ATTR{resolution}=="200"
ATTR{rate}=="100"
ATTR{bind_mode}=="auto"
ATTR{resync_time}=="0"
ATTR{jenks}=="135"
ATTR{reach}=="10"
ATTR{speed}=="180"
ATTR{ztime}=="38"
ATTR{draghys}=="255"
ATTR{description}=="Synaptics pass-through"
ATTR{mindrag}=="20"
ATTR{ext_dev}=="1"
ATTR{skipback}=="0"
ATTR{upthresh}=="255"
ATTR{resetafter}=="5"
ATTR{thresh}=="8"
ATTR{protocol}=="TPPS/2"
ATTR{press_to_select}=="0"
ATTR{sensitivity}=="255"
ATTR{inertia}=="6"
ATTR{firmware_id}==""
looking at parent device '/devices/platform/i8042/serio1':
KERNELS=="serio1"
SUBSYSTEMS=="serio"
DRIVERS=="psmouse"
ATTRS{resolution}=="200"
ATTRS{rate}=="80"
ATTRS{bind_mode}=="auto"
ATTRS{resync_time}=="0"
ATTRS{description}=="i8042 AUX port"
ATTRS{resetafter}=="5"
ATTRS{protocol}=="SynPS/2"
ATTRS{firmware_id}=="PNP: LEN0015 PNP0f13"
looking at parent device '/devices/platform/i8042':
KERNELS=="i8042"
SUBSYSTEMS=="platform"
DRIVERS=="i8042"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
EDIT:
tried with these two rules, no dice:
KERNEL=="serio2", ATTR{description}=="Synaptics pass-through", ATTR{speed}="180", ATTR{sensitivity}="255", RUN+="touch /tmp/udevtest"
ATTR{description}=="Synaptics pass-through", ATTR{speed}="180", ATTR{sensitivity}="255", RUN+="touch /tmp/udevtest"
Last edited by jeroentbt (2014-09-14 21:23:33)

Mail Rules not applying to Sent folder

I have rules set up to color code my e-mails. They work fine in all my mailboxes (Inbox, Trash, personal folders), but do not work properly when applied to my 'Sent' folder (the messages all turn orange). What's the problem?
I have Gmail being forwarded to the Apple Mail program using IMAP settings.

there is no problem. Mail rules work on incoming mail only. if you want Mail rules to apply to sent messages you need a 3rd party plugin. MailActOn
http://www.indev.ca/MailActOn.html
can do it.

UDev rules not working for MidiSport 2x2 usb midi device

I installed arch a couple of months ago and am loving it so far. Any problems I've had so far have already been solved in the forums, but this one's really got me. I have a MidiSport 2x2 that I want the firmware to be loaded on everytime I plug it in. I installed (there's not an arch package) a package that is supposed to do just that. (It's called midisport-firmware-1.2.tar.gz). However, the package seems to be out of date (2006) and I even had to modify a couple places in the configure script to get it to work with current program revisions. However, once installed, it does nothing. It installed firmware files and udev rules for the device into a couple of directories. When I run the command that is supposed to load the firmware, it works fine. But for some reason, (I even checked the udev kernel log) it's like the event isn't even being triggered. Here's part of the original file that came with the package that's supposed to load the firmware:
# midisport-firmware.rules - udev rules for loading firmware into MidiSport devices
# DEVPATH=="/*.0" selects interface 0 only
# (some udev versions don't work with SYSFS{bInterfaceNumber})
# MidiSport 2x2
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1001/*", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx"
# vim: ft=conf
And here's what I modified it to in an attempt to make it work:
# MidiSport 2x2
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0763", ATTR{idProduct}=="1001", RUN+="/sbin/fxload -D /dev/%k -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx"
I would really appreciate help from anyone who knows about this kind of thing, as I can't figure out what's going wrong. If it's something wrong with the config, please let me know. Actually, some HAL events popped up when I was testing this out. Is it possible HAL is blocking the udev event somehow?

Hi,
The firmware files must be put in /lib/firmware so they can be found by the kernel. Are they being put there?

Rewriter rules not applied

Hi,
I have a rewriter ruleset and two gateways. For one of the two gateways this ruleset is applied correctly, for the some rules of it are not applied.
The rulesets are applied to the same uri and the gateways have the same configuration.
We are using 30�40 rulesets in total.
This smells like a bug. Any suggestion someone?

The problem I have is the following rules:
<Function name="fetcher.open" paramPatterns=",y," />
<Function name="xml*ttp.open" paramPatterns=",y,"/>
     
<Function name="open" paramPatterns="y"/>
<Function name="*.open" paramPatterns="y"/>
Now, when we have this applied to a file on the right url which contains fetcher.open(1,2,3), it should rewrite the second parameter, but it is rewriting the first one.
Does anybody know about the order or specificness of the rules applied in the case above?
Best regards,
Tim

Solved: Udev rules not working

I have file called "/etc/udev/rules.d/99-monitor-hotplug.rules" with this rule:
ACTION=="change", SUBSYSTEM=="drm", RUN+="/root/scripts/hotPlugMonitor.sh"
But hotPlugMonitor.sh-script is not ran even thought it has permission to be ran and
udevadm monitor --property
gives:
KERNEL[69983.904205] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
ACTION=change
DEVNAME=/dev/dri/card0
DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
DEVTYPE=drm_minor
HOTPLUG=1
MAJOR=226
MINOR=0
SEQNUM=1885
SUBSYSTEM=drm
UDEV [69983.905420] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
ACTION=change
DEVNAME=/dev/dri/card0
DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
DEVTYPE=drm_minor
HOTPLUG=1
ID_FOR_SEAT=drm-pci-0000_01_00_0
ID_PATH=pci-0000:01:00.0
ID_PATH_TAG=pci-0000_01_00_0
MAJOR=226
MINOR=0
SEQNUM=1885
SUBSYSTEM=drm
TAGS=:seat:uaccess:
USEC_INITIALIZED=6
when I detach my monitor.
Last edited by oilgame (2013-08-31 09:10:08)

You got the command slightly wrong. See the right command:
udevadm control --reload
From:
$ udevadm control --help | grep reload
--reload reload rules and databases

Mobile account managed preferences sync rules not applied

Hello everyone!
I am testing out mobile accounts and home sync on a few of the machines I have. My goal is too use mobile accounts as a way to backup small documents. I have many preference and Home sync rules applied to a group. All the machines I have added to this group seem to recognize these rules, but one machine does not. It is syncing folders and file types that I have excluded. I have checked the users managed preferences file and it appears to be correct, yet when I start a sync it does not appear to follow it's own managed preferences.
One thing I should add is that these machines have been using plain old local accounts and I have been migrating them to mobile accounts using this method:
http://www.macenterprise.org/articles/migratingalocalusertoanetworkuser
This method seems to work great except for the fact that the users preferences like the dock don't appear to be carried over.

Did you ever solve this? I have just started testing this in our office as well. It appears I have a machine that does not appear to obey the rules ether. I am also migrating local accounts to mobile accounts.

SA 520 Firewall rules not applying

I've set up 3 schuldes for
1) 04.00 - 08.00 PM
2) 10.00 - 11.59 PM
3) 12.00 - 10.00 AM
Locked the mac address on the client computer to an leased IP number.
Then I set up 3 rules to block from LAN to WAN for this local IP 192.168.75.70 at the Scheduled times. But it dosen't apply.
The firmware is 2.1.71
I can see the client get the right IP address.

I did try to reset it, but It did'nt do the trick. Still full connection, where it should be blocked.
Enabled LAN WAN ANY BLOCK by schedule 192.168.75.70 Any Always

Macbook not responding during bootup

When I went o wake my Macbook from sleep this morning, the sleep light was solid and the screen was dark. When I pressed keys, nothing happened so I had to force shut it down.
When I went to turn it back on the hard drive clicked 4 times after the normal boot up noise, and the screen stayed white. After a few seconds a picture of a folder with a question mark started flashing on the screen. I tried turning it on again, but it was the same. I even reset the SMC, and it was no different
I haven't found any fixes for this and nothing I did would make it boot up differently.

Then take a look at this Apple article and see if anything will work for you.
http://docs.info.apple.com/article.html?artnum=307005
If not, you will probably need to reinstall Leopard....

Unable to detect coreless keyboard during bootup

I have just updated my T60P's BIOS to 2.25. Now I could NOT use my coreless keyboard (LX710) to input the HDD password anymore. It seemed that the keyboard was NOT detected during bootup. But it worked fine after it finished bootup. What can I do to fix it? Your help is greatly appreciated.

it said that:
Executing LiveCycle PDFGenerator Acrobat Configuration Script.
Verifying LiveCycle ES2 location LiveCycle ES2 Location -- "C:\Adobe\Adobe LiveCycle ES2"
Finding Acrobat location Acrobat Pro Extended was not found to be installed on the machine.
Please install Acrobat Pro Extended and then run this configuration script.
PDFGenerator Acrobat Configuration Script execution completed.
which script is this ?

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

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?

CUPS not working, due to wrong udev rules.

Hey everyone,
i got a problem getting my Brother DCP-145C (Printer & Scanner) to work.
I already did a little research and found out that the udev rules aren't working out, i tried to fix it according to this thread
So here are a few outputs, that hopefully help:
Here is the problem, the printer should be in the group lp:
[root@myhost rules.d]# ls -l /dev/bus/usb/
total 0
drwxr-xr-x 2 root root 60 2009-12-08 14:17 001
drwxr-xr-x 2 root root 60 2009-12-08 14:17 002
drwxr-xr-x 2 root root 60 2009-12-08 14:17 003
drwxr-xr-x 2 root root 60 2009-12-08 14:17 004
drwxr-xr-x 2 root root 100 2009-12-08 14:17 005
drwxr-xr-x 2 root root 60 2009-12-08 14:17 006
drwxr-xr-x 2 root root 60 2009-12-08 14:17 007
drwxr-xr-x 2 root root 80 2009-12-08 14:34 008
usblp is blacklisted:
[root@myhost rules.d]# cat /etc/rc.conf |grep usblp
MODULES=(!usblp usbhid)
Here the printer and the udev rules:
[root@myhost rules.d]# lsusb|grep Brother
Bus 008 Device 003: ID 04f9:0206 Brother Industries, Ltd
[root@myhost rules.d]# cat *|grep 0206
ATTR{idVendor}=="04f9", ATTR{idProduct}=="0206", MODE:="0664", GROUP:="lp", ENV{libsane_matched}:="yes"
ATTRS{idVendor}=="04b0", ATTRS{idProduct}=="0206", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="proprietary", MODE="0660", GROUP="camera"
The first rule is from my self created 10-cups-usb.rules file:
[root@myhost rules.d]# cat 10-cups-usb.rules
#Brother DCP-145C
ATTR{idVendor}=="04f9", ATTR{idProduct}=="0206", MODE:="0664", GROUP:="lp", ENV{libsane_matched}:="yes"
I don't know if its interesting but here the dmesg output if i replug my printer:
[root@myhost rules.d]# dmesg|tail -n 10
usb 8-2: USB disconnect, address 2
usb 8-2: new full speed USB device using uhci_hcd and address 3
usb 8-2: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 9:0:0:0: Direct-Access Brother DCP-145C 1.00 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
sd 9:0:0:0: [sdc] Attached SCSI removable disk

Thanks for confirming this issue.
I did find a message on VersionTracker.com which included a link to the uninstaller:
<http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_14157>
I uninstalled using the utility and deleted any flash related files/folders manually and reinstalled the beta. This did not help.
I ran the uninstaller again and installed the previous verion (9,0,47,0) and all is well again.
Thanks!
Jim

Error: "Windows could not apply unattend settings during pass [offlineServicing]"

Hi,
Using Windows Deployment Services and PXE boot, I am getting an error when installing Windows 8.1 and Windows 2012R2:
"Windows could not apply unattend settings during pass [offlineServicing]"
Deploying Windows 7 does not have the same issue.
The images were created from MSDN ISO's downloaded directly from MDSN - no modifications.
Suggestions?
Thanks,
Mark

Just to be on safe side I would copy the Install.wim and boot.wim file. Then try to run the setup again with new files.
Thanks

Can I connect keyboard/mouse to shutdown Win2K when I dod not connect it during bootup?

I would like to bootup even keyboard/mouse is NOT connected, but the problem is I cannot use keyboard after then. Can I connect and use keyboard/mouse when I did not connect them during bootup?

When using Windows 2000 with default startup options, it will always check if a keyboard and mouse are connected or not. If it cannot find either of them it will give you a warning.
If you boot the computer without a keyboard nor a mouse connected to it, it will not load the necessary drivers and you will not be able to use either one of them after boot up. However, you can boot with a mouse and keyboard connected, and then remove them. This way you will be able to re-connect and use them again later on.
You could also use a keyboard/mouse emulator to start up your system. You will have to check with the provider of the emulator if this solution allows you to connect and use a normal mouse and keyboard after boot up.
You could also try to find out how to c
hange registry entries of Windows 2000, so it boots up without checking for neither mouse nor keyboard, and logs in automatically. This way you would not need a keyboard/mouse emulator, and you could try using a USB keyboard and a USB mouse. Windows 2000 offers native support for USB devices and they are hot swappable.
For this last option, keep in mind that only PXI-8176 and PXI-8175 controllers have 2 USB ports. PXI-8174 controllers have only one USB port, as some other older controllers, such us PXI-8170 and PXI-8156B.
Hope this helps,
Claudia Lorente
Applications Engineer
National Instruments

Udev rules not applied during bootup

Similar Messages

Maybe you are looking for