virtualbox-ose-modules-2.6.24-12-generic couldn't find kernel-modules

Please paste the output of "uname -a".

It looks like you have the -386 kernel installed, but no modules for it.

dpkg -l|grep linux-image
ii linux-image-2.6.24-12-generic 2.6.24-12.22 Linux kernel image for version 2.6.24 on x86
ii linux-image-generic 2.6.24.12.13 Generic Linux kernel image
ii virtualbox-ose-modules-2.6.24-12-generic 19 virtualbox-ose module for linux-image-2.6.24

uname -a
Linux daniel-laptop 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux

It's not the -386-kernel.

That's odd, because what the virtualbox-ose-modules package in the postinst script does, is (basically):
 sudo /sbin/depmod -q

Does running this manually also try to build the modules for -386?

Can you reproduce it by reinstalling the module package?

I have the same problem on 64-bit Ubuntu 8.04. I also notice that virtualbox-modules is "recommended" and therefore not installed, could that be it?

my uname -a:
Linux galactica 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

my apt-get install virtualbox-ose output:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libxalan110 libxerces27
Suggested packages:
  xalan bridge-utils virtualbox-ose-source
Recommended packages:
  virtualbox-ose-modules
The following NEW packages will be installed:
  libxalan110 libxerces27 virtualbox-ose
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 9204kB of archives.
After this operation, 31.5MB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://us.archive.ubuntu.com hardy/universe libxerces27 2.7.0-5 [1389kB]
Get:2 http://us.archive.ubuntu.com hardy/universe libxalan110 1.10-3.1 [1182kB]
Get:3 http://us.archive.ubuntu.com hardy/universe virtualbox-ose 1.5.6-dfsg-6ubuntu1 [6632kB]
Fetched 9204kB in 15s (611kB/s)
Preconfiguring packages ...
Selecting previously deselected package libxerces27.
(Reading database ... 113934 files and directories currently installed.)
Unpacking libxerces27 (from .../libxerces27_2.7.0-5_amd64.deb) ...
Selecting previously deselected package libxalan110.
Unpacking libxalan110 (from .../libxalan110_1.10-3.1_amd64.deb) ...
Selecting previously deselected package virtualbox-ose.
Unpacking virtualbox-ose (from .../virtualbox-ose_1.5.6-dfsg-6ubuntu1_amd64.deb) ...
Setting up libxerces27 (2.7.0-5) ...

Setting up libxalan110 (1.10-3.1) ...

Setting up virtualbox-ose (1.5.6-dfsg-6ubuntu1) ...
 * Starting VirtualBox host networking... [ OK ]
 * Starting VirtualBox kernel module vboxdrv
 * No suitable module for running kernel found.

Processing triggers for libc6 ...
ldconfig deferred processing now taking place

r0dzilla, your paste only shows the install of virtualbox-ose, no problems. And yes, you need to install virtualbox-ose-modules manually, because it caused problems when virtualbox-ose depended on it.
So, I don't think you have the same bug.

I had this issue also, and tried installing the modules manually asn Daniel mentioned. It appears to get rid of the "No suitable module..." message.

Would it be possible to change the package management so that it would automatically know and install the correct modules package as a dependency?

Daniel, any update from your side? (the bug gets hijacked already)

Peepsalot: no, it's currently not possible, see bug 152405.

It appears nobody has packaged the 2.6.24-18-generic modules yet for Virtualbox. The latest on my system, and the latest in the repo is virtualbox-ose-modules-2.6.24-17-generic.

Craig: are you using the hardy-security, but not the hardy-updates repo by any chance?
The modules are available through hardy-updates, see http://packages.ubuntu.com/search?keywords=virtualbox-ose-modules

I have updates selected, but for whatever reason virtualbox-ose-modules wouldn't update until I manually downloaded it. I didn't even see it in the repo when I tried an update / upgrade from apt-get. Strange.

Craig, do you have the meta package for your kernel flavor installed (e.g. virtualbox-ose-modules-generic)? This should take care of installing the current package for your kernel always.
If you've installed that one, it's maybe your Ubuntu archive mirror, which hasn't been synced for a while.

Anyway, I'm closing this bug as invalid, due to missing information and because it handles three different issues already.

Please report a new bug for anything that isn't fixed properly yet. Thank you.