linuxwacom / input-wacom

Linux kernel driver for Wacom devices
GNU General Public License v2.0
611 stars 58 forks source link

Wacom module not loaded for "key rejected by service" in Secure Boot #432

Open Vittucci opened 2 months ago

Vittucci commented 2 months ago

I have a Wacom One and I am trying to install the input-wacom drivers (last version, 1.2) in Ubuntu 22.04 on a Dell Precision following the instructions.

The installation went fine, the module is loaded and the tablet works well if I disable "Secure Boot".

However, when Secure Boot is enabled, the module is not loaded and the tablet does not work. This is the output of the command sudo modprobe wacom:

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

This is in spite of the fact that I followed the instructions at the page Secure Boot.

sudo update-secureboot-policy --new-key sudo mokutil --import /var/lib/shim-signed/mok/MOK.der

SKIP: /var/lib/shim-signed/mok/MOK.der is already enrolled

I have also tried to solve the issue by running the following commands:

if test -x ./autogen.sh --with-signing-key=/root/MOK.priv --with-signing-cert=/root/MOK.der; then ./autogen.sh --with-signing-key=/root/MOK.priv --with-signing-cert=/root/MOK.der; else ./configure --with-signing-key=/root/MOK.priv --with-signing-cert=/root/MOK.der; fi && make && sudo make install || echo "Build Failed"

and

if test -x ./autogen.sh --with-signing-key=/var/lib/shim-signed/mok/MOK.priv --with-signing-cert=/var/lib/shim-signed/mok/MOK.der; then ./autogen.sh --with-signing-key=/var/lib/shim-signed/mok/MOK.priv --with-signing-cert=/var/lib/shim-signed/mok/MOK.der; else ./configure --with-signing-key=/var/lib/shim-signed/mok/MOK.priv --with-signing-cert=/var/lib/shim-signed/mok/MOK.der; fi && make && sudo make install || echo "Build Failed"

Also in these cases the installation process goes fine, but the issue is still there.

Any suggestion?

Thanks.

meta4icalbot commented 1 month ago

Same here - Fedora 6.10.3-200.fc40.x86_64

Screenshot from 2024-08-10 22-25-05

This missing signing_key.pem file seems to be the issue but my research has not turned up anything useful so far. Following the Secure Boot guide seemed to make no difference.