sometimes there are “silly” bugs. a lot of laptops do have a physical switch or a hotkey for “airplane” mode that will disable the wifi. if so is it on or off ?
There is a key for it but it’s not in flightmode.
➜ ~ rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
1 wlan phy0 unblocked unblocked
@Olli is there a way to check the last updates done on the system/drivers etc. to see if in the last days something that has to do with WiFi got changed and revert that change?
yes you could try to check the journalctl but it is a hassle without knowing what to search for.
do you know how to install a different kernel ? it would be a fast check for testing if you install a previous lts kernel like 5.15-108.1 and boot into this.
do you know how to install a different kernel ?
Not really. Never did it before. But if it is just a few commands and quick, I could give it a try.
okay, i’m on plasma not on gnome so i’m not that big help in this case (but it should be similar to plasma). a question before, if you run the command below is your router detected in this list of output or does it show up any routers ?
nmcli device wifi list
Other things to try:
On the router, change channels(s) that wifi is using.
If you have MAC address filtering on the router, turn it off.
Reboot modem and router.
Does the card work with a live CD?
1 Like
that’s what i’m already thinking. checking if the nmcli command post any output and make sure it’s not a connection problem with the router itself. it’s a good try to shut down the computer and router. then start the router (sometimes they do a update of the router that takes some time) and if the router is working start the computer. just to make sure that it is not a “side-effect” with some router-issues.
next is also a very good test is the tip of @jrichard326 to start a live-cd and test if wifi is working with a live session. if it’s running with a live cd you can be sure that it is a problem with your system.
a question before, if you run the command below is your router detected in this list of output or does it show up any routers ?
Yes, I can see mine (with 70% signal strength) and also from the neighbors with more than 25% signal strength.
The router is fine but I have restarted it and my laptop multiple times since yesterday. It didn’t help. The router’s wifi is working perfectly on other devices like tv, macbook, phone, tablets etc. Just not on my work laptop (manjaro).
yes but it’s tested not to be the problem.
please post the output of
journalctl -u NetworkManager.service
next
From the inxi output …
Are you running a VPN or tunnel or proxy? Sometimes they can mess with things like dead-man kill switch
1 Like
not sure why the date shows March, 10th while system’s date is: ➜ ~ date Sa 6. Mai 13:24:47 CEST 2023
Mär 10 16:53:14 NetworkManager[1040]: <info> [1678463594.7137] manager: sleep: sleep requested (sleeping: no enabled: yes)
Mär 10 16:53:14 NetworkManager[1040]: <info> [1678463594.7138] device (wwan0mbim0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mär 10 16:53:14 NetworkManager[1040]: <info> [1678463594.7141] manager: NetworkManager state is now ASLEEP
Mär 10 16:53:14 NetworkManager[1040]: <info> [1678463594.7146] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0418] device (wlp2s0): supplicant interface state: completed -> disconnected
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0421] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0816] dhcp4 (wlp2s0): canceled DHCP transaction
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0816] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0817] dhcp4 (wlp2s0): state changed no lease
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0820] dhcp6 (wlp2s0): canceled DHCP transaction
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0820] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.0820] dhcp6 (wlp2s0): state changed no lease
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.1562] device (wlp2s0): set-hw-addr: set MAC address to E2:C5:85:2B:E2:E7 (scanning)
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.2712] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Mär 10 16:53:15 NetworkManager[1040]: <warn> [1678463595.2713] dns-sd-resolved[3a763f4e07163b90]: send-updates SetLinkDomains@4 failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The nam>
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.2718] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.2727] device (wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mär 10 16:53:15 NetworkManager[1040]: <info> [1678463595.3797] device (wlp2s0): set-hw-addr: reset MAC address to 30:03:C8:32:DD:4B (unmanage)
Mär 13 08:58:44 NetworkManager[1040]: <info> [1678694324.2220] manager: sleep: wake requested (sleeping: yes enabled: yes)
Mär 13 08:58:44 NetworkManager[1040]: <info> [1678694324.2222] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mär 13 08:58:44 NetworkManager[1040]: <info> [1678694324.3060] device (wlp2s0): set-hw-addr: set MAC address to 92:15:BE:AC:CB:C0 (scanning)
Mär 13 08:58:44 NetworkManager[1040]: <info> [1678694324.3549] manager: NetworkManager state is now CONNECTED_LOCAL
Mär 13 08:58:44 NetworkManager[1040]: <info> [1678694324.4005] device (wlp2s0): supplicant interface state: internal-starting -> disconnected
Mär 13 08:58:44 NetworkManager[1040]: <info> [1678694324.4006] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.7007] policy: auto-activating connection 'FRITZ!Box 7362 SL' (c8a7cb96-8210-43c3-a560-fd4a8cf61328)
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.7011] device (wlp2s0): Activation: starting connection 'FRITZ!Box 7362 SL' (c8a7cb96-8210-43c3-a560-fd4a8cf61328)
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.7011] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.7014] manager: NetworkManager state is now CONNECTING
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.7827] device (wlp2s0): set-hw-addr: reset MAC address to 30:03:C8:32:DD:4B (preserve)
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8333] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8337] device (wlp2s0): Activation: (wifi) access point 'FRITZ!Box 7362 SL' has security, but secrets are required.
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8337] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8339] sup-iface[25c0e4930ac07c77,17,wlp2s0]: wps: type pbc start...
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8342] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8353] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8356] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8359] device (wlp2s0): Activation: (wifi) connection 'FRITZ!Box 7362 SL' has security, and secrets exist. No new secrets needed.
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8360] Config: added 'ssid' value 'FRITZ!Box 7362 SL'
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8360] Config: added 'scan_ssid' value '1'
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8360] Config: added 'bgscan' value 'simple:30:-70:86400'
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8360] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8361] Config: added 'auth_alg' value 'OPEN'
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8361] Config: added 'psk' value '<hidden>'
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.8655] device (wlp2s0): supplicant interface state: interface_disabled -> inactive
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.9192] device (wlp2s0): supplicant interface state: inactive -> authenticating
Mär 13 08:58:50 NetworkManager[1040]: <info> [1678694330.9356] device (wlp2s0): supplicant interface state: authenticating -> associating
please post the status
systemctl status NetworkManager.service
and some possible weird thing of gnome itself. please also post the output of
sudo -u gdm dbus-launch gsettings list-recursively org.gnome.settings-daemon.plugins.power
@mishmosh yes, I think this wlp2s0 thing is it.
[18207.604403] wlp2s0: 80 MHz not supported, disabling VHT
[18207.670678] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 1/3)
[18208.430526] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 2/3)
[18209.444210] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 3/3)
[18210.423833] wlp2s0: authentication with 0c:8e:29:49:35:56 timed out
[18222.001296] ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting
[18222.001314] ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting
[18222.236823] wlp2s0: authenticate with 0c:8e:29:49:35:52
[18222.309331] wlp2s0: send auth to 0c:8e:29:49:35:52 (try 1/3)
[18223.391027] wlp2s0: send auth to 0c:8e:29:49:35:52 (try 2/3)
[18224.484376] wlp2s0: send auth to 0c:8e:29:49:35:52 (try 3/3)
[18225.497777] wlp2s0: authentication with 0c:8e:29:49:35:52 timed out
[18235.625387] wlp2s0: authenticate with 0c:8e:29:49:35:56
[18235.625416] wlp2s0: 80 MHz not supported, disabling VHT
[18235.692495] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 1/3)
[18236.377749] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 2/3)
[18237.417873] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 3/3)
[18238.457800] wlp2s0: authentication with 0c:8e:29:49:35:56 timed out
[18250.058732] ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting
[18250.059105] ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting
[18250.326211] wlp2s0: authenticate with 0c:8e:29:49:35:52
[18250.399112] wlp2s0: send auth to 0c:8e:29:49:35:52 (try 1/3)
[18251.378086] wlp2s0: send auth to 0c:8e:29:49:35:52 (try 2/3)
[18252.480022] wlp2s0: send auth to 0c:8e:29:49:35:52 (try 3/3)
[18253.524458] wlp2s0: authentication with 0c:8e:29:49:35:52 timed out
[18253.862652] kauditd_printk_skb: 89 callbacks suppressed
[18253.862654] audit: type=1101 audit(1683372880.345:663): pid=19282 uid=1000 auid=1000 ses=12 subj=unconfined msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="singhd" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[18253.863298] audit: type=1110 audit(1683372880.345:664): pid=19282 uid=1000 auid=1000 ses=12 subj=unconfined msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[18253.863385] audit: type=1105 audit(1683372880.345:665): pid=19282 uid=1000 auid=1000 ses=12 subj=unconfined msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[18263.662321] wlp2s0: authenticate with 0c:8e:29:49:35:56
[18263.662351] wlp2s0: 80 MHz not supported, disabling VHT
[18263.725788] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 1/3)
[18264.378211] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 2/3)
[18265.515989] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 3/3)
[18266.508073] wlp2s0: authentication with 0c:8e:29:49:35:56 timed out
[18278.115095] ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting
[18278.115429] ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting
[18278.405561] wlp2s0: authenticate with 0c:8e:29:49:35:56
[18278.405585] wlp2s0: 80 MHz not supported, disabling VHT
[18278.457246] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 1/3)
[18279.391682] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 2/3)
[18280.476910] wlp2s0: send auth to 0c:8e:29:49:35:56 (try 3/3)
[18281.471865] wlp2s0: authentication with 0c:8e:29:49:35:56 timed out
Somehow, I feel like my problem has to do with this error:
Failed to set the requested Country regulatory setting
No one has addressed it so far.
we already checked that with
iw reg get
and it was set to global. do you need a specific country related ? where are you from and are there some regulations in your country that we need to know ?
➜ ~ systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
Active: active (running) since Sat 2023-05-06 08:30:37 CEST; 5h 7min ago
Docs: man:NetworkManager(8)
Main PID: 1169 (NetworkManager)
Tasks: 4 (limit: 27978)
Memory: 20.9M
CPU: 45.494s
CGroup: /system.slice/NetworkManager.service
└─1169 /usr/bin/NetworkManager --no-daemon
Mai 06 13:37:36 NetworkManager[1169]: <info> [1683373056.0196] device (wlp2s0): supplicant interface state: disconnected -> scanning
Mai 06 13:37:36 NetworkManager[1169]: <info> [1683373056.1736] device (wlp2s0): supplicant interface state: scanning -> authenticating
Mai 06 13:37:38 NetworkManager[1169]: <info> [1683373058.9002] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Mai 06 13:37:48 NetworkManager[1169]: <warn> [1683373068.5417] device (wlp2s0): Activation: (wifi) association took too long, failing activation
Mai 06 13:37:48 NetworkManager[1169]: <info> [1683373068.5417] device (wlp2s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Mai 06 13:37:48 NetworkManager[1169]: <info> [1683373068.6187] device (wlp2s0): set-hw-addr: set MAC address to D6:15:9F:46:F1:3B (scanning)
Mai 06 13:37:48 NetworkManager[1169]: <warn> [1683373068.7007] device (wlp2s0): Activation: failed for connection 'WLAN-445BDD'
Mai 06 13:37:48 NetworkManager[1169]: <info> [1683373068.7008] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Mai 06 13:37:48 NetworkManager[1169]: <info> [1683373068.7010] device (wlp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mai 06 13:37:48 NetworkManager[1169]: <info> [1683373068.7493] device (wlp2s0): supplicant interface state: interface_disabled -> inactive
org.gnome.settings-daemon.plugins.power ambient-enabled true
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim true
org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery true
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 1200
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
we already checked that with
Ah, sorry, I see.
I am in Germany. I don’t know really myself if that’s the case.
I did not do any changes to the WiFi/Network settings and it was working fine. Maybe this error used to come before too but I wouldn’t know. So probably unrelated, you think?
from here it seems that your authentication of the existing wifi-profile is failing. do you use a vpn as already asked ? try to create a new profile for testing and connect to your router with it.
Yes, as mentioned above, I suspect this wlp2s0 has something to do with vpn.
If I remember correctly one of the IT guys told me that we use tailscale as a service for vpn, that runs in the background.
Hmm if those are today’s logs, a possible scenario: the system clock thought it was March (based on a last-saved date-time) until the NTP service (systemd-timesyncd.service) was able to connect.
More likely those are old logs