USB adapter TP-Link Archer T2U PLUS [RTL8821AU] found but no wifi network

English Hardware
1

My lsusb shows:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 048d:5702 Integrated Technology Express, Inc. RGB LED Controller
Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Nano Receiver
Bus 001 Device 008: ID 2357:0120 TP-Link Archer T2U PLUS [RTL8821AU]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

So my adapter is present. But when I try to use wifi from network manager says
“No wi-fi adapter found”

I check previous similar threads, I didn’t find a solution. In a google search I found this topic which says there is driver in-kernel after 6.13 (mine is 6.13.1-1-default)

2

Post:
modprobe -c | grep 2357

3

mitsos@tumbleweed:~> sudo modprobe -c | grep 2357
[sudo] password for root:
alias usb:v2357p000DddcdscdpicFFisc00ip00in* option
alias usb:v2357p0100ddcdscdpiciscipin rtl8192cu
alias usb:v2357p0100ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p0105ddcdscdpiciscipin mt76x0u
alias usb:v2357p0107ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p0108ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p0109ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p010Bddcdscdpiciscipin mt76x0u
alias usb:v2357p010CddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p0111ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p0115ddcdscdpicFFiscFFipFFin* rtw88_8822bu
alias usb:v2357p0116ddcdscdpicFFiscFFipFFin* rtw88_8822bu
alias usb:v2357p0117ddcdscdpicFFiscFFipFFin* rtw88_8822bu
alias usb:v2357p011EddcdscdpicFFiscFFipFFin* rtw88_8821au
alias usb:v2357p0123ddcdscdpiciscipin mt76x0u
alias usb:v2357p0126ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p012DddcdscdpicFFiscFFipFFin* rtw88_8822bu
alias usb:v2357p012EddcdscdpicFFiscFFipFFin* rtw88_8822bu
alias usb:v2357p0135ddcdscdpicFFiscFFipFFin* rtl8xxxu
alias usb:v2357p0138ddcdscdpicFFiscFFipFFin* rtw88_8822bu
alias usb:v2357p0201ddcdscdpiciscipin option
alias usb:v2357p0201ddcdscdpiciscipin04 qmi_wwan
alias usb:v2357p0601ddcdscdpiciscipin r8152
alias usb:v2357p9000ddcdscdpiciscipin option
alias usb:v2357p9000ddcdscdpiciscipin04 qmi_wwan

4

So no ID of your Chip.
Try this Repo:
zypper ar -f https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Tumbleweed/ Sauerland-hardware
and install:
zypper in rtl8821au-kmp-default
reboot and if secure boot is enabled add the key to the mok.

It is build from the sources you have posted.

5

What this mean. What key?

PS. secure boot is enabled

6

Repository: Sauerland-hardware
Key Fingerprint: E02A 9907 1237 E2D2 9F47 05C1 E81F 5FB0 A416 781F
Key Name: home:Sauerland OBS Project home:Sauerland@build.opensuse.org
Key Algorithm: RSA 2048
Key Created: Fri 26 May 2023 02:20:09 PM EEST
Key Expires: Sun 03 Aug 2025 02:20:09 PM EEST
Rpm Name: gpg-pubkey-a416781f-647095e9

the fingerprint?

7

If you install the kmp, there will also installed a ueficert.rpm.

These has the keys of my obs build inside and if you reboot, you will get a blue screen.

This is the example when installing nvidia drivers and reboot:
https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot

You have to do the same after installing the rtl8821au-kmp.

8

No, this is the key of the Repo.

The files in the rtl8821au-kmp are digitally signed and the key is in the rtl8821au-ueficert.rpm which will be installed as dependency.

But you have to insert the key to the mok database.

9

Would I have the option to boot from snapshot before the blue screen, so to rollback if everything goes wrong?

10

no.

But if the key is not inserted, the files from the kmps are not loaded, nothing more.

All others will work and you can insert the key “by hand” once more.

You have only to follow the 5 picture with the blue mok-screen posted by me for installing nvidia.

11

That is how secure boot works in Linux…

It’s a “feature” added by Microsoft.

12

I stack in password. I don’t have a password for secure boot. So I continue to boot and nothing happened, nothing loaded. How to add key “by hand”?

13

password is root password

14

Post:

mokutil --list-enrolled | grep -iB 10 issue
15

mitsos@tumbleweed:~> mokutil --list-enrolled | grep -iB 10 issue
[key 1]
Owner: 605dab50-e046-4300-abb6-3dd810dd8b23
SHA1 Fingerprint: 46:59:83:8c:82:03:fe:15:52:ad:19:e1:86:09:db:21:7e:3a:d2:4f
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=openSUSE Secure Boot CA, C=DE, L=Nuremberg, O=openSUSE Project/emailAddress=build@opensuse.org

16

But now no blue screen appears, the boot continues as usual

17

Next time please use Code-Tags.

18

I will, I didn’t know, sorry…

19

Thats the normal behavior, only one time after inserting a new kmp.

As root:

mokutil --import /etc/uefi/certs/FA6CB96E.crt

That will import the key for my kernel-modules.

Reboot, go to the blue mok, use the root password.

20 
mitsos@tumbleweed:~> sudo mokutil --import /etc/uefi/certs/FA6CB96E.crt
SKIP: /etc/uefi/certs/FA6CB96E.crt is already enrolled

The wifi continues to not working - “No wifi adapter” in network manager