You are not logged in.
During the boot process, loading user-specified modules fails. I checked my /etc/rc.conf and had the following line:
MODULES=(vboxdrv, loop)
I ran the commands below to see if the modules had been loaded... and it appears they have:
[esuhl@i7pc ~]$ lsmod | grep vboxdrv
vboxdrv 1790690 2 vboxnetflt,vboxnetadp
[esuhl@i7pc ~]$ lsmod | grep loop
loop 18526 0
I'm no expert when it comes to Linux, so I've probably done something daft! Can anyone suggest what might be causing the failure?
Thanks.
Last edited by esuhl (2012-02-11 01:35:08)
Offline
This always fixes it for me:
/etc/rc.d/vboxdrv setup
Offline
As far as I know, if the OP is using Vbox modules installed from the official repo, he won't find a daemon to run in his /etc/rc.d.
Try removing the comma from MODULES; use only spaces to separate modules.
Edit: run
dmesg | grep "module-name"
to find out what's going on.
Last edited by bohoomil (2012-02-10 21:28:32)
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
I run virtualbox-bin from the aur, and need to rebuild the modules after every kernel upgrade.
Offline
Try removing the comma from MODULES; use only spaces to separate modules.
D'oh! I knew it would be something simple! How embarrassing!
Thanks for your help :-)
Offline