Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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 have a zip drive that alternately mounts on /dev/sda and /dev/sdb each time I reboot. I'm not positive that it switches EVERY time, but it's pretty close to it. My system is the same each time I boot, so am confused as to why the alternation. It is somewhat of a pain because I'm trying to wean my wife from windoze and have a desktop icon set up for mounting and I really want some consistency.
my zip (para port, 250 mb) always stays mounted to /dev/sda4
is yours external or internal?? is it para port or USB??
what do you have listed in /etc/fstab
That's pretty strange. I thought the system allocated the devices sequentially, so if you had a /dev/sdb then /dev/sda must be in use for something else. Try also command
dmesg | grep /dev/sd
to see what else might be around when zip is at /dev/sdb.
The ref to /mnt/camera suggests you may sometimes have a USB device (like a camera) attached. That could certainly have an effect on device allocation.
I don't know how to interpret the error messages. There is file called parport.txt in the kernel source (in Documentation subdir) which has some relevant looking info.
The camera usb cable is always plugged into the computer at boot, but the camera is never hooked up on boot, and it is rarely used anyway, so that is constant. I am using the current slack10 kernel, 2.4.26 I believe. I didn't see anything in parport.txt that looked useful to my situation.
The kernel messages seem to indicate a faulty USB mass storage device is detected, and this is occupying /dev/sda. It seems unlikely, but maybe the camera cable itself is generating some spurious feedback when the port is probed. Anyway, that is all I can think of.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.