Ask Your Question
0

fedora 18 virtualbox Kernel driver not installed (rc=-1908)

asked 2013-06-06 08:54:05 -0600

aelh9355 gravatar image

updated 2014-09-28 11:09:37 -0600

mether gravatar image

I installed Fedora 18 on my brand new laptop thinkpad x230 after got about 1.4GB update kernel upgrade to 3.9.4-200.fc18.x86_64 , I've installed VirtualBox4.2-4.2.12_84980_fedora18-1.x86_64 - after run virtualbox i got error "virtualbox Kernel driver not installed (rc=-1908)" and after run /etc/init.d/vboxdrv setup :

topping VirtualBox kernel modules                          [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules            [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS[  OK  ]
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

i installed following kernel modules:

#rpm -qa |grep -i kernel
kernel-headers-3.9.4-200.fc18.x86_64
kernel-tools-libs-3.9.4-200.fc18.x86_64
kernel-devel-3.6.10-4.fc18.x86_64
kernel-tools-libs-devel-3.9.4-200.fc18.x86_64
kernel-tools-3.9.4-200.fc18.x86_64
kernel-3.9.4-200.fc18.x86_64
kernel-devel-3.9.4-200.fc18.x86_64
kernel-3.6.10-4.fc18.x86_64
abrt-addon-kerneloops-2.1.4-3.fc18.x86_64
kernel-modules-extra-3.9.4-200.fc18.x86_64
libreport-plugin-kerneloops-2.1.4-4.fc18.x86_64
 and also dkms-2.2.0.3-4.fc18.noarch

/var/log/vbox-install.log:

Uninstalling modules from DKMS
  removing old DKMS module vboxhost version  4.2.12

-------- Uninstall Beginning --------
Module:  vboxhost
Version: 4.2.12
Kernel:  3.9.4-200.fc18.x86_64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.9.4-200.fc18.x86_64/extra/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.9.4-200.fc18.x86_64/extra/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.9.4-200.fc18.x86_64/extra/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxpci.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.9.4-200.fc18.x86_64/extra/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall completed.

------------------------------
Deleting module version: 4.2.12
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxhost/4.2.12/source ->
                 /usr/src/vboxhost-4.2.12

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.9.4-200.fc18.x86_64 -C /lib/modules/3.9.4-200.fc18.x86_64/build M=/var/lib/dkms/vboxhost/4.2.12/build.........
cleaning build area....

DKMS: build completed.

vboxdrv:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.9.4-200.fc18.x86_64/extra/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.9.4-200.fc18.x86_64/extra/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2013-06-06 16:20:39 -0600

hedayat gravatar image

updated 2013-06-06 16:21:34 -0600

Please "listen" to what system is telling you: "modprobe vboxdrv failed. Please use 'dmesg' to find out why". You should provide "dmesg" output, but you didn't. Instead, you've provided lots of not-requested and probably not-useful information. Run '/etc/init.d/vboxdrv setup' and then 'dmesg' to see what is going wrong.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-06-06 08:54:05 -0600

Seen: 2,704 times

Last updated: Jun 07 '13