On Sun, 21 Dec 2014 14:31:45 +0200 Gevisz <gev...@gmail.com> wrote: > On Sun, 21 Dec 2014 12:34:03 +0100 "J. Roeleveld" <jo...@antarean.org> wrote: > > > On Sunday, December 21, 2014 01:13:01 PM Gevisz wrote: > > > On Sun, 21 Dec 2014 11:47:10 +0100 "J. Roeleveld" <jo...@antarean.org> > > wrote: > > > > On Sunday, December 21, 2014 10:16:50 AM Gevisz wrote: > > > > > Tonight I have compiled a new sys-kernel/gentoo-sources > > > > > version 3.17.7 (the previous version was 3.16.5). > > > > > Everything as usual: > > > > > 1) copy .config from /usr/src/linux-3.16.5-gentoo to /usr/src/linux > > > > > > > > > > that points to the /usr/src/linux-3.17.7-gentoo, > > > > > > > > > > 2) `cd /usr/src/linux` > > > > > 3) `make oldconfig`, > > > > > 4) `make && make modules_install`, > > > > > 5) copy bzImage, .config and System.map to /boot, > > > > > > > > > > and, finally, > > > > > > > > > > 6) `emerge @module-rebuild`. > > > > > > > > > > Unfortunately, the last operation, that in my case usually > > > > > recompiles kernel modules needed for VirtualBox, failed with > > > > > the message I provide below. It is very strange for me > > > > > because I do not think that those (sometimes unconscious :) > > > > > choices I made during `make oldconfig` can influence building > > > > > VirtualBox kernel modules. > > > > > > > > > > >>> Install virtualbox-modules-4.2.24 into > > > > > >>> /var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/image/ > > > > > >>> category app-emulation > > > > > > > > > > * Installing vboxdrv module > > > > > * Installing vboxnetflt module > > > > > * Installing vboxnetadp module > > > > > > > > > > install: cannot stat ‘vboxnetadp.ko’: No such file or directory > > > > > !!! doins: vboxnetadp.ko does not exist > > > > > > > > > > * ERROR: app-emulation/virtualbox-modules-4.2.24::gentoo failed > > > > > (install > > > > > > > > > > phase): * doins failed > > > > > > > > > > * > > > > > * If you need support, post the output of `emerge --info > > > > > > > > > > '=app-emulation/virtualbox-modules-4.2.24::gentoo'`, * the complete > > > > > build > > > > > log and the output of `emerge -pqv > > > > > '=app-emulation/virtualbox-modules-4.2.24::gentoo'`. * The complete > > > > > build > > > > > log is located at > > > > > '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/temp/build.log > > > > > '. > > > > > * The ebuild environment file is located at > > > > > '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/temp/environme > > > > > nt' > > > > > . * Working directory: > > > > > '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work' * S: > > > > > '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work' * QA > > > > > > > > > > Notice: file does not exist: > > > > > * > > > > > * doins: vboxnetadp.ko does not exist > > > > > > > > > > And this is the output from `emerge --info > > > > > '=app-emulation/virtualbox-modules-4.2.24::gentoo'`: > > > > > > > > > > > > > > > Any thought? > > > > > > > > Can you provide the complete build log as well? > > > > > > Yes. > > > > > > The contents of the file > > > /var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/temp/build.log > > > is provided below. > > > > > > > <SNIP - only interested in vboxnetadp build> > > > > > *** Building 'vboxnetadp' module *** > > > make[1]: Entering directory > > > '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxnetadp' > > > make KBUILD_VERBOSE= > > > SUBDIRS=/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxn > > > etadp > > > SRCROOT=/var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxn > > > etadp CONFIG_MODULE_SIG= -C /usr/src/linux modules make[2]: Entering > > > directory '/usr/src/linux-3.17.7-gentoo' > > > CC [M] > > > /var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxnetadp/li > > > nux/VBoxNetAdp-linux.o CC [M] > > > /var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxnetadp/VB > > > oxNetAdp.o > > > /var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxnetadp/li > > > nux/VBoxNetAdp-linux.c: In function ‘vboxNetAdpOsCreate’: > > > /var/tmp/portage/app-emulation/virtualbox-modules-4.2.24/work/vboxnetadp/li > > > nux/VBoxNetAdp-linux.c:186:48: error: macro "alloc_netdev" requires 4 > > > arguments, but only 3 given vboxNetAdpNetDevInit); > > > ^ > > > > Here is the first error, ignoring the rest. > > > > Googling the error brings us to: > > http://pietrushnic.github.io/blog/2014/09/20/virtualbox-dkms-fix-alloc-netdev-problems-when-compiling-with-3-dot-17-dot-0-rcx-headers/ > > > > In short, Kernel 3.7.x has issues with Virtualbox. > > > > Checking the change-log for virtualbox-modules, I find: > > ******virtualbox-modules-4.3.14-r1 (03 Sep 2014) > > > > 03 Sep 2014; Matthew Thode <prometheanf...@gentoo.org> > > +files/virtualbox-modules-3.17.patch, > > +virtualbox-modules-4.3.14-r1.ebuild, > > -virtualbox-modules-4.3.14.ebuild: > > bumping for 3.17 support > > > > ***** > > > > Try a newer version of virtualbox, 4.3.14 or higher would be a good start. > > Thank you. So far my solution would be to stick with 3.16.5 kernel until > its next release or stabilization of the next version of the VirtualBox.
After upgrading to virtualbox 4.3.18 (as it appeared in the stable tree) the problem disappeared.
