virtualbox 4.0 problem with /dev/vboxdrv. ubuntu 10-10

Asked by Randall Weston

Installed Virtual-box 4.0 when starting application I get error "Kernel driver not installed (rc=-1908)

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. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

DKMS shows that it is installed --------

(pbiostar@hpbiostar-G31D-M7:~$ sudo apt-get install dkms
[sudo] password for hpbiostar:
Reading package lists... Done
Building dependency tree
Reading state information... Done
dkms is already the newest version.
dkms set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Attempted to run-----

 (hpbiostar@hpbiostar-G31D-M7:~$ /etc/init.d/vboxdrv setup
bash: /etc/init.d/vboxdrv: No such file or directory
hpbiostar@hpbiostar-G31D-M7:~$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
hpbiostar@hpbiostar-G31D-M7:~$

I have read every installation manual and post I could find including Oracle Documentation and can't seem to get it to work.

any help would be appreciated!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu virtualbox-ose Edit question
Assignee:
No assignee Edit question
Solved by:
Randall Weston
Solved:
Last query:
Last reply:
Revision history for this message
Tobias (ulbricht-tobias) said :
#1

Could you provide the output of an attempt to re-install virtualbox:

$ sudo apt-get remove virtualbox-4.0
$ sudo apt-get install virtualbox-4.0

I had no problems running virtualbox then, but I had VB-3.2 installed before, so...

Revision history for this message
Randall Weston (randallweston) said :
#2

I have removed and reinstalled before, here are the results.

hpbiostar@hpbiostar-G31D-M7:~$ sudo apt-get remove virtualbox-4.0
[sudo] password for hpbiostar:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libqt4-opengl libsdl-ttf2.0-0
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  virtualbox-4.0
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 110MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 159870 files and directories currently installed.)
Removing virtualbox-4.0 ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...
Processing triggers for shared-mime-info ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for python-support ...
hpbiostar@hpbiostar-G31D-M7:~$

Re installed

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  virtualbox-4.0
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/56.9MB of archives.
After this operation, 110MB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously deselected package virtualbox-4.0.
(Reading database ... 159286 files and directories currently installed.)
Unpacking virtualbox-4.0 (from .../virtualbox-4.0_4.0.0-69151~Ubuntu~maverick_i386.deb) ...
Processing triggers for ureadahead ...
Processing triggers for shared-mime-info ...
Processing triggers for desktop-file-utils ...
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...
Processing triggers for hicolor-icon-theme ...
Processing triggers for python-support ...
Setting up virtualbox-4.0 (4.0.0-69151~Ubuntu~maverick) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Processing triggers for python-central ...
hpbiostar@hpbiostar-G31D-M7:~$

Still getting error

Kernel driver not installed (rc=-1908)

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. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

Revision history for this message
Randall Weston (randallweston) said :
#3

I also tried to update the kernel with the following with no success

pbiostar@hpbiostar-G31D-M7:~$ sudo apt-get install linux-headers-generic build-essential
[sudo] password for hpbiostar:
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
build-essential set to manually installed.
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

hpbiostar@hpbiostar-G31D-M7:~$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
hpbiostar@hpbiostar-G31D-M7:~$

Revision history for this message
Maarten Jacobs (maarten256) said :
#4

I assume you checked if /etc/init.d/vboxdrv actually exists on your machine? I am running VB 4.0 without issue, although I installed via Synaptic (which shouldn't make a difference, right?). The package properties for VB 4.0 shows me that /etc/init.d/vboxdrv was installed (and it actually resides in that folder).

Revision history for this message
Randall Weston (randallweston) said :
#5

I did check to see if that file exists. and for some reason it is not showing up, Here are the results for a check of that directory

hpbiostar@hpbiostar-G31D-M7:~$ ls /etc/init.d/vboxdr
ls: cannot access /etc/init.d/vboxdr: No such file or directory
hpbiostar@hpbiostar-G31D-M7:~$

I am in the process of deleting all files associated with virtual-box. From the V-box Forum is looks like the sequence in which the installation may have failed to build the kernel, dkms must be installed first and I am not sure that happened. will post results. Thanks for the reply. I have been struggling with this all day!

Revision history for this message
Randall Weston (randallweston) said :
#6

Well that was the Problem!!!!!! I deleted all virtual-box files "complete removal" using synaptic package manager. I also deleted dkms "compete removal".

  I re-installed dkms (sudo apt-get install dkms build-essential linux-headers-generic)

 I then re-installed Virtual-box 4.0 using Synaptic package manager. Opened Virtual-box and was able to access virtual machines.

Thanks for YOUR support, It really helps to get feedback when your are working on problems, I have found Launchpad extremely helpful.