[Solved]Network connection random drops

Wroric · 2025-11-28 21:51:58

Hello, I just started using Archlinux with KDE+SDDM on a new laptop and the connection drops regularly, and it keeps me from using Steam to stream games on it. Here are all the info I can give so far:

My Laptop Specs:

Operating System: Arch Linux
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.12.59-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8365U CPU @ 1.60GHz
Memory: 32 Gio of RAM (31.1 Gio usable)
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: HP
Product Name: HP EliteBook 840 G6
System Version: SBKPFV3

What I've tested so far:

I've checked other devices, their connections works fine, so it's not coming for my local connection.

It happens with Wifi and Ethernet connection, same regularity.

I tried a bunch of commands to dig info but for the most part i'm too much of a newbie to interpret it correctly:

> lspci -k | grep -A 3 -i network
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11)
Subsystem: Intel Corporation Device 0030
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

~> tree
/etc/systemd/system/
/etc/systemd/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.network1.service -> /usr/lib/systemd/system/systemd-networkd.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/sddm.service
|-- getty.target.wants
| `-- getty@tty1.service -> /usr/lib/systemd/system/getty@.service
|-- multi-user.target.wants
| |-- NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
| |-- iwd.service -> /usr/lib/systemd/system/iwd.service
| |-- remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
| |-- systemd-networkd.service -> /usr/lib/systemd/system/systemd-networkd.service
| `-- ufw.service -> /usr/lib/systemd/system/ufw.service
|-- network-online.target.wants
| |-- NetworkManager-wait-online.service -> /usr/lib/systemd/system/NetworkManager-wait-online.service
| `-- systemd-networkd-wait-online.service -> /usr/lib/systemd/system/systemd-networkd-wait-online.service
|-- sockets.target.wants
| |-- systemd-networkd-varlink.socket -> /usr/lib/systemd/system/systemd-networkd-varlink.socket
| |-- systemd-networkd.socket -> /usr/lib/systemd/system/systemd-networkd.socket
| |-- systemd-resolved-monitor.socket -> /usr/lib/systemd/system/systemd-resolved-monitor.socket
| |-- systemd-resolved-varlink.socket -> /usr/lib/systemd/system/systemd-resolved-varlink.socket
| `-- systemd-userdbd.socket -> /usr/lib/systemd/system/systemd-userdbd.socket
|-- sysinit.target.wants
| |-- systemd-network-generator.service -> /usr/lib/systemd/system/systemd-network-generator.service
| |-- systemd-resolved.service -> /usr/lib/systemd/system/systemd-resolved.service
| `-- systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service
`-- timers.target.wants
`-- fstrim.timer -> /usr/lib/systemd/system/fstrim.timer

Please let me know if you need more info, thanks

Last edited by Wroric (2025-12-13 09:48:53)

V1del · 2025-11-29 02:14:50

You have three conflicting network services running. Assuming you want sys tray integration, disable systemd-networkd and iwd and only keep NetworkManager enabled. Reboot your system after doing so, check whether things have gotten more stable.

Wroric · 2025-11-29 04:22:38

Yes it worked, thank you very much

seth · 2025-11-29 09:33:49

\o/
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.

Wroric · 2025-11-29 14:25:36

I was about to do that but the problem came back, or rather i think i didn't test the connection long enough.
There is a slight difference, the drops occur less often (from one every 5 to one every 10-12 minutes approximately).
Systemd-networkd and iwd are still disabled.

seth · 2025-11-29 15:58:23

Please post your complete system journal for the boot after such connection losses

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

Wroric · 2025-11-29 16:42:39

Here's the result as you requested :
http://0x0.st/K4Db.txt

Last edited by Wroric (2025-11-29 16:44:53)

seth · 2025-11-29 16:49:58

The journal is only 2 minutes and there's no indication for any kind of network loss in it.
You connect to 'Livebox-24A0' on 5280 MHz w/o any issues.

What's your metric for "drops" here?
nb. you're running UFW (a firewall)

Wroric · 2025-11-29 17:08:46

I use the ping command and test it out with Steam with the graph visuals for network perf of the remote play activated.
With the ping 1.1.1.1 command, I visualize the drops when the time go from 3-5 to 90-100, in sync with the drops with Steam.
nb:I will check if there is a known issue between ufw and steam remote play, thanks for the tip.

Last edited by Wroric (2025-11-29 17:14:28)

seth · 2025-11-29 17:18:44

Please monitor

ping _gateway

Edit: also did that actually happen during the 2 minutes covered by the journal you posted?

Last edited by seth (2025-11-29 17:22:32)

Wroric · 2025-11-29 17:40:19

Yes, it happened just before i hit the command to generate the journal. It tend to happen every 10 minutes, but the first drop happen very soon after the boot.

And it also happen just now with ping _gateway.

Time at 3 to 6ms in general, and the "drop" is at 113ms, the second one just 4 minutes later, at 120ms.

I also allowed the ports for steam remote in ufw, just in case.

seth · 2025-11-29 17:47:07

Nov 29 17:32:03 Prozac wpa_supplicant[581]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=0
Nov 29 17:32:14 Prozac wpa_supplicant[581]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-69 noise=9999 txrate=780000

Can you get closer to the AP and test the stability there? (-70db isn't outright terrible but it's also not exactly good)

Wroric · 2025-11-29 18:05:06

I just tested with my laptop right above the AP, and indeed the "drops" still occurs but are significantly smaller (20-30ms).
I tried Steam and the drops in the remote play stays as violent as they were (from 60 fps to 12-15fps, during 3 seconds to several minutes btw).

seth · 2025-11-29 18:26:16

Can you test the (steam) performance w/ the wired connection (just to see whether that's driven by the wifi performance at all)
Also test ping w/o running steam (or any other known network traffic resp. monitor the latter) to make sure it's not simply impacted by the side-load.

Wroric · 2025-11-29 19:10:05

Okay, so for the Steam performance, on wired it worked just fine (which is an important improvement, because yesterday the drops occured also with the wired connection).
Ping stay the same w/o anything running by it with wifi.

Last edited by Wroric (2025-11-29 19:11:10)

Wroric · 2025-11-29 22:45:11

I've continued to do some digging, like showed my wifi card seems to be not recognized properly when i use this command :

 ~> lspci -k | grep -A 3 -i network
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11)
        Subsystem: Intel Corporation Device 0030
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

Also, i found this other command line in some post about my exact wifi card not working properly, which give me the following result:

> sudo dmesg | grep -i iwlwifi 
[sudo] password for wroric: 
[    5.716477] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    5.718004] iwlwifi 0000:00:14.3: Detected crf-id 0x2816, cnv-id 0x1000100 wfpm id 0x80000000
[    5.718024] iwlwifi 0000:00:14.3: PCI dev 9df0/0030, rev=0x312, rfid=0x105110
[    5.718030] iwlwifi 0000:00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz
[    5.730921] iwlwifi 0000:00:14.3: WRT: Overriding region id 0
[    5.730926] iwlwifi 0000:00:14.3: WRT: Overriding region id 1
[    5.730929] iwlwifi 0000:00:14.3: WRT: Overriding region id 2
[    5.730931] iwlwifi 0000:00:14.3: WRT: Overriding region id 3
[    5.730933] iwlwifi 0000:00:14.3: WRT: Overriding region id 4
[    5.730934] iwlwifi 0000:00:14.3: WRT: Overriding region id 6
[    5.730936] iwlwifi 0000:00:14.3: WRT: Overriding region id 8
[    5.730938] iwlwifi 0000:00:14.3: WRT: Overriding region id 9
[    5.730942] iwlwifi 0000:00:14.3: WRT: Overriding region id 10
[    5.730945] iwlwifi 0000:00:14.3: WRT: Overriding region id 11
[    5.730947] iwlwifi 0000:00:14.3: WRT: Overriding region id 15
[    5.730948] iwlwifi 0000:00:14.3: WRT: Overriding region id 16
[    5.730950] iwlwifi 0000:00:14.3: WRT: Overriding region id 18
[    5.730958] iwlwifi 0000:00:14.3: WRT: Overriding region id 19
[    5.730961] iwlwifi 0000:00:14.3: WRT: Overriding region id 20
[    5.730966] iwlwifi 0000:00:14.3: WRT: Overriding region id 21
[    5.730969] iwlwifi 0000:00:14.3: WRT: Overriding region id 28
[    5.731474] iwlwifi 0000:00:14.3: loaded firmware version 46.7e3e4b69.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[    6.099122] iwlwifi 0000:00:14.3: base HW address: 54:8d:5a:be:3c:aa, OTP minor version: 0x4

(And i figured how to insert properly code in here, baby steps!)

Hope it wiil be useful, thanks for your time and your patience !

Wroric · 2025-11-30 19:32:14

Extra info: It seems that my wifi card is not supported by iwlwifi (not listed in https://wiki.debian.org/iwlwifi#supported ). Is there an alternative of iwlwifi for Intel wifi cards ? Or am I sentenced to buy an usb wifi adapter ?

seth · 2025-11-30 21:07:28

https://wiki.debian.org/iwlwifi#supported wrote:

Debian 3.16 (3.16.7-ckt9-2) kernel images

Your hardware didn't exist when that kernel was current.
Also if the module would not support the chip it would not show up in lspci and the wifi would not work at all.

Disable powersaving:

iwlmvm. power_scheme=1 iwlwifi.power_save=0

https://wiki.archlinux.org/title/Kernel_parameters

iw dev wlan0 set power_save off

This setting is transient, see https://wiki.archlinux.org/title/Power_ … interfaces (which does the exact opposite)

Can you test the NIC against a different AP (your phone hotspot or switch the current AP to a 2.4GHz channel)?

Wroric · 2025-11-30 21:41:40

So I tested a different AP (the router at my neighbor's apartment, after asking him of course), same "drops" occurs.
I disabled powersaving as you suggested, and the "drops" remains, but are less powerful. It's still pretty annoying when using steam remote, but it's clearly an improvement.
I tested also after this on my neighbor's AP and mine, same behavior in each case.

seth · 2025-11-30 21:45:25

Do you also get those drops w/ "ping -n _gateway"?

Wroric · 2025-11-30 22:03:48

Yes, but it get globally better, during 10 minutes of running ping -n _gateway, I've got 7 "drops", one 115ms, two 40ms and four 20ish ms. The avg time is still at 3-6ms.

seth · 2025-11-30 22:16:45

Might be your DNS server, try to set it to 1.1.1.1 (cloudflare) or 8.8.8.8 (google)

Wroric · 2025-11-30 22:25:27

Changed it but no effect, drops still there.

seth · 2025-12-01 16:38:03

Let's see whether there's an obvious pattern to the drops…

ping -c64 _gateway

(this is gonna ping _gateway 64 times and hopefully be enough)

Wroric · 2025-12-01 19:26:15

Here's the result :

~> ping -c64 _gateway
PING _gateway (fe80::1adf:26ff:fe12:5210%wlan0) 56 data bytes
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=1 ttl=64 time=9.04 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=2 ttl=255 time=5.45 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=3 ttl=255 time=8.51 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=4 ttl=255 time=6.16 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=5 ttl=255 time=4.93 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=6 ttl=255 time=5.26 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=7 ttl=255 time=5.74 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=8 ttl=255 time=7.04 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=9 ttl=255 time=4.92 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=10 ttl=255 time=6.08 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=11 ttl=255 time=5.67 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=12 ttl=255 time=6.34 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=13 ttl=255 time=6.10 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=14 ttl=255 time=7.95 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=15 ttl=255 time=7.18 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=16 ttl=255 time=6.69 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=17 ttl=255 time=6.13 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=18 ttl=255 time=5.56 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=19 ttl=255 time=5.33 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=20 ttl=255 time=6.13 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=21 ttl=255 time=5.88 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=22 ttl=255 time=4.09 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=23 ttl=255 time=5.84 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=24 ttl=255 time=5.97 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=25 ttl=255 time=6.26 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=26 ttl=255 time=6.56 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=27 ttl=255 time=65.6 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=28 ttl=255 time=69.9 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=29 ttl=255 time=5.84 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=30 ttl=255 time=6.27 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=31 ttl=255 time=5.67 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=32 ttl=255 time=5.97 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=33 ttl=255 time=6.08 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=34 ttl=255 time=5.21 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=35 ttl=255 time=5.63 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=36 ttl=255 time=5.76 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=37 ttl=255 time=5.36 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=38 ttl=255 time=7.81 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=39 ttl=255 time=4.16 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=40 ttl=255 time=5.59 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=41 ttl=255 time=5.81 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=42 ttl=255 time=5.17 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=43 ttl=255 time=5.92 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=44 ttl=255 time=4.52 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=45 ttl=255 time=7.43 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=46 ttl=255 time=6.45 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=47 ttl=255 time=5.57 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=48 ttl=255 time=7.56 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=49 ttl=255 time=6.04 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=50 ttl=255 time=5.47 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=51 ttl=255 time=5.95 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=52 ttl=255 time=5.80 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=53 ttl=255 time=6.43 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=54 ttl=255 time=5.41 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=55 ttl=255 time=5.39 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=56 ttl=255 time=5.85 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=57 ttl=255 time=5.75 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=58 ttl=255 time=10.1 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=59 ttl=255 time=13.6 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=60 ttl=255 time=10.0 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=61 ttl=255 time=5.68 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=62 ttl=255 time=5.95 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=63 ttl=255 time=4.66 ms
64 bytes from _gateway (fe80::1adf:26ff:fe12:5210%wlan0): icmp_seq=64 ttl=255 time=5.56 ms

Arch Linux

#1 2025-11-28 21:51:58

[Solved]Network connection random drops

#2 2025-11-29 02:14:50

Re: [Solved]Network connection random drops

#3 2025-11-29 04:22:38

Re: [Solved]Network connection random drops

#4 2025-11-29 09:33:49

Re: [Solved]Network connection random drops

#5 2025-11-29 14:25:36

Re: [Solved]Network connection random drops

#6 2025-11-29 15:58:23

Re: [Solved]Network connection random drops

#7 2025-11-29 16:42:39

Re: [Solved]Network connection random drops

#8 2025-11-29 16:49:58

Re: [Solved]Network connection random drops

#9 2025-11-29 17:08:46

Re: [Solved]Network connection random drops

#10 2025-11-29 17:18:44

Re: [Solved]Network connection random drops

#11 2025-11-29 17:40:19

Re: [Solved]Network connection random drops

#12 2025-11-29 17:47:07

Re: [Solved]Network connection random drops

#13 2025-11-29 18:05:06

Re: [Solved]Network connection random drops

#14 2025-11-29 18:26:16

Re: [Solved]Network connection random drops

#15 2025-11-29 19:10:05

Re: [Solved]Network connection random drops

#16 2025-11-29 22:45:11

Re: [Solved]Network connection random drops

#17 2025-11-30 19:32:14

Re: [Solved]Network connection random drops

#18 2025-11-30 21:07:28

Re: [Solved]Network connection random drops

#19 2025-11-30 21:41:40

Re: [Solved]Network connection random drops

#20 2025-11-30 21:45:25

Re: [Solved]Network connection random drops

#21 2025-11-30 22:03:48

Re: [Solved]Network connection random drops

#22 2025-11-30 22:16:45

Re: [Solved]Network connection random drops

#23 2025-11-30 22:25:27

Re: [Solved]Network connection random drops

#24 2025-12-01 16:38:03

Re: [Solved]Network connection random drops

#25 2025-12-01 19:26:15

Re: [Solved]Network connection random drops

Board footer