Arch Linux

Retoran

Member

Registered: 2023-02-27

Posts: 1

v412loopback-dkms fails to install when kernel upgraded to 6.16.3

As described in the title, the v412loopback 0.15.0 dkms package failed to reinstall itself when the kernel was upgraded to 6.16.3.

This generated this message when upgrading:

( 5/15) Install DKMS modules
...
==> dkms install --no-depmod v4l2loopback/0.15.0 -k 6.16.3-zen1-1-zen

Error! Bad return status for module build on kernel: 6.16.3-zen1-1-zen (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.15.0/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback/0.15.0 -k 6.16.3-zen1-1-zen' exited 10
...
==> dkms install --no-depmod v4l2loopback/0.15.0 -k 6.16.3-arch1-1

Error! Bad return status for module build on kernel: 6.16.3-arch1-1 (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.15.0/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback/0.15.0 -k 6.16.3-arch1-1' exited 10

and the make log looks like this:

DKMS (dkms-3.2.1) make.log for v4l2loopback/0.15.0 for kernel 6.16.3-arch1-1 (x86_64)
Sun 24 Aug 14:59:04 BST 2025

Building module(s)
# command: make -j24 KERNELRELEASE=6.16.3-arch1-1 KERNEL_DIR=/usr/lib/modules/6.16.3-arch1-1/build v4l2loopback
grep: /etc/dkms/framework.conf.d/*.conf: No such file or directory

++++++ To sign the  module, you must set KBUILD_SIGN_KEY/KBUILD_SIGN_CERT to point to the signing key/certificate!
++++++ For your convenience, we try to read these variables as 'mok_signing_key' resp. 'mok_certificate' from /etc/dkms/framework.conf /etc/dkms/framework.conf.d/*.conf

++++++ If your certificate requires a password, pass it via the KBUILD_SIGN_PIN env-var!
grep: /etc/dkms/framework.conf.d/*.conf: No such file or directory
++++++ E.g. using 'export KBUILD_SIGN_PIN; read -s -p "Passphrase for signing key : " KBUILD_SIGN_PIN; sudo --preserve-env=KBUILD_SIGN_PIN make sign'

Building v4l2-loopback driver...
make -C /usr/lib/modules/6.16.3-arch1-1/build M=/var/lib/dkms/v4l2loopback/0.15.0/build KCPPFLAGS="" modules
make[1]: Entering directory '/usr/lib/modules/6.16.3-arch1-1/build'
make[2]: Entering directory '/var/lib/dkms/v4l2loopback/0.15.0/build'
  CC [M]  v4l2loopback.o
v4l2loopback.c: In function ‘v4l2_loopback_add’:
v4l2loopback.c:2904:9: error: implicit declaration of function ‘setup_timer’ [-Wimplicit-function-declaration]
 2904 |         setup_timer(&dev->sustain_timer, sustain_timer_clb, nr);
      |         ^~~~~~~~~~~
make[4]: *** [/usr/lib/modules/6.16.3-arch1-1/build/scripts/Makefile.build:287: v4l2loopback.o] Error 1
make[3]: *** [/usr/lib/modules/6.16.3-arch1-1/build/Makefile:2003: .] Error 2
make[2]: *** [/usr/lib/modules/6.16.3-arch1-1/build/Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/var/lib/dkms/v4l2loopback/0.15.0/build'
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.16.3-arch1-1/build'
make: *** [Makefile:53: v4l2loopback.ko] Error 2

# exit code: 2
# elapsed time: 00:00:00
----------------------------------------------------------------

I assume this is because setup_timer is no longer supported in the new kernel version, but could be wrong.
Unsure if this needs to be raised as an issue for this package, or if the kernel just updated before v412loopback-dkms and it'll soon be updated to be compatible with the new kernel.

loqs

Member

Registered: 2014-03-06

Posts: 18,867

Re: v412loopback-dkms fails to install when kernel upgraded to 6.16.3

See https://gitlab.archlinux.org/archlinux/ … -/issues/4.

Last edited by loqs (2025-08-24 14:23:48)