On Tue, Jul 24, 2018 at 10:25 AM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 07/24/18 12:08, Sudhir Khanger wrote:
> systemd-modules-load.service fails at boot and then it probably builds the modules.
> After the system boots, systemd-modules-load.service has active status and not
> failed. But the only way to get rid of Failed to start Load Kernel Modules**is by
> rebuilding initramfs via command dracut -v -f. This error crops up everytime you
> install a new kernel irrespective of VirtualBox's installation source.
>
Nope....
As a matter of fact, systemd-modules-load.service never runs on my system. Why?
None of these conditions are met....
ConditionDirectoryNotEmpty=|/lib/modules-load.d
ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d
ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d
ConditionDirectoryNotEmpty=|/etc/modules-load.d
ConditionDirectoryNotEmpty=|/run/modules-load.d
ConditionKernelCommandLine=|modules-load
ConditionKernelCommandLine=|rd.modules-load
[egreshko@meimei ~]$ ll /lib/modules-load.d
total 0
[egreshko@meimei ~]$ ll /usr/lib/modules-load.d
total 0
[egreshko@meimei ~]$ ll /usr/local/lib/modules-load.d
ls: cannot access '/usr/local/lib/modules-load.d': No such file or directory
[egreshko@meimei ~]$ ll /etc/modules-load.d
total 0
[egreshko@meimei ~]$ ll /run/modules-load.d
ls: cannot access '/run/modules-load.d': No such file or directory
And the kernel command line does not contain either of those parameters.
So.
[egreshko@meimei proc]$ journalctl -u systemd-modules-load.service
-- Logs begin at Thu 2017-12-21 09:55:27 CST, end at Tue 2018-07-24 12:39:54 CST. >
-- No entries --
I never have to run dracut to get rid of anything.
As I've already shown in my previous message it is vboxdrv.sh that checks/loads the
vbox drivers.
It does it here in the script
if ! $MODPROBE vboxdrv > /dev/null 2>&1; then
setup
And then goes here if the modprobe fails.
# setup_script
setup()
{
begin_msg "Building VirtualBox kernel modules" console
log "Building the main VirtualBox module."
And it creates the /var/log/vbox-setup.log
[egreshko@meimei log]$ cat vbox-setup.log
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/P2MTTXEPYI7CGN7SP7Z5UROJZXPULZWA/
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/GUBU7IZL4OAC4EE6Y2J3Z6KP3HYP2TUK/
