arm-strong Posted February 14, 2023 Share Posted February 14, 2023 I have a 8811CU WiFi dongle that failed to work on my Nanopi Neo. When connecting using nmcli, I get this error "Error: Connection activation failed: (7) Secrets were required, but not provided." The device is correctly recognized and I can perform iw scan without issue. I tried with 6.1.7(edge) and 5.15.89(current) kernel, and install the driver from https://github.com/morrownr/8821cu-20210916, all end up with the exact same error. Here's the journal log where "nl80211: kernel reports: Authentication algorithm number required" error stands out. Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4565] audit: op="connection-update" uuid="5723cd52-fc51-48bf-ab79-33a902d143b6" name="MySSID" args="802-11-wireless-security.psk" pid=5230 uid=1000 result="success" Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4781] device (wlx90deadbeef85): Activation: starting connection 'MySSID' (5723cd52-fc51-48bf-ab79-33a902d143b6) Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4795] audit: op="connection-activate" uuid="5723cd52-fc51-48bf-ab79-33a902d143b6" name="MySSID" pid=5230 uid=1000 result="success" Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4810] device (wlx90deadbeef85): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4871] device (wlx90deadbeef85): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4910] device (wlx90deadbeef85): Activation: (wifi) access point 'MySSID' has security, but secrets are required. Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.4913] device (wlx90deadbeef85): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5164] device (wlx90deadbeef85): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5201] device (wlx90deadbeef85): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5232] device (wlx90deadbeef85): Activation: (wifi) connection 'MySSID' has security, and secrets exist. No new secrets needed. Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5236] Config: added 'ssid' value 'MySSID' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5237] Config: added 'scan_ssid' value '1' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5238] Config: added 'bgscan' value 'simple:30:-70:86400' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5241] Config: added 'key_mgmt' value 'SAE FT-SAE' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5243] Config: added 'auth_alg' value 'OPEN' Feb 14 13:51:55 nanopi-neo NetworkManager[513]: <info> [1676400715.5244] Config: added 'psk' value '<hidden>' Feb 14 13:51:55 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: Trying to associate with e8:9f:ff:00:ff:00 (SSID='MySSID' freq=2452 MHz) Feb 14 13:51:55 nanopi-neo wpa_supplicant[540]: nl80211: kernel reports: Authentication algorithm number required Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=2452 ht_enabled=1 ch_offset=0 ch_width=20 MHz cf1=2452 cf2=0 Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.6389] device (wlx90deadbeef85): supplicant interface state: inactive -> associating Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.6391] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: inactive -> associating Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-ASSOC-REJECT status_code=53 Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=1 duration=10 reason=CONN_FAILED Feb 14 13:51:56 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.8990] device (wlx90deadbeef85): supplicant interface state: associating -> disconnected Feb 14 13:51:56 nanopi-neo NetworkManager[513]: <info> [1676400716.8993] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: associating -> disconnected Feb 14 13:52:07 nanopi-neo NetworkManager[513]: <info> [1676400727.9463] device (wlx90deadbeef85): supplicant interface state: disconnected -> scanning Feb 14 13:52:07 nanopi-neo NetworkManager[513]: <info> [1676400727.9467] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: disconnected -> scanning Feb 14 13:52:12 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-SSID-REENABLED id=0 ssid="MySSID" Feb 14 13:52:12 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: Trying to associate with ea:9f:ff:00:ff:00 (SSID='MySSID' freq=5220 MHz) Feb 14 13:52:12 nanopi-neo wpa_supplicant[540]: nl80211: kernel reports: Authentication algorithm number required Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5220 ht_enabled=1 ch_offset=1 ch_width=80 MHz cf1=5210 cf2=0 Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.5834] device (wlx90deadbeef85): supplicant interface state: scanning -> associating Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.5837] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: scanning -> associating Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-ASSOC-REJECT status_code=53 Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MySSID" auth_failures=2 duration=20 reason=CONN_FAILED Feb 14 13:52:13 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.6529] device (wlx90deadbeef85): supplicant interface state: associating -> disconnected Feb 14 13:52:13 nanopi-neo NetworkManager[513]: <info> [1676400733.6532] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: associating -> disconnected Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3324] device (wlx90deadbeef85): Activation: (wifi) association took too long Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <info> [1676400740.3328] device (wlx90deadbeef85): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3516] device (wlx90deadbeef85): Activation: (wifi) asking for new secrets Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3633] device (wlx90deadbeef85): no secrets: No agents were available for this request. Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <info> [1676400740.3636] device (wlx90deadbeef85): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <warn> [1676400740.3755] device (wlx90deadbeef85): Activation: failed for connection 'MySSID' Feb 14 13:52:20 nanopi-neo NetworkManager[513]: <info> [1676400740.3788] device (wlx90deadbeef85): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 14 13:52:30 nanopi-neo wpa_supplicant[540]: wlx90deadbeef85: Reject scan trigger since one is already pending Feb 14 13:52:32 nanopi-neo NetworkManager[513]: <info> [1676400752.3693] device (wlx90deadbeef85): supplicant interface state: disconnected -> inactive Feb 14 13:52:32 nanopi-neo NetworkManager[513]: <info> [1676400752.3697] device (p2p-dev-wlx90deadbeef85): supplicant management interface state: disconnected -> inactive 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.