LinuxQuestions.org
Help answer threads with 0 replies.
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 12-25-2012, 07:12 AM   #1
lkraemer
Member
 
Registered: Aug 2008
Posts: 111

Rep: Reputation: 10
VirtualBox Kernel Driver Missing after Update?


I'm running Slackware 14 (32 Bit) and I have VirtualBox 4.20 installed.

After the update a few days ago to the 3.7.1-smp Kernel, I can't get VirtualBox to run.
I keep getting the following ERROR Message.

Quote:
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
Obviously the "/etc/init.d/vboxdrv setup" command doesn't work in Slackware 14.
(NOTE: Slackware 14 uses /etc/rc.d/rc.vboxdrv setup)

I've tried, as root to reinstall VirtualBox with:
Code:
sh VirtualBox-4.2.0-80737-Linux_x86.run
which should have rebuilt the Kernel module, from what I've read on this forum, but I still get the error message.

The reinstall appears to have rebuilt the Kernel module, if I can believe the messages:
Code:
root@slackware:/home/larry/Downloads/VirtualBox-4.2.0# sh VirtualBox-4.2.0-80737-Linux_x86.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation............
VirtualBox Version 4.2.0 r80737 (2012-09-13T06:21:32Z) installer
Removing previous installation of VirtualBox 4.2.0 r80737 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

root@slackware:/home/larry/Downloads/VirtualBox-4.2.0#
Here is the output of lsmod:
Code:
bash-4.2$ lsmod                  
Module                  Size  Used by
snd_seq_dummy           1120  0 
snd_seq_oss            24893  0 
snd_seq_midi_event      4569  1 snd_seq_oss
snd_seq                41529  5 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy
snd_seq_device          4245  3 snd_seq,snd_seq_oss,snd_seq_dummy
snd_pcm_oss            33574  0 
snd_mixer_oss          12984  3 snd_pcm_oss
ipv6                  241406  30 
cpufreq_ondemand        5751  2 
speedstep_lib           2568  0 
lp                      7120  0 
ppdev                   4743  0 
parport_pc             16628  0 
parport                25872  3 lp,ppdev,parport_pc
fuse                   60081  3 
uvcvideo               62628  0 
videobuf2_vmalloc       1889  1 uvcvideo
hid_generic              734  0 
videobuf2_memops        1679  1 videobuf2_vmalloc
usbhid                 32331  0 
videobuf2_core         20745  1 uvcvideo
hid                    68013  2 hid_generic,usbhid
videodev               78949  2 uvcvideo,videobuf2_core
joydev                  7561  0 
i915                  464467  2 
acpi_cpufreq            6375  1 
mperf                    920  1 acpi_cpufreq
intel_agp               8585  1 i915
ath9k                  85726  0 
ath9k_common            1565  1 ath9k
ath9k_hw              340460  2 ath9k_common,ath9k
drm_kms_helper         22428  1 i915
drm                   181048  3 i915,drm_kms_helper
jme                    32718  0 
ath                    12310  3 ath9k_common,ath9k,ath9k_hw
snd_hda_codec_hdmi     24945  1 
freq_table              2151  2 cpufreq_ondemand,acpi_cpufreq
psmouse                64034  0 
processor              24177  1 acpi_cpufreq
i2c_i801               12296  0 
mac80211              360113  1 ath9k
lpc_ich                10166  0 
snd_hda_codec_conexant    39202  1 
sdhci_pci               8906  0 
sdhci                  21449  1 sdhci_pci
intel_gtt              12501  3 i915,intel_agp
video                  10046  1 i915
thermal                 6910  0 
thermal_sys            13032  3 video,thermal,processor
coretemp                4983  0 
cfg80211              153879  3 ath,ath9k,mac80211
asus_laptop            15659  0 
i2c_algo_bit            4576  1 i915
sparse_keymap           2493  1 asus_laptop
snd_hda_intel          23291  4 
rfkill                 12745  4 cfg80211,asus_laptop
mmc_core               75525  2 sdhci,sdhci_pci
mei                    27563  0 
jmb38x_ms               7250  0 
intel_ips              10060  0 
microcode              10006  0 
mii                     3400  1 jme
agpgart                21960  3 drm,intel_agp,intel_gtt
battery                 9693  0 
i2c_core               16712  6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev
memstick                5545  1 jmb38x_ms
snd_hda_codec          83143  3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel
snd_hwdep               4867  1 snd_hda_codec
snd_pcm                62564  4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc          6127  2 snd_pcm,snd_hda_intel
snd_timer              14767  2 snd_pcm,snd_seq
hwmon                   1002  2 coretemp,thermal_sys
snd                    44778  16 snd_pcm_oss,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_oss,snd_seq_device,snd_mixer_oss
soundcore               4379  3 snd
serio_raw               3546  0 
evdev                   7813  11 
input_polldev           2167  1 asus_laptop
button                  3737  1 i915
ac                      2660  0 
loop                   14586  0 
bash-4.2$
I've even rebooted, just to make sure that wasn't the problem.
What am I missing, or overlooking? I need VirtualBox running again.

Thanks.

Larry

Last edited by lkraemer; 12-25-2012 at 05:51 PM.
 
Old 12-25-2012, 07:39 AM   #2
StreamThreader
Member
 
Registered: Mar 2012
Location: Ukraine/Odesa
Distribution: Slackware
Posts: 96

Rep: Reputation: 9
In rc.xxx files search string:
exit 0
or another exit command in rc scripts.
 
Old 12-25-2012, 08:01 AM   #3
lkraemer
Member
 
Registered: Aug 2008
Posts: 111

Original Poster
Rep: Reputation: 10
There must be a problem when trying to re-install the same version, that the Kernel modules do not get built, because I decided to update to version 4.2.6 from 4.2.0 and I noticed that the script took longer to run. Likewise, The same kernel modules built message lead me to believe the Kernel Modules were rebuilt. And like MAGIC, VirtualBox is up and running. But, what happens to the folks that are running the current version?

Code:
root@slackware:/home/larry/Downloads/VirtualBox-4.2.6# sh VirtualBox-4.2.6-82870-Linux_x86.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation............
VirtualBox Version 4.2.6 r82870 (2012-12-19T14:43:33Z) installer
Removing previous installation of VirtualBox 4.2.0 r80737 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

root@slackware:/home/larry/Downloads/VirtualBox-4.2.6#
WHEW! I'm marking this as solved for me, but there are problems that still exist and should be easily duplicated.

THANKS.

Larry
 
Old 12-25-2012, 01:29 PM   #4
Grischuna
Member
 
Registered: Mar 2009
Distribution: Slackware64 14.0 multilib
Posts: 44

Rep: Reputation: 0
Quote:
Originally Posted by lkraemer View Post
There must be a problem when trying to re-install the same version, that the Kernel modules do not get built, because I decided to update to version 4.2.6 from 4.2.0 and I noticed that the script took longer to run. Likewise, The same kernel modules built message lead me to believe the Kernel Modules were rebuilt. And like MAGIC, VirtualBox is up and running. But, what happens to the folks that are running the current version?

Code:
root@slackware:/home/larry/Downloads/VirtualBox-4.2.6# sh VirtualBox-4.2.6-82870-Linux_x86.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation............
VirtualBox Version 4.2.6 r82870 (2012-12-19T14:43:33Z) installer
Removing previous installation of VirtualBox 4.2.0 r80737 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

root@slackware:/home/larry/Downloads/VirtualBox-4.2.6#
WHEW! I'm marking this as solved for me, but there are problems that still exist and should be easily duplicated.

THANKS.

Larry

Hello,

I faced the same issue but fixed it with the help of AlienBob's entry in his blog a while ago. Here the URL. Hope it can help others.

Cheers
 
Old 12-25-2012, 10:39 PM   #5
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 508

Rep: Reputation: Disabled
Quote:
Originally Posted by lkraemer View Post
There must be a problem when trying to re-install the same version, that the Kernel modules do not get built, because I decided to update to version 4.2.6 from 4.2.0 and I noticed that the script took longer to run. Likewise, The same kernel modules built message lead me to believe the Kernel Modules were rebuilt. And like MAGIC, VirtualBox is up and running. But, what happens to the folks that are running the current version?
The is no problem with re-installing the same version of VirtualBox. I do it all the time. Did it after I upgraded to the latest kernel in -current.

After upgrading my kernel, I verified that the symlinks pointed to the new kernel, ran mkinitrd for the new kernel, ran lilo, then reboot. Then ran /etc/rc.d/rc.vboxdrv setup or ./VirtualBox-version-arch.run. That last part is important, you must rebuild the vbox kernel modules under the new kernel. I suspect that was the magic.
 
Old 12-26-2012, 10:55 AM   #6
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 492
Blog Entries: 1

Rep: Reputation: 55
In my case, after I accomplished all of the upgrades, including the 3.7.1 kernel, the vbox (4.2.0) drivers would not build. I got an error saying that building the drivers had failed & to check the log. The log was not helpful. I upgraded to VB-4.2.6 & all worked well.
Regards,
Bill
 
  


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
LXer: The VirtualBox Kernel Driver Is Tainted Crap LXer Syndicated Linux News 0 10-11-2011 12:50 PM
VirtualBox broken after kernel update in Arch Linux MTK358 Linux - Software 10 09-06-2010 08:51 PM
Virtualbox Error - Kernel driver not installed (rc=-1908) callumacrae Linux - Software 11 10-28-2009 03:13 PM
Virtualbox driver missing on ose using Mandriva 8 Fred Caro Mandriva 18 12-06-2008 08:43 AM
Virtualbox opensource missing VER-VM-DRIVER Fred Caro Linux - Newbie 3 06-02-2008 10:39 AM


All times are GMT -5. The time now is 11:37 PM.

Main Menu
Advertisement
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