Description of problem:
mkinitrd only looks for /etc/modprobe.conf when looking for module command-line options for the modules it loads. Fedora 9 is now storing modprobe configuration in separate files in /etc/modprobe.d but mkinitrd does not look in this location.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a module option to a new file in /etc/modprobe.d, for example:
options sata_nv adma=1
2. Run mkinitrd
3. Dump the contents of the initrd and check for any /etc/modprobe.conf file - there is none
No /etc/modprobe.conf file.
Options from /etc/modprobe.d are either copied into the initrd as-is or extracted into a modprobe.conf file.
This makes it impossible for the user to specify command-line options for kernel modules loaded in the initrd.
This is still a problem in Fedora 10.
In case it matters, I'll add my vote for fixing this. Like many modern desktops, my machine uses SATA drives; in Fedora kernels, libata is loaded as a kernel module (by initrd), not built into the kernel; so options for libata that are listed in /etc/modprobe.d are ignored right now.
Appears to still be a problem in Fedora 11 (mkinitrd-6.0.86-2.fc11).
Dracut in Fedora 12 doesn't seem to have this problem from inspecting the code anyway, it looks like all the /etc/modprobe.d files get dumped into the initrd.
Appears fixed in Fedora 12.