SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I'm having an issue using 2 differnet USB flash drive devices on my Slack 10 system running the 2.4.26 kernel. If I just use one device, everything works fine with it mounting as /dev/sda1 on /mnt/usb.
If I use the 2nd device (not at the same time but alternately), it says no device found at /dev/sda1. To get around this I have to become root, modprobe -r usb-storage then modprobe usb-storage, in effect, reload this module. Then it mounts fine. As long as I keep mounting/unmounting this same device, cool.
However, if I go back to use the first device, I get the same error and must do the same procedure to get around it. It seems the usb-storage module doesn't handle different devices without reloading. Is there a fix for this? Or, is there a way this manual workaround process can be automated?
I have the same problem. The second device is recognized as /dev/sdb1. This is interesting as i'm developing a package which autoconfigure the automounter (submount for now) and many other things. And i didn't find an answer to this problem.
I hade the same situation with memory cards in my laptop PCMCIA slot. Discovered from /var/lib/pcmcia/stab that the first card inserted into the double slot (either slot) goes on /dev/hde1 and the second on hdg1. Like sporks I just mapped /dev/hde1 to /mnt/Card1 and /dev/hdg1 to /mnt/Card2.
The solution is to use udev and hotplug.
In fact, you can create a symlink of a device probed by hotplug.
Then, you could use this symling in /etc/fstab to mount this device without knowing the real device name /dev/sd?1
A good tutorial : http://www.reactivated.net/udevrules.php
Originally posted by JohnKFT I hade the same situation with memory cards in my laptop PCMCIA slot. Discovered from /var/lib/pcmcia/stab that the first card inserted into the double slot (either slot) goes on /dev/hde1 and the second on hdg1. Like sporks I just mapped /dev/hde1 to /mnt/Card1 and /dev/hdg1 to /mnt/Card2.
Yes, I should have been more clear, the first one plugged in is /dev/sda1 or the first one from the right on the USB hub becomes /dev/sda1 then /dev/sdb1.
When I'm trying to use udevinfo (for one of my usb sticks (which is either sdc or sdd)), I get the following message:
user@box:~# udevinfo -q path -n /dev/sdc
unable to open udev database
I'm using kernel-2.4.26 with slack-10.0 (udev-026-i486-1.tgz package ist installed).
Could it be that the udev rules could only be used with the 2.6.x kernel?
Could it be that the udev rules could only be used with the 2.6.x kernel?
Yes. 2.4 kernels use devfs for device management, whereas 2.6 uses udev/sysfs. Therefore, udev rules do not apply to devfs (and neither do they apply to the 2.4 kernels).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.