Update to "Latest" breaks Virtualbox system [Solved]
Posted: Tue Jul 26, 2011 7:01 am
I've just tried to change my LMDE systems to use the new mintupdate-debian and the "latest" repository. I run one under Windows 7 using VirtualBox (latest edition) and the other on an old laptop. The Laptop system is fine, but I have come across a problem running under VirtualBox. Having updated the systems the kernel was updated from something ending in 686 to 686pae and it is with the latter that the problem lies. When I boot to this kernel Virtualbox's Guest Additions won't install. They are essential to run full screen - otherwise my old eyes have to cope with running in a little window. Attempting to install gives this error:-
Quote on ..........................................................................................
bob@debian-desktop /media/cdrom0 $ sudo sh VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.0.12 Guest Additions for Linux.........
VirtualBox Guest Additions installer
Removing installed version 4.0.12 of VirtualBox Guest Additions...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.
...fail!
Your system does not seem to be set up to build kernel modules.
Look at /var/log/vboxadd-install.log to find out what went wrong.
Once you have corrected it, you can run
/etc/init.d/vboxadd setup
to build them.
Doing non-kernel setup of the Guest Additions ...done.
Installing the Window System drivers
Installing X.Org Server 1.10 modules ...done.
Setting up the Window System to use the Guest Additions ...done.
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.
Installing graphics libraries and desktop services components ...done.
Quote off..................................................................................
The log referred to doesn't mean much to me - it just says :-
Quote on.................................................................................
Uninstalling modules from DKMS
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxguest/4.0.12/source ->
/usr/src/vboxguest-4.0.12
DKMS: add Completed.
Error! Your kernel headers for kernel 2.6.39-2-686-pae cannot be found at
/lib/modules/2.6.39-2-686-pae/build or /lib/modules/2.6.39-2-686-pae/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without
Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
Quote off.............................................................................
Being fairly non-technical this means little to me except that it would appear that the new kernel is incomplete (no headers?) or in the wrong directory, or not configured correctly. I can get round the problem by booting to the old (none sae) kernel in Grub and re-installing the Vitualbox Guest Additions, but such an error looks to me as though it may cause other problems elsewhere, and would be better fixed now before it becomes too deeply embedded in the update system.
Regards,
Bob
I have written this long diatribe not so much because I'd like a fix for it, (I would, of course) but because we were asked to report back on problems with the new system.
Quote on ..........................................................................................
bob@debian-desktop /media/cdrom0 $ sudo sh VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.0.12 Guest Additions for Linux.........
VirtualBox Guest Additions installer
Removing installed version 4.0.12 of VirtualBox Guest Additions...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.
...fail!
Your system does not seem to be set up to build kernel modules.
Look at /var/log/vboxadd-install.log to find out what went wrong.
Once you have corrected it, you can run
/etc/init.d/vboxadd setup
to build them.
Doing non-kernel setup of the Guest Additions ...done.
Installing the Window System drivers
Installing X.Org Server 1.10 modules ...done.
Setting up the Window System to use the Guest Additions ...done.
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.
Installing graphics libraries and desktop services components ...done.
Quote off..................................................................................
The log referred to doesn't mean much to me - it just says :-
Quote on.................................................................................
Uninstalling modules from DKMS
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxguest/4.0.12/source ->
/usr/src/vboxguest-4.0.12
DKMS: add Completed.
Error! Your kernel headers for kernel 2.6.39-2-686-pae cannot be found at
/lib/modules/2.6.39-2-686-pae/build or /lib/modules/2.6.39-2-686-pae/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without
Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
Quote off.............................................................................
Being fairly non-technical this means little to me except that it would appear that the new kernel is incomplete (no headers?) or in the wrong directory, or not configured correctly. I can get round the problem by booting to the old (none sae) kernel in Grub and re-installing the Vitualbox Guest Additions, but such an error looks to me as though it may cause other problems elsewhere, and would be better fixed now before it becomes too deeply embedded in the update system.
Regards,
Bob
I have written this long diatribe not so much because I'd like a fix for it, (I would, of course) but because we were asked to report back on problems with the new system.