Timothy Renner <timothy.ren...@...> writes: > I am looking to find a way to get a module added to the initrd > automatically, whenever mkinitrd is invoked. I can use the --with > flag to force a module in, but if for some reason the ramdisk is > automatically rebuilt (The Driver Update process) or if somebody > manually re-runs mkinitrd, it will no longer be included and our > system will no longer boot. It looks like /etc/modprobe.conf or > /etc/modprobe.d is useful for SCSI modules only. Is there any other > configuration file that can be used to tell mkinitrd to automatically > include *any* arbitrary module? > > Thanks, > -Tim
I know this discussion ended some time ago, but I came across it while searching a similar problem. /etc/modprobe.conf should process any included module. If it doesn't, try running 'depmod -a <kernel-version>' and then making your initrd. Subsequent kernel updates should have no negative impact *unless* you have some third party modules in /etc/depmod.d/depmod.conf. see: http://dup.et.redhat.com/ We ended up removing a lot of third party modules installed via some IBM update scripts (on IBM system X hardware), so we could return to stock kernel modules, so I know the depmod/mkinitrd process works. If you want to verify, copy your recently made initrd to an empty folder. Rename it with a .gz extension and(there is likely an easier way to do this): gzip -d filename.gz cpio -i < filename Verify your module is loaded in the 'init' script. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
