VirtualBox OSE wrecks xserver/nvidia and won't uninstall properly
Bug #224170 reported by
Eric Springer
This bug report is a duplicate of:
Bug #226960: Installing module for wrong kernel flavor breaks system (modules missing).
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| virtualbox-ose-modules (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: virtualbox-ose
Installing Virtualbox works fine. When trying to launch a virtual machine, it complains that the virtualbox modules is not loaded (Should be included as a dependency?). After installing required modules, nvidia does not appear to work. X server starts in low resolution mode.
After removing virtualbox and the module package, it doesn't get properly removed as can be illustrated with:
modprobe -l | grep vbox
which returns
/lib/modules/
I'm unable to get nvidia or xserver working properly anymore. Since someone will ask for it, I've included xorg.conf
Revision history for this message
| Eric Springer (erikina) wrote | #1 |
Revision history for this message
| Daniel Hahler (blueyed) wrote | #2 |
| Changed in virtualbox-ose: | |
| status: | New → Invalid |
To post a comment you must log in.
You've probably picked the wrong modules (virtualbox-
This pulled in the -386 kernel image (without the kernel modules, like nvidia drivers).
(Removing the package won't unload the driver).
This is probably caused by "bug 226960".
To fix this, make sure that you boot the generic kernel (press ESC during boot for the Grub menu). Afterwards you may remove the -386 kernel image again.