On 02/28/2014 03:23 PM, Ed Greshko issued this missive:
On 03/01/14 07:14, dennismccloud@xxxxxxxxxxxxx wrote:
Thanks for your help. You were correct that it was a problem with the kernel needing to be rebuilt after adding/changing files to the /etc/modules-load.d and /etc/modprobe.d directory.
Made a copy of the existing /boot/initramfs-$(uname -r).img file and re-ran the command to rebuild the kernel file:
# dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
I went back and checked the man pages on modules-load.d and modprobe.d and neither mentions having to run dracut or mkinitrd after adding file to these directories. Lesson learned.
You're welcome.
I don't know where that information may be documented.
It wouldn't be. If the device in question is hot-pluggable, then the act
of plugging it in after boot would cause the udev stuff to invoke the
modprobe. Since the device isn't hot-pluggable (it's there when you boot
the machine), then the module must be loaded in the initrd image to be
active at boot. Hence the need to run dracut.
As far as I know, this has always been the case. If you need the module
at boot, you need to have it in the initrd image.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- I'm afraid my karma just ran over your dogma -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
