Closed RENANZG closed 11 months ago
Your modinfo doesn't show any signature in the module.
user@debian:~$ sudo modinfo rtw_8723du
filename: /lib/modules/6.1.0-11-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw_8723du.ko
license: Dual BSD/GPL
description: Realtek 802.11n wireless 8723du driver
author: Hans Ulli Kroll <linux@ulli-kroll.de>
alias: usb:v7392pD611d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0BDApD723d*dc*dsc*dp*icFFiscFFipFFin*
depends: rtw_usb,usbcore,rtw_8723d
retpoline: Y
name: rtw_8723du
vermagic: 6.1.0-11-amd64 SMP preempt mod_unload modversions
The example of a proper signed module:
# modinfo rtw88_8723d
filename: /lib/modules/5.14.21-150500.55.12-default/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko.zst
license: Dual BSD/GPL
description: Realtek 802.11n wireless 8723d driver
author: Realtek Corporation
firmware: rtw88/rtw8723d_fw.bin
suserelease: SLE15-SP5
srcversion: 954CA4E2A92196B0BE8E3E6
depends: rtw88_core
supported: yes
retpoline: Y
intree: Y
name: rtw88_8723d
vermagic: 5.14.21-150500.55.12-default SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: SUSE Linux Enterprise Secure Boot CA
sig_key: CA:FC:B5:D7:5E:C5:89:82
sig_hashalgo: sha256
signature: 91:30:AA:2A:A8:F9:6C:C7:06:C3:BD:B3:3A:2D:B3:D2:BF:85:4F:09:
3D:5A:E9:52:B9:BC:BF:0D:47:85:65:47:C9:C9:7C:D8:76:00:E7:09:
6F:04:B3:99:ED:DA:F2:27:2E:34:AF:B8:E1:17:0A:1C:87:D8:61:E3:
50:64:86:70:D8:26:7A:02:A8:6E:52:A1:3E:19:C2:3E:75:08:CA:EE:
4C:94:DE:64:A0:28:55:42:D7:7D:E1:E5:53:0D:94:FE:F4:B1:0C:3E:
C1:A4:82:0D:28:A0:57:4A:03:09:82:14:2E:86:80:96:7E:5B:95:D6:
4F:DD:D8:10:FB:96:DA:EC:BC:AC:1C:5F:15:2A:24:BA:64:9C:0B:35:
6F:84:BF:DC:44:C8:E5:B4:9C:8A:DB:A9:66:30:9F:E9:7E:E0:A3:54:
08:3E:A6:FE:A5:28:AA:55:E6:AB:07:0D:B2:FB:60:9A:F2:86:39:CF:
32:78:B1:77:F9:31:13:50:3E:CA:8D:44:2A:BD:69:C3:9C:19:7B:E1:
5C:2D:3E:45:20:58:30:B7:FD:11:BF:D9:60:95:39:17:04:56:9C:A7:
99:C0:5A:18:30:14:A4:B9:F0:03:45:5A:7C:DC:4F:40:90:CE:37:5B:
E5:0F:31:DF:E0:B8:4F:6C:23:AF:B0:2E:27:25:A5:5A
It seems to me that your build process didn't sign the module properly, and this is beyond the scope of mokutil.
Noob here. Why can't I make the module work with secure boot enabled?
As for the kernel:
As for wifi:
[b]I'm pretty sure it has to do with DKMS, as the Debian Wiki tutorial confused me. [/b]
Some possible causes:
Cause:: Kernel module was at two different locations. I found this strange situation:
Other signated driver "de", much more estrange:
Cause: need to create a X.509 key pair (a public key and a corresponding secret key) to use as a MOK.
Cause: Error with DKMS "With the current state of the DKMS package, if a user attempts to install any package that includes a third-party driver (Broadcom WiFi, VirtualBox, v4l2loobpack, etc.), the process of signing the newly built driver with a MOK key will fail silently. This means that any packages and hardware that require third-party drivers are currently unusable on a system with Secure Boot. This bug has been tested and verified to occur with the bcmwl-kernel-source package, but also is very likely to affect any other packages that use DKMS modules."
Its correct to say that "Microsoft screwed this whole MOK stuff up badly" ?
Debian Bug report logs - #989463 please align shim-signed dkms behaviour with Ubuntu
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989463
Thanks !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!