Nevermind fix with a reboot and fsck
Nevermind fix with a reboot and fsck
Last edited by hanzomon4; September 6th, 2006 at 11:45 PM.
I haven't tried this yet, but I'm curious to know if it will work with more than one usb drive. I have four (yes 4, i'm ashamed to say) Cruzer Minis from SanDisk that I use for various things. Following the guide, each needs something unique to identify it so it can be mounted at the same place. But all have Product Name "cruzer mini" and the same product id, etc. so what would I do in this case? Thanks in advance and apologies if this is a dumb question.
i dont know about a product ID but i used a model string and mine worked fine on dapper, maybe you could mask the sd?1 part to reflect the various sticks?
heres myfileCode:10-local.rules
and after a quickCode:BUS=="usb", SYSFS{Model}=="MTM809A2-103 00 Rev: 1.01", KERNEL=="sd?1", NAME="mysonSD", SYMLINK="usbdevices/mysonSD"
i was in buisness.Code:sudo /etc/init.d/udev restart
This is odd. When I used update-manager to upgrade to Edgy, update-manager removed udev. No problem; I reinstalled it. But now none of my udev rules work anymore.
The permissions and ownership appear to be set correctly:
And the rules file itself is unchanged from when it did work.Code:>ls -l /etc/udev/rules.d/10-local-rules -rw-r--r-- 1 root root 202 2006-10-29 16:55 /etc/udev/rules.d/10-local-rules
Nevertheless, when I plug in my "ipod" (a Samsung knockoff), the device node still gets created at /dev/sda1 and not at /dev/ipod like it's supposed to.Code:>cat /etc/udev/rules.d/10-local-rules BUS="scsi", SYSFS{model}="YP-U1", KERNEL="sd?1", NAME="ipod" BUS="scsi", SYSFS{vendor}="Motorola", KERNEL="sd?1", NAME="phone" BUS="scsi", SYSFS{model}="PSP", KERNEL="sd?1", NAME="psp"
And yes, I've tried running "/etc/init.d/udev restart". Over and over, in fact.
Any ideas?
Last edited by dugan; October 30th, 2006 at 03:08 AM.
I'm also experiencing this.
Would be nice of somebody had a fix for this...
I have a LaCie-disk (was /dev/LaCie now is /dev/sda3) that I want mounted at /media/LaCie. But when I double-click it to mount it I get a message saying the mount point could not be established.
But when I manually create the directory /media/LaCie the disk mounts no problemo... at /media/LaCie-1
My fix is to make a link from /media/LaCie to /media/LaCie-1
Now when I restart and double-click on the disk it mounts at /media/LaCie-2. So I remove /media/LaCie and /media/LaCie-1. Won't mount.
I then do
Still won't mount. So I remove the link and create the directory /media/LaCie and the disk mounts at /media/LaCie-1 again.Code:>sudo ln -s /media/LaCie-1 /media/Lacie
I can then remove /media/LaCie and make the link again.
Now everything works, but it's still annoying.Code:>sudo ln -s /media/LaCie-1 /media/Lacie
Permanent fix would be nice...
Yeay, I've fixed it!
In the first post it said:
But it should be KERNEL=="sd?1". (it does say so on the line above it)- The option KERNEL="sd?1" will only match locations like /dev/sda1, /dev/sdb1 and more importantly, it won't match nodes like /dev/sda, /dev/sdb, which can be fdisk'ed. The 'Writing udev rules' guide also mentions this.
Now it works again!
Okay I did it.
1. renamed my 10-local-rules file to 10-local.rules
2. smacked self upside the head
3. Changed the contents of 10-local.rules to:
Code:BUS=="scsi", SYSFS{model}=="YP-U1", KERNEL=="sd?1", NAME="ipod" BUS=="scsi", SYSFS{vendor}=="Motorola", KERNEL=="sd?1", NAME="phone" BUS=="scsi", SYSFS{model}=="PSP", KERNEL=="sd?1", NAME="psp"
Hi, just a quick thanks for this guide.
I have 4 seperate USB devices that I regularly swap in and out and it's been driving me mad that they always appear on the wrong mount point.
I'd heard udev could be the answer and tonight I decided to look into it.
It took me around 20 minutes from reading your guide to having it all working perfectly.
Thanks a lot.
ok, this is a very good howto, and I was struggling like crazy with the same base document you used. No one seemed to know how to do this, and and a howto I was following didn't mention udev rules at all.
Question: your base document and your howto both talk about devices, but how about lirc? It's not a block device, but a class in the sys tree, so I'm doing my best here, but I'm not at all sure I'm doing it right. At the latest edit, my 10-local.rules file looks like this:
BUS=="ide", KERNEL=="hdc", MODE="0666", SYMLINK+="cdrom", GROUP="cdrom"
BUS=="ide", KERNEL=="hdc", MODE="0777", SYMLINK+="cdrw", GROUP="cdrom"
BUS=="ide", KERNEL=="hdc", MODE="0666", SYMLINK+="dvd", GROUP="cdrom"
BUS=="ide", KERNEL=="hdc", MODE="0777", SYMLINK+="dvdrw", GROUP="cdrom"
SUBSYSTEM!="usb_device", ACTION!="add", GOTO="_end"
# For brotherBUS=="usb", KERNEL=="lirc0", SUBSYSTEM=="lirc", SYSFS{dev}=="61:0",
SYSFS{idVendor}=="04f9", MODE="666", GROUP="scanner"
LABEL="_end"GROUP=”daemon”, MODE="0777", SYMLINK="usbdevices/remote", RUN+="/usr/local/bin/change-channel-lirc.pl"
Obviously I want certain devices writable and executable by all users, as lirc needs to be. And I didn't give it a name because I don't need it to be in a persistant place.
Thank you; I hope it will work better than the last attempt , and we'll see it if works just as well with Edgy. A lot of people are having real trouble with lirc, so perhaps this late reply will bubble it up.
wgaprotest/dennister
HTPC system: amd64 x2/3800+; A8N32-SLI Dlx; 2G RAM; Mozart case w Antec TP II 550W PS; Sata 300G + IDE 300G; Nvidia 7800GT; Hauppauge WinTV PVR-250; LG 4176B
Bookmarks