![]() Also, my bootloader boots the kernel by name, regardless of whether or not newer kernels exist.Īs mentioned in my original post, this problem appears to be triggered by booting the Ubuntu OS on different hardware than it was running on previously. Auto update is off and I've verified that the kernel version is not changing. I am positive I'm not updating to a new kernel. Try modprobe vboxdrv and see what happens. Check if there are vboxdrv / vboxnetflt / vboxnetadp modules available for your current kernel. So if you are at the state where the modules are not loaded then try to find out why. ![]() Once the kernel modules are built for the current kernel, they load fine here during every boot. If you do NOT update the kernel (even no silent update) then you could try to debug this problem yourself - I cannot reproduce it here using a plain vanilla Lucid installation. The task of the recompilation is usually done by DKMS. From your description I assume that you just did a kernel update and there was no kernel module available for the new kernel. ![]() A kernel driver not installed usually happens if there is either no module available for the current running kernel or if (for some reason) the startup script which ensures that the kernel modules are loaded is not properly executed during boot. ![]() This happens only occasionally and a system reboot will sometimes "solve" the problem. It seems to occur after we have been running the system on one PC and then boot the same host image on a different PC. We also have been experiencing this Kernel driver not installed error on occasion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |