again that hardy heron bug - help, please?

[mala]

I am quite the newbie, please consider this if you answer

After a long time without connection to the internet, hardy heron updated quite thoroughly - after which I could not use vbox any longer. I found a description for this issue under #1622 . I had the same problem as user timtripcony, I received the message "No suitable module for running kernel found." Now what? I did remove the file vbox.cfg before trying.

Any suggestions?

Thanks in advance!

[Sasquatch]

What kernel are you running? It should be, by default, generic. If you run Xen too, and you run on that kernel, then there isn't indeed no compatible kernel to run on, because the Xen kernel is not supported. Also, check if you have the kernel module. You can check that by doing an 'ls /dev/' and see if you have a 'vboxdrv' there. If not, execute 'sudo /etc/init.d/vboxdrv setup'.

[mala]

Thanks for your reply!
ls /dev/ does not list vboxdrv.
After trying the line you suggested,
sudo /etc/init.d/vboxdrv start produces "No suitable module for running kernel found"
sudo /etc/init.d/vboxdrv status produces "VirtualBox kernel module is not loaded"

I don't know what to do now.

After deleting that vbox.cfg - file, clicking the icon on my desktop doesn't do anything at all anymore (at least I think there's a connection ...)

Do you have further suggestions for me, Sasquatch?

[mala]

forgot to mention: I didn't hear about Xen before (just visited wikipedia). I'm not aware of it running on my system, but vbox worked fine for several weeks, so why would it matter?
(once more: truly a newbie)

[mndo]

Probabily in the middle of the updates a new kernel version was installed, so you just need to make sure you have the kernel headers for the kernel you are running

Code: Select all

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

and then

Code: Select all

sudo /etc/init.d/vboxdrv setup

that should be solve it.

Cumps

[mala]

Thanks for answering!

The first line you suggested produced the output that linux-headers-2.6.24-19 are already the current version.
The second one got me exactly the same results as before.

Any further suggestions, please?

[rsgooch]

I am quite the newbie, please consider this if you answer

After a long time without connection to the internet, hardy heron updated quite thoroughly - after which I could not use vbox any longer. I found a description for this issue under #1622 . I had the same problem as user timtripcony, I received the message "No suitable module for running kernel found." Now what? I did remove the file vbox.cfg before trying.

Any suggestions?

Thanks in advance!

Have you installed he Virtual box OSE modules for your kernel? If you have not then you can install them from Synaptic like this:

Applications->Accessories->Terminal
in the Terminal Window type "uname -a" remember or write this down. This is your kernel version.

type "exit" to close terminal window

System->Administration->Synaptic Package Manager

type your password in the dialog box

click search and enter "virtualbox"

In the list find the entry for "virtualbox-ose-modules-generic" and click it.
this is a placeholder for you current kernel verify that synaptic placed an additional tick in the correct kernel version that you wrote down earlier.

Click apply, close synaptic after it finishes installing modules and run virtualbox this should solve your module issues, it solved mine.

[mala]

thanks for your instructions!

So far, I didn't manage, though. Maybe I didn't click enough packages? Do I need everything with 2.6.24-19 in it? There are a few - are there others that need to be included?

Thanks again,
mala

[reilus]

thanks for your instructions!

So far, I didn't manage, though. Maybe I didn't click enough packages? Do I need everything with 2.6.24-19 in it? There are a few - are there others that need to be included?

Thanks again,
mala

I'm having the same problem. When I installed the other packages, and did the status check, the kernel is loaded. However, when I run virtualbox, I still get the same error.

I don't know what the deal is with this thing....