Can't make it work on MacBook Pro 13,3

[cristianmiranda]

Hi, I found your repo and it gave me high hopes since I'm struggling with this bcm43602 issue for quite some time now. It's nice to know that I'm not alone after all 😄

I've tested your workaround on my MacBook Pro 13,3 but I get the same results as before after suspend. This is what I'm doing manually (I though it'd be good to test it like this before taking the time to create an automated service):

Before suspend:

nmcli radio wifi off
sleep 3
sudo modprobe -rf brcmfmac

On wake:

sudo modprobe brcmfmac
sleep 3
nmcli radio wifi on

After suspension I'm not able to connect to 5GHz netoworks anymore, and bluetooth behaves erratically (I guess this is because it's controlled by the same board).

Is modprobe.blacklist=brcmfmac mandatory if I'm testing this manually? Thanks again for the script!

---

UPDATE: I added blacklisted brcmfmac (and rebooted of course), but nothing changed 😢 Any ideas?

[GiovanniGrieco]

Hi Cristian, unfortunately I don't have this macbook anymore, so I cannot reproduce your issue. From what I remember, the kernel argument modprobe.blacklist=brcmfmac is required to blacklist the module at system boot, then the service will start it up automatically (if the service is enabled on systemd, of course).

My advice is to check the kernel ring buffer to see any problem related to Bluetooth / Wi-Fi @ 5GHz that could arise with/without this script.

I leave this issue open in case someone finds useful bits of information.