Arch Linux User Repository

If you encountered any problems, set debug log use echo 5 > /proc/net/rtl88x2bu/log_level or modprobe 88x2bu rtw_drv_log_level=5, and post your dmesg and network managers logs to https://pastebin.com/ .

@RinCat, one thing I could add is the NIC seems to be always in DORMANT state, see

3: wlp3s0f0u2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether c6:8f:f9:79:7f:a5 brd ff:ff:ff:ff:ff:ff

@RinCat the Archer T3U is the only interface I have which is able to see and connect to WiFi, so I haven't explicitly selected it but there is no choice. Thanks for the clarification on the drivers

@dpm Hi, did you set which interface to use for that WiFi network? BTW rtl8812b and rtl8822b use the same WiFi driver.

Hi @RinCat, thank you for providing the package. I have recently bought an Archer T3U (rtl8812bu) adapater for my desktop and installed this package. I have the sample problem reported by @sklorpion one month ago. i.e. the dkms seems to be correctly loaded, there is one new NIC, I can see the Wifi from NetworkManager but once inserted a correct password then it keeps asking it and does not connect to the net. There are two things that are strange according to me, looking at the dmesg output: first, the adapter seems to be power up and down cyclically and the second it seems that the adapater is read as rtl8822b and not as rtl8812b as I expected.

Pastebin for dmesg: https://pastebin.com/CvrYESw2

Pastebin for NetworkManager: https://pastebin.com/pA7hnqGk (since you were asking @sklorpion too, the P2P device seems to be created directly from the driver NetworkManager[4517]: <info> [1603440136.8254] Wi-Fi P2P device controlled by interface wlp3s0f0u2 created)

@noideas4thisname try set log_level to 5 and see if something wrong. And is this only happened recently?

I'm facing the same issues as @MildlyProductive and all my networks re-prompt for auth when I know the password is correct. It does not seem like a config issue on the router - I've changed that a few times and can't find a culprit. The driver seems to be loading correctly and I can scan, but connecting fails.

If you encountered any problems, set debug log use echo 5 > /proc/net/rtl88x2bu/log_level or modprobe 88x2bu rtw_drv_log_level=5, and post your dmesg and network managers logs to https://pastebin.com/ .

@MildlyProductive that package is 2018 version driver, and this one is 2020 version. If both have similar issue, I cannot tell when/where the problem come from.

@RinCat only recently. The thing is I previously used this package: https://aur.archlinux.org/packages/rtl8822bu-dkms-git/ but had a similar issue. I then tried this package today and the issue remained.

@MildlyProductive is this happened only recently update, or happened as always? thanks.