sys-apps/openrc-0.41.2 was installed during system upgrade yesterday. Openrc reported that kernel modules specified in /etc/conf.d/modules could not be loaded twice. I read /etc/init.d/modules. It loads kernel modules twice.
The only way I know of that it would do that is if the module is configured in /etc/conf.d/modules *and* one of the modules-load.d directories. If that is the issue you should remove the extra listing from /etc/conf.d/modules or /etc/modules-load.d/*.conf.
/etc/modules-load.d/lm_sensors.conf loads it87. /etc/conf.d/modules loads "vboxdrv vboxnetflt vboxnetadp vboxpci snd-aloop"
Please attach the output from the following command: # rc-service --verbose modules restart Thanks, William
~> sudo rc-service --verbose modules restart Password: modules | * WARNING: you are stopping a boot service modules |modules | * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh /etc/init.d/modules stop modules |modules | * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh /etc/init.d/modules start modules | * Loading module it87 ... modules | * Failed to load it87 [ !! ] modules | * Loading module vboxdrv ... modules | * Failed to load vboxdrv [ !! ] modules | * Loading module vboxnetflt ... modules | * Failed to load vboxnetflt [ !! ] modules | * Loading module vboxnetadp ... modules | * Failed to load vboxnetadp [ !! ] modules | * Loading module vboxpci ... modules | * Failed to load vboxpci [ !! ] modules | * Loading kernel modules ... modules |modprobe: ERROR: could not insert 'vboxdrv': Module already in kernel modules |modprobe: ERROR: could not insert 'vboxnetflt': Module already in kernel modules |modprobe: ERROR: could not insert 'vboxnetadp': Module already in kernel modules |modprobe: ERROR: could not insert 'vboxpci': Module already in kernel modules |modprobe: ERROR: could not insert 'snd_aloop': Module already in kernel
Perhaps, linux kernel loads modules before /etc/init.d/modules does?
That is correct, the modules are already loaded. The solution is to tweak /etc/conf.d/modules until those messages go away.
It turned out that /usr/lib/modules-load.d/virtualbox.conf belongs to app-emulation/virtualbox-modules and /etc/init.d/modules loads modules in virtualbox.conf during boot.
