Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
root@darkstar:/home/david# udevinfo -a -p /sys/block/sde
Udevinfo 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.
OK I am confused on which BUS i should use sinbce there are at least 2 listed in this here is everything that udevinfo -a -p /sys/block/sde supplied me.
Quote:
root@darkstar:/home/david# udevinfo -a -p /sys/block/sde
Udevinfo 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.
in your rule, taking stuff from the second section of your output from udevinfo. Edit: obviously this isn't a complete rule as there's no NAME or SYMLINK in it.
What did you use for NAME and/or SYMLINK in your rule? Check if there's a node in /dev with that name. You can do this with ls, e.g. if you named the device "usbdisk", run "ls /dev/usbdisk" and see if there's anything there.
Try disconnecting the device (unmount it before doing so, if it's mounted) and reconnecting it and then trying again. Sometimes I have this with udev when adding a new rule.
OK, I ran a udevtest and this was the results maybe it can help in determining what is happening. Only thing is I have no idea of what to look for to fix anything.Here is what the results from the test give
Quote:
root@darkstar:/dev# udevtest /block/sde
main: looking at device '/block/sde' from subsystem 'block'
udev_rules_get_name: rule applied, 'sde' becomes 'sde'
run_program: '/lib/udev/usb_id -x'
run_program: '/lib/udev/usb_id' (stdout) 'ID_VENDOR=WD'
run_program: '/lib/udev/usb_id' (stdout) 'ID_MODEL=5000AAKS_Externa'
run_program: '/lib/udev/usb_id' (stdout) 'ID_REVISION=101a'
run_program: '/lib/udev/usb_id' (stdout) 'ID_SERIAL=WD_5000AAKS_Externa_57442D574341505730333539303535'
run_program: '/lib/udev/usb_id' (stdout) 'ID_TYPE=disk'
run_program: '/lib/udev/usb_id' (stdout) 'ID_BUS=usb'
run_program: '/lib/udev/usb_id' returned with status 0
udev_rules_get_name: add symlink 'disk/by-id/usb-WD_5000AAKS_Externa_57442D574341505730333539303535'
run_program: '/lib/udev/path_id /block/sde'
run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:00:07.2-usb-0:1.2:1.0-scsi-0:0:0:0'
run_program: '/lib/udev/path_id' returned with status 0
udev_rules_get_name: add symlink 'disk/by-path/pci-0000:00:07.2-usb-0:1.2:1.0-scsi-0:0:0:0'
run_program: '/lib/udev/vol_id --export /dev/.tmp-8-64'
run_program: '/lib/udev/vol_id' (stderr) '/dev/.tmp-8-64: unknown volume type'
run_program: '/lib/udev/vol_id' returned with status 4
run_program: '/lib/udev/edd_id --export /dev/.tmp-8-64'
run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support'
run_program: '/lib/udev/edd_id' returned with status 2
udev_device_event: device '/block/sde' already in database, validate currently present symlinks
udev_node_add: creating device node '/dev/sde', major = '8', minor = '64', mode = '0660', uid = '0', gid = '6'
udev_node_add: creating symlink '/dev/disk/by-id/usb-WD_5000AAKS_Externa_57442D574341505730333539303535' to '../../sde'
udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:00:07.2-usb-0:1.2:1.0-scsi-0:0:0:0' to '../../sde'
main: run: 'socket:/org/kernel/udev/monitor'
Last edited by sulvereagle59; 06-08-2007 at 11:23 AM.
In your fstab, you can now just use the symlinks as the device name in the first column and everything else as before. So, for your external hard disk, you used to have an entry like this:
/dev/sda2 /E vfat noauto,user,rw,exec,sync 0 0
You can now change the "/dev/sda2" to "/dev/usbhd2". The partition numbers are the same as before. I think you needed to mount /dev/sda5 to get it to work, right? So you'd actually use /dev/usbhd5. Does that make sense?
Similarly, just add an entry for your flash drives using /dev/usb-storage in the first column.
Here are my two entries
One's for my flash drive and the other is for my digital audio player.
Like you, I've got two flash drives and my udev rules are set up to call them both "flash". I don't know what would happen if I tried plugging them both in at the same time. I think maybe you'd have to use different names, rather than "usb-storage" for both.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.