Arch Linux User Repository

Official binaries of linux-lqx, linux-lqx-headers, and linux-lqx-docs are now available: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#liquorix

Signing key import instructions: sudo pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-keys 9AE4078033F8024D && sudo pacman-key --lsign-key 9AE4078033F8024D; done

@sir_lucjan Are you sure about that? In my /var/lib/dkms/vboxhost you can see this:

drwxr-xr-x 1 root root 144 10.02.2021 08:17 6.1.18_OSE/ lrwxrwxrwx 1 root root 33 08.02.2021 21:48 kernel-5.10.14-arch1-1-x86_64 -> 6.1.18_OSE/5.10.14-arch1-1/x86_64/ lrwxrwxrwx 1 root root 46 08.02.2021 13:47 kernel-5.10.14-hardened1-1-hardened-x86_64 -> 6.1.18_OSE/5.10.14-hardened1-1-hardened/x86_64/ lrwxrwxrwx 1 root root 36 08.02.2021 21:46 kernel-5.10.14-zen1-1-zen-x86_64 -> 6.1.18_OSE/5.10.14-zen1-1-zen/x86_64/

In other words, for my other installed kernels the module it's been created.

Probably the bug has to do with the latest binutils. Similar problems occur on other kernels as well.

Same issue as Anarconda, the make.log says:

DKMS make.log for vboxhost-6.1.18_OSE for kernel 5.10.14-lqx2-1-lqx (x86_64)
Wed 10 Feb 11:41:21 GMT 2021
make: Entering directory '/usr/lib/modules/5.10.14-lqx2-1-lqx/build'
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetadp/VBoxNetAdp.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub() is missing an ELF size annotation
/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: missing symbol for insn at offset 0x0

make[2]: *** [scripts/Makefile.build:279: /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o] Error 255
make[2]: *** Deleting file '/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o'
make[2]: *** Waiting for unfinished jobs....
  LD [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetadp/vboxnetadp.o
  LD [M]  /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/vboxnetflt.o
make[1]: *** [scripts/Makefile.build:496: /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv] Error 2
make: *** [Makefile:1801: /var/lib/dkms/vboxhost/6.1.18_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/5.10.14-lqx2-1-lqx/build'

Usually vboxhost module is build correctly but with 5.10.14 series I'm getting this:

==> dkms install --no-depmod -m vboxhost -v 6.1.18_OSE -k 5.10.14-lqx2-1-lqx Error! Bad return status for module build on kernel: 5.10.14-lqx2-1-lqx (x86_64) Consult /var/lib/dkms/vboxhost/6.1.18_OSE/build/make.log for more information. ==> Warning, `dkms install --no-depmod -m vboxhost -v 6.1.18_OSE -k 5.10.14-lqx2-1-lqx' returned 10

What can I do? Thanks in advance.

@Anarconda, the .12 update was pretty small with no block patches. You might have a bad drive that only sometimes has issues at boot. I recommend checking the smart data on your drives to see if anything is primed to fail soon.

Just to let you know the following messages are shown by dmesg with .12

"[ 161.707995] ata8.00: failed command: READ FPDMA QUEUED [ 161.707999] ata8.00: cmd 60/00:18:20:b7:84/0a:00:2c:00:00/40 tag 3 ncq dma 1310720 in res 40/00:20:20:c1:84/00:00:2c:00:00/40 Emask 0x10 (ATA bus error) [ 161.708000] ata8.00: status: { DRDY } [ 161.708001] ata8.00: failed command: READ FPDMA QUEUED [ 161.708004] ata8.00: cmd 60/00:20:20:c1:84/02:00:2c:00:00/40 tag 4 ncq dma 262144 in res 40/00:20:20:c1:84/00:00:2c:00:00/40 Emask 0x10 (ATA bus error)"

reverting to .11 messages are gone. Thanks for your efforts.

This is likely a Virtualbox issue, not a linux-lqx issue. They have to have their modules be able to be built against this version of the kernel. Usually with custom kernels it takes a bit. I've noticed it for well over a year when using kernels like linux-zen, linux-tkg, etc., and sometimes even regular linux, for the first few versions of a new kernel (like up to X.Y.7 or so)

Virtualbox Machines not working properly after upgrading to the most recent version of Linux-lqx [5.10 and up].
Loading modules: modprobe: FATAL: Module vboxnetadp not found in directory /lib/modules/5.10.4-lqx1-1-lqx
modprobe: FATAL: Module vboxnetflt not found in directory /lib/modules/5.10.4-lqx1-1-lqx
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.10.4-lqx1-1-lqx

I can confirm messages are gone. Thanks again.

@Anarconda, next release (5.10.3.lqx2-1), should fix it. The issue appears to be a BPF feature that depends on userspace tool built with the kernel. The error itself is completely benign otherwise.