Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
So everything I've read says that redhat 8.0 and later is plug and play for usb mass storage devices. Well, I have an iomega zip 250 that doesn't want to be plug and play.
I found a site last week that walked me through which files to load to power it on and use it...fine. But it didn't stick, and I lost the site that told me how to do it. So now I'm stuck again. Can someone please tell me how to make my redhat 9.0 allow my zip drive to be plug-and-play...maybe even accessible through the gnome desktop right-click "disks" menu?
Be sure to have usb mass storgage configured in your kernel. I thnk you need scsi emulation enabled as well. Run a dmesg as root and you should get a messeage somewhere that looks like this:
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
usb-uhci.c: interrupt, status 3, frame# 1578
Vendor: IOMEGA Model: ZIP 100 Rev: 44.W
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
USB Mass Storage support registered.
And then a little later you'll see this:
PCI: Found IRQ 9 for device 02:0a.0
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
usb-uhci.c: interrupt, status 3, frame# 160
This means that my zip drive can be found at /dev/sda (if it's windows formated it will be sda4). Just add that to your fstab and you are good to go.
If you've gotten it to work before then I'm sure your kernel is setup and ready to go. Does redhat have a file called /etc/modules.autoload? It's been a while since I've tinkered with redhat (yahoo gentoo!). If there is, just add the name of the modules to that file. For example, here's my /etc/modules.autoload file:
# /etc/modules.autoload.d/kernel-2.4: kernel modules to load when system boots.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload.d/kernel-2.4,v 1.1 2003/03/09 09:06:23 azarah Exp $
# Note that this file is for 2.4 kernels. If you need different modules
# for a 2.5 kernel, you can create /etc/modules.autoload.d/kernel-2.5
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line. Comments begin with # and
# are ignored. Read man modules.autoload for additional details.
Based on another thread I stumbled across here, I figured out the syntax for my fstab file...I just used "auto", and used the users switch, and viola! It's in my right-click disks menu. Great. But it doesn't work...trying to mount tells me that there is probably no media in the drive. Ok, so I manually mount. When I go to unmount, it says it can't do it because /mnt/zip250 doesn't match fstab. Interesting...
Right, I don't have a modules.autoload file, but I did have my modules.conf file. I added the line you said and rebooted, but it was the same thing...I can go into root and manually insmod the three files then mount it, but it wasn't loaded itself.
Getting close...I can feel it. Is there any way to write a script maybe...have it load the three modules and mount the zip at startup? But then I'll still have the tempermental desktop menu...sigh...well, we'll get it eventually, right? :-)
OK...I tried editing rc.local like you said...no effect. Nothing seems to load these modules before login. So I turn to the other promising possibility mentioned...how would I go about recompiling my kernel to include these instead of modules, like busbarn suggested?
Or would switching to gentoo be a better solution? I'm a new linux user, struggling to switch over from windows, and I just installed Redhat because that's what I'd always heard of. I read the gentoo vs. redhat thread, and it sounds promising, but does "hardware compatability" that they promise really mean this problem will go away? I'm still early enough in, I wouldn't mind switching to gentoo if it would be better for me in the long run.