WiFi drops randomly while gaming

Cheeseman · 10 January 2026 07:04

I’ve been having issues with my networking for a while now. I’ve gone through 3 motherboards over the last year dealing with different flavors of onboard wifi problems. I’m at my wits end and really don’t want to use windows.

I made the switch to Garuda a few months ago and feel like the transition from windows has been slower than expected. That is, I know very little linux - please be patient with me.

I suppose it only makes sense to focus on the current board/wifi situation here. I’ve tried swapping boards in an attempt to fix what I thought were faulty boards - not so sure now. I have a USB wifi dongle to use when I need to. I dual-boot windows 10 and my mobo has drivers for everything but wifi. So I use that dongle. On both Garuda and windows I get my network dropping randomly.

I started having my system monitor open on my other monitor while gaming to keep an eye on its behavior when things act up. I got a screenshot just a moment ago when I notice another drop. I’d upload/attach it, but new users aren’t allowed.

The upload & download lines drop from normal activity to zero for 0.5 ~ 3 seconds every 20~60 seconds. The dongle doesn’t seem to offer any help on either OS.

I figured out at some point that I didn’t have the correct drivers - which has been resolved, I think. I’ve since been following this forum post for potential things to try. Below are some specific commands I’ve tried just tonight.

sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae  msi=1; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe rtw89_8922ae msi=0 msix=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae swenc=1 ips=0 fwlps=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae pcie_aspm=off; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae pcie_aspm=off pci=nomsi; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae pcie_aspm=off pci=noaer; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae ips=0 rtw_power_mgnt=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae fwlps=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae debug=0 disable_watchdog=N fwlps=N swlps=Y swenc=Y ips=N msi=0; X - X - sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae disable_watchdog=0 swlps=1 swenc=1 ips=0 fwlps=0 msi=1 debug=0 int_clear=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae ips=0 fwlps=0 swlps=1 disable_watchdog=1 int_clear=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae debug=0 disable_watchdog=N fwlps=N swlps=Y swenc=Y ips=N msi=0; X - X - sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae int_clear=0 rtw_power_mgnt=0; sudo systemctl start NetworkManager
sudo systemctl stop NetworkManager; sudo modprobe -rv rtw89_8922ae; sleep 3; sudo modprobe -v rtw89_8922ae swenc=1 ips=0 swlps=1 fwlps=0 disable_watchdog=1; sudo systemctl start NetworkManager

Any help would be appreciated. Let me know if I’ve missed anything.

garuda-inxi:

System:
Kernel: 6.18.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=26007408-d3a5-4db2-b859-6effa20327fc rw rootflags=subvol=@
quiet loglevel=3
Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.21.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X870 AORUS ELITE WIFI7 v: -CF-WCP
serial: <superuser required>
Mobo: Gigabyte model: X870 AORUS ELITE WIFI7 v: x.x
serial: <superuser required> uuid: <superuser required> Firmware: BIOS
vendor: American Megatrends LLC. v: F2 date: 08/14/2024
Battery:
ID-1: hidpp_battery_0 charge: 79% condition: N/A volts: 3.99 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
serial: <filter> charging: status: discharging cycles: N/A
Device-1: apple_mfi_fastcharge_9-5 model: N/A serial: N/A charge: N/A
status: N/A
CPU:
Info: model: AMD Ryzen 9 9900X bits: 64 type: MT MCP arch: Zen 5 gen: 5
level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
model-id: 0x44 (68) stepping: 0 microcode: 0xB40401A
Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 960 KiB desc: d-12x48 KiB; i-12x32 KiB L2: 12 MiB
desc: 12x1024 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 5479 min/max: 614/5662 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 5479 2: 5479 3: 5479
4: 5479 5: 5479 6: 5479 7: 5479 8: 5479 9: 5479 10: 5479 11: 5479 12: 5479
13: 5479 14: 5479 15: 5479 16: 5479 17: 5479 18: 5479 19: 5479 20: 5479
21: 5479 22: 5479 23: 5479 24: 5479 bogomips: 210787
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070 Ti] vendor: Micro-Star MSI
driver: nvidia v: 590.48.01 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-11) arch: Lovelace
code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
speed: 16 GT/s lanes: 8 link-max: lanes: 16 ports: active: DP-1,DP-2
empty: DP-3,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2782 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Gigabyte driver: N/A alternate: amdgpu arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 73:00.0 chip-ID: 1002:13c0 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
gpu: nv_platform,nvidia,nvidia-nvswitch d-rect: 5120x1440 display-ID: 0
Monitor-1: DP-1 pos: primary,left model: Samsung C49RG9x serial: <filter>
built: 2038 res: mode: 2560x1440 hz: 100 scale: 100% (1) dpi: 55 gamma: 1.2
size: 1190x340mm (46.97x13.23") diag: 1239mm (48.8") modes: max: 2560x1440
min: 640x480
Monitor-2: DP-2 pos: right model: Samsung C49RG9x serial: <filter>
built: 2038 res: mode: 2560x1440 hz: 100 scale: 100% (1) dpi: 55 gamma: 1.2
size: 1190x340mm (46.97x13.23") diag: 1239mm (48.8") modes: max: 2560x1440
min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 25.3.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
memory: 11.71 GiB display-ID: :1.0
API: Vulkan v: 1.4.335 layers: 16 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 Ti driver: nvidia v: 590.48.01 device-ID: 10de:2782
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.6 256 bits)
driver: mesa llvmpipe v: 25.3.3-arch1.1 (LLVM 21.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA AD104 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 73:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 73:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.18.3-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: down mac: <filter>
Device-2: Realtek RTL8922AE 802.11be PCIe Wireless Network Adapter
driver: rtw89_8922ae_git v: kernel modules: rtw89_8922ae pcie: gen: 2
speed: 5 GT/s lanes: 1 port: c000 bus-ID: 07:00.0 chip-ID: 10ec:8922
class-ID: 0280
IF: wlp7s0 state: up mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:4 chip-ID: 0bda:8922
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 12.95 TiB used: 5.35 TiB (41.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD BLACK SN770 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 731100WD temp: 48.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: A750 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000VN008-2DR166
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5980 serial: <filter> fw-rev: SC60 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDXPS240G
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST8000DM004-2U9188
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 156.15 GiB (16.8%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 156.15 GiB (16.8%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 156.15 GiB (16.8%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 156.15 GiB (16.8%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.45 GiB used: 76 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 65.5 C mobo: 50.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.45 GiB
used: 12.83 GiB (42.1%)
Processes: 568 Power: uptime: 2h 13m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.13 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1807 libs: 507 tools: octopi,paru pm: rpm
pkgs: 0 Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash v: 5.3.9
default: fish v: 4.3.3 running-in: konsole inxi: 3.3.40
Garuda (2.11.1-1):
System install date:     2025-09-26
Garuda release:          250916
Last full system update: 2026-01-09
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard garuda-hardware-profile-standard-x11
Windows dual boot:       <superuser required>
Failed units:
--- System Health Check Report ---
24/26 checks run in 0.44 seconds ⌛
Powered by garuda-health 🦅

filo · 10 January 2026 09:48

Hi there, welcome to the forum.
Maybe you could take a look at this suggestion in the Arch wiki:

If it doesn’t work, as usual, make sure to try other kernels as well (e.g. linux-lts).

tbg · 10 January 2026 15:31

Hi there @Cheeseman.

Before we can even start to diagnose your issue, we need to know a bunch of very basic information. Pease answer all questions below in full.

How far is your access point (router) away from your computer?

Are you dealing with transmitting your signal through many walls, or concrete walls?

Are you in a complex with many clashing WiFi signals close by?

Do you have other computers using wifi in your home, if so is their WiFi problem free?

Have you tested your WiFi connection’s signal strength?

Have you tested your WiFi using only the 2.4 GHz band?

Have you tested an alternate router model?

Were the different motherboards you tested all using exactly the same model of WiFi?

There are a ton of different things that would need to be run down to figure out what is causing your WiFi issues.

Or…

In this situation using a desktop computer, I’d highly. recommend switching to a powerline networking solution. For someone having such extreme wifi problems a powerline network adapter setup is likely your best solution from a reliability standpoint. Especially since you stated even Windows has the same type of problem with dropped connections in your location. When even Windows WiFi isn’t working properly you’ve got some pretty big problems.

Yes, a powerline network solution costs more initially, but from a speed and reliability standpoint (especially if gaming) its worth the extra expense.

The beautiful thing about a powerline adapter setup is that you no longer have to deal with installing drivers for Windows or Linux. A powerline networking setup is basically plug and play, and unless your home wiring is 100 years old it should be 100% rock solid.

I’ve used powerline networking in the past for my home computers and it’s pretty near as trouble free as running Ethernet cable, (without the tripping hazard).

I’m not saying your WiFi problems with your Realtek adapter are insurmountable, but from the sounds of things you’ve got your work cut out for you to try and eliminate your issues.

In the future when purchasing a motherboard intended for use with Linux, I’d highly recommend only purchasing motherboards that come with Intel WiFi onboard. I’m not saying Intel WiFi is problem free, but when using Linux, Intel is the way to go.

I’m a little too busy ATM, to try and troubleshoot your WiFi issues. However, if you spend the money for a powerline setup your headaches should be over permanently. Realtek WiFi drivers tend to break pretty regularly upon update. Powerline adapters have no driver issues to deal with, so no headaches. Just a word to the wise.

Seimus · 10 January 2026 16:25

One additional question from me…

Did you connect the Antennas that come with your MOBO to the MOBO?

Cheeseman · 12 January 2026 21:59

All very good points and directions to try out. I’ll keep that intel wifi in mind for future reference. FWIW - my kid got me my current board (listed in the shell output).

Current setup context / additional details

I have a mesh system (2 nodes) with the satellite sitting on my desk. The 2 nodes are connected via Ethernet cable (tripping hazard ). My external antenna is plugged in to the mobo and aimed at the node 3ft away. I used the Gigabyte app in win11 to optimize placement and orientation for signal strength. It’s now -70~85db from what I remember.

I’ve used the powerline networking before and might explore that for the backbone & my PC as part of this process. For now I’m investigating what’s going on. I’m really trying to make linux work for my daily driver.

The game I’ve been testing with has plenty of other issues and is in early access, so I’m expecting some issues. At this point, I’m looking to replicate this baseline behavior in my Garuda OS. Day-to-day usage I don’t really notice any issues in Garuda. Other than maybe having web pages taking a couple of seconds to load sometimes. These issues, so far, are only really noticeable while playing some games. I’d like to get this figured out so I can stream the chaos again.

My Orbi network is WiFi 7 and toutes that it auto-magically switches clients between 2.4, 5, and 6 GHZ based on signal strength. So I don’t have immediate visibility to which one I’m connected to at any given moment. Given that the router is only 3ft (1M) away from the node, I don’t see a point in investigating that yet. I live in a house with only a handful of other networks even listed on my phone/PC, so network congestion seems unlikely.

My kid (who bought me this board) share the same board as me that I just swapped out and noticed the same issues I had disappear. So changing the same board out resulted in the issues I was facing going away. That makes two faulty boards in a row - from two different mfg. While still possible, it seems highly unlikely I’d have a 3/3 faulty boards out of the boxes.

Updates

I ended up “upgrading” my windows install to 11 and got to test things yesterday. I’m considering my wifi behavior on win11 as my baseline going forward. One of the games I’ve been having network related problems with ran mostly fine with a couple various issues:

Once in a while, my network drops and I’m kicked from the server.
Some stuttering / “lag spikes” / network hiccups
once in a while I’ll see the network/wifi tab disappear entirely from windows task manager’s graphs. It comes back on its own after ~5-10 seconds.

I’ve probably missed some details again, so please let me know if you can think of anything.

Cheeseman · 12 January 2026 22:08

@filo - just changed the settings for my rtw89.conf. I’ll look into the kernal version if that doesn’t do it.

That bit about “you may experience unstable connections” seems promising.

Cheeseman · 15 January 2026 17:58

Just an update on this here. I tried the .conf change with no success. I’ve been fighting with joining world/games on win11 since “upgrading” and haven’t had a chance to try updating the kernal version. Is there a guide to simplify this process for me? I’m so tired from fighting with my systems lately.

Apocalypticus · 15 January 2026 18:28

Yes, here it is…

garuda-update

Cheeseman · 15 January 2026 19:06

Well, now I feel silly. I just ran that & will update when I get a chance to run things again.

tbg · 15 January 2026 19:51

Several things worth mentioning about your above statement:

The WiFi 7 Linux drivers from most manufacturers are very immature and many are still far from reliable at this point. Even the WiFi 7 Windows drivers for many models are still far from problem free. Basically, WIFI 7 is still a bit of a crap shoot in Linux at this stage of development. The bugs will get worked out eventually, but we’re not there yet.

Switching constantly between bands is often a big reason for dropped connections. In many cases it’s better to pick one band that seems the most reliable and lock the connection to that single band.

Another thing worth testing is to switch your network to only using IPv4, or IPv6, not both. It’s usually IPv6 that causes dropped connections, but it cuts both ways sometimes.

I would also be sure to disable network manager’s power saving option, (if you haven’t tried this already).

It may also be worth testing the linux-firmware-gitpackage to see if this results in any improvement. Uninstall the package if your WiFi shows no improvement.

You may also want to uninstall the proprietary WiFi driver you installed and return to using the in-kernel driver. Once the proprietary driver is uninstalled test out 3 or 4 different Linux kernels. Test at least the following kernels:

linux-lts
linux-mainline
linux
linux-hardened

Apocalypticus · 15 January 2026 21:48

There’s no reason for that. Things like that are human and happen to all of us from time to time.

Cheeseman · 21 January 2026 15:10

(I don’t understand why I haven’t seen your reply until now - I’ve been checking on this every day. smh.)

I used wavemon recently to try catching anything helpful while gaming and noticed the powersaving was on. Are there some resources/docs you can point me to for turning that off, choosing just one wifi band, and/or uninstalling my current drivers? I’m sure I could figure those out, but I feel like I don’t have much time to dig into things recently. I’ll try these things later today either way.

FWIW - I found bottles for running games. It doesn’t do anything for the network issues, but the other things I’ve run into seem better.

tbg · 22 January 2026 09:05

Hello there my man.

I could be wrong, but I’ve got the feeling I’m far, far older than you my dude. As I’m in my sunset years, I think between the two of us, the odds are it’s far more likely that “I don’t have much time to dig into things”.

Generally, many common suggestions I give have likely been posted dozens of times on this forum, and thousands of times on the interwebz. A quick search should return no shortage of hits If you put in even a modicum of effort.

For example, if you search my statement:

Those search terms result in 50+ hits on the Garuda forum, our search engine doesn’t even bother giving a hit count above 50.

Alternately, you can search the extensive Arch Linux online documentation such as:

Hint:

You know you want to

See: 3.83 NetworkManager in the above link

I also saw a rather surprising solution for Realtek Wifi adapters dropping connections that I’ve never seen before today. install the following packages kwin-x11 and plasma-x11-session. Then, reboot your computer and at the SDDM Login screen select the X11 session (not Wayland).

Apocalypticus · 22 January 2026 13:38

offtopic

We have a saying that “you become more patient with age.”
I always have to strongly disagree with that, because I don’t have that much time left to be patient