Problem with 8812au driver

English Network/Internet
1

I have had a problem with the 8812au driver. My dongle is a Linksys WUSB6300 on openSUSE 15.3
I had read on another thread that secured boot has to be disabled for the module to load, which does seem to be accurate. Per instructions previously received, here is the output of lsusb:

 Bus 005 Device 008: ID 13b1:003f Linksys WUSB6300 802.11a/b/g/n/ac Wireless Adapter [Realtek RTL
8812AU]

I can also provide other information. With secure boot disabled, I get the following warning, but the dongle does work correctly:

new high-speed USB device number 8 using xhci_hcd 
 3701.430963] usb 5-2.2: New USB device found, idVendor=13b1, idProduct=003f, bcdDevice= 0.00 
 3701.430965] usb 5-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 
 3701.430966] usb 5-2.2: Product: WUSB6300 
 3701.430967] usb 5-2.2: Manufacturer: Linksys 
 3701.430967] usb 5-2.2: SerialNumber: 34 
 3701.535006] cfg80211: Loading compiled-in X.509 certificates for regulatory database 
 3701.535181] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' 
 3701.571878] 8812au: loading out-of-tree module taints kernel. 
 3701.572486] 8812au: module verification failed: signature and/or required key missing - taint
ing kernel

With secure boot enabled, I get the following error:

New USB device found, idVendor=13b1, idProduct=003f, bcdDevice= 0.00 
   57.208678] usb 5-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 
   57.208679] usb 5-2.2: Product: WUSB6300 
   57.208680] usb 5-2.2: Manufacturer: Linksys 
   57.208681] usb 5-2.2: SerialNumber: 34 
   57.322986] cfg80211: Loading compiled-in X.509 certificates for regulatory database 
   57.323103] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' 
   57.395528] 8812au: Loading of module with unavailable key is rejected

Finally, if I try to manually insert the driver under secure boot:

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

The link in the Yast description of the driver points to a git hub version of the driver that is marked as obsolete, but that may not be an updated URL. I asked the git hub developer and he states that he is unaware of the problem and that it should work with secure boot, but that DKMS needs to be enabled.

2

So what problem with driver do you have? It seems to work.

if I try to manually insert the driver under secure boot:

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

Why do you expect that manually loading driver will work if automatic loading did not?

I asked the git hub developer and he states that he is unaware of the problem and that it should work with secure boot, but that DKMS needs to be enabled.

DKMS has absolutely nothing to do with secure boot. You need to sign module with your key and enroll corresponding certificate into firmware. You did not explain where your driver comes from or how you built it so it is impossible to say anything more specific.

3

It works only if secure boot is disabled. I was trying to see if there is a way around that problem since secure boot does add more protection.
I didn’t expect it to work by manual insertion of the driver. It was done only for informational purposes.

Since my original post, I have installed the newest version form Sauerland, along with the efi certificate. I’ll post back after a reboot.

4

Solved with Sauerland driver and efi-cert. I was prompted for MOK managment upon reboot and installed the key.