#989644 iwd: fails to connect to AP from macbook 15,2 or MacBookPro15,1 with firmware BCM4364/3

Package:
iwd
Source:
iwd
Description:
wireless daemon for Linux
Submitter:
Alejandro Valenzuela
Date:
2021-11-30 11:30:05 UTC
Severity:
important
Tags:
#989644#5
Date:
2021-06-09 09:04:54 UTC
From:
To:
Dear Maintainer,

When I upgraded to version 1.14-3, immediately after reloading iwd as prompted
by the system, my wifi disconnected and it became impossible to connect to it
again. I tried restarting the computer and router and a variety of options and
actions (switching the AP channel, trying the 5GHz and 2.4GHz networks) which
did not help, and finally I found out that if I downgrade to 1.13-2 or 1.12-1
and restart, I can connect again without any issues.
If I upgrade to 1.14-3 again -no other packages involved-, I am again unable to
connect after the iwd service is restarted no matter what (including restarting
the computer again) so I'm fairly confident the issue was introduced in a
version after 1.13-2. (I only have access to 1.14-3)

Some extra information which might be relevant:
The wireless card is a Broadcom 4364 present in an intel macbook 15,2 (late
2019 model).

Broadcom dmesg line:
[    5.206303] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/3 wl0: Mar 28
2019 19:17:52 version 9.137.9.0.32.6.34 FWID 01-36f56c94


I attach an iwd --debug and iwmon outputs. (The network I'm trying to connect
the computer to is called "zemlya")

One of the many things I tried was connecting through wpa_supplicant, which
resulted in the following line:

wlan0: Trying to associate with SSID 'zemlya'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=70:8b:cd:e6:9b:04 status_code=16

#989644#10
Date:
2021-06-20 01:37:17 UTC
From:
To:
I was also hit by this bug.  Downgrading to 1.13-2 and rebooting fixed the
issue.


dmesg output for loading the firmware:

$ sudo dmesg | grep brcm
[    3.502146] usbcore: registered new interface driver brcmfmac
[    3.522197] brcmfmac 0000:03:00.0: enabling device (0000 -> 0002)
[    3.637016] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[    3.639047] brcmfmac 0000:03:00.0: firmware: direct-loading firmware brcm/brcmfmac4364-pcie.bin
[    3.639344] brcmfmac 0000:03:00.0: firmware: direct-loading firmware brcm/brcmfmac4364-pcie.Apple Inc.-MacBookPro15,1.txt
[    4.340822] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[    4.341315] brcmfmac 0000:03:00.0: firmware: direct-loading firmware brcm/brcmfmac4364-pcie.clm_blob
[    4.380890] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/3 wl0: Oct 23 2019 08:32:36 version 9.137.11.0.32.6.36 FWID 01-671ec60c

#989644#15
Date:
2021-06-20 07:12:23 UTC
From:
To:
control: tag -1 +upstream

Hi Alejandro and Timur,

Thanksd for your bug reporting.

IWD has seen only upstream changes since release 1.9 (packaging changes
since then has only affected metadata and testsuite).

I have now released 1.15-1 to experimental.  Upstream changes between
1.14 and 1.15 mentions no bugfixes, only feature improvements, but
perhaps some of that anyway improves behavior on your MacBooks.

Please tell if 1.15-1 works for you or not.  And if it doesn't then also
please consider reporting the issue upstream.  Better if you report it
yourself, since you have the hardware needed to test things so I expect
that me acting as proxy would only slow down the process for no benefit.

Upstream contact info is here (at the bottom):
https://iwd.wiki.kernel.org/

If you do report the issue upstream, then please share a link to the
upstream issue report here.


Kind regards,

 - Jonas

#989644#26
Date:
2021-07-07 08:23:12 UTC
From:
To:
Hello Jonas and Timur,

I can confirm the issue still exists in 1.15-1 and will report the bug
upstream as requested

Thanks for the message and sorry for replying so late!
/Alejandro

#989644#31
Date:
2021-07-07 08:38:16 UTC
From:
To:
Quoting Alejandro Valenzuela (2021-07-07 10:23:12)

Thanks!

(also: no need for apology)


 - Jonas

#989644#36
Date:
2021-11-30 14:56:06 UTC
From:
To:
Hi Alejandro (and Tim),

Quoting Alejandro Valenzuela (2021-07-07 10:23:12)

Any news on this?

Several upstream releases was released since this was reported, perhaps
fixing this issue.  Have any of you tested if this persist with newer
releases of IWD?

Kind regards,

 - Jonas