LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   RHEL4 insmod/modprobe issues (https://www.linuxquestions.org/questions/linux-newbie-8/rhel4-insmod-modprobe-issues-663854/)

t3chn0m0nk3y 09-04-2008 08:15 AM

>currently when the module is loaded and you run modprobe -a and then a modprobe -l |grep rr174x.ko does it still give you the FATAL: error?

No it reads:

/lib/modules/2.6.9-78.0.1.ELsmp/kernel/drivers/scsi/rr174x.ko

>Also, what directory is the module you're loading located?

I compiled the source in a dir I created /drivers, which contained the source tree in a convoluted dir structure:

/drivers/rr174x-linux-src-v2.1/product/rr1740pm/linux

Here the config.c, Makefile, and .build/ are located. I ran Make to create rr174x.ko

from this directory I ran insmod. However later as stated in the OP, I cp the .ko file to the location above /lib/...

I will attempt the other commands later today after a conference call is planned to do some other pertinent work on this box. Feel free to IM me at the names provided in my email reply.

thanks again!

jschiwal 09-04-2008 08:37 AM

Does the module load fine manually and work? If so, I think you want to add the module to your initrd so that it is loaded as soon as you need it. Especially if your system partitions are on the raid controller.

Look at man "mkinitrd" for the --with=MODULE option.

Also, it this is a 2.6 kernel, try using modprobe instead of insmod.

---

I looked at one of the driver downloads. It contains a script that performs these two lines:
Code:

                /sbin/depmod -a ${kver} &&
                /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with=${DRIVER} --builtin=sata_mv /boot/initrd-${kver}.img ${kver}


t3chn0m0nk3y 09-04-2008 10:13 AM

I will be attempting to use the mkinitrd option that misconfiguration suggested, I'm just wainting for an opportunity since the server is live.

The reason I'm using insmod instead of modprobe, is that modprobe doesn't work properly. again as stated in earlier posts, it gives a FATAL error unable to locate the module.

Also, the driver was compiled from source, so I'm not sure where that script was. It certainly wasn't in any of the docs included in the compile process as I followed them to the letter.

-TM

t3chn0m0nk3y 09-04-2008 12:42 PM

Thanks to both misconfiguration and jschiwal for their help!

made a backup of kern.img in /boot

ran "mkinitrd -f --with=rr174x initrd-$(uname -r).img $(uname -r)"

made sure the entry in /etc/fstab was correct and rebooted

WORKED LIKE A CHARM!!

thanks again to all!!

-TM


All times are GMT -5. The time now is 08:43 AM.