On Thu, Apr 29, 2021 at 01:36:13PM +0100, Paul Smith wrote:
Thanks, Jonathan. Can you detect any problem in the make.log:
# more /var/lib/dkms/v4l2loopback/0.12.5/5.11.16-300.fc34.x86_64/x86_64/log/make.log DKMS make.log for v4l2loopback-0.12.5 for kernel 5.11.16-300.fc34.x86_64 (x86_64 ) Thu Apr 29 09:21:31 AM WEST 2021 Building v4l2-loopback driver... make -C /lib/modules/5.11.16-300.fc34.x86_64/build M=/var/lib/dkms/v4l2loopback/ 0.12.5/build modules make[1]: Entering directory '/usr/src/kernels/5.11.16-300.fc34.x86_64' CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o MODPOST /var/lib/dkms/v4l2loopback/0.12.5/build/Module.symvers CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.mod.o LD [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko BTF [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko Skipping BTF generation for /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback .ko due to unavailability of vmlinux make[1]: Leaving directory '/usr/src/kernels/5.11.16-300.fc34.x86_64'
#
That looks like it built OK. Does 'sudo dkms status v4l2loopback' say everything is OK?