[SOLVED] Kernel update, video drivers, and virtualbox

[irvcobb]

A couple of days ago updated (via Synaptic) a couple of my (64-bit) systems, which brought in kernel 3.7.0-4-generic. In both cases, the upgrade broke things, specifically things that that build their own kernel modules: nvidia drivers, radeon drivers, and virtualbox. On the nvidia system I was able to get the drivers going by using K|Applications|System|Additional Drivers, but this fails on the radeon system.

Attempts to reinstall virtualbox gives this:

----------------------------
Preparing to replace virtualbox 4.1.18-dfsg-1ubuntu1.1 (using .../virtualbox_4.1.18-dfsg-1ubuntu1.1_amd64.deb) ...
Unpacking replacement virtualbox ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up virtualbox (4.1.18-dfsg-1ubuntu1.1) ...
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found
[fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.
------------------------------

Kernel headers and such are installed.

Any thoughts? This is a game killer for me on the radeon system, which is slow and really needs the video card working in order to be usable.

Irv

[OneLine]

...which brought in kernel 3.7.0-4-generic...Any thoughts?

Could you tell a bit more: http://www.kubuntuforums.net/showthr...W-GUY-lt-lt-lt

About the kernel - the kernel 3.7.0-4 is available for the Raring /1/. There has been reports of the problems with the AMD & kernel 3.7 /2/ but here it seems to work (with the Raring).

The Raring is at the pre alpha stage - there will be lot of breakages ahead.

If you are using some PPA repositories it would be helpful to mention that.



Links

1. http://packages.ubuntu.com/search?ke...ll&section=all
2. http://ubuntuforums.org/showthread.php?t=2085789

[irvcobb]

Release: 12.10
No Wubi.
KDE 4.9.3
Grub Legacy version
Vista also installed.

Information about your PC:

Type Desktop
Central Processor Unit make Intel 64-bit
GPU: NVIDIA Corporation G80 [GeForce 8800 GTS] (rev a2)
4 gb RAM
2 internal HDs
1 internal Optical Drive

Yes, I'm using PPAs:
-----------------------------------
deb http://mirror.anl.gov/pub/ubuntu/ quantal main restricted
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal main restricted
deb http://mirror.anl.gov/pub/ubuntu/ quantal-updates main restricted
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-updates main restricted
deb http://mirror.anl.gov/pub/ubuntu/ quantal universe
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal universe
deb http://mirror.anl.gov/pub/ubuntu/ quantal-updates universe
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-updates universe
deb http://mirror.anl.gov/pub/ubuntu/ quantal multiverse
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal multiverse
deb http://mirror.anl.gov/pub/ubuntu/ quantal-updates multiverse
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-updates multiverse
deb http://mirror.anl.gov/pub/ubuntu/ quantal-backports main restricted universe multiverse
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-backports main restricted universe multiverse
deb http://mirror.anl.gov/pub/ubuntu/ quantal-security main restricted
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-security main restricted
deb http://mirror.anl.gov/pub/ubuntu/ quantal-security universe
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-security universe
deb http://mirror.anl.gov/pub/ubuntu/ quantal-security multiverse
deb-src http://mirror.anl.gov/pub/ubuntu/ quantal-security multiverse
deb http://archive.canonical.com/ubuntu quantal partner
deb http://extras.ubuntu.com/ubuntu quantal main
apt-fast-stable-quantal.list.save:deb http://ppa.launchpad.net/apt-fast/stable/kubuntu quantal main
blue-shell-firefox-kde-quantal.list:deb http://ppa.launchpad.net/blue-shell/firefox-kde/ubuntu quantal main
blue-shell-firefox-kde-quantal.list.save:deb http://ppa.launchpad.net/blue-shell/firefox-kde/ubuntu quantal main
dhor-myway-quantal.list:deb http://ppa.launchpad.net/dhor/myway/ubuntu quantal main
dhor-myway-quantal.list.save:deb http://ppa.launchpad.net/dhor/myway/ubuntu quantal main
ehoover-compholio-quantal.list:deb http://ppa.launchpad.net/ehoover/compholio/ubuntu quantal main
ehoover-compholio-quantal.list:deb-src http://ppa.launchpad.net/ehoover/compholio/ubuntu quantal main
google-chrome.list:deb http://dl.google.com/linux/chrome/deb/ stable main
google-chrome.list.save:deb http://dl.google.com/linux/chrome/deb/ stable main
kubuntu-ppa-backports-quantal.list:deb http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu quantal main
kubuntu-ppa-backports-quantal.list.save:deb http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu quantal main
kubuntu-ppa-beta-quantal.list.save:deb-src http://ppa.launchpad.net/kubuntu-ppa/beta/ubuntu quantal main
kubuntu-ppa-ppa-quantal.list:deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu quantal main
kubuntu-ppa-ppa-quantal.list:deb-src http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu quantal main
kubuntu-ppa-ppa-quantal.list.save:deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu quantal main
kubuntu-ppa-ppa-quantal.list.save:deb-src http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu quantal main
libreoffice-ppa-quantal.list:deb http://ppa.launchpad.net/libreoffice/ppa/ubuntu quantal main
libreoffice-ppa-quantal.list.save:deb http://ppa.launchpad.net/libreoffice/ppa/ubuntu quantal main
webupd8team-y-ppa-manager-quantal.list:deb http://ppa.launchpad.net/webupd8team...manager/ubuntu quantal main
webupd8team-y-ppa-manager-quantal.list.save:deb http://ppa.launchpad.net/webupd8team...manager/ubuntu quantal main
xorg-edgers-ppa-quantal.list:deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu quantal main
xorg-edgers-ppa-quantal.list.save:deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu quantal main
------------------------------------------------


So the Raring thing is my problem. I'm guessing. Not sure how I got into that when all the repos and ppas are quantal? Backports or Beta?

I've tried booting with an older kernel. Get the same error trying to reinstall virtualbox.

[luckyone]

See here: https://www.virtualbox.org/manual/ch...lkernelmodules

Note the red text below.

The VirtualBox kernel module




VirtualBox uses a special kernel module called vboxdrv to perform physical memory allocation and to gain control of the processor for guest system execution. Without this kernel module, you can still use the VirtualBox manager to configure virtual machines, but they will not start. In addition, there are the network kernel modules vboxnetflt and vboxnetadp which are required for the more advanced networking features of VirtualBox.
The VirtualBox kernel module is automatically installed on your system when you install VirtualBox. To maintain it with future kernel updates, for those Linux distributions which provide it -- most current ones -- we recommend installing Dynamic Kernel Module Support (DKMS)^[9]. This framework helps with building and upgrading kernel modules.
If DKMS is not already installed, execute one of the following:

• On an Ubuntu system:
  
  
  sudo apt-get install dkms
• On a Fedora system:
  
  yum install dkms
• On a Mandriva or Mageia system:
  
  urpmi dkms

If DKMS is available and installed, the VirtualBox kernel module should always work automatically, and it will be automatically rebuilt if your host kernel is updated.
Otherwise, there are only two situations in which you will need to worry about the kernel module:

1. The original installation fails. This probably means that your Linux system is not prepared for building external kernel modules.
   Most Linux distributions can be set up simply by installing the right packages - normally, these will be the GNU compiler (GCC), GNU Make (make) and packages containing header files for your kernel - and making sure that all system updates are installed and that the system is running the most up-to-date kernel included in the distribution. The version numbers of the header file packages must be the same as that of the kernel you are using.
   • With Debian and Ubuntu releases, you must install the right version of the linux-headers and if it exists the linux-kbuild package. Current Ubuntu releases should have the right packages installed by default.
   • In even older Debian and Ubuntu releases, you must install the right version of the kernel-headers package.
   • On Fedora and Redhat systems, the package is kernel-devel.
   • On SUSE and openSUSE Linux, you must install the right versions of the kernel-source and kernel-syms packages.
   • If you have built your own kernel, you will need to make sure that you also installed all the required header and other files for building external modules to the right locations. The details of how to do this will depend on how you built your kernel, and if you are unsure you should consult the documentation which you followed to do so.
   
   
2. The kernel of your Linux host was updated and DKMS is not installed. In that case, the kernel module will need to be reinstalled by executing (as root):
   
   
   /etc/init.d/vboxdrv setup

[ronw]

Virtualbox in the standard repos is behind the times. I don't know if the 4.2 series works on hosts with 3.7.0-4, but from the 4.2 changelog:

* Linux hosts / guests: Linux 3.7-rc1 fixes

https://www.virtualbox.org/wiki/Changelog

[irvcobb]

sudo apt-get install dkms

Reading package lists... Done
Building dependency tree
Reading state information... Done
dkms is already the newest version.
dkms set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

sudo /etc/init.d/vboxdrv setup

sudo: /etc/init.d/vboxdrv: command not found

irv@meshach:~$ sudo apt-get install --reinstall virtualbox-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/480 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 311986 files and directories currently installed.)
Preparing to replace virtualbox-dkms 4.1.18-dfsg-1ubuntu1.1 (using .../virtualbox-dkms_4.1.18-dfsg-1ubuntu1.1_all.deb) ...

-------- Uninstall Beginning --------
Module: virtualbox
Version: 4.1.18
Kernel: 3.5.0-18-generic (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
- Uninstallation
- Deleting from: /lib/modules/3.5.0-18-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
- Uninstallation
- Deleting from: /lib/modules/3.5.0-18-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
- Uninstallation
- Deleting from: /lib/modules/3.5.0-18-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.


vboxpci.ko:
- Uninstallation
- Deleting from: /lib/modules/3.5.0-18-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.

depmod......

DKMS: uninstall completed.

------------------------------
Deleting module version: 4.1.18
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement virtualbox-dkms ...
Setting up virtualbox-dkms (4.1.18-dfsg-1ubuntu1.1) ...
Loading new virtualbox-4.1.18 DKMS files...
Building only for 3.7.0-4-generic
Building initial module for 3.7.0-4-generic
Traceback (most recent call last):
File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.7.0-4-generic (x86_64)
Consult /var/lib/dkms/virtualbox/4.1.18/build/make.log for more information.
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found
[fail]
invoke-rc.d: initscript virtualbox, action "restart" failed.

[luckyone]

I had to use 4.18 here as 4.2 would not work on my 12.10.

[irvcobb]

I got it all sorted by reverting to a previous kernel and reinstalling all the virtualbox packages.

Anybody have thoughts about which ppa may have provided the 3.7 kernel? I'd like to lose it before I have further issues.

[ronw]

xorg-edgers

[OneLine]

Where the package come from / How to find out origin of package : http://forums.debian.net/viewtopic.php?f=10&t=62708

Example with the Opera:

:~$ apt-cache policy opera
opera:
Installed: 12.11.1661
Candidate: 12.11.1661
Version table:
*** 12.11.1661 0
500 http://deb.opera.com/opera/ stable/non-free amd64 Packages
100 /var/lib/dpkg/status

[irvcobb]

Thanks!

[irvcobb]

For reference:

linux-image-3.7.0-4-generic:
Installed: (none)
Candidate: 3.7.0-4.12
Version table:
3.7.0-4.12 0
500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ quantal/main amd64 Packages

[Guest]

I use 4.8

http://www.centplay.com/affiliate/games_4320/