I had a related problem - I could not see *any* new versions of
virtualbox-ose-modules-2.6.24-xx after virtualbox-ose-
modules-2.6.24-16, even though I could see all of the kernel images
from linux-image-2.6.24-16-generic to linux-image-2.6.24-24-generic.
Traced my issue to the default apt
Awesome, thanks for providing a fix!! I confirm this fix works.
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I meant the original fix, I have not tried any other 'fix'.
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm happy for you!!
:D
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Que lio este!!!
bueno... veamos que tal mi ingles :D
SOLUTION:
1- unistall OSE version (complete)
sudo aptitude purge virtualbox-source
sudo aptitude purge virtualbox-ose
sudo aptitude purge virtualbox-ose-source
sudo aptitude purge virtualbox-ose-modules-
sudo aptitude
This bug was fixed in the package virtualbox-ose-modules - 24.0.8
---
virtualbox-ose-modules (24.0.8) hardy-proposed; urgency=low
* Rebuild for 2.6.24-23 (LP: #303199)
-- Daniel Hahler ubu...@thequod.de Wed, 03 Dec 2008 00:43:18 +0100
** Changed in: virtualbox-ose-modules
I can confirm the proposed workaround works in an updated Ubuntu Hardy:
From a terminal window:
sudo apt-get install virtualbox-ose-source module-assistant
sudo module-assistant auto-install virtualbox-ose-source
sudo /etc/init.d/vboxdrv start
I believe this is needed for every kernel upgrade.
HughBranes, this bug report is not the same as your issue. This report
applies only to Hardy, and a fix is awaiting testing in -proposed. If
you believe your issue is a bug, you should file a separate bug report.
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You
Using module-assistant auto-install isn't working with the current
virtualbox-ose-source package.
Auto-install is expecting to find the virtualbox sources under /usr/src
and doesn't, so fails. The file list reveals that the sources are not
being placed where auto-install expects them:
If anybody still needs it, I've build the modules for the -22 kernel in
my PPA: https://launchpad.net/~andreas-wenning/+archive
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I did not use virtualbox for a few days...
I restarted it yesterday... I used it for the whole day and today the
same...
My CPU now seems to work properly... so I have to revise my previous
comment.
The Steven's method works very well... maybe I had just to restart the
pc before complaining...
Not an issue in jaunty and intrepid, those releases use DKMS.
** Changed in: virtualbox-ose-modules (Ubuntu)
Status: Triaged = Invalid
** Changed in: virtualbox-ose-modules (Ubuntu Intrepid)
Status: New = Invalid
** Changed in: virtualbox-ose-modules (Ubuntu Hardy)
Status:
Prezemyslaw,
The PUEL does not forbid using it in a commercial project. It's a bit of a
misnomer. From the licence:
§ 2 Grant of license. (1) Sun grants you a personal right to install and
execute the Product on a Host Computer for Personal Use or Educational
Use or for Evaluation. “Personal
I tried rebuilding the module for -22 but it refused to compile on
amd64, and I can't use the PUEL version because I'm using VB for
commercial purposes. So I'm stuck on -21 kernel :[
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification
One can build virtualbox kernel module package for the latest kernel
using module assistant and virtualbox-ose-source package.
First, 'apt-get install virtualbox-ose-source', that would install
module-assistant too if it's not allready installed.
Then, go to /usr/src, there will be
It's even simpler than that:
sudo apt-get install virtualbox-ose-source
sudo module-assistant auto-install virtualbox-ose-source
sudo /etc/init.d/vboxdrv start
(the last step basically just loads the module with modprobe, but it
also does a little bit of house keeping)
And you might only need
Thanks Steven, it works !
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi all,
Steven I've done what you said and my VM is magically restarted but...
...but, unfortunately now, my CPU si always at 100% even when the VM is
doing nothing...
Any possible solution?
is it because the generic module is not as good as the proper one?!?
Thanks anyway for you help!!!
luchomax,
no es que las actualizaciones sean profundas, la realidad es que es muy
raro que haya problemas después de una actualización (aunque los casos
se dan), en mi caso por ejemplo solo he visto problemas con este
software y es por la forma en que esta desarrollado... pero aun te falle
algo
Hola Angel Sanchez
la verdad que tus datos me han sido lo suficientemente claros, recientemente
empece a usar kubuntu desde una version mucho anterior para evitar estos
problemas de las actualizaciones de version y desconocia que las
actualizaciones eran tan profundas.
Me salvaste la vida!!!
Sorry, but linux has just bumped the ABI to -23 in hardy-proposed.
Could you prepare a -23 build of virtualbox-ose-modules for SRU to
replace it?
I don't think there's much point in accepting the current version.
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You
Steve, I don't know how long it will take this time until linux gets updated in
-updates.
The current upload is meant to fix the current problem.
My plan was to prepare a new upload, when it's been propagated to
-updates.
Anyway, I've uploaded 24.0.8 for the -23 kernel now.
While I have your
To fix the problem, temporaly, you should reboot from the last kernel,
in this case, the 2.6-24-21 until an update will be available. That's
the solution that Angel Sanchez sugest.
Here's a link reporting the problem and puting the solution also in
english:
Subscribing ubuntu-archive:
Please approve my upload of the module to hardy-proposed
(https://edge.launchpad.net/ubuntu/hardy/+queue?queue_state=1queue_text=virtualbox-ose-modules).
I know that it does not match the kernel ABI in hardy-proposed, but it
is meant to go into hardy-updates to match
Hi Daniel,
Thanks for all your work. I've followed your advice and switched to the
virtualbox.org version and everything works just fine even with the
latest kernel.
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are
excuseme for spanish but my english is very bad I only read a litle bit
english.. THIS IS A SOLUTION AT YOUR TROUBLE (PROBLEMA) ON
VIRTUALBOX.
estamos jodidos..
aunque yo no actualice, pues me lo suponia...
AQUI LES VA UNA POSIBLE SOLUCION
Bueno chicos, ya que estan metidos en
Este es un ejemplo de mi grub para que lo tomen de referencia a ver si
entienden de que les hablo
do this:
sudo gedit /boot/grub/menu.lst
veran esto y lo podran modificar, pero cuidado esto no es necesario,
es solo otro camino a la solucion, solo que lo considero mas
complejo
Hi Daniel,
Would it be an idea to make a *second* VirtualBox-OSE-Modules-Generic
version, which does have the dependency set to the kernel modules? In
that case the users can chose between either being in-dependent of
Virtualbox and install the latest kernel once it's available (as it is
now, but
I see the same problem.
--
virtualbox-ose-modules broken AGAIN
https://bugs.launchpad.net/bugs/303199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Daniel,
Thanks for your feedback on this issue. I'm going to switch my father to use
the PUEL version of Virtualbox as a workaround to this problem. I'm kind of
worried that you're not informed about incoming kernel updates though. I hope
that in time a solution to that kind of problem will
I guess you've got the choice between staying on hardy, and having to
wait a bit after each kernel update for the necessary rebuild/upload to
occur, or you can upgrade to intrepid where, I believe, DKMS will nicely
rebuild the module for you automatically each time the kernel is
updated.
Now,
I certainly appreciate the work of everyone that puts time into Ubuntu,
including Daniel. However, if someone doesn't complain, how exactly would
anything get fixed? Also, this doesn't help to correct the underlying issue.
How does Daniel know that a kernel update is coming that is going to
I've uploaded a new version for 2.6.24-22 to hardy-proposed (which already has
a -23 kernel itself, so it will break sometime again, when this gets to
-updates).
I don't know about security releases beforehand or even new updates in
hardy-proposed.
And yes, luckily this is fixed for Intrepid
Any Idea when the new module will be out. I have some work stored in my
VM that i have to access by this Monday and I'd rather not go back a
kernel and have to recompile my graphics drivers. Anyone know any rough
dates?
Regards,
-B.
--
So I was going to try to install the non-OSE version. However, when I
went to clone my .vdi file,it still needs the new module for the new
kernel to even clone the file... :( any work arounds for this?
Regards,
-B.
--
35 matches
Mail list logo
