You are not logged in.
Following the problems with 060-1, I went back to 058-4 - everything was fine, as expected. When I saw 060-2 and then 060-3 in current, I figured I'd give it another shot. It looked fine initially i.e. it didn't break my network. However, none of my custom rules for USB devices are working under 060-3.
So I'm back to 058-4 - and everything's fine again.
Offline
i have two rules files in /etc/udev/rules.d :
00-perso.rules
10-udev.rules
all my usb stick rules are in my perso files.
even if the pero file should be treated first, my usb sticks and ipod were not detected and treated according to my perso rules.
I had to comment out most of the scsi rules in 10-udev.rules for it to work:
# scsi block devices
#BUS="scsi", KERNEL="sd[a-z]", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="sd[a-z][0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="sd[a-i][a-z]", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="sd[a-i][a-z][0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="s[grt][0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="scd[0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="st[0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="nst[0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
only after that my usb sticks were detected and processed by udev with my own rules.
I just installed ARCH for the first time a few days ago so i don't know if this problem was due to the new udev version or not.
hope this helps
t o m d e b
_______________________________________
"the urge to destroy is a creative urge."
Mikhail Bakunin.
Offline
Thanks for that. I'm happy enough to run with 058-4 until this is sorted, but useful to know anyway.
Would you mind checking what version you're running?
Thanks.
Offline
Would you mind checking what version you're running?
i am running 0.60-3
t o m d e b
_______________________________________
"the urge to destroy is a creative urge."
Mikhail Bakunin.
Offline
udev 060-5 is out. There is some changes in the use of rules: http://www.archlinux.org/news.php#162
Offline
Got it Snowman - thanks.
Offline
Hey guys, udev 061 has just been released so Judd might be pushing yet another Arch udev release out the door soon...
oz
Offline
Man, I sure hope they don't rip devfs out for the kernel anytime soon.
Offline
Man, I sure hope they don't rip devfs out for the kernel anytime soon.
count on it in the next kernel. Better make the switch now.
Offline
Man, I sure hope they don't rip devfs out for the kernel anytime soon.
hehe... it appears that udev 060-5 has cleared up most of the problems that everyone was experiencing so I don't think you'll have too tough of a time dropping devfs and going to udev. Hope not, anyway...
oz
Offline
Btw, I discovered some funny fact reading the udev manpage:
When writing udev rules, using a single "=" as comparison operator is deprecated. For comparing values people should use "==".
The single "=" should only be used for assignment, like for NAME="%k".
Example rule for hotplugging my Zaurus to the network:
KERNEL=="usb0", DRIVER=="usbnet", NAME="%k", RUN="/etc/udev/scripts/zaurusnet.sh"
Offline
Yes, "=" as comparison operator is deprecated but still can be used. I'd expect another udev release some time soon :-)
For all the people writing custom udev rules: there were many changes in udev rules handling since 057. For example if you don't want standard rules to change your custom rules you can add OPTIONS="last_rule" which will stop processing rules for a given device. More info about this in the forums and bug reports.
The best source for information about changes in udev is the RELEASE-NOTES file in the sources.
Offline
Has anyone else noticed this today ?? :
[root@myhost myusername]# pacman -Syu
:: Synchronizing package databases...
:: current is up to date
:: extra is up to date
Targets: udev-062-1
Total Package Size: 0.1 MB
Proceed with upgrade? [Y/n] y
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
udev: /etc/scsi_id.config: exists in filesystem
errors occurred, no packages were upgraded.
[root@myhost myusername]#
Thanks.
Offline
You can force the upgrade with -Sf or -Sfu without any problems.
Offline
Has anyone else noticed this today ??
Yep, here's more on this: http://bbs.archlinux.org/viewtopic.php?t=13845
oz
Offline
Cheers guys - I'll hop over to that thread
Offline