I have been looking for a couple of days for information on getting my tp-link AC1300 (Archer T3U) working. I have the drivers installed (i hope they are the right ones) but it is not recognized as a wireless connection.
Here is what I’m working with:
inxi -Fazy
System:
Kernel: 5.19.17-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.19-x86_64
root=UUID=99f6dfd4-9c9b-4fac-8d5c-0b286e0f7477 rw quiet
udev.log_priority=3
Desktop: KDE Plasma v: 5.26.4 tk: Qt v: 5.15.7 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: M5A97 v: Rev 1.xx
serial: <superuser required> BIOS: American Megatrends v: 0901
date: 11/24/2011
CPU:
Info: model: AMD FX-6100 bits: 64 type: MT MCP arch: Bulldozer level: v2
built: 2011 process: GF 32nm family: 0x15 (21) model-id: 1 stepping: 2
microcode: 0x600063E
Topology: cpus: 1x cores: 6 smt: enabled cache: L1: 288 KiB
desc: d-6x16 KiB; i-3x64 KiB L2: 6 MiB desc: 3x2 MiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 1408 high: 1448 min/max: 1400/3300 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1448 2: 1400
3: 1400 4: 1400 5: 1400 6: 1400 bogomips: 39744
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: GCN-4
code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 2
speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: DVI-D-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 01:00.0
chip-ID: 1002:67df class-ID: 0300 temp: 38.0 C
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 444x277mm (17.48x10.91")
s-diag: 523mm (20.6")
Monitor-1: DVI-D-1 mapped: DVI-D-0 model: HP L2045w serial: <filter>
built: 2009 res: 1680x1050 hz: 60 dpi: 99 gamma: 1.2
size: 430x270mm (16.93x10.63") diag: 508mm (20") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: OpenGL v: 4.6 Mesa 22.2.4 renderer: AMD Radeon RX 570 Series
(polaris10 LLVM 14.0.6 DRM 3.47 5.19.17-2-MANJARO) direct render: Yes
Audio:
Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel
bus-ID: 4-4:4 v: kernel chip-ID: 1130:1620 bus-ID: 00:14.2 chip-ID: 1002:4383
class-ID: 0300 class-ID: 0403
Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
chip-ID: 1002:aaf0 class-ID: 0403
Device-3: Tenx USB AUDIO type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound API: ALSA v: k5.19.17-2-MANJARO running: yes
Sound Server-1: JACK v: 1.9.21 running: no
Sound Server-2: PulseAudio v: 16.1 running: yes
Sound Server-3: PipeWire v: 0.3.61 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK P8P67 and other motherboards driver: r8169 v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.36 TiB used: 260.17 GiB (18.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD5000AACS-61M6B2 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
scheme: MBR
Partition:
ID-1: / raw-size: 931.51 GiB size: 915.81 GiB (98.31%)
used: 199.87 GiB (21.8%) fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 16.9 C mobo: N/A gpu: amdgpu temp: 38.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 203
Info:
Processes: 239 Uptime: 3h 55m wakeups: 0 Memory: 15.57 GiB
used: 3.9 GiB (25.1%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 1552 pm: pacman pkgs: 1528
libs: 474 tools: pamac pm: flatpak pkgs: 24 Shell: Zsh v: 5.9 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.24
It appears that the device is recognized:
lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 1130:1620 Tenx Technology, Inc. USB AUDIO
Bus 004 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 004 Device 002: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
But it is not recognized as a network connection:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether c8:60:00:70:20:df brd ff:ff:ff:ff:ff:ff
inet 10.0.0.129/24 brd 10.0.0.255 scope global dynamic noprefixroute enp2s0
valid_lft 171803sec preferred_lft 171803sec
inet 10.0.0.130/24 brd 10.0.0.255 scope global secondary dynamic noprefixroute enp2s0
valid_lft 171808sec preferred_lft 150208sec
inet6 2601:681:202:b0d0::dc95/128 scope global dynamic noprefixroute
valid_lft 213094sec preferred_lft 213094sec
inet6 2601:681:202:b0d0:c2a3:d46d:e4a8:87b5/64 scope global dynamic noprefixroute
valid_lft 300sec preferred_lft 300sec
inet6 2601:681:202:b0d0:1f90:c0a2:ce7c:41dc/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 299sec preferred_lft 299sec
inet6 fe80::3bc0:f8d5:19f6:873c/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::3e3e:2acf:2f17:75e6/64 scope link noprefixroute
valid_lft forever preferred_lft forever
I have searched the internet over (including this forum) and have found similar problems but nothing that gives me a working solution.
Thanks in advance for any assistance.
What one driver you installed?
According to your model, it should be rtl88x2bu-dkms-git from AUR.
Yes, that’s the one. Sorry, I should have included that detail in the original post.
- headers installed? (needed for driver compilation)
pamac install linux519-headers
- driver loaded?
lsusb -vt
I was not aware that this was needed. I thought that installing drivers and restarting would be enough. After following your instructions all is working as advertised.
I guess I still have a lot to learn, especially when it comes to the networking aspects of Linux.
Thank you for the assist.
Which is weird beacuse if you don’t have the headers installed, it should have complained about that during the installation of the driver.
I didn’t notice any complaints, but maybe I just wasn’t paying attention. 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.