Wifi instability with TP-LINK Archer TX20E

Hello, I’ve been having constant issues recently with a lot of instability with wifi where my connection just dies for no apparent reason and sometimes gets completely disconnected from the network and can’t reconnect until whatever service is handling the network is restarted. So far I’ve tried to switch from NetworkManager to iwd which made no real difference. Something to note is that currently tp-link on their website provides the rtl8852BE driver for wifi which is not supported past linux kernel versions over 6.0.0. The driver currently in use is rtw89, from what I understand from the output of lsmod the driver currently in use is rtw89:

rtw89_8852be           12288  0
rtw89_8852b           376832  1 rtw89_8852be
rtw89_pci              86016  1 rtw89_8852be
rtw89_core            688128  2 rtw89_8852b,rtw89_pci
mac80211             1662976  2 rtw89_core,rtw89_pci
cfg80211             1376256  3 rtw89_8852b,rtw89_core,mac80211

I should also note that using lts kernel 6.1.69-1 somehow breaks everything even more with the adapter not being detected at all.

Here is the inxi output:

 nik@nik-pc ~  inxi -Fxxz
  Kernel: 6.6.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 dm: SDDM
    Distro: EndeavourOS base: Arch Linux
  Type: Desktop System: Gigabyte product: B550 GAMING X V2 v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: B550 GAMING X V2 v: x.x serial: <superuser required>
    UEFI: American Megatrends LLC. v: FDa date: 07/18/2023
  Info: 8-core model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+
    rev: 2 cache: L1: 512 KiB L2: 4 MiB L3: 96 MiB
  Speed (MHz): avg: 3571 high: 4442 min/max: 2200/4549 boost: enabled cores:
    1: 4442 2: 3553 3: 3545 4: 4442 5: 3551 6: 3553 7: 2200 8: 3553 9: 4439
    10: 3550 11: 4442 12: 2200 13: 3552 14: 2200 15: 3551 16: 4371
    bogomips: 108595
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
    vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
    lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 08:00.0
    chip-ID: 1002:73df
  Display: x11 server: X.Org v: 21.1.10 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: 1920x1080 s-dpi: 96
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Samsung C27F390 res: 1920x1080
    dpi: 82 diag: 686mm (27")
  API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    surfaceless: drv: radeonsi x11: drv: radeonsi inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.1-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
    navi22 LLVM 16.0.6 DRM 3.54 6.6.8-zen1-1-zen) device-ID: 1002:73df
  API: Vulkan v: 1.3.274 surfaces: xcb,xlib device: 0 type: discrete-gpu
    driver: amd device-ID: 1002:73df
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 1002:ab28
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 0a:00.4 chip-ID: 1022:1487
  Device-3: Kingston HyperX SoloCast
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 3-3:4 chip-ID: 0951:170f
  API: ALSA v: k6.6.8-zen1-1-zen status: kernel-api
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
  Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network vendor: AzureWave
    driver: rtw89_8852be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 04:00.0 chip-ID: 10ec:b852
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168
  IF: enp5s0 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-9:3 chip-ID: 13d3:3570
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: yes address: N/A
  Local Storage: total: 2.73 TiB used: 582.9 GiB (20.9%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 33.9 C
  ID-2: /dev/sda vendor: Toshiba model: HDWD220 size: 1.82 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-1: / size: 881 GiB used: 420.31 GiB (47.7%) fs: ext4 dev: /dev/nvme0n1p2
  ID-1: swap-1 type: partition size: 34.39 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3
  System Temperatures: cpu: 42.2 C mobo: 27.0 C gpu: amdgpu temp: 42.0 C
    mem: 38.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
  Processes: 378 Uptime: 31m Memory: total: 32 GiB available: 31.26 GiB
  used: 6.44 GiB (20.6%) Init: systemd v: 255 default: graphical Compilers:
  gcc: 13.2.1 clang: 16.0.6 Packages: 1290 pm: pacman pkgs: 1279 pm: flatpak
  pkgs: 11 Shell: nu running-in: tmux: inxi: 3.3.31

I just realized that there is a specific hardware section. I don’t think I can move this however.

Not sure if this helps.

1 Like

Alright I’ll attempt running this for a few days and tell you if it helps. Thanks for the help.

Well so far no other problems so I guess I just need the git version of the driver which isn’t ideal but much better than my previous situation.

Lets hope it stays that way at least for a while. I think this chip is pretty new.

Edit: I have a number of tp-link wifi Pcie-e adapters and i just picked up a newer one not installed yet which is an Archer also but don’t remember the model off the top of my head. It is the AX standard though.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.