On Wed, 9 Oct 2002, Charles R. Anderson wrote:
Date: Wed, 9 Oct 2002 08:52:04 -0400 From: Charles R. Anderson <cra@WPI.EDU> Reply-To: wlug@mail.wlug.org To: Worcester Linux Users Group <wlug@mail.wlug.org> Subject: Re: [Wlug] loading modules
subssn594> Could /etc/sysconfig/hwconf be the right place to fix this?
The module might be loading in the initial ramdisk. After changing modules.conf try creating a new one:
mkinitrd /boot/initrd-2.4.18-14 2.4.18-14
You can take a look at that script to see how it discovers which module to load. It is pretty tricky and does call kudzu, so maybe the hwconf thing is right.
-- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
It's working!!! Here's what I found... 1. /etc/sysconfig/hwconf is written at boot time. I have no idea what part of the boot sequence writes it, but the modification date suggests that it's very early. 2. I had to modify the line in /etc/modules.conf before running mkinitrd. This was special because the HBA is seen as a SCSI device. For other devices, the --preload=module and --with=module options would probably work. mkinitrd is a script, so you can read it to see where it's getting data. After booting, lsmod showed that the right module was loaded. Charles, thanks for the great hint. Bill