Arch Linux

Eino

Member

Registered: 2023-01-25

Posts: 4

Intermittent wifi dropouts

Here's the log I think is most relevant; please let me know if there are other relevant logs. Each time a disconnect occurs, there is a similar entry to the one below in the logs.

journalctl -ef

---
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: carrier lost - roaming
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: changing route to 192.168.0.0/24
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: changing default route via 192.168.0.2
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: carrier acquired
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: IAID a9:fb:d9:3e
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: rebinding lease of 192.168.0.162
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: leased 192.168.0.162 for 7200 seconds
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: changing route to 192.168.0.0/24
Jan 24 21:43:45 defiant dhcpcd[796]: wlp0s20f3: changing default route via 192.168.0.2
---

Last edited by Eino (2026-03-25 19:35:13)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,483

Re: Intermittent wifi dropouts

You've at least dhcpcd and NM enabled and they're gonna knock each other out.
Post the output

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

If you intend to use NM, disable all other network managing services.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,111

Re: Intermittent wifi dropouts

dhcpcd is running in these outputs so it isn't disabled. Post

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Edit: Fuck I took to long to realise the cmd is probably in my clipboard history

Last edited by V1del (2023-01-25 08:50:30)

Eino

Member

Registered: 2023-01-25

Posts: 4

Re: Intermittent wifi dropouts

Thanks for the prompt replies!

Output:

adsklicensing.service                    | multi-user.target.wants
avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
bumblebeed.service                       | graphical.target.wants
cronie.service                           | multi-user.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
muse-hub.service                         | multi-user.target.wants
netctl@wlp0s20f3\x2dwn.service           | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.service                       | multi-user.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
xdg-user-dirs-update.service             | default.target.wants

I have no memory of installing or enabling netctl. I've removed the package, and rebooted. It no longer appears as an entry in the above output. I'm not seeing any dhcpcd in the logs anymore (I assume a consequence of either rebooting or removing netctl), but the dropouts have not stopped. Here's the journalctl output now:

Jan 25 08:13:15 defiant NetworkManager[473]: <warn>  [1674652395.1190] device (wlp0s20f3): link timed out.
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.1195] device (wlp0s20f3): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.1199] manager: NetworkManager state is now DISCONNECTED
Jan 25 08:13:15 defiant avahi-daemon[465]: Interface wlp0s20f3.IPv6 no longer relevant for mDNS.
Jan 25 08:13:15 defiant avahi-daemon[465]: Leaving mDNS multicast group on interface wlp0s20f3.IPv6 with address fe80::bf24:4c09:d22f:6da9.
Jan 25 08:13:15 defiant avahi-daemon[465]: Interface wlp0s20f3.IPv4 no longer relevant for mDNS.
Jan 25 08:13:15 defiant avahi-daemon[465]: Leaving mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.0.164.
Jan 25 08:13:15 defiant avahi-daemon[465]: Withdrawing address record for fe80::bf24:4c09:d22f:6da9 on wlp0s20f3.
Jan 25 08:13:15 defiant avahi-daemon[465]: Withdrawing address record for 192.168.0.164 on wlp0s20f3.
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.1483] device (wlp0s20f3): set-hw-addr: set MAC address to 62:45:CA:0E:65:62 (scanning)
Jan 25 08:13:15 defiant wpa_supplicant[690]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Jan 25 08:13:15 defiant avahi-daemon[465]: Joining mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.0.164.
Jan 25 08:13:15 defiant avahi-daemon[465]: New relevant interface wlp0s20f3.IPv4 for mDNS.
Jan 25 08:13:15 defiant avahi-daemon[465]: Registering new address record for 192.168.0.164 on wlp0s20f3.IPv4.
Jan 25 08:13:15 defiant NetworkManager[473]: <warn>  [1674652395.1493] device (wlp0s20f3): Activation: failed for connection 'wn'
Jan 25 08:13:15 defiant dbus-daemon[468]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=473 comm="/usr/bin/NetworkManager --no-daemon")
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.1499] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.1708] dhcp4 (wlp0s20f3): canceled DHCP transaction
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.1709] dhcp4 (wlp0s20f3): state changed no lease
Jan 25 08:13:15 defiant wpa_supplicant[690]: wlp0s20f3: Reject scan trigger since one is already pending
Jan 25 08:13:15 defiant avahi-daemon[465]: Withdrawing address record for 192.168.0.164 on wlp0s20f3.
Jan 25 08:13:15 defiant avahi-daemon[465]: Leaving mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.0.164.
Jan 25 08:13:15 defiant avahi-daemon[465]: Interface wlp0s20f3.IPv4 no longer relevant for mDNS.
Jan 25 08:13:15 defiant systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 25 08:13:15 defiant dbus-daemon[468]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 25 08:13:15 defiant systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 25 08:13:15 defiant audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 25 08:13:15 defiant kernel: audit: type=1130 audit(1674652395.181:522): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.2047] device (wlp0s20f3): supplicant interface state: scanning -> interface_disabled
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.2048] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> interface_disabled
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.2048] device (wlp0s20f3): supplicant interface state: interface_disabled -> disconnected
Jan 25 08:13:15 defiant NetworkManager[473]: <info>  [1674652395.2048] device (p2p-dev-wlp0s20f3): supplicant management interface state: interface_disabled -> disconnected
Jan 25 08:13:17 defiant wpa_supplicant[690]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.8814] policy: auto-activating connection 'wn' (a0a6c0f8-daab-40ae-8e6f-060064804371)
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.8825] device (wlp0s20f3): Activation: starting connection 'wn' (a0a6c0f8-daab-40ae-8e6f-060064804371)
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.8827] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.8833] manager: NetworkManager state is now CONNECTING
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9124] device (wlp0s20f3): set-hw-addr: reset MAC address to DC:41:A9:FB:D9:3E (preserve)
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9138] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9144] device (wlp0s20f3): Activation: (wifi) access point 'wn' has security, but secrets are required.
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9144] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9148] sup-iface[3832335c76cfd332,0,wlp0s20f3]: wps: type pbc start...
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9163] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9170] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9175] device (wlp0s20f3): Activation: (wifi) connection 'wn' has security, and secrets exist.  No new secrets needed.
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9175] Config: added 'ssid' value 'wn'
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9176] Config: added 'scan_ssid' value '1'
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9176] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9176] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9177] Config: added 'auth_alg' value 'OPEN'
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9177] Config: added 'psk' value '<hidden>'
Jan 25 08:13:17 defiant wpa_supplicant[690]: wlp0s20f3: WPS-CANCEL
Jan 25 08:13:17 defiant wpa_supplicant[690]: wlp0s20f3: SME: Trying to authenticate with 74:da:88:fe:bd:33 (SSID='wn' freq=2417 MHz)
Jan 25 08:13:17 defiant kernel: wlp0s20f3: authenticate with 74:da:88:fe:bd:33
Jan 25 08:13:17 defiant kernel: wlp0s20f3: 80 MHz not supported, disabling VHT
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9631] device (wlp0s20f3): supplicant interface state: disconnected -> authenticating
Jan 25 08:13:17 defiant NetworkManager[473]: <info>  [1674652397.9631] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> authenticating
Jan 25 08:13:17 defiant kernel: wlp0s20f3: send auth to 74:da:88:fe:bd:33 (try 1/3)
Jan 25 08:13:18 defiant wpa_supplicant[690]: wlp0s20f3: Trying to associate with 74:da:88:fe:bd:33 (SSID='wn' freq=2417 MHz)
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.0465] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.0465] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jan 25 08:13:18 defiant kernel: wlp0s20f3: authenticated
Jan 25 08:13:18 defiant kernel: wlp0s20f3: associate with 74:da:88:fe:bd:33 (try 1/3)
Jan 25 08:13:18 defiant kernel: wlp0s20f3: RX AssocResp from 74:da:88:fe:bd:33 (capab=0x431 status=0 aid=4)
Jan 25 08:13:18 defiant wpa_supplicant[690]: wlp0s20f3: Associated with 74:da:88:fe:bd:33
Jan 25 08:13:18 defiant wpa_supplicant[690]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 25 08:13:18 defiant kernel: wlp0s20f3: associated
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.0681] device (wlp0s20f3): supplicant interface state: associating -> 4way_handshake
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.0682] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> 4way_handshake
Jan 25 08:13:18 defiant wpa_supplicant[690]: wlp0s20f3: WPA: Key negotiation completed with 74:da:88:fe:bd:33 [PTK=CCMP GTK=CCMP]
Jan 25 08:13:18 defiant wpa_supplicant[690]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 74:da:88:fe:bd:33 completed [id=0 id_str=]
Jan 25 08:13:18 defiant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1353] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
Jan 25 08:13:18 defiant wpa_supplicant[690]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=26000
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1354] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "wn"
Jan 25 08:13:18 defiant avahi-daemon[465]: Joining mDNS multicast group on interface wlp0s20f3.IPv6 with address fe80::bf24:4c09:d22f:6da9.
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1354] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed
Jan 25 08:13:18 defiant avahi-daemon[465]: New relevant interface wlp0s20f3.IPv6 for mDNS.
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1357] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:18 defiant avahi-daemon[465]: Registering new address record for fe80::bf24:4c09:d22f:6da9 on wlp0s20f3.*.
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1364] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1553] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.0.164
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1564] policy: set 'wn' (wlp0s20f3) as default for IPv4 routing and DNS
Jan 25 08:13:18 defiant avahi-daemon[465]: Joining mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.0.164.
Jan 25 08:13:18 defiant avahi-daemon[465]: New relevant interface wlp0s20f3.IPv4 for mDNS.
Jan 25 08:13:18 defiant avahi-daemon[465]: Registering new address record for 192.168.0.164 on wlp0s20f3.IPv4.
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1653] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1690] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1694] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1700] manager: NetworkManager state is now CONNECTED_SITE
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.1717] device (wlp0s20f3): Activation: successful, device activated.
Jan 25 08:13:18 defiant NetworkManager[473]: <info>  [1674652398.5996] manager: NetworkManager state is now CONNECTED_GLOBAL

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,483

Re: Intermittent wifi dropouts

This only shows that the link times out and then a reconnection, it cannot show the cause for the initial timeout.
Don't post random excerpts, post the entire journal for the boot.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Eino

Member

Registered: 2023-01-25

Posts: 4

Re: Intermittent wifi dropouts

My apologies. Here's the entire log from last boot, with a timeout right at the end.

Last edited by Eino (2026-03-25 19:38:09)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,483

Re: Intermittent wifi dropouts

Jan 27 19:23:04 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=52000
Jan 27 19:53:32 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-56 noise=9999 txrate=144400
Jan 27 19:53:42 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=144400
Jan 27 19:54:20 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-57 noise=9999 txrate=144400
Jan 27 19:54:23 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=144400
Jan 27 19:54:29 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-58 noise=9999 txrate=130000
Jan 27 19:54:58 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=130000
Jan 27 19:55:01 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=144400
Jan 27 20:05:32 defiant kernel: wlp0s20f3: Connection to AP 74:da:88:fe:bd:33 lost
Jan 27 20:05:33 defiant wpa_supplicant[646]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=74:da:88:fe:bd:33 reason=4 locally_generated=1
Jan 27 20:05:33 defiant NetworkManager[516]: <info>  [1674867933.0860] device (wlp0s20f3): supplicant interface state: completed -> disconnected
Jan 27 20:05:33 defiant NetworkManager[516]: <info>  [1674867933.0860] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected
Jan 27 20:05:33 defiant NetworkManager[516]: <info>  [1674867933.1649] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Jan 27 20:05:33 defiant NetworkManager[516]: <info>  [1674867933.1649] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Jan 27 20:05:43 defiant wpa_supplicant[646]: wlp0s20f3: SME: Trying to authenticate with 74:da:88:fe:bd:33 (SSID='wn' freq=2417 MHz)
Jan 27 20:05:43 defiant kernel: wlp0s20f3: authenticate with 74:da:88:fe:bd:33

The signal is ok-ish and the all out of a sudden the AP is gone; there's nothing around that to explain any failure so my best guess would be to disable https://wiki.archlinux.org/title/Power_ … _(iwlwifi)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Eino

Member

Registered: 2023-01-25

Posts: 4

Re: Intermittent wifi dropouts

I set 

options iwlwifi power_save=0

in /etc/modprobe.d/iwlwifi.conf

but the issue appears to persist.

Last edited by Eino (2026-03-25 19:37:42)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,483

Re: Intermittent wifi dropouts

iwlwifi shows up very early, it's maybe in the initramfs.

systool -vm iwlwifi

Since you're on a 2.4GHz band and

Jan 29 02:38:44 defiant kernel: Bluetooth: hci0: Ignoring error of Inquiry Cancel command

immediately precedes the beacon loss, try to disable/rfkill bluetooth.

You can also try to disable the bus power manangement, by adding

pcie_aspm=off

to the kernel commandline.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc