no module built for 2.6.24-17-generic

Can confirm this issue. Though we should be able to build our own modules based on virtualbox-ose-source using module-assistant, I'd love to see updated packages in the repos. What's the official approach to do that?

Thanks,
Daniel

Yes there is no vbox module for 2.6.24-17 kernel...

Any idea when the kernel modules will be released?

Thanks
JK

On Mon, May 5, 2008 at 10:41 AM, Daniel Rheinbay <email address hidden> wrote:
> Can confirm this issue. Though we should be able to build our own
> modules based on virtualbox-ose-source
I tried `apt-get source --compile virtualbox-ose-source` but it complaied:
...
dpatch apply-all
applying patch 01-no-64bit-guest to ./ ... ok.
applying patch 02-2.6.25 to ./ ... ok.
applying patch 03-config-kmk to ./ ... ok.
applying patch 04-localconf-kmk to ./ ... failed.
...
> using module-assistant,
I found no reference of virtualbox in the list of modules displayed by
module-assistant.

--
Lucian

This bug was fixed in the package virtualbox-ose-modules - 24.1

---------------
virtualbox-ose-modules (24.1) intrepid; urgency=low

  * Rebuild for 2.6.24-17 (LP: #226753)

 -- Daniel Hahler <email address hidden> Mon, 05 May 2008 17:12:54 +0200

Will this package be uploaded to the Hardy repositories? I see in the changelog that is targeted for Intrepid.

virtualbox-ose-modules (24.1) __intrepid__ ; urgency=low

Jordi, thanks for catching my mistake.
I've re-uploaded it as 24.0.1 for hardy-proposed, now waiting for approval.

Accepted into -proposed, please test and give feedback here

I am writing this 16 hours after the post directly above this post, so it looks like 16 hours later the 24.0.1 version is still not there ( no .17 kernel ) is that right ?

The package is queued for building (since 18 hours already, see https://edge.launchpad.net/ubuntu/hardy/+source/virtualbox-ose-modules/+builds).
The build daemons (https://edge.launchpad.net/+builds) appear to be busy building all the packages for Intrepid. So you "just" have to wait. As a workaround, you could use the old kernel until then. I'll try to reach somebody on IRC about it.

@Daniel
I just checked to see if the release is available yet and it does not look like it is. your links show that it was compiled last night or the job ran, I'm not real sure if it ran clean or not, there was too much for me to understand in the logs. anyway, I'm not rushing because I took your advice and am using the official release kernel instead of the proposed kernel to work around this. its all good. my suspicions are that there may have been an issue with this job and thats why its not yet showing up in the repo. anyway, I have a working VM now , so there is no great rush now, just idle curiosity to see this bug closed.

The binary packages are now waiting in the NEW queue (https://edge.launchpad.net/ubuntu/hardy/+queue) (since 18 hours).
You could already install the .deb manually from there (e.g. using GDebi or "sudo dpkg -i") - or just wait some more.. :)

you could just ping an archive admin to request new processing, no need to set the bug state back to 'fix committed'. ;)

(if that wasn't clear, I mean that the packages have been approved through the new queue now)

ok, its finally there, however I get the following error when trying to retrieve from synaptic : W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/universe/v/virtualbox-ose-modules/virtualbox-ose-modules-generic_24.0.1_amd64.deb
  404 Not Found [IP: 91.189.88.46 80]

ok, IP is now found and package was installed. However not successfully installed. To get VirtualBox to run, I had to issue the following command : sudo insmod /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko that I found in another thread which solved my problem and VirtualBox is now running on .17 kernel proposed. humm, I failed to reboot computer to see if fix survives re-boot, I'm running a VM now that is doing a major upgrade that will take sometime so I have no way of testing across a boot at the moment.

Please check the install scripts to insure that proper configuration takes place during the modules install. it was only a fluke that I had read the posts in the other thread and remembered this insmod might fix kernel driver issue failing after installing.

after rebooting I get the following error:

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Please install the virtualbox-ose-modules package for your kernel, e.g. virtualbox-ose-modules-generic..
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).

Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

which means that it does not survive reboots. I have to issue the following command after each boot to get Virtualbox to work:

sudo insmod /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko

Gene, please check if running "sudo depmod" manually allows you to use "modprobe" afterwards (e.g. "modprobe -r vboxdrv" to remove the module and "modprobe vboxdrv" to insert it.)
Depmod gets run on package installation, but maybe that failed somehow?!

@daniel

this is the output of your request:

gene@amd64:~$ sudo depmod
[sudo] password for gene:
gene@amd64:~$ modprobe -r vboxdrv
gene@amd64:~$ modprobe vboxdrv
FATAL: Error inserting vboxdrv (/lib/modules/2.6.24-17-generic/misc/vboxdrv.ko): Operation not permitted

ok, so I ran sudo insmod /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko again to get virtualbox working again then your command :
gene@amd64:~$ modprobe -r vboxdrv
FATAL: Error removing vboxdrv (/lib/modules/2.6.24-17-generic/misc/vboxdrv.ko): Operation not permitted

so I guess that I am not permitted to run modprobe now that depmod has been run ? did I even do what you wanted me to try correctly ?

On Sun, May 11, 2008 at 1:39 PM, Gene Caldwell <email address hidden> wrote:
> @daniel
>
> this is the output of your request:
>
> gene@amd64:~$ sudo depmod
> [sudo] password for gene:
> gene@amd64:~$ modprobe -r vboxdrv
> gene@amd64:~$ modprobe vboxdrv
try:
gene@amd64:~$ sudo modprobe vboxdrv

> FATAL: Error inserting vboxdrv (/lib/modules/2.6.24-17-generic/misc/vboxdrv.ko): Operation not permitted
>

--
Lucian

On Sun, May 11, 2008 at 1:49 PM, Gene Caldwell <email address hidden> wrote:
> ok, so I ran sudo insmod /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko again to get virtualbox working again then your command :
> gene@amd64:~$ modprobe -r vboxdrv
> FATAL: Error removing vboxdrv (/lib/modules/2.6.24-17-generic/misc/vboxdrv.ko): Operation not permitted
>
> so I guess that I am not permitted to run modprobe now that depmod has
> been run ? did I even do what you wanted me to try correctly ?

I get the same errors if I don't run them with sudo.
Because of security issues only users with special capabilities can
insert/remove kernel modules.
Run them all with sudo!

--
Lucian

@Daniel
hummm, ok, so I decided to see if I could survive reboots after the "sudo insmod /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko" now that I ran "sudo depmod" manually and it actually does survive reboots now....I booted twice and virtualbox is working without errors now,,,,,,,

@Lucian
I did not try adding sudo infront of the command as Daniel put quotes around what he wanted me to try, one of them with sudo, 2 of them without...and now that I seem to be working I do not want to risk breaking what is now working. Did you see/notice that the first command he wanted run was "sudo depmod" ? I think that is the guy that fixed it. I no longer have to run "sudo insmod /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko"

Gene, "modprobe" is only a shortcut to "insmod", but apparently needs updates "deps" (what depmod generates).
I've missed the "sudo" in the commands I've given you to try, sorry for the confusion.
In fact, not "insmod" does survive the reboot, but now "modprobe vboxdrv" (as root in the init script) works for you.
I've no idea though, why the depmod cache wasn't uptodate before.

Bug 202542 appears to be related.

This isn't "Fix released".
We still need at least two verifications that the update from -proposed works (as good as the previous version), especially since the kernel from -proposed now has been copied to -updates.

Just tried, and installing from proposed worked for me.

confirmed :)

On Tue, May 27, 2008 at 1:27 AM, Daniel Hahler <email address hidden> wrote:
> This isn't "Fix released".
> We still need at least two verifications that the update from -proposed works (as good as the previous version), especially since the kernel from -proposed now has been copied to -updates.
>
> ** Changed in: virtualbox-ose-modules (Ubuntu)
> Status: Fix Released => Fix Committed
>
> --
> no module built for 2.6.24-17-generic
> https://bugs.launchpad.net/bugs/226753
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Lucian

It works for me too.

I've had the same problem. After applying today's updates, VirtualBox stopped working. Temporarily enabling the hardy-proposed updates in synaptic and installing the updated kernel module fixed the problem. VirtualBox seems to be running fine again. Thanks.

Works for me, too.

Hardy proposed works for me too.

the hardy proposed works for me

Marking as verification-done and subscribing ubuntu-archive - hoping that this is appropriate.

Hardy proposed works for me too.

Oh crap, 20 days later and it's still not in there??? Is this normal for it to take so long? Confirmed here too, proposed works.

Confirmed here on Hardy 64-bit as well - why would you release a kernel that breaks something in the repositories?

Copied to hardy-updates.

once again an issue after the hardy heron kernel update from 2.6.24-21 to -22. the modules don't seem to be in hardy-proposed, either ... that's not exactly what i'd call long term support :-|

thoralf, see bug 303199 for this.