22.10 beta: v4l2loopback key was rejected by modprobe

Bug #1991584 reported by Waldo
This bug report is a duplicate of:  Bug #1991725: fails to sign kernel modules. Edit Remove
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
v4l2loopback (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using amd64 version of new 22.10 beta. When I

sudo modprobe v4l2loopback [stuff]

I get:

modprobe: ERROR: could not insert 'v4l2loopback': Key was rejected by service

Looks like a signature issue. Secure boot is on.

Relevant packages involved:

ii v4l2loopback-dkms 0.12.7-2ubuntu1 all Source for the v4l2loopback driver (DKMS)
ii linux-image-5.19.0-15-generic 5.19.0-15.15 amd64 Signed kernel image generic

Should not need to self-sign this. At least didn't in 22.04.

Tried removing/reinstalling but no success.

Cheers!

Tags: v4l2loopback
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in v4l2loopback (Ubuntu):
status: New → Confirmed
Revision history for this message
Blaze (blaze) wrote :

It is not specific for v4l2loopback. You can reproduce this issue with any dkms module, ie iwlwifi-dkms or virtualbox-dkms

Revision history for this message
Waldo (vvaldo) wrote :

.... and nvidia-dkms-515 as I just discovered.

This needs to get fixed quick.

Revision history for this message
Waldo (vvaldo) wrote :

So nvidia-dkms worked in secure boot once I switched drivers away from and then back to nvidia-515.

As for v4l2loopback-dkms -- I tried to install --reinstall, but that didn't work.

Then I noticed here that other packages were actually already providing v4l2loopback:

https://packages.ubuntu.com/kinetic/v4l2loopback-dkms

so I tried just removing it:

sudo apt purge v4l2loopback-dkms

This resulted in other packages not being needed, which I removed with apt autoremove:

  dctrl-tools dh-dkms dkms

Then tried to modprobe v4l2loopback and it worked!

So I'm guessing i must have had it installed 2x-- as it was, in my case, already provided by:

linux-image-5.19.0-21-generic

Hope this helps anyone who's encountered this issue.

tl;dr -- I had v4l2loopback-dkms manually installed in 22.04, but apparently it's not needed any more in 22.10 and actually messes things up in secure boot mode, so apt purge it.

Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

I guess this is a duplicate of bug #1991725.

Revision history for this message
Jorge Pérez Lara (jorgesgk) wrote :

Please check this solution: It worked for me for the broadcom wl.ko module. Maybe it may work for your module too?

https://discourse.ubuntu.com/t/dkms-package-support-extra-drivers-does-not-work-in-ubuntu-22-10-install-media/31655

There's a typo, though. The command should be:

sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der /lib/modules/5.19.0-23-generic/updates/dkms/wl.ko

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.