Slow and unstable Wifi in Arch Linux

melsonic · 2025-06-18 18:26:07

Hi, I recently installed Arch Linux on my laptop along with Windows 11. Although everything seems to be working fine, I have been facing a lot of issues with slow and unstable wifi. On Windows 11, the wifi is stable and speed is good enough. However, on Arch, the wifi keeps connecting and disconnecting.

Till now I have tried the following steps
- changing the NM backend to iwd
- Setting regdomain
- Disabled power saving option on wlan

Here is my system info
- ASUS TUF Gaming A15 F
- Kernel: Linux 6.15.2-2-cachs
- CPU: AMD Ryzen 7 7435HS (16) @ 4.55 GHz
- GPU: NVIDIA GeForce RTX 2050 [Discrete]
- Network Adapter: Realtek RTL8852BE PCIe

Please help!

Scimmia · 2025-06-18 18:31:33

If you have 'tree' installed, what is the output of `tree /etc/systemd/`? We most often see things like this when people have more than one thing trying to manage the interface.

melsonic · 2025-06-18 18:35:23

❯ tree /etc/systemd
/etc/systemd
├── coredump.conf
├── homed.conf
├── journald.conf
├── journal-remote.conf
├── journal-upload.conf
├── logind.conf
├── network
├── networkd.conf
├── oomd.conf
├── pstore.conf
├── resolved.conf
├── sleep.conf
├── system
│   ├── bluetooth.target.wants
│   │   └── bluetooth.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── dbus-org.bluez.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── dbus-org.freedesktop.Avahi.service -> /usr/lib/systemd/system/avahi-daemon.service
│   ├── dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
│   ├── dbus-org.freedesktop.resolve1.service -> /usr/lib/systemd/system/systemd-resolved.service
│   ├── dbus-org.freedesktop.timesync1.service -> /usr/lib/systemd/system/systemd-timesyncd.service
│   ├── display-manager.service -> /usr/lib/systemd/system/ly.service
│   ├── getty.target.wants
│   │   └── getty@tty1.service -> /usr/lib/systemd/system/getty@.service
│   ├── graphical.target.wants
│   │   └── switcheroo-control.service -> /usr/lib/systemd/system/switcheroo-control.service
│   ├── local-fs.target.wants
│   │   └── ananicy-cpp.service -> /usr/lib/systemd/system/ananicy-cpp.service
│   ├── multi-user.target.wants
│   │   ├── avahi-daemon.service -> /usr/lib/systemd/system/avahi-daemon.service
│   │   ├── docker.service -> /usr/lib/systemd/system/docker.service
│   │   ├── NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
│   │   ├── nvidia-powerd.service -> /usr/lib/systemd/system/nvidia-powerd.service
│   │   ├── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
│   │   └── ufw.service -> /usr/lib/systemd/system/ufw.service
│   ├── network-online.target.wants
│   │   └── NetworkManager-wait-online.service -> /usr/lib/systemd/system/NetworkManager-wait-online.service
│   ├── sockets.target.wants
│   │   ├── avahi-daemon.socket -> /usr/lib/systemd/system/avahi-daemon.socket
│   │   └── systemd-userdbd.socket -> /usr/lib/systemd/system/systemd-userdbd.socket
│   ├── sysinit.target.wants
│   │   ├── systemd-resolved.service -> /usr/lib/systemd/system/systemd-resolved.service
│   │   └── systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service
│   ├── systemd-hibernate.service.wants
│   │   ├── nvidia-hibernate.service -> /usr/lib/systemd/system/nvidia-hibernate.service
│   │   └── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   ├── systemd-suspend.service.wants
│   │   ├── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   │   └── nvidia-suspend.service -> /usr/lib/systemd/system/nvidia-suspend.service
│   ├── systemd-suspend-then-hibernate.service.wants
│   │   └── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   └── timers.target.wants
│       └── fstrim.timer -> /usr/lib/systemd/system/fstrim.timer
├── system.conf
├── timesyncd.conf
├── user
│   ├── default.target.wants
│   │   └── xdg-user-dirs-update.service -> /usr/lib/systemd/user/xdg-user-dirs-update.service
│   ├── pipewire.service.wants
│   │   └── wireplumber.service -> /usr/lib/systemd/user/wireplumber.service
│   ├── pipewire-session-manager.service -> /usr/lib/systemd/user/wireplumber.service
│   └── sockets.target.wants
│       ├── p11-kit-server.socket -> /usr/lib/systemd/user/p11-kit-server.socket
│       ├── pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket
│       └── pipewire.socket -> /usr/lib/systemd/user/pipewire.socket
└── user.conf

This is the output

Last edited by melsonic (2025-06-19 16:35:35)

seth · 2025-06-19 16:24:46

Please use [code][/code] tags, the bbs predated markdown by approximately your age. Edit your post in this regard.

along with Windows 11

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Radio is the #1 victim of this condition.

In doubt please post your complete system journal for the boot after such connection rollercoaster

sudo journalctl -b | curl -F 'file=@-' 0x0.st

NM is very chatty, maybe something shows up (and if it's not a competing service and actually, indeed, truely, really, absolutely not the hibernating windows it might be just roaming between 2.4 and 5GHz)

melsonic · 2025-06-21 09:30:45

Jun 21 14:38:38 neilbenz iwd[738]: event: state, old: disconnected, new: autoconnect_quick
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.2598] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.2601] device (wlan0): new IWD device state is disconnected
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.2641] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.2647] device (wlan0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Jun 21 14:38:38 neilbenz iwd[738]: udev interface=wlan0 ifindex=4
Jun 21 14:38:38 neilbenz avahi-daemon[674]: Server startup complete. Host name is neilbenz.local. Local service cookie is 797014714.
Jun 21 14:38:38 neilbenz iwd[738]: event: connect-info, ssid: Vihari Grand 2C-5G, bss: bc:62:d2:a7:01:29, signal: -67, load: 17/255
Jun 21 14:38:38 neilbenz iwd[738]: event: state, old: autoconnect_quick, new: connecting (auto)
Jun 21 14:38:38 neilbenz kernel: wlan0: authenticate with bc:62:d2:a7:01:29 (local address=1c:ce:51:97:0d:3e)
Jun 21 14:38:38 neilbenz kernel: wlan0: send auth to bc:62:d2:a7:01:29 (try 1/3)
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.8070] device (wlan0): new IWD device state is connecting
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.8073] device (wlan0): Activation: starting connection 'Vihari Grand 2C-5G' (73b5966b-6252-4a7f-af46-7d9ec157701d)
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.8073] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.8074] manager: NetworkManager state is now CONNECTING
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.8075] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 21 14:38:38 neilbenz kernel: wlan0: authenticated
Jun 21 14:38:38 neilbenz kernel: wlan0: associate with bc:62:d2:a7:01:29 (try 1/3)
Jun 21 14:38:38 neilbenz kernel: wlan0: RX AssocResp from bc:62:d2:a7:01:29 (capab=0x111 status=0 aid=9)
Jun 21 14:38:38 neilbenz kernel: wlan0: associated
Jun 21 14:38:38 neilbenz kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by bc:62:d2:a7:01:29
Jun 21 14:38:38 neilbenz iwd[738]: event: state, old: connecting (auto), new: connected
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.9984] device (wlan0): new IWD device state is connected
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.9986] device (wlan0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 21 14:38:38 neilbenz NetworkManager[673]: <info>  [1750496918.9995] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 14:38:39 neilbenz avahi-daemon[674]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::80f8:e1:a5c7:575b.
Jun 21 14:38:39 neilbenz avahi-daemon[674]: New relevant interface wlan0.IPv6 for mDNS.
Jun 21 14:38:39 neilbenz avahi-daemon[674]: Registering new address record for fe80::80f8:e1:a5c7:575b on wlan0.*.
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.2110] dhcp4 (wlan0): state changed no lease
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.3854] dhcp4 (wlan0): state changed new lease, address=192.168.1.29, acd pending
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5561] dhcp4 (wlan0): state changed new lease, address=192.168.1.29
Jun 21 14:38:39 neilbenz avahi-daemon[674]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.29.
Jun 21 14:38:39 neilbenz avahi-daemon[674]: New relevant interface wlan0.IPv4 for mDNS.
Jun 21 14:38:39 neilbenz avahi-daemon[674]: Registering new address record for 192.168.1.29 on wlan0.IPv4.
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5567] policy: set 'Vihari Grand 2C-5G' (wlan0) as default for IPv4 routing and DNS
Jun 21 14:38:39 neilbenz systemd-resolved[464]: wlan0: Bus client set default route setting: yes
Jun 21 14:38:39 neilbenz systemd-resolved[464]: wlan0: Bus client set DNS server list to: 192.168.1.1
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5808] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5821] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5821] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5823] manager: NetworkManager state is now CONNECTED_SITE
Jun 21 14:38:39 neilbenz NetworkManager[673]: <info>  [1750496919.5824] device (wlan0): Activation: successful, device activated.
Jun 21 14:38:40 neilbenz NetworkManager[673]: <info>  [1750496920.1644] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 21 14:38:42 neilbenz systemd[1]: systemd-rfkill.service: Deactivated successfully.

seth · 2025-06-21 10:21:50

That's 2s showing some completely untroubled connection.
What do you think we can read out of that about the suggested problem?

If you want us to look at it, post the journal - not some random excerpt.

Arch Linux

#1 2025-06-18 18:26:07

Slow and unstable Wifi in Arch Linux

#2 2025-06-18 18:31:33

Re: Slow and unstable Wifi in Arch Linux

#3 2025-06-18 18:35:23

Re: Slow and unstable Wifi in Arch Linux

#4 2025-06-19 16:24:46

Re: Slow and unstable Wifi in Arch Linux

#5 2025-06-21 09:30:45

Re: Slow and unstable Wifi in Arch Linux

#6 2025-06-21 10:21:50

Re: Slow and unstable Wifi in Arch Linux

Board footer