Click to See Complete Forum and Search --> : Slackware Linux bootup on ATA 133 controller


ncp100
07-15-2004, 03:05 PM
Okay this is my problem - I have a ITE8212 IDE raid controller card which is connected to a hard drive (the only hard drive in the system). I booted using the slack 10.0 CD it would not see the hard drive, so

1. I downloaded the drivers onto a floppy - mount /dev/fd0 /mnt
2. Loaded the driver using insmod -f /mnt/iteraid.o (I had to use the -f coz of linux version incompatibility.
3. It detected my hard drive, and I created a linux partition and installed linux on it, created lilo for boot up etc.
4. When I boot up my machine and select Linux at the lilo loader, it comes up with a kernel panic error - at this point I'm assuming its because linux does not see my hard drive.
5. Boot of the CD again and compile the kernel with the iteraid drivers copied to the /usr/src/linux/drivers/scsi folder.
6. After booting up again, I get a Setup signature not found.

My thought is if I can somehow force the module to load on bootup I should be all set. I have added the option insmod_opt=-f in the modules.conf file and still no luck.

Any help is appreciated.

Thanks

ph34r
07-15-2004, 03:14 PM
Custom kernel wtih the support built into it?

ncp100
07-15-2004, 03:49 PM
I copied the iteraid.c and iteraid.h files into the driver/scsi folder as 3w-xxxx.c and 3w-xxxx.h and under the menuconfig changed SCSI low level drivers to 3ware raid support.

JohnT
07-15-2004, 04:25 PM
Add the line "/sbin/modprobe/ iteraid" to your /etc/rc.d.rc.modules file.

ncp100
07-15-2004, 04:31 PM
That will not force the module to load right? Because to install Linux I had to do a insmod -f iteraid.o
Or will that take into consideration the insmod_opt=-f line that I added in the modules.conf file?

JohnT
07-15-2004, 04:40 PM
Or will that take into consideration the insmod_opt=-f line that I added in the modules.conf file? It should, but I don't know the correct syntax, so that's something you'll have to play with. You might just try it in the same line in /etc/rc.d/rc.modules with the loading.

From man modprobe:
If any arguments are given after the modulename, they are
passed to the kernel (in addition to any options listed in
the configuration file).

ncp100
07-17-2004, 05:13 PM
Adding the line in the rc.modules file did not work. Now i'm trying to create a initrd image and see if that will work.