Trouble setting up VirtualBox

UltraZelda64 · 2012-06-27 23:07:49

Running the latest stable CrunchBang with backports; just did an apt-get update and apt-get dist-upgrade not too long ago so it's pretty freshly up-to-date. I tried installing VirtualBox (not the first time; last time, I uninstalled it because I couldn't get it to work). Upon installation, the following errors are produced:

Stopping VirtualBox kernel modules.
Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed!
 failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.

...

Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Stopping VirtualBox kernel modules.
Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed!
 failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.

The uname -a command gives me:

Linux ramirez 3.2.0-0.bpo.1-amd64 #1 SMP Sat Feb 11 08:41:32 UTC 2012 x86_64 GNU/Linux

Yet, according to Synaptic, the following packages are installed:
linux-headers-3.2.0-0.bpo.2-common, linux-headers-3.2.0-0.bpo.2-amd64

...and I just installed the kernel sources for 3.2.0 just to be safe. The kernel version "bpo.1" doesn't seem to match up with the installed headers "bpo.2", that's all I can tell.

Last edited by UltraZelda64 (2012-06-27 23:21:09)

fortyseven · 2012-06-28 07:58:45

I had similar issues a while ago; iirc, it had something to do with not having a PAE kernel or something, I'm not too sure.

el_koraco · 2012-06-28 08:14:37

UltraZelda64 wrote:

The uname -a command gives me:
Linux ramirez 3.2.0-0.bpo.1-amd64 #1 SMP Sat Feb 11 08:41:32 UTC 2012 x86_64 GNU/Linux
Yet, according to Synaptic, the following packages are installed:
linux-headers-3.2.0-0.bpo.2-common, linux-headers-3.2.0-0.bpo.2-amd64
...and I just installed the kernel sources for 3.2.0 just to be safe. The kernel version "bpo.1" doesn't seem to match up with the installed headers "bpo.2", that's all I can tell.

You are running the bpo1 kernel and have the bpo2 headers. Match those, either bpo1 kernel plus headers or bpo2 kernel and headers. The easiest thing is to run

sudo apt-get install linux-headers-$(uname -r)

UltraZelda64 · 2012-06-28 23:51:18

I tried the above command and I get this:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package linux-headers-3.2.0-0.bpo.1-amd64
E: Couldn't find any package by regex 'linux-headers-3.2.0-0.bpo.1-amd64'

I didn't see any bpo.1 stuff when looking around in Synaptic either.

I'm about to try just installing the bpo.2 kernel and try booting from it... don't know why I have to, because I would think the kernel headers for the kernel that was installed by default should either be installed to begin with or be available in the repository.

el_koraco · 2012-06-28 23:55:17

Ah, I see the bpo1 kernel and headers are no longer available in the repositories. Install the bpo2 kernel and try again. This is some repository cockup.

UltraZelda64 · 2012-06-29 00:03:03

Yep--I'm back after a reboot into the new kernel, uninstalling and reinstalling VirtualBox. This time upon installation it told me that it found one kernel that it could build a kernel module for and preceded to do it.

Two questions though. Isn't there some command that re-initiates the setting up of a package without reinstalling it? I can't remember what it is, but I thought for sure there was one in Debian.

And also... what *is* the difference between the bpo.1 and bpo.2 kernels?

And thanks for the help!

el_koraco · 2012-06-29 00:21:50

There is dkms, it builds out of tree kernel modules. It needs headers for a new kernel though, so you got a catch 44 situation. Plus, it depends on how stuff is packaged, and you can't be 100 percent sure with third party packages.

pvsage · 2012-06-29 05:12:07

el_koraco wrote:

Ah, I see the bpo1 kernel and headers are no longer available in the repositories. Install the bpo2 kernel and try again. This is some repository cockup.

It's not a cockup; apparently the Debian developers decided the bpo.2 kernel was stable enough for them to purge the bpo.1 kernel from their repos.

@UZ64: If you have any trouble with bpo.2, I can hook you up with whatever you need for the bpo.1 kernel and/or headers.

UltraZelda64 · 2012-06-29 22:06:15

Nah, the new kernel seems to be running fine. I'd just like to know what the difference is between the two.

Last edited by UltraZelda64 (2012-06-29 22:08:41)

el_koraco · 2012-06-29 22:35:19

UltraZelda64 wrote:

I'd just like to know what the difference is between the two.

bpo1 is something like upstream kernel 3.2.1 and bpo2 is 3.2.18 or something. Run an apt-cache policy on the kernel and you'll get the exact upstream number. Debianizing the name is what confused you here.

hinto · 2012-07-01 03:23:41

smxi keeps me humming right along... even with new kernels.
-Hinto

CrunchBang Linux

SEARCH

#1 2012-06-27 23:07:49

Trouble setting up VirtualBox

#2 2012-06-28 07:58:45

Re: Trouble setting up VirtualBox

#3 2012-06-28 08:14:37

Re: Trouble setting up VirtualBox

#4 2012-06-28 23:51:18

Re: Trouble setting up VirtualBox

#5 2012-06-28 23:55:17

Re: Trouble setting up VirtualBox

#6 2012-06-29 00:03:03

Re: Trouble setting up VirtualBox

#7 2012-06-29 00:21:50

Re: Trouble setting up VirtualBox

#8 2012-06-29 05:12:07

Re: Trouble setting up VirtualBox

#9 2012-06-29 22:06:15

Re: Trouble setting up VirtualBox

#10 2012-06-29 22:35:19

Re: Trouble setting up VirtualBox

#11 2012-07-01 03:23:41

Re: Trouble setting up VirtualBox

Board footer