Problem with VirtualBox after upgrading kernel to 4.5.2
Hi there,
I've been running VirtualBox 5.0 (now 5.0.20) from the Oracle repository for several months with no problems on my Linux Mint 17.3 box. I have just upgraded the Linux kernel to 4.5.2 through the instructions on this site: https://mintguide.org/system/602-ins...inux-mint.html . It went well, apart from the following error produced a couple of times when installing the relevant debs: Code:
Error! Could not locate dkms.conf file. Code:
Kernel driver not installed (rc=-1908) Does anyone know what my next step should be? |
(more info)
On running dpkg-reconfigure virtualbox-5.0, the result is: Code:
addgroup: The group `vboxusers' already exists as a system group. Exiting. |
Hello Hydrurga,
I have had a similar issue with Virtualbox before. Since you upgraded your kernel, it could be a module issue. run /etc/init.d/vboxdrv setup and let me know the output, then try the following: Code:
# modprobe vboxdrv Sincerely, donald3.heckel |
Hi Donald.
Output of /etc/init.d/vboxdrv setup: Code:
Stopping VirtualBox kernel modules ...done. Code:
Uninstalling modules from DKMS |
Results of modprobes:
modprobe: FATAL: Module vboxdrv not found. and same for others. |
I take it you installed the kernel-headers for the new kernel and, possibly, the whole source also?
|
Quote:
linux-headers-4.5.2-040502-generic_4.5.2-040502.201604200335_amd64.deb linux-headers-4.5.2-040502_4.5.2-040502.201604200335_all.deb linux-image-4.5.2-040502-generic_4.5.2-040502.201604200335_amd64.deb Running dkms autoinstall also fails to upgrade the other package in dkms, ndiswrapper, with the same error about a missing gcc command line option -fstack-protector-strong in its error log. It's looking likely that I need to upgrade gcc, but I'm not yet sure about how I go about this. |
Hello hydraruga,
This is a common issue amongst kernel upgrades and virtualbox. Hang in there. There we go ;) Your Virtualbox application still thinks you're running your old kernel. Now we are making progress. Try adding the following modules to your /etc/modules: Code:
vboxdrv vboxpci vbox-host-dkms vboxnetadp vboxnetflt And then reboot and run /etc/init.d/vboxdrv restart again. Let me know how it goes and paste your output again if something goes wrong. Sincerely, donald3.heckel |
Quote:
Also, just in case it's important, my system doesn't have a directory /etc/modules. |
Update:
It's showing this for the other modules too? :( If all else fails, you could try a Virtualbox reinstall. Code:
sudo apt-get autoremove virtualbox Download: http://download.virtualbox.org/virtu...inux_amd64.run And then run: Code:
chmod +x VirtualBox-5.0.20-106931-Linux_amd64.run Sincerely, donald3.heckel |
Update:
No problem hydra. Code:
sudo nano /etc/modules Update: You could just run the following: Code:
sudo echo "vboxdrv vboxpci vbox-host-dkms vboxnetadp vboxnetflt" >> /etc/modules donald3.heckel |
Thanks Donald, but I suspect that the compiles will fail unless I can update gcc to 4.9 in order to support the -fstack-protector-strong command line option.
The questions arise then: (i) how would I do this? (ii) what are the risks involved in upgrading gcc on an otherwise stable system (if 4.9 becomes my default compiler then I'd better be pretty sure that any future programs to be installed which expect the 4.8 compiler are not going to fall over i.e. that there is perfect backwards-compatibility)? |
Quote:
|
I suggest you run the .run file instead of compiling it from source. It should build everything for you.
You're doing good. Sincerely, donald3.heckel |
Quote:
|
Quote:
|
Quote:
sudo apt-get autoremove virtualbox sudo apt-get purge virtualbox how will this affect my current images (of which there are several) once I've reinstalled VirtualBox? Will I have to reconnect them all? |
Quote:
Info: About the /etc/modules, it will load those modules on boot if all goes well. Sincerely, donald3.heckel |
Your Virtualbox images should be unaffected. When you reinstall, be sure to add them back in.
If you are too concerned, I suggest you temporarily move them out of the way say ~/vboxBaks for example. Sincerely, donald3.heckel |
Let me know how it goes.
Sincerely, donald3.heckel |
OK, I uninstalled, purged and installed VirtualBox exactly as you suggested. The result of the installation was:
Code:
Verifying archive integrity... All good. The build log complains about the lack of support for -fstack-protector-strong as before. |
Ahhh okay.
Assuming the module loading won't work, Post the output of uname -r. Sincerely, donald3.heckel |
Quote:
Make sure you have them loaded. If it does not work, let me know the output of your uname -r. |
Quote:
Code:
lp uname -r gives 4.5.2-040502-generic |
Donald, thanks for all your help, but I'm going to restore my previous o/s from backup (I tried rebooting into the older kernel but VirtualBox is now balking for another reason - it will be cleaner to just restore things as they were). I reckon my experiment with upgrading my kernel is at an end... ;)
|
No problem. I hope you found this useful. At least we tried! :D
Sincerely, donald3.heckel |
Quote:
header files, and all that other stuff it needs to build what it needs to? I did a remove everything, but my files with installes in them. then reinstalled it, let it pull in the dependices and do its thing, it saved me a lot of problems and such. mine just picks the installed VirtOS's when its reinstlled due to the config dir it puts in /home/user/xxx you might have to twik it a little to get them working, but you do not lose anything. I didn't anyways. |
All times are GMT -5. The time now is 12:24 PM. |