You are not logged in.

#1 2024-06-20 15:05:17

Lex0s
Member
Registered: 2023-10-03
Posts: 17

[HW problem] nmcli lists and shows wi-fi networks but won't connect.

I've been using a Realtek RTL8821CE usb wi-fi adapter since April as a replacement for my dead internal wi-fi adapter of my laptop and it has been working pretty well until 2 days ago. As the title suggests, using "nmtui" and "nmcli" allows me to see the networks available including mine, but won't connect to it, the output always is:

Error: Connection activation failed: The Wi-Fi network could not be found

I tried to connect it to my phone's hotspot network and it just works randomly, it connects, it stays connected for some minutes and then it disconnects and won't connect again unless I unplug and plug the adapter. My wifi can display 2 networks, a 4G version and a 5G version, what happens when I connect to my phone's wifi also happens with the 4G version. The only one that won't make a connection is the 5G displayed version no matter what from what it seems.

I deleted the network from nmcli and decided to try to connect it again, and didn't work. So I deleted the network again and decided to save the logs from "dmesg" and "journalctl -xe" from the attempt of network manager to connect to it using the usb device:

journalct -xe
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0002] device (wlan1): Activation: starting connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0004] audit: op="connection-add-activate" uuid="074e7d53-e1fa-4901-9651-bb4bf9690e96" name="fh_95c690_5G" pid=1225 uid=1000 resul>
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0010] device (wlan1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0012] manager: NetworkManager state is now CONNECTING
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0014] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0017] device (wlan1): Activation: (wifi) access point 'fh_95c690_5G' has security, but secrets are required.
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0017] device (wlan1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0026] device (wlan1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0028] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0030] device (wlan1): Activation: (wifi) connection 'fh_95c690_5G' has security, and secrets exist.  No new secrets needed.
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0030] Config: added 'ssid' value 'fh_95c690_5G'
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0030] Config: added 'scan_ssid' value '1'
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0030] Config: added 'bgscan' value 'simple:30:-70:86400'
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0031] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0031] Config: added 'auth_alg' value 'OPEN'
Jun 20 10:31:38 Lex0ss NetworkManager[486]: <info>  [1718893898.0031] Config: added 'psk' value '<hidden>'
Jun 20 10:31:39 Lex0ss NetworkManager[486]: <info>  [1718893899.8274] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:31:41 Lex0ss systemd[764]: Started tmux child pane 1232 launched by process 1041.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 185.
Jun 20 10:31:42 Lex0ss wpa_supplicant[664]: wlan1: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 10:31:44 Lex0ss kernel: wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
Jun 20 10:31:44 Lex0ss NetworkManager[486]: <info>  [1718893904.5759] device (wlan1): supplicant interface state: scanning -> authenticating
Jun 20 10:31:44 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
Jun 20 10:31:45 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
Jun 20 10:31:46 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
Jun 20 10:31:47 Lex0ss kernel: wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
Jun 20 10:31:47 Lex0ss NetworkManager[486]: <info>  [1718893907.2059] device (wlan1): supplicant interface state: authenticating -> disconnected
Jun 20 10:31:49 Lex0ss NetworkManager[486]: <info>  [1718893909.1894] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:31:52 Lex0ss wpa_supplicant[664]: wlan1: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 10:31:53 Lex0ss systemd[1]: Unmounting EFI System Partition Automount...
░░ Subject: A stop job for unit efi.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit efi.mount has begun execution.
░░
░░ The job identifier is 1148.
Jun 20 10:31:53 Lex0ss systemd[1]: efi.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit efi.mount has successfully entered the 'dead' state.
Jun 20 10:31:53 Lex0ss systemd[1]: Unmounted EFI System Partition Automount.
░░ Subject: A stop job for unit efi.mount has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit efi.mount has finished.
░░
░░ The job identifier is 1148 and the job result is done.
Jun 20 10:31:53 Lex0ss kernel: wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
Jun 20 10:31:53 Lex0ss NetworkManager[486]: <info>  [1718893913.9825] device (wlan1): supplicant interface state: scanning -> authenticating
Jun 20 10:31:53 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
Jun 20 10:31:55 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
Jun 20 10:31:56 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
Jun 20 10:31:57 Lex0ss kernel: wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
Jun 20 10:31:57 Lex0ss NetworkManager[486]: <info>  [1718893917.2233] device (wlan1): supplicant interface state: authenticating -> disconnected
Jun 20 10:31:59 Lex0ss NetworkManager[486]: <info>  [1718893919.5743] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:32:03 Lex0ss NetworkManager[486]: <warn>  [1718893923.7275] device (wlan1): Activation: (wifi) association took too long, failing activation
Jun 20 10:32:03 Lex0ss NetworkManager[486]: <info>  [1718893923.7276] device (wlan1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 20 10:32:03 Lex0ss NetworkManager[486]: <info>  [1718893923.7280] manager: NetworkManager state is now DISCONNECTED
Jun 20 10:32:03 Lex0ss NetworkManager[486]: <warn>  [1718893923.7284] device (wlan1): Activation: failed for connection 'fh_95c690_5G'
Jun 20 10:32:03 Lex0ss NetworkManager[486]: <info>  [1718893923.7291] device (wlan1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3413] device (wlan1): supplicant interface state: scanning -> disconnected
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3427] policy: auto-activating connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3435] device (wlan1): Activation: starting connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3437] device (wlan1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3441] manager: NetworkManager state is now CONNECTING
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3445] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3450] device (wlan1): Activation: (wifi) access point 'fh_95c690_5G' has security, but secrets are required.
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3450] device (wlan1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3464] device (wlan1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3467] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3470] device (wlan1): Activation: (wifi) connection 'fh_95c690_5G' has security, and secrets exist.  No new secrets needed.
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3471] Config: added 'ssid' value 'fh_95c690_5G'
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3471] Config: added 'scan_ssid' value '1'
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3471] Config: added 'bgscan' value 'simple:30:-70:86400'
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3471] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3472] Config: added 'auth_alg' value 'OPEN'
Jun 20 10:32:08 Lex0ss NetworkManager[486]: <info>  [1718893928.3472] Config: added 'psk' value '<hidden>'
Jun 20 10:32:08 Lex0ss wpa_supplicant[664]: wlan1: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 10:32:10 Lex0ss kernel: wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
Jun 20 10:32:10 Lex0ss NetworkManager[486]: <info>  [1718893930.1325] device (wlan1): supplicant interface state: disconnected -> authenticating
Jun 20 10:32:10 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
Jun 20 10:32:11 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
Jun 20 10:32:12 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
Jun 20 10:32:13 Lex0ss kernel: wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
Jun 20 10:32:13 Lex0ss NetworkManager[486]: <info>  [1718893933.2139] device (wlan1): supplicant interface state: authenticating -> disconnected
Jun 20 10:32:16 Lex0ss NetworkManager[486]: <info>  [1718893936.0984] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:32:30 Lex0ss sudo[1274]: Matixannder : TTY=pts/5 ; PWD=/home/Matixannder ; USER=root ; COMMAND=/usr/bin/dmesg -T
Jun 20 10:32:30 Lex0ss sudo[1274]: pam_unix(sudo:session): session opened for user root(uid=0) by Matixannder(uid=1000)
Jun 20 10:32:30 Lex0ss sudo[1274]: pam_unix(sudo:session): session closed for user root
Jun 20 10:32:33 Lex0ss NetworkManager[486]: <warn>  [1718893953.7280] device (wlan1): Activation: (wifi) association took too long, failing activation
Jun 20 10:32:33 Lex0ss NetworkManager[486]: <info>  [1718893953.7281] device (wlan1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 20 10:32:33 Lex0ss NetworkManager[486]: <info>  [1718893953.7286] manager: NetworkManager state is now DISCONNECTED
Jun 20 10:32:33 Lex0ss NetworkManager[486]: <warn>  [1718893953.7290] device (wlan1): Activation: failed for connection 'fh_95c690_5G'
Jun 20 10:32:33 Lex0ss NetworkManager[486]: <info>  [1718893953.7293] device (wlan1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 20 10:32:35 Lex0ss wpa_supplicant[664]: wlan1: Reject scan trigger since one is already pending
Jun 20 10:32:41 Lex0ss wpa_supplicant[664]: wlan1: Reject scan trigger since one is already pending
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2746] policy: auto-activating connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2752] device (wlan1): Activation: starting connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2754] device (wlan1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2757] manager: NetworkManager state is now CONNECTING
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2761] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2764] device (wlan1): Activation: (wifi) access point 'fh_95c690_5G' has security, but secrets are required.
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2765] device (wlan1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2779] device (wlan1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2783] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2786] device (wlan1): Activation: (wifi) connection 'fh_95c690_5G' has security, and secrets exist.  No new secrets needed.
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2786] Config: added 'ssid' value 'fh_95c690_5G'
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2786] Config: added 'scan_ssid' value '1'
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2786] Config: added 'bgscan' value 'simple:30:-70:86400'
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2786] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2787] Config: added 'auth_alg' value 'OPEN'
Jun 20 10:33:08 Lex0ss NetworkManager[486]: <info>  [1718893988.2787] Config: added 'psk' value '<hidden>'
Jun 20 10:33:08 Lex0ss wpa_supplicant[664]: wlan1: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 10:33:09 Lex0ss kernel: wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
Jun 20 10:33:09 Lex0ss NetworkManager[486]: <info>  [1718893989.9391] device (wlan1): supplicant interface state: scanning -> authenticating
Jun 20 10:33:09 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
Jun 20 10:33:11 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
Jun 20 10:33:12 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
Jun 20 10:33:13 Lex0ss kernel: wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
Jun 20 10:33:13 Lex0ss wpa_supplicant[664]: wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=1 duration=10 reason=CONN_FAILED
Jun 20 10:33:13 Lex0ss NetworkManager[486]: <info>  [1718893993.2307] device (wlan1): supplicant interface state: authenticating -> disconnected
Jun 20 10:33:19 Lex0ss NetworkManager[486]: <info>  [1718893999.8712] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:33:23 Lex0ss wpa_supplicant[664]: wlan1: CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
Jun 20 10:33:23 Lex0ss wpa_supplicant[664]: wlan1: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 10:33:25 Lex0ss kernel: wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
Jun 20 10:33:25 Lex0ss NetworkManager[486]: <info>  [1718894005.3083] device (wlan1): supplicant interface state: scanning -> authenticating
Jun 20 10:33:25 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
Jun 20 10:33:26 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
Jun 20 10:33:27 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
Jun 20 10:33:28 Lex0ss kernel: wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
Jun 20 10:33:28 Lex0ss wpa_supplicant[664]: BSSID 6c:a4:d1:95:c6:94 ignore list count incremented to 2, ignoring for 10 seconds
Jun 20 10:33:28 Lex0ss wpa_supplicant[664]: wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=2 duration=20 reason=CONN_FAILED
Jun 20 10:33:28 Lex0ss NetworkManager[486]: <info>  [1718894008.1967] device (wlan1): supplicant interface state: authenticating -> disconnected
Jun 20 10:33:33 Lex0ss NetworkManager[486]: <warn>  [1718894013.7283] device (wlan1): Activation: (wifi) association took too long, failing activation
Jun 20 10:33:33 Lex0ss NetworkManager[486]: <info>  [1718894013.7283] device (wlan1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 20 10:33:33 Lex0ss NetworkManager[486]: <info>  [1718894013.7287] manager: NetworkManager state is now DISCONNECTED
Jun 20 10:33:33 Lex0ss NetworkManager[486]: <warn>  [1718894013.7289] device (wlan1): Activation: failed for connection 'fh_95c690_5G'
Jun 20 10:33:33 Lex0ss NetworkManager[486]: <info>  [1718894013.7291] device (wlan1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2309] policy: auto-activating connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2314] device (wlan1): Activation: starting connection 'fh_95c690_5G' (074e7d53-e1fa-4901-9651-bb4bf9690e96)
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2315] device (wlan1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2315] device (wlan1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2315] device (wlan1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2318] manager: NetworkManager state is now CONNECTING
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2321] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2325] device (wlan1): Activation: (wifi) access point 'fh_95c690_5G' has security, but secrets are required.
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2325] device (wlan1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2333] device (wlan1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2335] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2336] device (wlan1): Activation: (wifi) connection 'fh_95c690_5G' has security, and secrets exist.  No new secrets needed.
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2337] Config: added 'ssid' value 'fh_95c690_5G'
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2337] Config: added 'scan_ssid' value '1'
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2337] Config: added 'bgscan' value 'simple:30:-70:86400'
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2337] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2337] Config: added 'auth_alg' value 'OPEN'
Jun 20 10:33:34 Lex0ss NetworkManager[486]: <info>  [1718894014.2337] Config: added 'psk' value '<hidden>'
Jun 20 10:33:39 Lex0ss NetworkManager[486]: <info>  [1718894019.9810] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:33:42 Lex0ss wpa_supplicant[664]: wlan1: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 10:33:44 Lex0ss kernel: wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
Jun 20 10:33:44 Lex0ss NetworkManager[486]: <info>  [1718894024.7459] device (wlan1): supplicant interface state: scanning -> authenticating
Jun 20 10:33:44 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
Jun 20 10:33:46 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
Jun 20 10:33:47 Lex0ss kernel: wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
Jun 20 10:33:48 Lex0ss kernel: wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
Jun 20 10:33:48 Lex0ss wpa_supplicant[664]: wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=1 duration=10 reason=CONN_FAILED
Jun 20 10:33:48 Lex0ss NetworkManager[486]: <info>  [1718894028.2568] device (wlan1): supplicant interface state: authenticating -> disconnected
Jun 20 10:33:59 Lex0ss NetworkManager[486]: <warn>  [1718894039.7285] device (wlan1): Activation: (wifi) association took too long, failing activation
Jun 20 10:33:59 Lex0ss NetworkManager[486]: <info>  [1718894039.7286] device (wlan1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 20 10:33:59 Lex0ss NetworkManager[486]: <info>  [1718894039.7290] manager: NetworkManager state is now DISCONNECTED
Jun 20 10:33:59 Lex0ss NetworkManager[486]: <warn>  [1718894039.7294] device (wlan1): Activation: failed for connection 'fh_95c690_5G'
Jun 20 10:33:59 Lex0ss NetworkManager[486]: <info>  [1718894039.7297] device (wlan1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 20 10:33:59 Lex0ss wpa_supplicant[664]: wlan1: Reject scan trigger since one is already pending
Jun 20 10:33:59 Lex0ss NetworkManager[486]: <info>  [1718894039.9516] device (wlan1): supplicant interface state: disconnected -> scanning
Jun 20 10:34:02 Lex0ss NetworkManager[486]: <info>  [1718894042.7472] device (wlan1): supplicant interface state: scanning -> disconnected
Jun 20 10:34:06 Lex0ss wpa_supplicant[664]: wlan1: Reject scan trigger since one is already pending
Jun 20 10:35:10 Lex0ss sudo[1295]: Matixannder : TTY=pts/5 ; PWD=/home/Matixannder ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jun 20 10:35:10 Lex0ss sudo[1295]: pam_unix(sudo:session): session opened for user root(uid=0) by Matixannder(uid=1000)
Jun 20 10:35:32 Lex0ss sudo[1295]: pam_unix(sudo:session): session closed for user root
Jun 20 10:36:09 Lex0ss sudo[1303]: Matixannder : TTY=pts/5 ; PWD=/home/Matixannder ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jun 20 10:36:09 Lex0ss sudo[1303]: pam_unix(sudo:session): session opened for user root(uid=0) by Matixannder(uid=1000)
Jun 20 10:36:10 Lex0ss sudo[1303]: pam_unix(sudo:session): session closed for user root
Jun 20 10:36:23 Lex0ss sudo[1321]: Matixannder : TTY=pts/5 ; PWD=/home/Matixannder ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jun 20 10:36:23 Lex0ss sudo[1321]: pam_unix(sudo:session): session opened for user root(uid=0) by Matixannder(uid=1000)
dmesg -T
[Thu Jun 20 10:29:48 2024] usb 1-2: new high-speed USB device number 4 using xhci_hcd
[Thu Jun 20 10:29:48 2024] usb 1-2: New USB device found, idVendor=0bda, idProduct=b812, bcdDevice= 2.10
[Thu Jun 20 10:29:48 2024] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Thu Jun 20 10:29:48 2024] usb 1-2: Product: 802.11ac NIC
[Thu Jun 20 10:29:48 2024] usb 1-2: Manufacturer: Realtek
[Thu Jun 20 10:29:48 2024] usb 1-2: SerialNumber: 123456
[Thu Jun 20 10:29:49 2024] rtw_8822bu 1-2:1.0: Firmware version 27.2.0, H2C version 13
[Thu Jun 20 10:29:50 2024] usbcore: registered new interface driver rtw_8822bu
[Thu Jun 20 10:29:51 2024] systemd-journald[298]: /var/log/journal/d82f53efc8ee4eeca6e35b0064df9cb9/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[Thu Jun 20 10:31:44 2024] wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
[Thu Jun 20 10:31:44 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
[Thu Jun 20 10:31:45 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
[Thu Jun 20 10:31:46 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
[Thu Jun 20 10:31:47 2024] wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
[Thu Jun 20 10:31:53 2024] wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
[Thu Jun 20 10:31:53 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
[Thu Jun 20 10:31:55 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
[Thu Jun 20 10:31:56 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
[Thu Jun 20 10:31:57 2024] wlan1: authentication with 6c:a4:d1:95:c6:94 timed out
[Thu Jun 20 10:32:10 2024] wlan1: authenticate with 6c:a4:d1:95:c6:94 (local address=90:91:64:86:4a:6f)
[Thu Jun 20 10:32:10 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 1/3)
[Thu Jun 20 10:32:11 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 2/3)
[Thu Jun 20 10:32:12 2024] wlan1: send auth to 6c:a4:d1:95:c6:94 (try 3/3)
[Thu Jun 20 10:32:13 2024] wlan1: authentication with 6c:a4:d1:95:c6:94 timed out

What do you think it can be the problem? Thanks for any help in advance

Last edited by Lex0s (2024-06-24 22:17:02)

Offline

#2 2024-06-20 15:46:03

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

The primary reason for the described symptoms is https://wiki.archlinux.org/title/Networ … domization so try to disable that and reboot system and in doubt (and if you can) the AP.

Otherwise please post your complete system journal for a boot covering such failure:

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

The last page of the journal lacks the context leading up to the failure and please never. EVER. use "-x" as it's really just spam cluttering the journal with ridiculous "explanations" of the obvious.

Offline

#3 2024-06-20 21:58:24

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

Did both things and it didn't work, it connects to the networks, but won't receive and upload any package. this is the result of the command that you gave me:

http://0x0.st/XT6d.txt

Offline

#4 2024-06-20 22:30:08

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

You keep associating and then get kicked for inactivity after a beacon loss despite the reported signal is always "ok" (it's not great, but not weak either)

This here is super-sketchy:

Jun 20 16:50:38 Lex0ss wpa_supplicant[646]: wlan1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=650000
Jun 20 16:50:41 Lex0ss kernel: rtw_8822bu 3-2:1.0: firmware failed to leave lps state
Jun 20 16:50:46 Lex0ss wpa_supplicant[646]: wlan1: CTRL-EVENT-BEACON-LOSS
Jun 20 16:50:47 Lex0ss kernel: rtw_8822bu 3-2:1.0: firmware failed to leave lps state
Jun 20 16:50:47 Lex0ss systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jun 20 16:50:49 Lex0ss kernel: rtw_8822bu 3-2:1.0: firmware failed to leave lps state
Jun 20 16:50:50 Lex0ss systemd-resolved[449]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 2803:c600:1:60::130.
Jun 20 16:50:51 Lex0ss kernel:  3-2:1.0: firmware failed to leave lps state

Both nics are enabled, you're not using the device-bound interface names (likely because you've iwd installed), the order of wlan0/wlan1 isn't deterministic and it looks A LOT like you're using the rtw_8822bu chip while your OP sounds like you intend to use the rtw_8821ce one?
Disable the internal wifi NIC or remove iwd to get "predictable" (ie. positional, they can still change w/ BIOS updates but not on every boot) interface names and make sure to use the rtw_8821ce NIC.

Offline

#5 2024-06-21 00:58:31

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

The usb adapter that I'm trying to use is rtw_8822bu. I deactivated the internal  wifi adapter and removed iwd, but the problem persists.

It happened something weird, I unpluged and pluged because I wanted to see what I could see on journalctl  and it connected to my network, but I still don't have access to the internet, not even "ping" return any packages from URLs. Here's the result of journalctl -b again http://0x0.st/XT0s.txt.

This is the line that logs the moment I unpluged it:

Jun 20 21:51:00 Lex0ss kernel: usb 3-2: USB disconnect, device number 2

Last edited by Lex0s (2024-06-21 02:03:34)

Offline

#6 2024-06-21 06:58:30

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

Nothing has change wrt the overall pattern

Jun 20 21:59:52 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 21:59:54 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
Jun 20 21:59:54 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: Associated with 6c:a4:d1:95:c6:94
Jun 20 21:59:54 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 20 21:59:54 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: WPA: Key negotiation completed with 6c:a4:d1:95:c6:94 [PTK=CCMP GTK=CCMP]
Jun 20 21:59:54 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: CTRL-EVENT-CONNECTED - Connection to 6c:a4:d1:95:c6:94 completed [id=0 id_str=]
Jun 20 21:59:54 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise=9999 txrate=780000
Jun 20 22:00:03 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: CTRL-EVENT-BEACON-LOSS
Jun 20 22:00:04 Lex0ss wpa_supplicant[798]: wlp4s0f3u2: CTRL-EVENT-DISCONNECTED bssid=6c:a4:d1:95:c6:94 reason=4 locally_generated=1

Associate. Beacon loss. Disconnect for inactivity.

1. Try "rtw88_core.disable_lps_deep=Y", https://wiki.archlinux.org/title/Kernel_parameters
2. Same problem w/ the LTS kernel?
3. Is there a parallel windows installation?
4. https://wiki.archlinux.org/title/Power_ … utosuspend - "usbcore.autosuspend=-1" will disable it
5. do you have more success connectig to a 2.4GHz network?
6. Did you try another usb slot (the wifi dongles draw quite some power, you seem to exclusively have USB 3.1 hubs. though. Maybe the physical position is relevant)

Offline

#7 2024-06-21 15:31:36

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

I'll go trying each step and writing what happened so I won't forget it while I'm doing other stuff:

1. Try "rtw88_core.disable_lps_deep=Y", https://wiki.archlinux.org/title/Kernel_parameters

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet rtw88_core.disable_lps_deep=Y"

Then reboot it (I'm not pretty familiar with GRUB, it just suited my BIOS and worked out of the box, so I preferred to do it this way to be sure). It still didn't change anything.

3. Is there a parallel windows installation?

Yes I have a dual-boot, but I made sure every time that it updates (a.k.a Windows do whatever the hell it wants) to deactivate hibernation and fast start from the Powershell. The problem though started as I say 3-4 days ago and in that frame of time I haven't boot into it. I will try to see if the adapter works there to be sure.

4. https://wiki.archlinux.org/title/Power_ … utosuspend - "usbcore.autosuspend=-1" will disable it

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet rtw88_core.disable_lps_deep=Y usbcore.autosuspend=5"

Then reboot again, I still can't connect

5. do you have more success connectig to a 2.4GHz network?

I actually tried this first, and yes. It works pretty inconsistently, at the start it connected to it but it was like I had no access to the internet or it worked very slow at best. After I tried the points from 1 and 4, it improved, connection is a little more stable and I can load pages from the wiki, and do other stuff, but the connection is still pretty slow, barely reaching 1 or 2 MB of download speed and 1 MB of upload speed, compared to my phone that when I connect it to the same network version with the same frequency band, it says that reach 18 MB of download speed. And it still disconnects after some minutes and struggles to reconnect.

6. Did you try another usb slot (the wifi dongles draw quite some power, you seem to exclusively have USB 3.1 hubs. though. Maybe the physical position is relevant)

Yes, sometimes it improves, sometimes it doesn't. Asides from the fact that the connection seems (I haven't tried enough times to see if it is 100% true) to last longer in the right slot than the left one, speed and consistency when it comes to connect to the networks are pretty much the same. Same applies to the 5G network, it could and could not connect to it but I won't receive any packages. And if by position you mean how close the device is to the hotspot, I usually plug it to the left slot because that's the direction where the the router is.

Offline

#8 2024-06-21 16:12:49

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

Editing /etc/default/grub is inert - you've to also grub-mkconfig.
Alternatively just press "e" and edit the commandline at the bootloader.
And use "usbcore.autosuspend=-1", not "5"

Offline

#9 2024-06-21 18:41:13

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

I change the "usbcore.autosuspend=-1". Nothing changed after reboot. At this point I think it should be a hardware problem with the device. I just can't make it work with the 5G network and barely works with the 2.4Ghz. Also tried with the lts linux kernel and the results were the same.


I even tried to deactivate the in-kernel driver of the device and install this one and the results are the same, so I don't know what to do. I decided to check again the documentation that the same github account let here (that set me up to choose the adapter in the first place), and I think I remember that an statement that said the realtek chipsets are pretty fragile and prone to break. So, I don't know. Is there anything else that you could suggest me to do? if not tell me and will mark this thread as hardware problem. Sadly in my country there is no market of mediatek chipsets, so I think I'll just have to cope with it.

Last edited by Lex0s (2024-06-21 18:42:40)

Offline

#10 2024-06-21 20:42:12

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

You got this part?

Editing /etc/default/grub is inert - you've to also grub-mkconfig.
Alternatively just press "e" and edit the commandline at the bootloader.

cat /proc/cmdline

will show the commandline that was actually applied.

I'd then cut out NM and use either iwd or wpa_supplicant manually (or at most wpa_supplicant via wifi-menu from the netctl package)
Next to the forementioned parameters try to explcitily

iw dev wlp4s0f3u2 set power_save off

Your initial journal had

Jun 20 16:50:41 Lex0ss kernel: rtw_8822bu 3-2:1.0: firmware failed to leave lps state
Jun 20 16:52:13 Lex0ss kernel: rtw_8822bu 3-2:1.0: write register 0x1b80 failed with -71
Jun 20 16:52:13 Lex0ss kernel: rtw_8822bu 3-2:1.0: failed to do USB write, ret=-19
Jun 20 16:52:13 Lex0ss kernel: rtw_8822bu 3-2:1.0: failed to send h2c packet
Jun 20 16:54:45 Lex0ss kernel: rtw_8822bu 1-2:1.0: write register 0x5 failed with -71
Jun 20 16:54:45 Lex0ss kernel: rtw_8822bu 1-2:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71

what all yells "power issues".

Did you use https://aur.archlinux.org/packages/rtl88x2bu-dkms-git ?
What does the journal for that driver look like?

Offline

#11 2024-06-22 18:29:57

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

Yeah I tried yesterday, I tried both. This is the journal of the morrownr driver: http://0x0.st/XAQ_.txt

And this is the RinCat driver journal output: http://0x0.st/XAQE.txt

As you can see, none of them mention the "lsp state" problem that appeared in the beginning, I guess that 1 of the points that you mentioned earlier already fixed it

You got this part?

Editing /etc/default/grub is inert - you've to also grub-mkconfig.
Alternatively just press "e" and edit the commandline at the bootloader.

Yeah, I knew that I have to run grub-mkconfig -o after doing the changes.

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=b6f8f8d5-d9c6-4a9d-a252-5e0063322c41 rw loglevel=3 quiet rtw88_core.disable_lps_deep=Y usbcore.autosuspend=-1

I'll go finish some things out and then I'll return and edit this response with the results of iw.

Last edited by Lex0s (2024-06-22 22:52:26)

Offline

#12 2024-06-22 22:55:50

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

https://github.com/morrownr/88x2bu-20210702 :

Jun 22 13:51:25 Lex0ss wpa_supplicant[1468]: wlp4s0f4u2: Trying to associate with 6c:a4:d1:95:c6:90 (SSID='fh_95c690' freq=2412 MHz)
Jun 22 13:51:25 Lex0ss NetworkManager[579]: <info>  [1719078685.3736] device (wlp4s0f4u2): supplicant interface state: disconnected -> associating
Jun 22 13:51:25 Lex0ss NetworkManager[579]: <info>  [1719078685.3736] device (p2p-dev-wlp4s0f4u2): supplicant management interface state: disconnected -> associating
Jun 22 13:51:25 Lex0ss wpa_supplicant[1468]: wlp4s0f4u2: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=2412 ht_enabled=1 ch_offset=0 ch_width=20 MHz cf1=2412 cf2=0
Jun 22 13:51:27 Lex0ss wpa_supplicant[1468]: wlp4s0f4u2: CTRL-EVENT-ASSOC-REJECT status_code=1
Jun 22 13:51:27 Lex0ss wpa_supplicant[1468]: wlp4s0f4u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 22 13:51:27 Lex0ss wpa_supplicant[1468]: wlp4s0f4u2: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL

https://aur.archlinux.org/packages/rtl88x2bu-dkms-git

Jun 22 14:19:21 Lex0ss wpa_supplicant[40065]: wlp4s0f4u2: Trying to associate with 6c:a4:d1:95:c6:90 (SSID='fh_95c690' freq=2412 MHz)
Jun 22 14:19:21 Lex0ss kernel: RTW: [HALMAC][ALWAYS]shall R reg twice!!
Jun 22 14:19:22 Lex0ss kernel: start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384)
Jun 22 14:19:22 Lex0ss wpa_supplicant[40065]: wlp4s0f4u2: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=2412 ht_enabled=1 ch_offset=0 ch_width=20 MHz cf1=2412 cf2=0
Jun 22 14:19:22 Lex0ss NetworkManager[610]: <info>  [1719080362.6019] device (wlp4s0f4u2): supplicant interface state: disconnected -> associating
Jun 22 14:19:22 Lex0ss NetworkManager[610]: <info>  [1719080362.6019] device (p2p-dev-wlp4s0f4u2): supplicant management interface state: disconnected -> associating
Jun 22 14:19:22 Lex0ss kernel: RTW: nolinked power save leave
Jun 22 14:19:22 Lex0ss kernel: RTW: rtw_set_802_11_connect(wlp4s0f4u2)  fw_state=0x00000008
Jun 22 14:19:22 Lex0ss kernel: RTW: start auth
Jun 22 14:19:24 Lex0ss wpa_supplicant[40065]: wlp4s0f4u2: CTRL-EVENT-ASSOC-REJECT status_code=1
Jun 22 14:19:24 Lex0ss wpa_supplicant[40065]: wlp4s0f4u2: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 22 14:19:24 Lex0ss wpa_supplicant[40065]: wlp4s0f4u2: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL

In both cases the AP tells you to get lost.

Yes I have a dual-boot, but I made sure every time that it updates (a.k.a Windows do whatever the hell it wants) to deactivate hibernation and fast start from the Powershell. The problem though started as I say 3-4 days ago and in that frame of time I haven't boot into it. I will try to see if the adapter works there to be sure.

If the manual connects w/o NM also fail, double, triple and quadruple check the condition and in doub try to reboot the router.

Offline

#13 2024-06-23 00:38:12

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

It seems that the same pattern repeats in wpa_cli after I set the device with wpa_supplicant. I did it 3 times, trying both USB slots, I tried once with the RinCat driver and the in-kernel driver before and after I made sure that Windows had hibernation and fast-start turned off.

The first time it didn't even showed networks, and in the other slot it just said FAIL when I tried to scan networks:

wpa_cli scan && scan_results

<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
> scan_results
bssid / frequency / signal level / flags / ssid

With the in-kernel driver:

wpa_cli add_network 0 && > set_network 0 ssid "fh_95c690_5G" 

> enable_network 0
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=1 duration=10 reason=CONN_FAILED
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=2 duration=31 reason=CONN_FAILED
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=3 duration=51 reason=CONN_FAILED
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=4 duration=83 reason=CONN_FAILED
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>Trying to associate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5290 cf2=0
<3>CTRL-EVENT-ASSOC-REJECT status_code=1
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=5 duration=62 reason=CONN_FAILED
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL

And after checking Windows:

> enable_network 0
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=1 duration=10 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=2 duration=28 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=3 duration=43 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=4 duration=68 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-NETWORK-NOT-FOUND
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>SME: Trying to authenticate with 6c:a4:d1:95:c6:94 (SSID='fh_95c690_5G' freq=5260 MHz)
<3>CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="fh_95c690_5G" auth_failures=5 duration=69 reason=CONN_FAILED
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>CTRL-EVENT-SSID-REENABLED id=0 ssid="fh_95c690_5G"
<3>CTRL-EVENT-NETWORK-NOT-FOUND

Offline

#14 2024-06-24 05:47:00

seth
Member
Registered: 2012-09-03
Posts: 54,484

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

Before the windows boot the AP rejects you, afterwards it can't even be found and this starts to look like your previous thread… can you test the behavior of the built-in chip on windows?
The external dongle still works as expected on windows?

Offline

#15 2024-06-24 22:16:04

Lex0s
Member
Registered: 2023-10-03
Posts: 17

Re: [HW problem] nmcli lists and shows wi-fi networks but won't connect.

No. In Windows happens the same with the device plugged in both slots. So I'll be marking this as a hardware problem, because I have no problem with tethering neither in Windows, so it has to be something with the chip. But thanks for all the support man. At least I made sure that a lot of things in the OS are doing well

Last edited by Lex0s (2024-06-24 22:18:09)

Offline

Board footer

Powered by FluxBB