On Saturday 22 January 2011 13:24:08 MRH wrote: > Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From > that moment it stopped working, saying that the kernel driver (vboxdrv) > is not loaded and suggesting to run /etc/init.d/vboxdrv setup > > This fails: > ---------- > Stopping VirtualBox kernel modules:done.. > Uninstalling old VirtualBox DKMS kernel modules:done.. > Trying to register the VirtualBox kernel modules using DKMS: > Error! Bad return status for module build on kernel: 2.6.38-rc1.mrh.01 > (x86_64) > Consult the make.log in the build directory > /var/lib/dkms/vboxhost/4.0.2/build/ for more information. > > Failed, trying without DKMS ... failed! > Recompiling VirtualBox kernel modules: > Look at /var/log/vbox-install.log to find out what went wrong ... failed! > ---------- > > The above is the /var/log/vbox-install.log > Below /var/lib/dkms/vboxhost/4.0.2/build/make.log > ---------- > DKMS make.log for vboxhost-4.0.2 for kernel 2.6.38-rc1.mrh.01 (x86_64) > Sat Jan 22 18:07:34 GMT 2011 > make: Entering directory `/usr/src/linux-2.6.38-rc1' > LD /var/lib/dkms/vboxhost/4.0.2/build/built-in.o > LD /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/built-in.o > CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o > In file included from > /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30, > from > /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal.h:35, > from > /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.c:31: > /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/iprt/types.h:105:31: > error: linux/autoconf.h: No such fil > e or directory > make[2]: *** > [/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o] Error 1 > make[1]: *** [/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv] Error 2 > make: *** [_module_/var/lib/dkms/vboxhost/4.0.2/build] Error 2 > make: Leaving directory `/usr/src/linux-2.6.38-rc1' > ---------- > > I have home-build kernel, I had the same problem on 2.6.32 first, which > worked nicely with VirtualBox 3.2 but stopped after installing VB 4.0 - > unfortunately it seems it doesn't help going back to the VB 3.2 version, > as the kernel driver module has been deleted and it fails building in > the same way. So it seems there is a problem in building kernel modules. > I have the same problem with nvidia proprietary driver - fails building. > > I suspect the problem is I build the kernel with --append-to-version: > > make-kpkg --initrd --revision=.mrh.01 --append-to-version=.mrh.01 > > but this helps me keeping things tidy. > > Now I have no idea where is the problem, is it a known bug or I do > something wrong (but it worked to me until recently). And I'm afraid I > have no idea which package is the culprit.
For the home-built kernels, you want to also build the kernel-headers target, which will create the "-headers" .deb file, which you can also install. Use the same append-to-version as for the kernel image target, and it should work without further intervention. I have some really good notes on this somewhere, but can't find them just now, but as I recall, the make-kpkg docs are pretty good. -- A. -- Andrew Reid / rei...@bellatlantic.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101221826.41577.rei...@bellatlantic.net