I have a system where I need to load a driver newer than the one that comes
with the distribution. This is the 3w-9xxx.ko driver for the 3Ware 9690 SAS
controller and is in /lib/modules/2.6.18-53.el5/modules/kernel/drivers/scsi.
I have following line in my kickstart config that loads a newer version of
this driver using an image of a driver disk:
driverdisk --source=http://installserver/RHEL-5.1-SERVER-X86_64/images/dd.img
This works fine, and newer driver ends up in
/lib/modules/<kernelname>/updates. I can see this happen in the
anaconda.log file:
17:42:32 INFO : modules to insert 3w-9xxx
17:42:32 INFO : module 3w-9xxx found on driver disk 3ware Storage
Controller Driver Disk
17:42:32 INFO : loaded 3w-9xxx from /tmp/ramfs/DD-0/modules.cgz
17:42:34 INFO : inserted /tmp/3w-9xxx.ko
17:42:58 WARNING : Didn't find any package providing module 3w-9xxx
10:48:02 INFO : running: 'cd /mnt/sysimage/lib/modules; gunzip <
/tmp/ramfs/DD-0/modules.cgz | /mnt/sysimage/bin/cpio --quiet -iumd
2.6.18-53.el5/x86_64/3w-9xxx.ko 2.6.18-53.el5/3w-9xxx.ko '
10:48:02 INFO : moving
/mnt/sysimage/lib/modules/2.6.18-53.el5/x86_64/3w-9xxx.ko to
/mnt/sysimage/lib/modules/2.6.18-53.el5/updates/3w-9xxx.ko
The problem is that subsequent kernel updates run the /sbin/weak-modules
command, which expects the driver to be in /lib/modules/<kernelname>/extra
(and seems to ignore the "updates" directory). The result is that the newer
driver never gets linked to subsequent kernels. At the moment, I use the
following in my kickstart config to address this:
%post
mv /lib/modules/2.6.18-53.el5/updates/3w-9xxx.ko
/lib/modules/2.6.18-53.el5/extra/
Is there a way to get kickstart to use the "extra" directory instead of
"updates" ? I'm assuming that I can't easy change the behavior of
/sbin/weak-modules or /sbin/new-kernel-pkg.
thanks
-e
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
