LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-17-2011, 05:34 PM   #1
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 337

Rep: Reputation: 27
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.
 
Old 06-17-2011, 06:30 PM   #2
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
Quote:
I upgraded to slackware64_current
Did you happen to upgrade from Slackware 32 bit? If so, you have to upgrade to the 64 bit version of VB.
Regards,
Bill
 
Old 06-17-2011, 06:44 PM   #3
Reuti
Senior Member
 
Registered: Dec 2004
Location: Marburg, Germany
Distribution: openSUSE 11.4
Posts: 1,319

Rep: Reputation: 252Reputation: 252Reputation: 252
What happens when you issue modprobe vboxdrv by hand?
 
Old 06-17-2011, 07:35 PM   #4
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 337

Original Poster
Rep: Reputation: 27
Quote:
Originally Posted by Reuti View Post
What happens when you issue modprobe vboxdrv by hand?
root@ook:/etc/rc.d# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.38.7/misc/vboxdrv.ko): Invalid module format
 
Old 06-17-2011, 07:37 PM   #5
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 337

Original Poster
Rep: Reputation: 27
Quote:
Originally Posted by TSquaredF View Post
Did you happen to upgrade from Slackware 32 bit? If so, you have to upgrade to the 64 bit version of VB.
Regards,
Bill
No, I've always used the 64bit version. I even tried to install the 32 bit version but it detects the 64 bit OS and won't install.
 
Old 06-17-2011, 09:57 PM   #6
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,233

Rep: Reputation: 176Reputation: 176
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.
 
Old 06-18-2011, 12:02 AM   #7
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 337

Original Poster
Rep: Reputation: 27
Quote:
Originally Posted by cwizardone View Post
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
 
Old 06-18-2011, 12:10 AM   #8
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 433

Rep: Reputation: 30
I tried to install VB 3.0.x in Slackware-current, and no way.
Only install VB 4.0.x instead ...

What version of VB are you?
 
Old 06-18-2011, 05:53 AM   #9
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,550

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
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
 
Old 06-18-2011, 07:13 AM   #10
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 475

Rep: Reputation: Disabled
Quote:
Originally Posted by Ook View Post
root@ook:/etc/rc.d# modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.38.7/misc/vboxdrv.ko): Invalid module format
cd to the /lib/modules/2.6.38.7/misc directory and run file on it, it should show as below:
Code:
bash-4.1$ file *
vboxdrv.ko:    ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped
vboxnetadp.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped
vboxnetflt.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped
I am running Virtual Box (installed using VirtualBox-4.0.8-71778-Linux_amd64.run) just fine in Slackware64-current.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware64 -current, SlackBuild's gksu problems run-helper... linus72 Slackware 5 07-15-2010 08:24 AM
[SOLVED] X Fails To Start After Upgrade to Slackware64-current hkothari Slackware 7 03-06-2010 09:40 PM
[SOLVED] Video Problems in VirtualBox on Slackware64-current TSquaredF Slackware 8 10-20-2009 11:44 PM
A question regarding Slackware64-current upgrade em21701 Slackware 4 08-09-2009 08:22 AM
Slackware64-current : can't have lilo updating the boot loader after kernel upgrade Didier Spaier Slackware 3 07-21-2009 08:00 AM


All times are GMT -5. The time now is 03:36 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration