FS#53552 - [virtualbox-host-dkms] "Error! Bad return status for module build ..." on drm-intel-nightly kernels

Attached to Project: Community Packages
Opened by Victor Trac (victortrac) - Monday, 03 April 2017, 18:42 GMT
Last edited by Christian Hesse (eworm) - Thursday, 24 August 2017, 06:43 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I run drm-intel-nightly to resolve some usb-c/external monitor issues. I have been unable to build virtualbox-host-dkms since kernel 4.10.x, and it's still failing on the 4.11.x builds.

I really have no idea how dkms works, so apologies in advance if this is a bad bug report.

Additional info:
* 4.11.0-1-drm-intel-nightly
* /var/lib/dkms/vboxhost/5.1.18_OSE/build/make.log:

DKMS make.log for vboxhost-5.1.18_OSE for kernel 4.11.0-1-drm-intel-nightly (x86_64)
Mon Apr 3 13:37:28 CDT 2017
make: Entering directory '/usr/lib/modules/4.11.0-1-drm-intel-nightly/build'
LD /var/lib/dkms/vboxhost/5.1.18_OSE/build/built-in.o
make[2]: *** No rule to make target '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o', needed by '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetadp/vboxnetadp.o'. Stop.
make[2]: *** Waiting for unfinished jobs....
LD /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetadp/built-in.o
make[1]: *** [scripts/Makefile.build:553: /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetadp] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** No rule to make target '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o', needed by '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetflt/vboxnetflt.o'. Stop.
make[2]: *** Waiting for unfinished jobs....
make[2]: *** No rule to make target '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxdrv/linux/SUPDrv-linux.o', needed by '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxdrv/vboxdrv.o'. Stop.
make[2]: *** Waiting for unfinished jobs....
LD /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetflt/built-in.o
LD /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxdrv/built-in.o
make[2]: *** No rule to make target '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxpci/linux/VBoxPci-linux.o', needed by '/var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxpci/vboxpci.o'. Stop.
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:553: /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxdrv] Error 2
make[1]: *** [scripts/Makefile.build:553: /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxnetflt] Error 2
LD /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxpci/built-in.o
make[1]: *** [scripts/Makefile.build:553: /var/lib/dkms/vboxhost/5.1.18_OSE/build/vboxpci] Error 2
make: *** [Makefile:1492: _module_/var/lib/dkms/vboxhost/5.1.18_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/4.11.0-1-drm-intel-nightly/build'


Steps to reproduce:
1. Build and run kernel from https://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-nightly
2. Run: sudo pacman -S community-testing/virtualbox-host-dkms


This task depends upon

Closed by  Christian Hesse (eworm)
Thursday, 24 August 2017, 06:43 GMT
Reason for closing:  No response
Additional comments about closing:  No response and probably caused by the kernel package.
Comment by Christian Hesse (eworm) - Sunday, 23 April 2017, 10:22 GMT
Did you install the kernel manually? I suppose kernel headers and/or build system are not installed properly.
Other than that... Possibly virtualbox modules are not (yet) compatible with linux 4.11.x - but the messages above indicate that things break before.
Comment by Victor Trac (victortrac) - Sunday, 23 April 2017, 19:13 GMT
@eworm I'm building a custom module using a PKDBUILD that is basically this: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-drm-intel-nightly

I guess I'll compare it to the mainline linux PKGBUILD (https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/linux) to see what's different. If you have a tip, would love to see it.
Comment by Christian Hesse (eworm) - Sunday, 23 April 2017, 20:28 GMT
Make sure the headers package is installed and /usr/lib/modules/$VERSION/build/ contains a valid module build environment.

Did you try to install any other dkms package to verify whether or not this is a kernel issue?

Loading...