VirtualBox won't run after upgrade to slackware64 current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Rep:
VirtualBox won't run after upgrade to slackware64 current
I upgraded to slackware64_current, and now I can't get any of my virtualbox machines to start.
I get "The VirtualBox kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/veoxdrv. Please reinstall the kernal module by executing '/etc/init.d/vboxdrv.setup"
So I execute /etc/rc.d/rc.vboxdrv setup, and I get:
root@ook:/etc/rc.d# ./rc.vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Trying to register the VirtualBox kernel modules using DKMS ...failed!
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
dmesg tells me:
vboxdrv: version magic '2.6.38.7 SMP preempt mod_unload ' should be '2.6.38.7 SMP mod_unload '
I'm not quite sure what it is trying to tell me, and I have less of a clue what to do about it. I'm currently downloading 13.37, and I'm going roll my system back to that, as I have got to have my VMs running - I make a living on this box (yeah, yeah, I know, it was stupid to upgrade to slackware current on a box I make a living on...<sigh>....it's never failed me before, so I became complacent....)
I'm currently running slackware 64 current as of today (6-1-2011):
Linux ook 2.6.38.7 #3 SMP Sun May 22 16:21:50 CDT 2011 x86_64 AMD Phenom(tm) II X6 1100T Processor AuthenticAMD GNU/Linux
I have 8gb Ram, more than enough memory to go around.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
Maybe I missed it, but did you re-install VirtualBox? Anytime you change the kernel you have to re-install VirtualBox and in the process it rebuilds the its kernel module.
Don't touch your ~.virtualbox directory, just re-install the file from Oracle and you should be fine.
I usually go to /opt/VirtualBox and run the uninstall.sh file, then go to where I store the VirtualBox-x.x.x-xxxxx-Linux_amd64.run package and run it.
You may also have to re-install the extension pack.
Last edited by cwizardone; 06-17-2011 at 10:11 PM.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
Maybe I missed it, but did you re-install VirtualBox? Anytime you change the kernel you have to re-install VirtualBox and in the process it rebuilds the its kernel module.
Don't touch your ~.virtualbox directory, just re-install the file from Oracle and you should be fine.
I usually go to /opt/VirtualBox and run the uninstall.sh file, then go to where I store the VirtualBox-x.x.x-xxxxx-Linux_amd64.run package and run it.
You may also have to re-install the extension pack.
I did indeed reinstall virtual box. Alas, no joy.
I just finished a restore to 13.37, and virtualbox works just fine. My best guess is that something between 13.37 and current changed that breaks virtualbox. If I get the time, I may try upgrading to current again just to see if it does the same thing again. But for now - I work on this box and alas don't have time to play
I used -Current (32 bit) and VB works fine here
If there's a change in the kernel, just run the VB installer again and it should work normally afterwards
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.