#1139636 modprobe evdi fails with "Key was rejected by service"

#1139636#5
Date:
2026-06-10 12:46:56 UTC
From:
To:
with secure boot enabled "modprobe evdi" fails with

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

Kernel is 7.0.12. dkms is version 3.2.2-1.

Hardware is a Lenovo P53s with Lenovo's new secure boot certificates
installed.


Regards
Harri

#1139636#10
Date:
2026-06-10 14:28:15 UTC
From:
To:

Hi Harri,

With secure boot enabled, Linux automatically sets itself into "lockdown
mode" (`man 7 kernel_lockdown`).  One of the effects of this is that kernel
modules must be signed by a key which is trusted --- in the case of shim, a
user key is automatically installed.  However, because you're dealing with
a Lenovo that comes with Linux from the factory, I'm not sure if they're
using the shim or not.

I would look into your boot logs and see if you see a line like "Loading
compiled-in X.509 certificates".  That will be the list of keys installed
at build time and at compile time. If you see Debian in there, then you're
using shim -- in that case, you can follow the instructions at:
https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key to put a enroll
a key and setup dkms to use it.  If you're not using shim... that's a
trickier problem, and I'm not sure off the top of my head how to fix it.
I'd reach out to the Debian support lists and see if anyone has any
suggestions.

Good luck!

Sincerely,

#1139636#15
Date:
2026-06-11 11:42:04 UTC
From:
To:
If I run dpkg-reconfigure evdi-dkms, then there is a line

	Signing key: /var/lib/dkms/mok.key

I had expected everything is set up, but I see my error.
Adding the certificate to the system using mokutil worked
for me. Bug report can be closed.

Regards
Harri

#1139636#20
Date:
2026-07-02 07:17:07 UTC
From:
To:
Version: 1.14.16+dfsg-1

Glad it's fixed!

Sincerely,