>On the 22/01/2011 23:20, MRH wrote: >> On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote: >> In<4d3b20c8.3080...@o2.pl>, MRH wrote: >>> 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 >> >> This file should be provided by the linux-headers-* package for your >> kernel. >> Make sure you are this package installed in order to build kernel >> modules. > > Installed. As I wrote before, I build and installed both linux-image and > linux-headers. > >> >>> I have home-build kernel. >>> >>> 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. >> >> I'm not familiar with make-kpkg since the stock Debian kernels have >> served me >> well so far. Does it prepare all the linux-* .debs? You'll need linux- >> headers-* for building kernel modules. > Yes, it builds: > linux-image-2.6.38-rc1.mrh.01_.mrh.01_amd64.deb > linux-headers-2.6.38-rc1.mrh.01_.mrh.01_amd64.deb > > and I have them installed. > > I tried reinstalling dkms, kernel-package, virtualbox, both linux image > and headers - still nothing. > > I installed stock debian kernel - then it worked -ish - I mean both > drivers have compiled, however X environment did not work (nvidia driver > didn't work) and some other things I use are not available in the stock > kernel. > > Kind regards, > Michal
I have the same setup, I build my kernel (2.6.37 currently) with kernel-package and both nvidia and VirtualBox 4 work fine (they build automatically with dkms). I don't use extraversion, only --append-to-version and --revision. The problem with extraversion and 2.6.37 is known, it's been reported here if I remember, look for a message starting with "kernel-package: 2.6.37" in the archives. But since it seems to affect only proprietary software I guess they'll have to adapt. -- 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/4d3b625b.9000...@googlemail.com
