Those messages are normal and not the cause of your problem. It tries multiple firmware filenames until one succeeds. You’ll have to look elsewhere to debug this. If ip link shows your wifi device, chances are the problem lies somewhere in userspace packages, not the kernel/firmware.
Are you sure rfkill isn’t just enabled? sudo rfkill to check.
root@macbookair-m2:~# rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
1 wlan phy0 unblocked unblocked
I think it might be related to selinux. I disabled selinux to get docker going (I was in a rush).
I was about to post back about those errors, I worked with Broadcom crap for a while and remember how misleading their “errors” were.
I’m tethered over usb now so I can fetch more. The interface is present - once you get past those errors this looks ok.
root@macbookair-m2:~# dmesg | grep brcmfmac
[ 3.223904] usbcore: registered new interface driver brcmfmac
[ 3.223937] brcmfmac 0000:01:00.0: Adding to iommu group 8
[ 3.223954] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[ 3.238722] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4387c2-pcie for chip BCM4387/7
[ 3.238900] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,hokkaido-TPHN-u-4.7-X0.bin failed with error -2
[ 3.238919] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,hokkaido-TPHN-u-4.7.bin failed with error -2
[ 3.239075] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,hokkaido-TPHN-u.bin failed with error -2
[ 3.239091] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,hokkaido-TPHN.bin failed with error -2
[ 3.239105] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,hokkaido-X0.bin failed with error -2
[ 3.240229] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.sig failed with error -2
[ 4.191254] brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
[ 4.194157] brcmfmac: brcmf_c_process_cal_blob: Calibration blob provided by platform, loading
[ 4.211535] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4387/7 wl0: May 27 2023 01:34:59 version 20.96.31.0.8.7.148 FWID 01-126f2c4c
[ 4.307992] brcmfmac 0000:01:00.0 wlp1s0f0: renamed from wlan0
From here it gets ugly. This is looping.
[ 19.449850] ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_DELTA error (-52)
[ 20.052196] ieee80211 phy0: brcmf_p2p_set_firmware: failed to update device address ret -52
[ 20.052895] ieee80211 phy0: brcmf_p2p_create_p2pdev: set p2p_disc error
[ 20.052899] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp1s0f type 10 failed: err=-52
[ 44.639355] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 44.639377] ieee80211 phy0: brcmf_cfg80211_disconnect: error (-5)
[ 46.687322] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 46.687346] ieee80211 phy0: brcmf_cfg80211_reg_notifier: Country code iovar returned err = -5
[ 48.735322] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 48.735342] ieee80211 phy0: brcmf_cfg80211_get_channel: chanspec failed (-5)
[ 50.783301] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 50.783323] ieee80211 phy0: brcmf_cfg80211_get_tx_power: error (-5)
[ 52.831263] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 52.831288] ieee80211 phy0: _brcmf_set_multicast_list: Setting mcast_list failed, -5
[ 54.879248] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 54.879271] ieee80211 phy0: _brcmf_set_multicast_list: Setting allmulti failed, -5
[ 56.927263] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 56.927293] ieee80211 phy0: brcmf_cfg80211_get_channel: chanspec failed (-5)
[ 58.975246] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 58.975269] ieee80211 phy0: brcmf_c_set_cur_etheraddr: Setting cur_etheraddr failed, -5
[ 61.023234] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 63.071226] ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[ 63.071261] ieee80211 phy0: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, err=-5
I don’t need you to spend a ton of time on one person’s problems. I can usb tether until I get home and use wired once I get home. If there’s anything obvious to try please call it out otherwise please work on stuff that helps more than one person. Thanks for all your hard work, Asahi is the best.
The first few errors (up to the p2p stuff) are normal (unsupported features). It’s at second 44 where things break. It looks like the wifi firmware just crashes.
The question now is what happened to cause it. If it’s something we can reproduce somehow then we can try to investigate. But it’s very difficult to debug this “remotely”.
Just as a sanity check, can you post the output of sha1sum /lib/firmware/vendor/brcm/*hokkaido*?
You can also put options brcmfmac debug=0xffffff in /etc/modprobe.d/brcmfmac-debug.conf and then run sudo dracut -f --kver=$(uname -r) and reboot. That will enable a lot of debug output, so expect things to slow down. But if you can reproduce the crashing wifi with that on, it might give as a clue as to what happened.
Unfortunately it’s connecting to my home wifi just fine. The struggles were with a hotel wifi (no password, captive portal) so it might be something specific to this. I’ll make sure I come back here if I see the issues again. Thanks.
Not sure if it’s the same issue, but on Friday, right after upgrading the kernel 6.9.5, I tried to connect to the SFO free wifi and it left my laptop unable to even browse for other networks. I downgraded to 6.8.9 and it got in the same state. If I ignored it, after a reboot I was able to use my phone’s hotspot.
I also set options brcmfmac debug=0xffffff and ran dracut -f --kver=$(uname -r), but I’m not seeing any verbose output in the journal even now, after upgrading to 6.9.9 (which I assume ran dracut as well).
The OP had a problem with a hotel wifi network, but was able to use a home network, so the problem was network dependent. If you are having problems with hotel or free public wifi please review the “Getting the login screen on hotel WiFi” posted previously.
If you have the problem with a home network, please start a new topic. For starters, show us the output from ip link and also check that rfkill isn’t enabled.
Thanks, sorry I missed your reply until now. I wasn’t getting an ip address like the person in that article was - my issue was more layer 2, some kind of wifi protocol combination that wasn’t working perhaps?