Skip to contentSkip to conversation

brcmfmac: BCM43602 in Touch Bar MacBook Pros not working properly

DISCUSSION Daniel Roschka 2 participants 3 messages Jul 25, 2017 – Jul 26, 2017

lore
Share & tools
lore
#0 lore raw

Hi,

All Apple MacBook Pro models with Touch Bar contain a BCM43602 Wi-Fi chip. This chip isn't working properly. While it is properly detected by brcmfmac and even shows wifi networks nearby, connections only succeed when being very, very close to the AP. Also 5Ghz networks aren't visible at all. Further details are written down in an issue opened half a year ago, which hasn't seen much activity since: https://bugzilla.kernel.org/show_bug.cgi?id=193121

As previous MacBook Pros had similar problems (see
https://bugzilla.kernel.org/show_bug.cgi?id=100201 and
https://bugzilla.kernel.org/show_bug.cgi?id=103201), which got resolved by a firmware update, I suspect that could be the solution for the current problems as well.

Is there anybody here who could take a look at that? That would be highly appreciated.

Regards,
Daniel

#1 lore raw
Quoted 9 lines · Daniel Roschka

Hi,

All Apple MacBook Pro models with Touch Bar contain a BCM43602 Wi-Fi chip. This chip isn't working properly. While it is properly detected by brcmfmac and even shows wifi networks nearby, connections only succeed when being very, very close to the AP. Also 5Ghz networks aren't visible at all. Further details are written down in an issue opened half a year ago, which hasn't seen much activity since: https://bugzilla.kernel.org/show_bug.cgi?id=193121

Quoted 8 lines

As previous MacBook Pros had similar problems (see
https://bugzilla.kernel.org/show_bug.cgi?id=100201 and
https://bugzilla.kernel.org/show_bug.cgi?id=103201), which got resolved by a firmware update, I suspect that could be the solution for the current problems as well.

Is there anybody here who could take a look at that? That would be highly appreciated.

Seems like your email(s) end up in my spam folder. I tend to chuck away that folder without a glance, but today I did have a peek. Sorry for missing previous attempts.

In bugzilla I see you are running the latest firmware, ie. 7.35.177.61. The problem back then was that firmware was lacking functionality to read the srom on the device. We fixed that with the firmware update. So not sure what might be the issue this time. Also checked the debug output file, but it seems to be missing details during probe. So if possible please do:

$ insmod brcmfmac debug=0xd416

Regards,
Arend

#2 lore raw
Quoted 3 lines · On Wednesday, 26. July 2017, 13:49:51 CEST you wrote:

So if possible please do:

$ insmod brcmfmac debug=0xd416

You'll find the log attached to the bugzilla report:
https://bugzilla.kernel.org/show_bug.cgi?id=193121#c8

If there's anything else I can provide to get to the ground of this issue, I'm happy to do so.

Daniel