1. You should install the meta package for your kernel flavor, e.g.
virtualbox-ose-modules-generic, which will always depend on the latest
available version, e.g. currently virtualbox-ose-modules-2.6.24-18-generic (or
-19-generic in hardy-proposed)
2. Yes, the package wasn't following the kernel
keeping the old kernel booted results in another problem: as soon as one
installs the new modules and gladly boots into the new system, the
module is still not loaded; one has to manually do the `depmod -a` again
and `/etc/init.d/vboxdrv restart`, although everything should be
properly installed. (
I just copied /lib/modules/2.6.24-17-generic/misc/vboxdrv.ko to
/lib/modules/2.6.24-18-generic/misc/vboxdrv.ko and everything works fine now.
Then run depmod so you can just type 'modprobe vboxdrv'.
Or you can keep the old '2.6.24-17' kernel booted.
--
Kernel updates break VirtualBox support
h
broke again for -18.
there is a thread on that topic on the ubuntu kernel-team mailing list,
mirrored at [1].
[1] http://www.nabble.com/-RFC--merging-virtualbox-ose-modules-into-
linux-ubuntu-modules-td17648442.html
--
Kernel updates break VirtualBox support
https://bugs.launchpad.net/bugs/2122
actually, i take that back.
I had loaded virtualbox-ose-modules-2.6.24-16 instead of the pointer
package "virtualbox-ose-modules"...
when I uninstalled/installed the pointer package, it got the -17
modules.
so I guess this isn't really a bug.
--
Kernel updates break VirtualBox support
https://
I had this problem again on the 2.4.24-16 to 2.4.24-16 on 2 different
machines. I don't even know what to do to fix this. I can't insmod
modules from older kernels.
--
Kernel updates break VirtualBox support
https://bugs.launchpad.net/bugs/212217
You received this bug notification because you are
I get the same issue everytime the kernel is updated. I think that's because
the virtualbox-ose-modules are built and ported to the official repositories a
always bit later then the kernel. It used to be always like this. I think it's
just a matter of time, when the new virtualbox-ose-modules fo
update to previous post. I missed the "recommended packages: virtualbox-
ose-modules" lines while using apt-get. that seems to have resolved the
driver issue though I would expect that it should really be a dependency
and force the install. I still don't know where the -15 version of the
driver cam
I've never used vitualbox before so after the upgrade to hardy release
and vmware-server broke yet again I gave it a try. Unfortunately I can
confirm the problem with the kernel module version not tracking the
current kernel. I installed from the standard repo and it went well
until:
Unpacking lib
So, I could load the vboxdrv modul with insmod:
"insmod /lib/modules/2.6.24-15-generic/misc/vboxdrv.ko"
Now virtualbox-ose works again.
--
Kernel updates break VirtualBox support
https://bugs.launchpad.net/bugs/212217
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I can also confirm the problem with viurtualbox-ose-modules not being
installed automatically when a new kernel is installed.
--
Kernel updates break VirtualBox support
https://bugs.launchpad.net/bugs/212217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I have installed manually the right vortulabox-ose modules for the latest
kernel (2.6.24-15) but but I get the error message saying U have to try
'modprobe vboxdrv' as root. After trying that I get another error " FATAL:
Module vboxdrv not found.". So it seems like the virtualbox-ose-modules are
I can confirm this bug.
Info:
Kubuntu Hardy beta with all updates as of April 6, 2008
VirtualBox OSE 1.5.6
Kernel 2.6.24-15-generic
** Changed in: ubuntu
Status: New => Confirmed
--
Kernel updates break VirtualBox support
https://bugs.launchpad.net/bugs/212217
You received this bug notif
13 matches
Mail list logo
