You are not logged in.
Hello,
I have a TP-Link Archer T3U USB wifi adapter, and I can see it fine when I run 'lsusb' however I can not see any wlan interace when I run 'ip link'.
My understanding is that this means I do not have the correct driver installed.
However, I have installed this driver without issue: https://aur.archlinux.org/packages/rtl88x2bu-dkms-git which I believe is the correct one.
When I run 'dkms status' I see that the driver is installed.
I am running an up-to-date Arch installation with the linux-lts kernel and headers. DE is KDE.
Am I doing something wrong?
Thanks in advance.
Nate
Last edited by linuxdeveloper.io (2022-03-28 21:02:47)
Offline
What *do* you have with ip link? wlan* isn't a default name in Arch anymore.
Offline
Also
which I believe is the correct one
post "lsusb" and the system journal ("sudo journalctl -b | curl -F 'file=@-' 0x0.st") because TP-Link wraps random chips under their brand that can differ from one gen to another.
It'll also tell us which drivers get loaded and whether there're any errors in that.
Online
What *do* you have with ip link? wlan* isn't a default name in Arch anymore.
It only shows the Ethernet link.
[user@host ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether d8:bb:c1:40:d9:86 brd ff:ff:ff:ff:ff:ff
[user@host ~]$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
Bus 003 Device 010: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 009: ID 0c45:7692 Microdia USB Keyboard
Bus 003 Device 008: ID 2357:0604 TP-Link TP-Link UB500 Adapter
Bus 003 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1462:7c56 Micro Star International MYSTIC LIGHT
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Also
which I believe is the correct one
post "lsusb" and the system journal ("sudo journalctl -b | curl -F 'file=@-' 0x0.st") because TP-Link wraps random chips under their brand that can differ from one gen to another.
It'll also tell us which drivers get loaded and whether there're any errors in that.
Offline
I am running an up-to-date Arch installation with the linux-lts kernel and headers.
The journal shows that you are not booting the -lts kernel. Did you compile the module for the 'linux' kernel as well?
Offline
linuxdeveloper.io wrote:I am running an up-to-date Arch installation with the linux-lts kernel and headers.
The journal shows that you are not booting the -lts kernel. Did you compile the module for the 'linux' kernel as well?
This is because when I try to install linux-lts with 'sudo pacman -S linux-lts' I get the following error:
Error! Bad return status for module build on kernel: 5.15.31-1-lts (x86_64)
Consult /var/lib/dkms/rtl8822bu/5.8.7.4/build/make.log for more information.
When I check the make.log file I see this error:
/var/lib/dkms/rtl8822bu/5.8.7.4/build/core/rtw_br_ext.c:20:18: fatal error: net/ipx.h: No such file or directory
My understanding is that ipx.h was removed from 5.15 and the latest version.
So it seems the driver only works with lts? But it won't compile with lts? I am confused.
Nate
Offline
AUR comments say that it builds fine with 5.16, so the question is if you built it with that, since that's the kernel you're using.
Offline
Can you please explain how I build it for 5.16? Doesn't 'yay -S rtl88x2bu-dkms-git' build it for the current kernel?
Offline
It builds for whatever kernels/headers are installed. The log tells you what it's actually doing.
Offline
I was wrong when I said I was on the latest version of Arch, I was running the 5.15 kernel. After installing the 5.16 kernel it worked. Thank you for your help!
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Done
Offline