Connection problems with one router

pihentagy · 21 December 2025 22:40

At my workplace wifi works ok. But at home, it simply cannot connect to my ISP provided router. Other devices can connect and use that. Using plasma, if that matters

mhwd-kernel -li
Currently running: 6.12.62-1-MANJARO (linux612)
The following kernels are installed in your system:
   * linux612

mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI


Warning: No installed USB configs!
inxi -Nxxx
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 7000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 14c3:0616 class-ID: 0280

Journalctl output when trying to connect to One-962B' and then switching back to pihentagy:

dec 21 23:30:19 powerplant NetworkManager[728]: <info>  [1766356219.9128] audit: op="statistics" interface="wlp2s0" ifindex=3 args="2000" pid=1166 uid=1000 result="success"
dec 21 23:30:19 powerplant kded6[1111]: Failed to notify "Created too many similar notifications in quick succession"
dec 21 23:30:27 powerplant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
dec 21 23:30:28 powerplant wpa_supplicant[848]: wlp2s0: Reject scan trigger since one is already pending
dec 21 23:30:28 powerplant NetworkManager[728]: <info>  [1766356228.4402] manager: NetworkManager state is now CONNECTED_GLOBAL
dec 21 23:30:28 powerplant systemd[1]: Starting Network Manager Script Dispatcher Service...
dec 21 23:30:28 powerplant systemd[1]: Started Network Manager Script Dispatcher Service.
dec 21 23:30:35 powerplant geoclue[1011]: Failed to query location: Query location SOUP error: Unknown Error
dec 21 23:30:38 powerplant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
dec 21 23:30:42 powerplant geoclue[1011]: Failed to query location: Query location SOUP error: Unknown Error
dec 21 23:33:04 powerplant baloo_file_extractor[39656]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
dec 21 23:33:05 powerplant rtkit-daemon[1007]: Supervising 12 threads of 8 processes of 1 users.
dec 21 23:33:05 powerplant rtkit-daemon[1007]: Supervising 12 threads of 8 processes of 1 users.
dec 21 23:33:06 powerplant NetworkManager[728]: <info>  [1766356386.6500] audit: op="statistics" interface="wlp2s0" ifindex=3 args="2000" pid=1166 uid=1000 result="success"
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.0430] device (wlp2s0): disconnecting for new activation request.
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.0430] device (wlp2s0): state change: activated -> deactivating (reason 'new-activation', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.0435] audit: op="connection-activate" uuid="d4801cc6-4aac-4c36-99db-d9b4127c72e0" name="One-962B" pid=1166 uid=1000 result="success"
dec 21 23:33:09 powerplant systemd[1]: Starting Network Manager Script Dispatcher Service...
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.0578] audit: op="statistics" interface="wlp2s0" ifindex=3 args="0" pid=1166 uid=1000 result="success"
dec 21 23:33:09 powerplant systemd[1]: Started Network Manager Script Dispatcher Service.
dec 21 23:33:09 powerplant kernel: wlp2s0: deauthenticating from 94:0c:6d:a9:fc:de by local choice (Reason: 3=DEAUTH_LEAVING)
dec 21 23:33:09 powerplant wpa_supplicant[848]: nl80211: send_event_marker failed: Source based routing not supported
dec 21 23:33:09 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=94:0c:6d:a9:fc:de reason=3 locally_generated=1
dec 21 23:33:09 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
dec 21 23:33:09 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.5114] device (wlp2s0): supplicant interface state: completed -> disconnected
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.5114] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.5115] device (wlp2s0): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.5117] dhcp4 (wlp2s0): canceled DHCP transaction
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.5117] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.5117] dhcp4 (wlp2s0): state changed no lease
dec 21 23:33:09 powerplant geoclue[1011]: Failed to query location: Could not connect to www.googleapis.com: Network is unreachable
dec 21 23:33:09 powerplant geoclue[1011]: Failed to query location: Could not connect to www.googleapis.com: Network is unreachable
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.6686] device (wlp2s0): set-hw-addr: set MAC address to 52:24:46:A9:F0:0B (scanning)
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.7396] device (wlp2s0): Activation: starting connection 'One-962B' (d4801cc6-4aac-4c36-99db-d9b4127c72e0)
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.7403] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.7403] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> interface_disabled
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.7406] device (wlp2s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.7407] manager: NetworkManager state is now CONNECTING
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8083] device (wlp2s0): set-hw-addr: reset MAC address to F4:4E:B4:8D:32:FB (preserve)
dec 21 23:33:09 powerplant geoclue[1011]: WiFi scan failed
dec 21 23:33:09 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-100
dec 21 23:33:09 powerplant kded6[1111]: Failed to notify "Created too many similar notifications in quick succession"
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8715] device (wlp2s0): state change: prepare -> config (reason 'none', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8717] device (wlp2s0): Activation: (wifi) access point 'One-962B' has security, but secrets are required.
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8717] device (wlp2s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8718] sup-iface[32d342aade0a6b3f,2,wlp2s0]: wps: type pbc start...
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8789] device (wlp2s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8790] device (wlp2s0): state change: prepare -> config (reason 'none', managed-type: 'full')
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8791] device (wlp2s0): Activation: (wifi) connection 'One-962B' has security, and secrets exist.  No new secrets needed.
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8791] Config: added 'ssid' value 'One-962B'
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8791] Config: added 'scan_ssid' value '1'
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8791] Config: added 'bgscan' value 'simple:30:-70:86400'
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8791] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.8791] Config: added 'psk' value '<hidden>'
dec 21 23:33:09 powerplant wpa_supplicant[848]: wlp2s0: WPS-CANCEL
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.9161] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.9161] device (p2p-dev-wlp2s0): supplicant management interface state: interface_disabled -> disconnected
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.9237] device (wlp2s0): supplicant interface state: disconnected -> scanning
dec 21 23:33:09 powerplant NetworkManager[728]: <info>  [1766356389.9237] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
dec 21 23:33:10 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
dec 21 23:33:10 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5200 max_tx_power=2000 no_ir=1
dec 21 23:33:10 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5200 max_tx_power=2000
dec 21 23:33:11 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
dec 21 23:33:11 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5240 max_tx_power=2000 no_ir=1
dec 21 23:33:11 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5240 max_tx_power=2000
dec 21 23:33:19 powerplant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
dec 21 23:33:30 powerplant wpa_supplicant[848]: wlp2s0: SME: Trying to authenticate with 90:5c:44:f6:e1:2b (SSID='One-962B' freq=2462 MHz)
dec 21 23:33:30 powerplant kernel: wlp2s0: authenticate with 90:5c:44:f6:e1:2b (local address=f4:4e:b4:8d:32:fb)
dec 21 23:33:30 powerplant NetworkManager[728]: <info>  [1766356410.6021] device (wlp2s0): supplicant interface state: scanning -> authenticating
dec 21 23:33:30 powerplant NetworkManager[728]: <info>  [1766356410.6021] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
dec 21 23:33:30 powerplant kernel: wlp2s0: send auth to 90:5c:44:f6:e1:2b (try 1/3)
dec 21 23:33:30 powerplant kernel: wlp2s0: send auth to 90:5c:44:f6:e1:2b (try 2/3)
dec 21 23:33:30 powerplant kernel: wlp2s0: send auth to 90:5c:44:f6:e1:2b (try 3/3)
dec 21 23:33:30 powerplant kernel: wlp2s0: authentication with 90:5c:44:f6:e1:2b timed out
dec 21 23:33:30 powerplant wpa_supplicant[848]: wlp2s0: Added BSSID 90:5c:44:f6:e1:2b into ignore list, ignoring for 10 seconds
dec 21 23:33:30 powerplant NetworkManager[728]: <info>  [1766356410.9968] device (wlp2s0): supplicant interface state: authenticating -> disconnected
dec 21 23:33:30 powerplant NetworkManager[728]: <info>  [1766356410.9968] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
dec 21 23:33:31 powerplant NetworkManager[728]: <info>  [1766356411.0970] device (wlp2s0): supplicant interface state: disconnected -> scanning
dec 21 23:33:31 powerplant NetworkManager[728]: <info>  [1766356411.0970] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.0373] device (wlp2s0): disconnecting for new activation request.
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.0374] device (wlp2s0): state change: config -> deactivating (reason 'new-activation', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.0374] manager: NetworkManager state is now CONNECTED_LOCAL
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.0377] audit: op="connection-activate" uuid="105928a3-683f-4996-8813-3f55ffd6d711" name="pihentagy" pid=1166 uid=1000 result="success"
dec 21 23:33:34 powerplant systemd[1]: Starting Network Manager Script Dispatcher Service...
dec 21 23:33:34 powerplant systemd[1]: Started Network Manager Script Dispatcher Service.
dec 21 23:33:34 powerplant NetworkManager[728]: <warn>  [1766356414.0882] device (wlp2s0): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.0882] device (wlp2s0): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.2027] device (wlp2s0): set-hw-addr: set MAC address to C6:26:06:39:A8:E8 (scanning)
dec 21 23:33:34 powerplant wpa_supplicant[848]: wlp2s0: Removed BSSID 90:5c:44:f6:e1:2b from ignore list (clear)
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.2725] device (wlp2s0): Activation: starting connection 'pihentagy' (105928a3-683f-4996-8813-3f55ffd6d711)
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.2730] device (wlp2s0): supplicant interface state: scanning -> inactive
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.2730] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> inactive
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.2731] device (wlp2s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.2731] manager: NetworkManager state is now CONNECTING
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.3350] device (wlp2s0): set-hw-addr: reset MAC address to F4:4E:B4:8D:32:FB (preserve)
dec 21 23:33:34 powerplant kded6[1111]: Failed to notify "Created too many similar notifications in quick succession"
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.3982] device (wlp2s0): state change: prepare -> config (reason 'none', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.3984] device (wlp2s0): Activation: (wifi) access point 'pihentagy' has security, but secrets are required.
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.3984] device (wlp2s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.3988] device (wlp2s0): supplicant interface state: inactive -> interface_disabled
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.3988] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> interface_disabled
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4064] device (wlp2s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4065] device (wlp2s0): state change: prepare -> config (reason 'none', managed-type: 'full')
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4067] device (wlp2s0): Activation: (wifi) connection 'pihentagy' has security, and secrets exist.  No new secrets needed.
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4067] Config: added 'ssid' value 'pihentagy'
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4067] Config: added 'scan_ssid' value '1'
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4067] Config: added 'bgscan' value 'simple:30:-70:86400'
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4067] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4068] Config: added 'psk' value '<hidden>'
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4397] device (wlp2s0): supplicant interface state: interface_disabled -> inactive
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.4397] device (p2p-dev-wlp2s0): supplicant management interface state: interface_disabled -> inactive
dec 21 23:33:34 powerplant wpa_supplicant[848]: wlp2s0: SME: Trying to authenticate with 94:0c:6d:a9:fc:de (SSID='pihentagy' freq=2452 MHz)
dec 21 23:33:34 powerplant kernel: wlp2s0: authenticate with 94:0c:6d:a9:fc:de (local address=f4:4e:b4:8d:32:fb)
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.6956] device (wlp2s0): supplicant interface state: inactive -> authenticating
dec 21 23:33:34 powerplant kernel: wlp2s0: send auth to 94:0c:6d:a9:fc:de (try 1/3)
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.6956] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> authenticating
dec 21 23:33:34 powerplant wpa_supplicant[848]: wlp2s0: Trying to associate with 94:0c:6d:a9:fc:de (SSID='pihentagy' freq=2452 MHz)
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.7014] device (wlp2s0): supplicant interface state: authenticating -> associating
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.7015] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
dec 21 23:33:34 powerplant kernel: wlp2s0: authenticated
dec 21 23:33:34 powerplant kernel: wlp2s0: associate with 94:0c:6d:a9:fc:de (try 1/3)
dec 21 23:33:34 powerplant kernel: wlp2s0: RX AssocResp from 94:0c:6d:a9:fc:de (capab=0x431 status=0 aid=24)
dec 21 23:33:34 powerplant wpa_supplicant[848]: wlp2s0: Associated with 94:0c:6d:a9:fc:de
dec 21 23:33:34 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
dec 21 23:33:34 powerplant kernel: wlp2s0: associated
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.7431] device (wlp2s0): supplicant interface state: associating -> associated
dec 21 23:33:34 powerplant NetworkManager[728]: <info>  [1766356414.7432] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.5417] device (wlp2s0): supplicant interface state: associated -> 4way_handshake
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.5417] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4way_handshake
dec 21 23:33:35 powerplant wpa_supplicant[848]: wlp2s0: WPA: Key negotiation completed with 94:0c:6d:a9:fc:de [PTK=CCMP GTK=TKIP]
dec 21 23:33:35 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 94:0c:6d:a9:fc:de completed [id=0 id_str=]
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.6112] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.6112] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "pihentagy"
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.6112] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.6117] device (wlp2s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.6120] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.6202] dhcp4 (wlp2s0): state changed new lease, address=192.168.1.111, acd pending
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.7823] dhcp4 (wlp2s0): state changed new lease, address=192.168.1.111
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.7878] policy: set 'pihentagy' (wlp2s0) as default for IPv4 routing and DNS
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.7988] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.7996] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.7997] device (wlp2s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.7998] manager: NetworkManager state is now CONNECTED_SITE
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.8000] device (wlp2s0): Activation: successful, device activated.
dec 21 23:33:35 powerplant NetworkManager[728]: <info>  [1766356415.8182] audit: op="statistics" interface="wlp2s0" ifindex=3 args="2000" pid=1166 uid=1000 result="success"
dec 21 23:33:35 powerplant kded6[1111]: Failed to notify "Created too many similar notifications in quick succession"
dec 21 23:33:36 powerplant wpa_supplicant[848]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-71 noise=9999 txrate=36000
dec 21 23:33:37 powerplant NetworkManager[728]: <info>  [1766356417.5365] manager: NetworkManager state is now CONNECTED_GLOBAL
dec 21 23:33:38 powerplant geoclue[1011]: Failed to query location: Query location SOUP error: Unknown Error

Do you have any advice? Or can I provide more data to help me figure out what’s wrong?

thanks

Mod edit:- Corrected pre-formatted text presentation. No charge.
Please take care when copying/pasting text.

Nachlese · 21 December 2025 23:04

I’m in a similar situation - but I have a different WiFi card.
A very old (as old as the laptop itself) Intel Centrino Wireless-N 2230

The router/modem my provider gave me works just fine with every other device
and my laptop WiFi works just fine with every other device.
Just not with the Router/Cable Modem my provider gave me.
No amount of fiddling with the options in the router made it work.

My solution was and still is:
use a second router, connected by cable to the first one.
The upside is:
I can place it at a more ideal spot, more in the center instead of in the far corner of my place - better reception …

soundofthunder · 22 December 2025 00:54

Some housekeeping.

Please avoid pasting garbage characters along with command output – I refer to anything similar to    ~  – all it takes is a little more care when selecting the text to copy.

Thanks.

What follows is from a standard template.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading

Highly Recommended

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):


`inxi -zv8`	(short-form)
`inxi --filter --verbosity=8`	(long-form)
`inxi` man pages	(manual)

Running `inxi` within a `chroot` environment

Add --color=0 to the long-form command, or…
Change the short-form command to inxi -zv8c0

Your privacy is respected

Update Announcements

Technical Resources

linux-aarhus · 22 December 2025 07:39

I am thinking - check in the router setup.

The following is a guess…

I only know the following because I had the issue that I couldn’t use WPA3 because then my printer wouldn’t connect.

If the router is set to use WPA3 it will enforce PMF (Protected Management Frames) and this may disconnect devices which do not support this type of connection.

So I had to create two wifi networks - I don’t use extra router or access points, just separate network broadcasts - one for IoT using WPA2 for our printer - and another using WPA3 for phones, tablets and computers.

Arrababiski · 22 December 2025 19:14

I see various “set MAC address” and “reset MAC address” in journalctl output. Some routers don’t like MAC address changes at all; you can try disabling it to see if that’s the cause.

sudo nano /etc/NetworkManager/conf.d/disable-random-mac.conf

Copy these two lines inside:

[device]
wifi.scan-rand-mac-address=no

And can you explain more clearly what this means? Can you see the SSIDs? Can you type the password? Did you connect and disconnect or no connection at all? Are you using any MAC filtering?

Molski · 23 December 2025 00:48

Both suggestions above are possible. No way to tell with the info.

dec 21 23:30:27 powerplant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
dec 21 23:30:28 powerplant wpa_supplicant[848]: wlp2s0: Reject scan trigger since one is already pending
dec 21 23:30:28 powerplant NetworkManager[728]: <info>  [1766356228.4402] manager: NetworkManager state is now CONNECTED_GLOBAL
dec 21 23:30:28 powerplant systemd[1]: Starting Network Manager Script Dispatcher Service...
dec 21 23:30:28 powerplant systemd[1]: Started Network Manager Script Dispatcher Service.
dec 21 23:30:38 powerplant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

It’s just restarting over and over, and there’s nothing useful here. So we can only guess.

journalctl -u NetworkManager -b

What would be more useful (on boot up until first connect).

But possibly even more useful, how far along is the device working..

What is the output of the following (the latter ones may not work if the first fail)
nmcli device status
nmcli device show wlp2s0
nmcli device wifi list ifname wlp2s0

pihentagy · 26 December 2025 21:00

I can see all SSIDs, but the Guest network and the 5G networks (Connection Error and High speed blackhole) does not connect at all. They keep asking the password even after disabling random mac as you advised and after a reboot. No MAC filtering at all, all settings on default, except setting up Guest and 5G connection points.

Arrababiski · 27 December 2025 18:04

pihentagy:

Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 7000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 14c3:0616 class-ID: 0280

I’ve just realized you’re using a MT7922 card with mt7921e driver, when there is a driver for mt7922e…

Is your computer a Lenovo Ideapad Pro? If so, read this (section 2):

github.com/morrownr/USB-WiFi

home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md

main

## How to install or update firmware for Mediatek-based USB WiFi adapters
(also Realtek rtw88 and rtw89 firmware)

Maintained by @morrownr

Updated: 2025-05-18

Purpose: Provide the steps to install or upgrade firmware for Mediatek
or rtw88 based USB WiFi adapters. Some Linux distros do not include the
firmware that is necessary to support USB WiFi adapters. Debian prior to
Debian 12 is a good example. Other distros make mistakes and leave the
firmware out of their distro and sometimes you may need to update the
firmware to a newer version. Then there are the numerous server distros
where wifi support, to include the firmware, may not be included because
the maintainers think wifi is not used in server applications.

Information: In-kernel drivers in Linux come in 2 or more parts. There
is what is normally called the driver, which is part of the kernel, and
there is the firmware (binary blob), which may be 1 or more files, and
is not part of the kernel. Firmware files are part of the distro and

This file has been truncated. show original

pihentagy · 3 January 2026 14:02

Maybe that’s the source of the problem. Just noting that I haven’t chosen mt7921e driver, just installed Manjaro “blindly”.

It is a Lenovo Thinkpad E16 with AMD Ryzen.

Followed section 2, but before I overwrote files in /lib/firmware/mediatek, I checked if they are differ at all, and found, they don’t!

> for i in *.bin.xz; do md5sum $i; md5sum /lib/firmware/mediatek/$i; done
8676c4a5a0d526eb719d3ddcd752bc2d  BT_RAM_CODE_MT7922_1_1_hdr.bin.xz
8676c4a5a0d526eb719d3ddcd752bc2d  /lib/firmware/mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin.xz
bc5ee35211b5a14cbab8fea4d653aa7e  WIFI_MT7922_patch_mcu_1_1_hdr.bin.xz
bc5ee35211b5a14cbab8fea4d653aa7e  /lib/firmware/mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin.xz
c5d6e02079cd371995564f7500fed775  WIFI_RAM_CODE_MT7922_1.bin.xz
c5d6e02079cd371995564f7500fed775  /lib/firmware/mediatek/WIFI_RAM_CODE_MT7922_1.bin.xz

So How to ask the kernel to use the correct driver?

Arrababiski · 3 January 2026 20:11

Drivers are called modules, you can see here how to handle it:

You can see the modules loaded with lsmod, or detailed info from one with modinfo mt7921e.

May be you can remove mt7921e driver with modprobe -r mt7921e and then load modprobe mt7922e (temporary). Or using conf files to blacklist mt7921e and load mt7922e permanently.

What is the exact model of the laptop (as appears on the label on the bottom)? Only to check the support page and see the exact network card model (MT7921e or MT7922e).

soundofthunder · 4 January 2026 02:09

Of possible interest:

github.com/morrownr/USB-WiFi

[Help]: MT7922e Wi-Fi6 speed not ideal

opened 08:34AM - 27 Apr 25 UTC

Williamclouf

### Checklist - [x] I acknowledge that support is provided on a best-effort bas…is. - [x] I acknowledge that the authors and contributors to this repository cannot be held responsible for the results of my use of any information contained in or linked from this repository. ### uname Linux 6.1.99 #32 SMP Mon Jan 20 15:50:32 CST 2025 aarch64 aarch64 aarch64 GNU/Linux ### lsusb ``` Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 13d3:3568 IMC Networks Wireless_Device ``` ### rfkill 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ### dkms ```text / ``` ### iw ```text phy#0 Interface wlan0 ifindex 4 wdev 0x1 addr 14:13:33:6e:ee:15 ssid mt7922 type AP channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz txpower 3.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 11304 0 0 0 60 4760957 17923 ``` ### What happened? I am using an MT7922 PCIe card, serving as an AP, everything is going well. But I heard that the mt79 driver has a 'txpower 3.00 dBm' issue. In the link https://github.com/openwrt/mt76/issues/935#issuecomment-2688143334, your comment indicates that iperf3 can achieve a speed of 1.24 Gbits/sec. I want to improve my bitrate, but I don't know if it's a txpower issue or a problem with my configuration or something else. Below is some output. iperf3 test, done through 1 wall with about 6 m/20 feet of distance. Even when I conduct an iperf3 download test about 1 feet away from the antenna, the maximum speed is only around 400 Mbps. ``` $ iperf3 -c 192.168.0.1 Connecting to host 192.168.0.1, port 5201 [ 5] local 192.168.0.177 port 54220 connected to 192.168.0.1 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 38.2 MBytes 319 Mbits/sec [ 5] 1.00-2.00 sec 38.4 MBytes 323 Mbits/sec [ 5] 2.00-3.00 sec 37.6 MBytes 315 Mbits/sec [ 5] 3.00-4.00 sec 37.8 MBytes 318 Mbits/sec [ 5] 4.00-5.00 sec 36.0 MBytes 302 Mbits/sec [ 5] 5.00-6.00 sec 38.2 MBytes 320 Mbits/sec [ 5] 6.00-7.00 sec 38.6 MBytes 323 Mbits/sec [ 5] 7.00-8.00 sec 36.1 MBytes 303 Mbits/sec [ 5] 8.00-9.00 sec 38.5 MBytes 324 Mbits/sec [ 5] 9.00-10.01 sec 36.8 MBytes 307 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 376 MBytes 315 Mbits/sec sender [ 5] 0.00-10.03 sec 374 MBytes 313 Mbits/sec receiver ``` Current Network Information on the macOS client, operates in 802.11ax mode. ``` mt7922: PHY Mode: 802.11ax Channel: 36 Network Type: Infrastructure Security: WPA2 Personal Signal / Noise: -65 dBm / -91 dBm Transmit Rate: 576 MCS Index: 4 ``` hostapd has been upgraded to the latest following `AP_Mode/Upgrade_hostapd.md` ``` $ hostapd -v hostapd v2.12-devel-hostap_2_11-838-g9fa657a73 User space daemon for IEEE 802.11 AP management, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator Copyright (c) 2002-2024, Jouni Malinen <j@w1.fi> and contributors ``` Here is my hostapd-wifi6.conf ```conf interface=wlan0 driver=nl80211 ssid=mt7922 wpa_passphrase=MyPassword hw_mode=a channel=36 country_code=US ieee80211d=1 logger_syslog=-1 logger_syslog_level=2 beacon_int=100 dtim_period=2 skip_inactivity_poll=1 auth_algs=1 max_num_sta=16 macaddr_acl=0 ignore_broadcast_ssid=0 okc=1 wpa=2 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256 wmm_enabled=1 ieee80211n=1 ht_capab=[LDPC][HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=1 vht_oper_centr_freq_seg0_idx=42 vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][SU-BEAMFORMEE][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][BF-ANTENNA-4][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] ieee80211ax=1 he_oper_chwidth=1 he_oper_centr_freq_seg0_idx=42 ```

Forum search 50+ results for MT7922.
It may be possible the OP has a proverbial

Arrababiski · 4 January 2026 17:19

Take a look at section 7.1.6:

pihentagy · 4 January 2026 21:05

QR code on bottom links to here

Text on bottom just says: ThinkPad E16 Gen 3

Done, but still cannot connect and keeps asking wifi password

Arrababiski · 5 January 2026 17:14

So this should be your wifi card (MT7922):

But reading some support articles, seems mt7921e and mt7922e use the same drivers so I don’t know what else can we try…

If it’s some kind of incompatibility between the card and the router, as @nachlese mentioned at the beginning, discovering it is now a matter of luck. Or it could be the dumbest thing in the world.

Do you also have Windows on the hard drive (to rule out fast boot)? Is secure boot disabled in the Bios?

Do you have any unusual or local characters in your guest & 5G passwords (in case your keyboard is misconfigured and is typing different characters you can’t see)?

In NetworkManager → Configure, delete the guest & 5G wifi connections and let the system create them again.

If your router allows you to choose wifi at 20/40/80 MHz, select 20MHz (I have sometimes seen stability problems with this). If you can choose between wifi a/b/g/n/ac/ax, exclude ac and ax.

If your router has a “smart network switching” option (to the one with the strongest signal), disable it.

Does your router have the latest firmware available (in case the incompatibility has already been resolved)?

Any error message typing sudo dmesg | grep -i "mt79"?

Try also these three commands, let’s see if anything strange appears.
hwinfo --network --verbose
hwinfo --netcard --verbose
hwinfo --wlan --verbose