You are not logged in.
Pages: 1
I have already fixed this issue, but would like to know why this happened.
I had a custom compiled kernel using the abs. A friend wanted to use a feature on my laptop which I didn't compile into the custom kernel, so I just did pacman -S kernel26.
I rebooted (not having the virtualbox modules since you need to run vbox_build_module to build them for each kernel). I was greeted with this message on reboot.
I ended up getting an arch install usb, chrooting, doing pacman -U kernel 2.6.31.4 (the previous kernel version), rebooted, got the same message. Then I went back to the installer and blacklisted all the vbox modules in my modules array (!vboxdrv !vboxnetflt !vboxnetadp) in /etc/rc.conf and that worked.
Previously, whenever I didn't have the vbox modules, it would just say error, couldn't load, not found, or something along those lines and it would keep booting normally.
Can anyone explain to me how/why I got this error instead of the normal (module not found) error?
Offline
Pages: 1