You are not logged in.
Pages: 1
I have this problem where my WiFi for some reason keeps disconnecting every now and then, beacause the password is incorrect, even though I typed in the correct password. I'm running Kde along with nm on my system, tried a fresh install wich didn't work, tried the solutions from https://bbs.archlinux.org/viewtopic.php?id=224932 which didn't work, and now I'm just stuck.
lspci -k output:
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [Stone Peak 2 AC]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifiip link output:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 18:31:bf:13:d4:56 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether f8:59:71:f1:c7:d7 brd ff:ff:ff:ff:ff:ffOffline
keeps disconnecting every now and then, beacause the password is incorrect
This makes no sense. If you're connected you don't have to issue the password again and if the password is wrong, you won't connect itfp.
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -fOffline
dbus-org.fedoraproject.FirewallD1.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
display-manager.service | system
firewalld.service | multi-user.target.wants
fstrim.timer | timers.target.wants
getty@tty1.service | getty.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
optimus-manager.service | graphical.target.wants
p11-kit-server.socket | sockets.target.wants
pipewire-pulse.socket | sockets.target.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wants
wireplumber.service | pipewire.service.wants
xdg-user-dirs-update.service | default.target.wantsOffline
Unfortunately not that simple - please post your complete system journal for a boot covering the problem,
sudo journalctl -b | curl -F 'file=@-' 0x0.stfor the current one, so we can see what's going on there.
Offline
Offline
May 22 09:45:43 aleks kernel: Linux version 6.9.1-arch1-1 (linux@archlinux) (gcc (GCC) 14.1.1 20240507, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Fri, 17 May 2024 16:56:38 +0000
May 22 09:47:21 aleks wpa_supplicant[611]: wlan0: Associated with 38:43:7d:ba:49:53
May 22 09:47:22 aleks NetworkManager[552]: <info> [1716364042.0604] dhcp4 (wlan0): state changed new lease, address=192.168.0.12
May 22 09:47:22 aleks wpa_supplicant[611]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise=9999 txrate=0
May 22 09:47:25 aleks wpa_supplicant[611]: wlan0: CTRL-EVENT-BEACON-LOSS
May 22 09:47:26 aleks kernel: wlan0: Connection to AP 38:43:7d:ba:49:53 lost
May 22 09:47:26 aleks kernel: iwlwifi 0000:02:00.0: missed beacons exceeds threshold, but receiving data. Stay connected, Expect bugs.
May 22 09:47:26 aleks kernel: iwlwifi 0000:02:00.0: missed_beacons:20, missed_beacons_since_rx:1
May 22 09:47:26 aleks wpa_supplicant[611]: wlan0: CTRL-EVENT-DISCONNECTED bssid=38:43:7d:ba:49:53 reason=4 locally_generated=1
May 22 09:47:27 aleks kernel: wlan0: associated
May 22 09:47:27 aleks NetworkManager[552]: <info> [1716364047.6412] device (wlan0): supplicant interface state: associating -> associated
May 22 09:47:27 aleks NetworkManager[552]: <info> [1716364047.6412] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
May 22 09:47:27 aleks kernel: iwlwifi 0000:02:00.0: missed beacons exceeds threshold, but receiving data. Stay connected, Expect bugs.
May 22 09:47:27 aleks kernel: iwlwifi 0000:02:00.0: missed_beacons:21, missed_beacons_since_rx:1
May 22 09:47:27 aleks kernel: iwlwifi 0000:02:00.0: missed beacons exceeds threshold, but receiving data. Stay connected, Expect bugs.
May 22 09:47:27 aleks kernel: iwlwifi 0000:02:00.0: missed_beacons:22, missed_beacons_since_rx:2
May 22 09:47:35 aleks kernel: iwlwifi 0000:02:00.0: missed_beacons:19, missed_beacons_since_rx:1
May 22 09:47:35 aleks wpa_supplicant[611]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-92 noise=9999 txrate=0
May 22 09:47:45 aleks wpa_supplicant[611]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise=9999 txrate=0
May 22 09:49:41 aleks wpa_supplicant[611]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=86700
May 22 10:22:52 aleks sudo[2570]: aleks : TTY=pts/1 ; PWD=/home/aleks ; USER=root ; COMMAND=/usr/bin/journalctl -b2 minutes into the boot you get connected but 5s later lose the connection, stated reason is "Disassociated due to inactivity" (4), immediately re-connect (no password is ever requested*) but the signal is originally extremely poor (-92 is borderline dead), ~10s later better (did you move closed to the AP?) and then there's no nework actiivity for the next 30m before you drew the journal.
Did that boot actually cover the colported incident?
The extremely poor signal will cause connection losses for pretty much sure.
1. range/distance/walls/em-shields
2. power saving
3. dual boot and hibernating windows, but probably not the case since there're only 3 partitions?
*
May 22 09:45:57 aleks NetworkManager[552]: <info> [1716363957.7030] device (wlan0): Activation: (wifi) access point 'KabelBox-0D54' has security, but secrets are required.
May 22 09:45:57 aleks NetworkManager[552]: <info> [1716363957.7091] device (wlan0): Activation: (wifi) connection 'KabelBox-0D54' has security, and secrets exist. No new secrets needed.Offline
My Wifi is pretty slow just by itself (3 MB/s, which is to be expected from german wifi tbh), but that never caused this problem on windows, I'm not dual booting with windows and I doubt it's any power saving option, since my laptop is plugged in all the time anyway
Offline
Your wifi throughput isn't defined by your geolocation, but the signal strength and available protocol.
https://en.wikipedia.org/wiki/IEEE_802. … escription - 3MB/s sound like 802.11g
I doubt it's any power saving option, since my laptop is plugged in all the time anyway
These two things are not related.
https://wiki.archlinux.org/title/Power_ … interfaces
systool -vm iwlwifi
systool -vm iwlmvm
iw dev wlan0 get power_saveDid that boot actually cover the colported incident?
Offline
Module = "iwlwifi"
Attributes:
coresize = "602112"
initsize = "0"
initstate = "live"
refcnt = "1"
srcversion = "01D67FB5E4BBE08A4EFB7BA"
taint = ""
uevent = <store method only>
Parameters:
11n_disable = "0"
amsdu_size = "0"
bt_coex_active = "Y"
debug = "0"
disable_11ac = "N"
disable_11ax = "N"
disable_11be = "N"
enable_ini = "16"
fw_restart = "Y"
led_mode = "0"
nvm_file = "(null)"
power_level = "0"
power_save = "N"
remove_when_gone = "N"
swcrypto = "0"
uapsd_disable = "3"
Sections:
Module = "iwlmvm"
Attributes:
coresize = "720896"
initsize = "0"
initstate = "live"
refcnt = "0"
srcversion = "2290C3DDD2266D63C589D16"
taint = ""
uevent = <store method only>
Parameters:
init_dbg = "N"
power_scheme = "2"
Sections:
Power save: onNever actually knew that WiFi has power saving lol
Offline
Try :lol:
seth wrote:Did that boot actually cover the colported incident?
Offline
So sorry, actually had no idea what that word meant. I made a new journal where the incident actually happened.
http://0x0.st/XZcc.txt
I caught the incident at 19:12, but since I was playing youtube and had an app fullscreen on my main monitor, it cloud have happened earlier in the logs where the wifi was already tweaking
Offline
May 23 18:48:44 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:54:05 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:55:10 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:57:18 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 19:09:55 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42NM tries to switch to the 5GHz AP but constantly fails.
May 23 18:48:44 aleks wpa_supplicant[605]: wlan0: SME: Trying to authenticate with 38:43:7d:ba:49:42 (SSID='KabelBox-0D54' freq=5700 MHz)
May 23 18:48:44 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:48:44 aleks kernel: wlan0: authenticate with 38:43:7d:ba:49:42 (local address=f8:59:71:f1:c7:d7)
May 23 18:48:44 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 1/3)
May 23 18:48:44 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 2/3)
May 23 18:48:44 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 3/3)
May 23 18:48:44 aleks kernel: wlan0: authentication with 38:43:7d:ba:49:42 timed out
May 23 18:48:44 aleks wpa_supplicant[605]: BSSID 38:43:7d:ba:49:42 ignore list count incremented to 2, ignoring for 10 seconds
May 23 18:54:05 aleks wpa_supplicant[605]: wlan0: SME: Trying to authenticate with 38:43:7d:ba:49:42 (SSID='KabelBox-0D54' freq=5700 MHz)
May 23 18:54:05 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:54:05 aleks kernel: wlan0: authenticate with 38:43:7d:ba:49:42 (local address=f8:59:71:f1:c7:d7)
May 23 18:54:05 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 1/3)
May 23 18:54:05 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 2/3)
May 23 18:54:05 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 3/3)
May 23 18:54:05 aleks kernel: wlan0: authentication with 38:43:7d:ba:49:42 timed out
May 23 18:54:05 aleks wpa_supplicant[605]: BSSID 38:43:7d:ba:49:42 ignore list count incremented to 3, ignoring for 60 seconds
May 23 18:55:10 aleks wpa_supplicant[605]: wlan0: SME: Trying to authenticate with 38:43:7d:ba:49:42 (SSID='KabelBox-0D54' freq=5700 MHz)
May 23 18:55:10 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:55:10 aleks kernel: wlan0: authenticate with 38:43:7d:ba:49:42 (local address=f8:59:71:f1:c7:d7)
May 23 18:55:10 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 1/3)
May 23 18:55:10 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 2/3)
May 23 18:55:10 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 3/3)
May 23 18:55:10 aleks kernel: wlan0: authentication with 38:43:7d:ba:49:42 timed out
May 23 18:55:10 aleks wpa_supplicant[605]: BSSID 38:43:7d:ba:49:42 ignore list count incremented to 4, ignoring for 120 seconds
May 23 18:57:18 aleks wpa_supplicant[605]: wlan0: SME: Trying to authenticate with 38:43:7d:ba:49:42 (SSID='KabelBox-0D54' freq=5700 MHz)
May 23 18:57:18 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 18:57:18 aleks kernel: wlan0: authenticate with 38:43:7d:ba:49:42 (local address=f8:59:71:f1:c7:d7)
May 23 18:57:18 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 1/3)
May 23 18:57:18 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 2/3)
May 23 18:57:18 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 3/3)
May 23 18:57:18 aleks kernel: wlan0: authentication with 38:43:7d:ba:49:42 timed out
May 23 18:57:19 aleks wpa_supplicant[605]: BSSID 38:43:7d:ba:49:42 ignore list count incremented to 5, ignoring for 600 seconds
May 23 19:09:55 aleks wpa_supplicant[605]: wlan0: SME: Trying to authenticate with 38:43:7d:ba:49:42 (SSID='KabelBox-0D54' freq=5700 MHz)
May 23 19:09:55 aleks kernel: wlan0: disconnect from AP 38:43:7d:ba:49:53 for new auth to 38:43:7d:ba:49:42
May 23 19:09:55 aleks kernel: wlan0: authenticate with 38:43:7d:ba:49:42 (local address=f8:59:71:f1:c7:d7)
May 23 19:09:55 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 1/3)
May 23 19:09:55 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 2/3)
May 23 19:09:55 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 3/3)
May 23 19:09:56 aleks kernel: wlan0: authentication with 38:43:7d:ba:49:42 timed out
May 23 19:09:56 aleks wpa_supplicant[605]: BSSID 38:43:7d:ba:49:42 ignore list count incremented to 6, ignoring for 1800 seconds
May 23 19:13:56 aleks wpa_supplicant[605]: wlan0: SME: Trying to authenticate with 38:43:7d:ba:49:42 (SSID='KabelBox-0D54' freq=5700 MHz)
May 23 19:13:56 aleks kernel: wlan0: authenticate with 38:43:7d:ba:49:42 (local address=f8:59:71:f1:c7:d7)
May 23 19:13:56 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 1/3)
May 23 19:13:56 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 2/3)
May 23 19:13:56 aleks kernel: wlan0: send auth to 38:43:7d:ba:49:42 (try 3/3)
May 23 19:13:56 aleks kernel: wlan0: authentication with 38:43:7d:ba:49:42 timed out
May 23 19:13:56 aleks wpa_supplicant[605]: BSSID 38:43:7d:ba:49:42 ignore list count incremented to 2, ignoring for 10 seconds38:43:7d:ba:49:53 is your 2.4GHz AP and that works.
=> Connect to the BSSID, not the SSID: https://wiki.archlinux.org/title/Networ … ets_(WiFi)
This btw. also means that you're not limted to 802.11g - can you get close to the AP?
SIdebar:
that never caused this problem on windows, I'm not dual booting with windows
Wa that on the same hardware from the same location?
Offline
I had windows on the same hardware and location, and I can't really get closer to the router, also I'll be gone for like a week now so I can't type in any terminal commands for now
Offline
Pages: 1