Activation (wifi) association took too long

Arthurmeade12 · 2024-09-08 01:02:08

Hello,

I have been having issues with connecting to my wifi network on my 2017 Intel iMac. NetworkManager consistently rejects the correct password when I use the GUI, and when I use nmcli it times out. I have tried to
- turn off ipv6, by running `echo 1 | sudo tee /proc/sys/net/ipv6/conf/all/disable_ipv6`
- turn off random MAC address scanning
I have posted output of lspci, uname, and a journal only for NetworkManager. A full journal is linked. (As evidenced by the journal) I have been using Ethernet to fix this problem temporarily.
Thanks for any help.

--------------------------------------------

/etc/NetworkManager/conf.d/30-mac-randomization.conf:

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

sudo journalctl -xeu NetworkManager :

Sep 07 19:36:52 meades-linux-imac NetworkManager[587]: <info>  [1725755812.3261] device (wlan0): supplicant interface state: associating -> disconnected
Sep 07 19:36:52 meades-linux-imac NetworkManager[587]: <info>  [1725755812.3261] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Sep 07 19:36:52 meades-linux-imac NetworkManager[587]: <info>  [1725755812.4605] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 07 19:36:52 meades-linux-imac NetworkManager[587]: <info>  [1725755812.4606] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 07 19:36:53 meades-linux-imac NetworkManager[587]: <info>  [1725755813.9137] device (wlan0): supplicant interface state: scanning -> associating
Sep 07 19:36:53 meades-linux-imac NetworkManager[587]: <info>  [1725755813.9137] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Sep 07 19:36:54 meades-linux-imac NetworkManager[587]: <info>  [1725755814.0852] device (wlan0): supplicant interface state: associating -> associated
Sep 07 19:36:54 meades-linux-imac NetworkManager[587]: <info>  [1725755814.0852] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 07 19:37:04 meades-linux-imac NetworkManager[587]: <info>  [1725755824.0902] device (wlan0): supplicant interface state: associated -> disconnected
Sep 07 19:37:04 meades-linux-imac NetworkManager[587]: <info>  [1725755824.0903] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Sep 07 19:37:04 meades-linux-imac NetworkManager[587]: <info>  [1725755824.1880] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 07 19:37:04 meades-linux-imac NetworkManager[587]: <info>  [1725755824.1881] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 07 19:37:05 meades-linux-imac NetworkManager[587]: <info>  [1725755825.6409] device (wlan0): supplicant interface state: scanning -> associating
Sep 07 19:37:05 meades-linux-imac NetworkManager[587]: <info>  [1725755825.6410] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Sep 07 19:37:05 meades-linux-imac NetworkManager[587]: <info>  [1725755825.8073] device (wlan0): supplicant interface state: associating -> associated
Sep 07 19:37:05 meades-linux-imac NetworkManager[587]: <info>  [1725755825.8074] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 07 19:37:15 meades-linux-imac NetworkManager[587]: <info>  [1725755835.8128] device (wlan0): supplicant interface state: associated -> disconnected
Sep 07 19:37:15 meades-linux-imac NetworkManager[587]: <info>  [1725755835.8128] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Sep 07 19:37:15 meades-linux-imac NetworkManager[587]: <info>  [1725755835.9110] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 07 19:37:15 meades-linux-imac NetworkManager[587]: <info>  [1725755835.9110] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 07 19:37:17 meades-linux-imac NetworkManager[587]: <warn>  [1725755837.2237] device (wlan0): Activation: (wifi) association took too long
Sep 07 19:37:17 meades-linux-imac NetworkManager[587]: <info>  [1725755837.2238] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 07 19:37:17 meades-linux-imac NetworkManager[587]: <warn>  [1725755837.2245] device (wlan0): Activation: (wifi) asking for new secrets
Sep 07 19:37:17 meades-linux-imac NetworkManager[587]: <info>  [1725755837.3452] device (wlan0): supplicant interface state: scanning -> inactive
Sep 07 19:37:17 meades-linux-imac NetworkManager[587]: <info>  [1725755837.3452] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1866] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1868] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] device (wlan0): Activation: (wifi) connection 'ATT8rvV9fC' has security, and secrets exist.  No new secrets needed.
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] Config: added 'ssid' value 'ATT8rvV9fC'
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] Config: added 'scan_ssid' value '1'
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] Config: added 'auth_alg' value 'OPEN'
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.1872] Config: added 'psk' value '<hidden>'
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.2324] device (wlan0): supplicant interface state: inactive -> scanning
Sep 07 19:37:44 meades-linux-imac NetworkManager[587]: <info>  [1725755864.2324] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Sep 07 19:37:45 meades-linux-imac NetworkManager[587]: <info>  [1725755865.7272] device (wlan0): supplicant interface state: scanning -> associating
Sep 07 19:37:45 meades-linux-imac NetworkManager[587]: <info>  [1725755865.7273] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Sep 07 19:37:45 meades-linux-imac NetworkManager[587]: <info>  [1725755865.9947] device (wlan0): supplicant interface state: associating -> associated
Sep 07 19:37:45 meades-linux-imac NetworkManager[587]: <info>  [1725755865.9947] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 07 19:37:55 meades-linux-imac NetworkManager[587]: <info>  [1725755875.9931] device (wlan0): supplicant interface state: associated -> disconnected
Sep 07 19:37:55 meades-linux-imac NetworkManager[587]: <info>  [1725755875.9932] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Sep 07 19:37:56 meades-linux-imac NetworkManager[587]: <info>  [1725755876.0961] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 07 19:37:56 meades-linux-imac NetworkManager[587]: <info>  [1725755876.0961] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 07 19:38:07 meades-linux-imac NetworkManager[587]: <info>  [1725755887.0775] device (wlan0): supplicant interface state: scanning -> associating
Sep 07 19:38:07 meades-linux-imac NetworkManager[587]: <info>  [1725755887.0781] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Sep 07 19:38:07 meades-linux-imac NetworkManager[587]: <info>  [1725755887.2437] device (wlan0): supplicant interface state: associating -> associated
Sep 07 19:38:07 meades-linux-imac NetworkManager[587]: <info>  [1725755887.2438] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <warn>  [1725755889.2228] device (wlan0): Activation: (wifi) association took too long
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <info>  [1725755889.2228] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <info>  [1725755889.2229] sup-iface[cc850a72ed8cf286,0,wlan0]: wps: type pbc start...
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <warn>  [1725755889.2231] device (wlan0): Activation: (wifi) asking for new secrets
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <info>  [1725755889.2259] device (wlan0): supplicant interface state: associated -> disconnected
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <info>  [1725755889.2259] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <info>  [1725755889.2344] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 07 19:38:09 meades-linux-imac NetworkManager[587]: <info>  [1725755889.2344] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 07 19:38:12 meades-linux-imac NetworkManager[587]: <warn>  [1725755892.4284] device (wlan0): no secrets: User canceled the secrets request.
Sep 07 19:38:12 meades-linux-imac NetworkManager[587]: <info>  [1725755892.4285] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Sep 07 19:38:12 meades-linux-imac NetworkManager[587]: <warn>  [1725755892.4295] device (wlan0): Activation: failed for connection 'ATT8rvV9fC'
Sep 07 19:38:12 meades-linux-imac NetworkManager[587]: <info>  [1725755892.4305] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 07 19:38:13 meades-linux-imac NetworkManager[587]: <info>  [1725755893.2063] device (wlan0): supplicant interface state: scanning -> inactive
Sep 07 19:38:13 meades-linux-imac NetworkManager[587]: <info>  [1725755893.2064] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive

uname -a :

Linux meades-linux-imac 6.10.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 04 Sep 2024 15:16:37 +0000 x86_64 GNU/Linux

sudo journalctl -b --no-pager : https://mclo.gs/74GGEF1

seth · 2024-09-08 07:45:35

Welcome to hell: https://wiki.archlinux.org/title/Broadcom_wireless

First off, disable dhcpcd (that's not gonna fix anything, but we also don't want it to get in the way later)

Sep 07 19:36:07 meades-linux-imac NetworkManager[587]: <warn>  [1725755767.5783] device (wlan0): no secrets: No agents were available for this request.
Sep 07 19:36:07 meades-linux-imac NetworkManager[587]: <info>  [1725755767.5783] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Sep 07 19:36:07 meades-linux-imac NetworkManager[587]: <warn>  [1725755767.5785] device (wlan0): Activation: failed for connection 'ATT8rvV9fC'
Sep 07 19:36:07 meades-linux-imac NetworkManager[587]: <info>  [1725755767.5785] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 07 19:36:07 meades-linux-imac wpa_supplicant[645]: wlan0: WPS-CANCEL

Pre-login association is canceled because https://wiki.archlinux.org/title/Networ … et_on_boot

Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8196] device (wlan0): Activation: starting connection 'ATT8rvV9fC' (cc64a40a-a6d8-49f5-8b22-e6b1c5eff827)
Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8197] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8203] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8207] device (wlan0): Activation: (wifi) access point 'ATT8rvV9fC' has security, but secrets are required.
Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8207] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8209] sup-iface[cc850a72ed8cf286,0,wlan0]: wps: type pbc start...
Sep 07 19:36:47 meades-linux-imac wpa_supplicant[645]: wlan0: WPS-PBC-ACTIVE

NM wants to connect but still needs a password (from your or some password manager

Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8659] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 07 19:36:47 meades-linux-imac NetworkManager[587]: <info>  [1725755807.8659] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 07 19:36:51 meades-linux-imac NetworkManager[587]: <info>  [1725755811.7071] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 19:36:51 meades-linux-imac NetworkManager[587]: <info>  [1725755811.7079] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 19:36:51 meades-linux-imac NetworkManager[587]: <info>  [1725755811.7085] device (wlan0): Activation: (wifi) connection 'ATT8rvV9fC' has security, and secrets exist.  No new secrets needed.
Sep 07 19:36:51 meades-linux-imac wpa_supplicant[645]: wlan0: WPS-CANCEL
Sep 07 19:36:51 meades-linux-imac wpa_supplicant[645]: wlan0: Trying to associate with SSID 'ATT8rvV9fC'
Sep 07 19:36:51 meades-linux-imac NetworkManager[587]: <info>  [1725755811.8591] device (wlan0): supplicant interface state: scanning -> associating
Sep 07 19:36:51 meades-linux-imac NetworkManager[587]: <info>  [1725755811.8592] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating

NM scans again, figures it now has the key and tries to associate w/ the AP

Sep 07 19:36:52 meades-linux-imac wpa_supplicant[645]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16

Which now tells you to fuck off…

===> https://bbs.archlinux.org/viewtopic.php … 8#p2144188

Other than that:
a) are you dual booting?
b) Can you connect to another AP (eg. phone hotspot)?
c) is it a 5GHz AP, https://wiki.archlinux.org/title/Broadc … a)_devices ?

Arthurmeade12 · 2024-09-09 12:00:15

Thanks for the reply; sorry that I won't be able to answer all these questions since I do not have access to this computer until later today.
a) Yes; the computer also has an extremely slow install of macOS Ventura. The wifi does not work on macOS either. Hardware problem?
b) I presume? I have ethernet on this computer connecting to the same router, is that sufficient? A phone hotspot should work, but I haven't tried.
c) Have to see when I get home.

seth · 2024-09-09 13:05:04

The wifi does not work on macOS either. Hardware problem?

a) Possibly, we'll see I had speculated on a hibernating windows (because that kills radio most of the time resp. drives APs nuts because you're getting a lease while you already have one)
b) the idea is to not use ethernet (esp. not while trying to get a lease via wifi, because the router might notice that your host already has one… and tell you to fuck off!) but instead connect via WiFi to the hotspot of the phone - to see whether the problem is specific to the host you're currently failing to connect to.

giordano · 2024-09-09 15:23:18

I also have an old macbook and am experiencing the same issue. I found this thread from a few weeks ago, but downgrading wpa_supplicant didn't do the trick for me. Edit: actually, after restarting the laptop (and getting an update of linux-lts to 6.6.50-1) wifi is now working again for me. It looks like restarting networkmanager wasn't sufficient for me (unless the update of linux-lts was important too).

Last edited by giordano (2024-09-09 15:55:25)

seth · 2024-09-09 19:58:01

Ah, yeah - bcrmfmac was affected too but w/o the kernel warning and was at least for one user not fixed: https://bbs.archlinux.org/viewtopic.php … 6#p2193096

Arthurmeade12 · 2024-09-09 23:48:30

I did not follow concerning bcrmfmac, hopefully that's unrelated.

Having trouble getting my phone and the iMac to talk to each other; the USB cables I was using for tethering were not recognized as USB cables by my phone, and the bluetooth tethering my phone offered was not found by the iMac. I can troubleshoot that more if it is important.

Upon reading the section about drivers in Broadcom wireless, I found that none of broadcom-wl, b43, brcm80211 are installed according to pacman. Am I missing a driver?

I've noticed that, according to line 495 of the journal, one of the devices involved has the string 14e4:43ba associated with it, which is mentioned here https://wiki.archlinux.org/title/Broadc … a)_devices. Going to investigate that.

Last edited by Arthurmeade12 (2024-09-09 23:49:07)

seth · 2024-09-10 05:47:58

I did not follow concerning bcrmfmac, hopefully that's unrelated.

No, that's you wifi driver.

none of broadcom-wl, b43, brcm80211 are installed according to pacman

Afaict yout chip isn't supported by broadcom-wl and the other two are part of the kernel package.

Try to add "brcmfmac.feature_disable=0x82000" to the https://wiki.archlinux.org/title/Kernel_parameters - according to Tha-Fox in the linked thread this is still required for him with more recent versions of wpa_supplicant.

Arthurmeade12 · 2024-09-11 01:44:52

Excuse me if I do not reply to this thread for several days; I am in the path of Hurricane Francine and may not have power for a while.

seth · 2024-09-11 05:34:23

No problem - there's a good chance I wouldn't be able to deal with any of this until the beginning of next week myself.
See you on the other side

Kaurin · 2024-09-21 12:09:12

seth wrote:

Try to add "brcmfmac.feature_disable=0x82000" to the https://wiki.archlinux.org/title/Kernel_parameters - according to Tha-Fox in the linked thread this is still required for him with more recent versions of wpa_supplicant.

Quoted advice fixed it for me - MacBookPro 11,5 (Mid-2015).

WiFi just stopped working after one of the package upgrades. I barely used this MacBook since instaling it some months ago so it was weird. Very happy to have found this thread.

lspci -k

04:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)
	Subsystem: Apple Inc. Device 0152
	Kernel driver in use: brcmfmac
	Kernel modules: brcmfmac

Arthurmeade12 · 2024-09-22 12:26:31

I haven't replied to this thread for a while because I forgot about it. I'll try the kernel parameter when I get home.

Arthurmeade12 · 2024-09-25 22:18:19

The bcrmfac kernel paramater is perfect! Thanks for the solution.

Arch Linux

#1 2024-09-08 01:02:08

Activation (wifi) association took too long

#2 2024-09-08 07:45:35

Re: Activation (wifi) association took too long

#3 2024-09-09 12:00:15

Re: Activation (wifi) association took too long

#4 2024-09-09 13:05:04

Re: Activation (wifi) association took too long

#5 2024-09-09 15:23:18

Re: Activation (wifi) association took too long

#6 2024-09-09 19:58:01

Re: Activation (wifi) association took too long

#7 2024-09-09 23:48:30

Re: Activation (wifi) association took too long

#8 2024-09-10 05:47:58

Re: Activation (wifi) association took too long

#9 2024-09-11 01:44:52

Re: Activation (wifi) association took too long

#10 2024-09-11 05:34:23

Re: Activation (wifi) association took too long

#11 2024-09-21 12:09:12

Re: Activation (wifi) association took too long

#12 2024-09-22 12:26:31

Re: Activation (wifi) association took too long

#13 2024-09-25 22:18:19

Re: Activation (wifi) association took too long

Board footer