Re: Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
I switched to custom kernel and came across this thread. I also use squeeze and this is what I have found. First of, Debian has the following versions of nvidia-kernel-dkms packages: squeeze: 195.36.31-6 sid/wheezy: 260.19.44-1 experimental: 270.30-1 The version in squeeze fail on anything above kernel 2.6.38 and none will compile on 2.6.39 because of BKL removal; nvidia-kernel-dkms depends on it; "include/linux/smp_lock.h" is missing and the driver will not compile without it. So I settled for kernel 2.6.38.4 and nvidia-kernel-dkms from experimental because it compiles without issue. The packages from sid/wheezy also work but why not use the latest and greatest. Here is what i did: cd /usr/src download the following packages from exerimental: libgl1-nvidia-glx_270.30-1_amd64.deb nvidia-glx_270.30-1_amd64.deb nvidia-kernel-dkms_270.30-1_amd64.deb nvidia-common_20110213+1_amd64.deb nvidia-kernel-common_20110213+1_amd64.deb download, untar and configure kernel 2.6.38.4. cd linux-2.6.38.4 fakeroot make-kpkg --initrd --revision=2.6.38.4+jj --append_to_version=+jj kernel_image; fakeroot make-kpkg --initrd --revision=2.6.38.4+jj --append_to_version=+jj kernel_headers dpkg -i linux-image-2.6.38.4+jj_2.6.38.4+jj_amd64.deb linux-headers-2.6.38.4+jj_2.6.38.4+jj_amd64.deb dpkg -i libgl1-nvidia-glx_270.30-1_amd64.deb nvidia-glx_270.30-1_amd64.deb nvidia-kernel-dkms_270.30-1_amd64.deb nvidia-common_20110213+1_amd64.deb nvidia-kernel-common_20110213+1_amd64.deb dpkg-reconfigure nvidia-kernel-dkms Best regards, Jonas Jensen -- 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/banlktin3y0ndtbfurkci9340ssnhum6...@mail.gmail.com
Subject=Re: Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
I switched to custom kernel and came across this thread. I also use squeeze and this is what I have found. First of, Debian has the following versions of nvidia-kernel-dkms packages: squeeze: 195.36.31-6 sid/wheezy: 260.19.44-1 experimental: 270.30-1 The version in squeeze fail on anything above kernel 2.6.38 and none will compile on 2.6.39 because of BKL removal; nvidia-kernel-dkms depends on it; "include/linux/smp_lock.h" is missing and the driver will not compile without it. So I settled for kernel 2.6.38.4 and nvidia-kernel-dkms from experimental because it compiles without issue. The packages from sid/wheezy also work but why not use the latest and greatest. Here is what i did: cd /usr/src download the following packages from exerimental: libgl1-nvidia-glx_270.30-1_amd64.deb nvidia-glx_270.30-1_amd64.deb nvidia-kernel-dkms_270.30-1_amd64.deb nvidia-common_20110213+1_amd64.deb nvidia-kernel-common_20110213+1_amd64.deb download, untar and configure kernel 2.6.38.4. cd linux-2.6.38.4 fakeroot make-kpkg --initrd --revision=2.6.38.4+jj --append_to_version=+jj kernel_image; fakeroot make-kpkg --initrd --revision=2.6.38.4+jj --append_to_version=+jj kernel_headers dpkg -i linux-image-2.6.38.4+jj_2.6.38.4+jj_amd64.deb linux-headers-2.6.38.4+jj_2.6.38.4+jj_amd64.deb dpkg -i libgl1-nvidia-glx_270.30-1_amd64.deb nvidia-glx_270.30-1_amd64.deb nvidia-kernel-dkms_270.30-1_amd64.deb nvidia-common_20110213+1_amd64.deb nvidia-kernel-common_20110213+1_amd64.deb dpkg-reconfigure nvidia-kernel-dkms Best regards, Jonas Jensen -- 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/banlktinsnwkfw328pljnb7nycqs7n8x...@mail.gmail.com
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
MRH writes: >On 23/01/11 04:53, Cameron Hutchison wrote: >> and I had to revert two commits to fix it: >> >> 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to >> regenerate kernel.release file when make kernelrelease) >> >> 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make kernelrelease" >> should show the correct full kernel version) >I'm afraid it's a bit beyond my skills at the moment - I guess it's >about getting source tree by svn and reverting the changes applied by >getting previous version of a file? You need to have the git kernel tree, and you use the "git revert" command. The second commit to revert (01ab1788) has a conflict when reverting, but that's pretty easy to resolve (if you know what you're doing :-)) >Thanks anyway - I hope it will start working for me at some point :) I haven't had time to look into what the correct fix would be, but I may have some time in the next few weeks. I'll put it on my todo list. -- 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/3d34.4d3f5ba2.3d...@getafix.xdna.net
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
On 23/01/11 04:53, Cameron Hutchison wrote: "tv.deb...@googlemail.com" writes: 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. Since I was the one to report that, I should correct some things I got wrong. The problem also exists in 2.6.36 - that's when it was introduced, and I had to revert two commits to fix it: 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to regenerate kernel.release file when make kernelrelease) 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make kernelrelease" should show the correct full kernel version) I don't know if this is related to the OP's issues - I don't use nvidia drivers. I'm afraid it's a bit beyond my skills at the moment - I guess it's about getting source tree by svn and reverting the changes applied by getting previous version of a file? Thanks anyway - I hope it will start working for me at some point :) -- Kind regards, Michal R. Hoffmann -- 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/4d3dee86.2090...@o2.pl
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
On 22/01/11 23:03, tv.deb...@googlemail.com wrote: [...] 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. Hmmm, that's interesting - I don't remember tinkering with extraversion directly - unless it's '-rc1' suffix which causes the trouble. I did a number of tests yesterday and I found that I cannot get 2.6.38-rc1 working at all, however I could finally get back 2.6.32 working again after I build it (with both --revision and --append-to-version). This required deleting /usr/src/linux soft link after restarting PC - it has been recreated automagically by 'something' pointing to 2.6.38-rc1 source. But after removing the link both /etc/init.d/vboxdrv setup m-a a-i nvidia worked and build me the modules. Still I don't know what's wrong with 2.6.38-rc1. Perhaps it's '-rc1' fault - I'll wait for stable 2.6.38 and will report back :) Thanks all for the advices. -- Kind regards, Michal R. Hoffmann -- 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/4d3ded69.7090...@o2.pl
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
"tv.deb...@googlemail.com" writes: >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. Since I was the one to report that, I should correct some things I got wrong. The problem also exists in 2.6.36 - that's when it was introduced, and I had to revert two commits to fix it: 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to regenerate kernel.release file when make kernelrelease) 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make kernelrelease" should show the correct full kernel version) I don't know if this is related to the OP's issues - I don't use nvidia drivers. -- 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/1f88.4d3bb44a.f1...@getafix.xdna.net
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
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
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
>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
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
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 -- Michal R. Hoffmann -- 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/4d3b5845.7000...@o2.pl
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
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. >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. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: VirtualBox 4 fails building kernel module (the same with nvidia module)
Hi, You're not gonna get much help using non-free software on a tarnished kernel. That said, when i have problems with VBox i just purge everything, dkms included, make sure the drivers are actually deleted, then reinstall, with dkms. Usually does the trick. HTH, Nuno -- Mars 2 Stay! http://xkcd.com/801/ /etc -- 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/AANLkTinK602hY5RJF=4vtr6r_wk3xg1q5feyre0at...@mail.gmail.com
VirtualBox 4 fails building kernel module (the same with nvidia module)
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. I use debian sid, kernel from http://www.kernel.org/ (2.6.32 or 2.6.38-rc1), have build and installed linux-image and linux-headers. Any ideas, please? -- Kind regards, Michal R. Hoffmann -- 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/4d3b20c8.3080...@o2.pl
