Red Hat Bugzilla – Bug 17067
mkinitrd does not seem to work....
Last modified: 2008-05-01 11:37:58 EDT
I installed pinstripe a while ago, just after it came out. I got a new
Adaptec AIC-7892 Ultra 160/m SCSI host adapter and ran the mkinitrd command
in order to create a new initrd image so that when the kernel booted, it
would load both my Buslogic and Adaptec drivers. Well, the kernel did not
load any of the two. What worries me is that since you guys have depricated
/etc/conf.modules in favor of /etc/modules.conf (ugg....) I'm wondering if
mkinitrd is looking at the wrong file. The man page for mkinitrd references
/etc/conf.modules and not /etc/modules.conf. Here look....
mkinitrd - creates initial ramdisk images for preloading
mkinitrd [-fv] [--with=module] [--preload=module]
[--version] [--fstab=fstab] image
mkinitrd creates filesystem images which are suitable for
use as Linux initial ramdisk (initrd) images. Such images
are often used for preloading the block device modules
(such as SCSI or RAID) which are needed to access the root
filesystem. mkinitrd automatically loads all
scsi_hostadapter entries in /etc/conf.modules, which makes
it simple to build and use kernels using moduler SCSI
Any module options specified in /etc/conf.modules are
passed to the modules as they are loaded by the initial
In anycase, it could be that something else is mucked up. I'll be glad to
assist in helping debug this problem.
mkinitrd definitely looks in modules.conf, and the man
page has been updated to reflect this in a later release.
this bug dies of old age.... reopen if it's still applicable