Ubuntu Installation :: VirtualBox - Kernel Driver Not Installed After Upgrade To Lucid?
May 4, 2010
I upgraded to Lucid last night, and I'm getting this error when I try to run virtualbox-ose:
Quote:
Kernel driver not installed (rc=-190 Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv' as root.
I try it, then I get:
Quote:
modprobe vboxdrv
FATAL: Module vboxdrv not found.
I have no idea what's going on. Can anyone help? The version of virtualbox is 3.1.6-dfsg-2ubuntu2
when I open virtualbox OSE and tried to run a vm i get this error
Code:
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. Re-setup 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. So i tried doing what it said and I got this error when i tried to run /etc/init.d/vboxdrv setup (as root)
Code:
Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged.Recompiling VirtualBox
[code]....
Then i ran dmesg and there was a ton of stuff that seemed to be unreleated so i ran dmesg -c to clear it. then i ran the vboxdrv this again then checked dmesg again expecting there to be nothing but the vboxdrv stuff but it was still blank.I really dont know what to do at this point I tried uninstalling and reinstalling but that makes no difference
I tried to install the new Vbox 3.2.6 through rpm as a guide told me but I first had errors with the older vbox dependencies, so I uninstalled vbox 3.1.8.2 and now I am with a vbox period. Is there something I can do to fix this I tried this tutorial didn't work for me [URL] and another on the fedora forum (lost the history). error I get is Recompiling VirtualBox kernel module [FAILED] and 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.
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. I've dkms installed and did a reboot as well.
I can see this error occurring in multiple past versions of suse. The answer seems to involve recompiling the open source version of VBox, but this is surely overkill. Isn't there a way to either a)get the right kernel version of VBox for 11.3 or b)set whatever permissions are required.
In all the answer so far I can't see a solution I can understand for these combinations, sues 11.3 and VBox 3.2.8. The error is consistent, and if the install doesn't work properly (it took my a few attempts even to install it without error messages) then surely its an issue either for Oracle or Suse? It runs ok but hwen trying to fire up a newly created XP VM this error message occurs trying to switch from W764bit to suse11.3 64bit
Since my distribution upgrade to 10.04 my VirtualBox guest of XP SP3 will not boot, it bluescreens and reboots. I can boot the guest in last known good config and in safe mode but I have no CDROM. I attempted a tools install over the lan but that resulted in the same blue screen. Tried installing the virtualbox-3.2 beta package and guest tools and had the same results..
I wonder if others have upgraded their Lucid kernel using the deb [URL]..repository. I have been using the repository for some time now without any apparent problems, and have gone from 2.6.36-1, through 2.6.37-10, and am now on 2.6.37-12.
All of these seem to work with no problems at all, but I am just wondering if other users can also report success, or if there are any trip-ups that might occur. I still keep updating the "standard" kernel from the main repos, ie 2.6.32-27, so I have that as a backup, but I'm just very curious about other people's findings.
I read recently about security flaws in the ubuntu kernel, and when I checked my kernel, it is 2.6.32-29-generic. I looked in synaptic, and I have the linux-generic meta-package - which should ensure upgrade to the latest kernel, and yet this is not being updated when I run update manager. There is a linux-image-2.6.35-25-generic, but the advice is not to install this directly (to avoid breaking dependencies, etc.), but to install the meta-package instead. Yet, the meta-package doesn't seem to be doing what is should do.
I want to use my video card, but after upgrade i got this message:
You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
will be apreciaTED, after running from terminal I got this
CODE: rey@rey-desktop:~$ sudo nvidia-xconfig [sudo] password for rey: Using X configuration file: "/etc/X11/xorg.conf". Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup' New X configuration file written to '/etc/X11/xorg.conf'
Recently, I installed a fresh 64bit Lucid Lynx on my Lenovo B450 laptop (previously on Mint8 64bit, based on Karmic). It's been really nice and speedy except for one thing - USB transfers to thumb drives and external hard drives were really slow (just like in the older Ubuntu releases). I had found some forum discussions on a fix to this by way of a kernel upgrade so I decided to go for it.
Went ahead and downloaded the kernel DEBs from [URL] and installed them. Voila! USB speed issue was fixed! Everything else seemed to work fine, except for some minor troubles with burning CDs and DVDs (I think I need to upgrade the drive's firmware - pretty bad situation as the update only runs on Windows).
However, the one 'bug' or 'annoyance' I noticed straight away was that my wireless wouldn't autostart after booting into the OS with the new 2.6.34-020634-generic (x86_64) kernel. I'd have to right-click on the NetworkManager icon on the notification tray and left-click '[ ] Enable Wireless' to flag the checkbox and my wireless would come right up and work ok (WPA2 at home, WEP at the office). Not a major problem, but this has been pretty irritating to say the least.
I am running Lucid Lynx kernel 2.6.32.24. Soon after the latest kernel update I noticed that Virtualbox would not launch when I clicked on the icon. I have searched the Internet for days, tried numerous possible fixes, over hours of effort, but can't get it working at all. Ubuntu Lucid runs great!! There are no errors just a few blinks of the hard drive indicator and nothing. Is there anyone out there that has seen this same issue?
I've just installed Lucid Lynx on both my machines in the interest of sitting and waiting for the Unity/Gnome 3 storm to blow over. On the HP (see below), everything works great, and I've followed instructions online on how to upgrade to LibreOffice, upgrade the kernel to 2.6.38 using the kernel PPA, etc.
However, on the IBM, I'm using Nvidia proprietary graphics drivers. These work well on the stock kernel that 10.04 installed (2.6.32-32), but installing 2.6.38 seems to break the driver. If I install the driver first, and then the kernel on top, X stops working and I have to revert to the default, generic driver to get back in. Once there, I cannot install the driver again. The Additional Drivers dialog goes through the motions, but then drops a "systemerror: installarchives() failed" error message.
So, is there a different version of the driver I should be trying to install? I should clarify at this point I tried all three options the Additional Drivers dialog provided me, all gave the same result (version 96, version 173, and version current).
Or should I leave the kernel at 2.6.32? Is there any downside to leaving it?
I had no problems up to the newest kernel version. But for 2.6.40-4 akmods fails to build the kmod with the following error:
Code: Building RPM using the command '/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.40-4.fc15.x86_64 /usr/src/akmods/VirtualBox-OSE-kmod.latest' Building modules, stage 2. MODPOST 1 modules CC /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-4.fc15.x86_64/vboxnetflt/vboxnetflt.mod.o LD [M] /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40- [Code]...
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/2.6.37.1-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I just did the upgrade and I want to turn off the display after 30 minutes. I check that selection but the display does not turn off after 30 minutes. It is still on. I enabled this setting through the power management. The screen saver is on, go to blank display but the monitor does not turn off.
On Windows, dual boot on the same machine, the monitor does display off. I don't know if this is part of the problem or not, but when I go to "System -> Preferences", there are two different "Screensaver" options.
I've been using an NVIDIA driver from NVIDIA's site (190.53) for a while. Now I want to upgrade to Lucid. 1) Is it recommended to uninstall this driver prior to upgrading to Lucid? 2) If yes, how do I go about this? Please be specific, since I don't want to presume anything and make a mistake.
Trying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS removing old DKMS module vboxdrv version 3.1.6 Deleting module version: 3.1.6 completely from the DKMS tree. Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source -> /usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.32.11-99.fc12.i686.PAE cannot be found at /lib/modules/2.6.32.11-99.fc12.i686.PAE/build or /lib/modules/2.6.32.11-99.fc12. code....
When I start up a virtual machine in Virtualbox on Suse 13.1 I see this message: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.
I have downloaded vbox from its site and installed it. I created a vm but when I try to start it, 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.
And when I try 'sudo /etc/init.d/vboxdrv setup', I get: Stopping VirtualBox kernel modules done Uninstalling old VirtualBox DKMS kernel modules done Trying to register the VirtualBox kernel modules using DKMS failed (Failed, trying without DKMS) Recompiling VirtualBox kernel modules failed (Look at /var/log/vbox-install.log to find out what went wrong)
And this is /var/log/vbox-install.log: Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I have installed the newer kernel 2.6.35.4 and everything seems fine. To compile it, I followed this tut, [URL]. The problem I have is everytime I try to install anything, I get an error "bcmwl-kernel-source failed to install or upgrade". The installation completes for the default 2.6.32.24 generic kernel but fails for this newer kernel.
Any software I try to install now fails for the .35 with the same error. I have attached 3 screenshots showing the error message in more details hopefully. I had installed the .34 kernel and had the exact problem (screenshot.jpg). Error message is shown very clearly in third attachment, sorry I couldn't manage to copy the error and paste it.
I have checked the known issues and the sticky post, it does not seem to be related. I have Ubuntu as my host OS and I want to run Windows as a guest.
Now, Here is the error:
Quote:
Kernel driver not installed (rc=-190
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. I have done the obvious:
I still have the same error. I just updated from Ubuntu 10.04 to 10.10, then I was prompted by virtual box to update to the newest version, then this happened.
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
I'm using Slackware 13.1 32bit and can't run virtualbox when I try to boot the virtual machine it shows me a window with the following message:
Quote:
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' run - /etc/rc.d/rc.vboxdrv setup
Quote:
Stopping VirtualBox kernel module ...done. Recompiling VirtualBox kernel module ...failed! (Look at /var/log/vbox-install.log to find out what went wrong) Check /var/log/vbox-install.log
Quote:
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.33.4-smp/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( echo;
I have a host ubuntu 11.04 with guest window 7, I have installed ubuntu OSE then install windows 7. Now I want to copy some files to windows 7 running on OSE on windows 7. How do I do this ?
I'm currently using the PUEL version of Virtualbox 3.0.12 and whenever I open it, it prompts me to update - see screengrab.
Clicking that link and choosing to open it via the package installer (see screengrab) results in the error screen below - another screengrab.
I then realised the deb file was named Jaunty, so went to the Vbox website to download the Karmic file.
Running that via package installer produces the same error - Error: Conflicts with the installed package 'virtualbox-3.0'
Do I need to remove the old version first? If so, how do I do that (given that this is the PUEL version not the open-source version) and will my existing virtual machines (I've got WinXP and ChromeOS) be safe and still work afterwards?
My reason for wanting to upgrade is to virtually try Ubuntu 10.4 which I just cannot get to run or install in Vbox (either from a CD or from the iso image)
Anyone know of a good guide to use reinstalling a wireless driver using ndiswrapper after a kernel updates? I seem to have to do it a lot, and I'm looking for some good directions.
I have an Nvidia graphics card,... actually I manage several workstations that run centos and have an nvidia video card. I also have a personal computer with ubuntu and an nvidia network card.
I would like to do a regular automatic update of those Centos workstations. (With a pilot group to test and then a full roll-out). Until oktober 2009 no major difference in automatic updating ubuntu and centos (apart from the differences between apt and yum):
After a kernel upgrade, the systems can not boot into it's Xorg gui, because the nvidia driver must be rebuild (=not recompiled, because this is partially object code, the driver is not opensource).
But from ubuntu 9.10 onwards, the kernel update process checks for the presence of propietary drivers like those of nvidia and does a rebuild on the reboot, so that the system can succesfully boot into the xorg GUI (and gdm or kdm) My question is: Are ther any plans for Centos to do the same, this would relief me from some upgrade hassle for the Centos workstations that I manage. Or does anyone know about a (good) automagic workaround?
