https://bugzilla.suse.com/show_bug.cgi?id=1231068 https://bugzilla.suse.com/show_bug.cgi?id=1231068#c2 Alexander Krupp <obs@akr.yagii.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID Flags|needinfo?(obs@akr.yagii.de) | --- Comment #2 from Alexander Krupp <obs@akr.yagii.de> --- Solved. Thank you for reminding me of secure boot and, implicitely, the intricacies of MOKs. The module is from the official repo. I cloned the system to a new machine, loosing the following relevant key in the process: name: v4l2loopback vermagic: 6.4.0-150600.21-default SMP preempt mod_unload modversions sig_id: PKCS#7 signer: openSUSE Secure Boot CA sig_key: FA:BE:D8:BF:40:9A:5E:65 After enrolling the certificate with mokutil, the module loads like a charm. I'll resolve this as INVALID. --- zypper info v4l2loopback-kmp-default --- Information for package v4l2loopback-kmp-default: ------------------------------------------------- Repository : Main Repository Name : v4l2loopback-kmp-default Version : 0.13.1_k6.4.0_150600.21-lp156.1.8 Arch : x86_64 Vendor : openSUSE Installed Size : 145.4 KiB Installed : Yes Status : up-to-date Source package : v4l2loopback-0.13.1-lp156.1.8.src Upstream URL : https://github.com/umlaeute/v4l2loopback Summary : A kernel module to create V4L2 loopback devices --- modprobe v4l2loopback journalctl: --- Oct 01 11:57:05 xxx kernel: Loading of module with unavailable key is rejected --- -- You are receiving this mail because: You are the assignee for the bug.