Anyone else experienced this?
3 Likes
YES⌠Broken 
Iâve swapped back to Eth Cable for nowâŚ
EDIT / UPDATE - TEMP FIX
Connected Eth cable, temporarily downgrade wpa_supplicant by running âsudo dnf downgrade wpa_supplicantâ and then reboot MBP 16" M1⌠and FIXED. Thanks for solution, grateful!
1 Like
Same here:
dmesg:
4.368290] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4378b1-pcie for chip BCM4378/3
[ 4.368538] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP-m-6.11-X0.bin failed with error -2
[ 4.368558] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP-m-6.11.bin failed with error -2
[ 4.368576] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP-m.bin failed with error -2
[ 4.368591] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP.bin failed with error -2
[ 4.368606] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-X0.bin failed with error -2
[ 4.369697] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.sig failed with error -2
Its connecting fine to wireless networks without passwords. suggests its wpa supplicant?
me too.
Connect to the internet by plugging in an Ethernet cable, then temporarily downgrade wpa_supplicant by running âsudo dnf downgrade wpa_supplicantâ
9 Likes
Thanks. I have to order a usb c to ethernet adapter for my MacBook Pro.
No other way to downgrade without cable?
You can tether with your phone connected to usb-c.
2 Likes
Thanks! That worked 
The problem I had wasnât only wifi⌠after upgrading to 6.9.12-400.asahi.fc40 on 03 Aug 2024, upon reboot not only was WiFi failing to connect, ip addr command was failing and systemctl status was hanging.
Fortunately, there is a new kernel 6.9.12-401.asahi.fc40 that fixes the problems with ip addr just hanging. However, to install the new kernel, first I connected a USB C-to-ethernet dongle to my Macbook Air M2. I rebooted, and as soon as the U-boot countdown menu finished, I pressed ESC to show the GRUB boot menu. On the problematic kernel 6.9.12-400 menu line, I pressed e (edit), and at the end of the kernel line (3rd line, or the line just above initrd), I appended a 3 (for runlevel 3, which will boot into a terminal instead of Graphical Session). Finally, I pressed Ctrl-x to boot with the edited GRUB options.
For some reason, when I chose either KDE Plasma or my Sway session in sddm graphical session manager, I was unable to run dnf commands, but when booting into runlevel 3 / terminal session, Ethernet works fine and I was able to run dnf --refresh up -y to get the latest kernel.
Now when booting into a GUI session, dnf and ip a are working fine; I tried dnf downgrade wpa_supplicant but wifi is still not connecting. dmesg shows the following Broadcom Wifi chip errors:
[ +0.254908] ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_DELTA error (-52)
[ +0.024374] ieee80211 phy0: brcmf_p2p_set_firmware: failed to update device address ret -52
[ +0.000656] ieee80211 phy0: brcmf_p2p_create_p2pdev: set p2p_disc error
[ +0.000001] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp1s0f type 10 failed: err=-52
For the time being, I will have to use Ethernet it seemsâŚ
EDIT: after a hard poweroff and poweron (not just reboot), wifi is working again (after the dnf downgrade wpa_supplicant)
Downgrading wpasupplicant with dnf fixed it for me. I had to reboot and then restart NetworkManager, then it connected. Looking at logs, I see two unusual errors that only happened after I upgraded to Fedora 40, and did not happen after I downgraded wpasupplicant:
wpa_supplicant[1026]: wlp1s0f0: Trying to associate with SSID '<###>'
kernel: ieee80211 phy0: brcmf_cfg80211_escan_handler: scan not ready, bsscfgidx=0
Aug 04 17:11:53
kernel: ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (69)
Association is successful, but then, Authentication with <xx:xx:xx:xx:xx:xx> timed out
Background:
- MBP 13" M1 2020
- Installed Asahi in May
- Didnât use it much, almost stock
- Upgraded to Fedora 40 on the 4th of August using the GUI
- Attempted to connect to network on channels 13 & 36
- Attempted different network on channels 11 & 56
- Country: DE
Adding âbrcmfmac.feature_disable=0x82000â to the kernel command line either at the bootloader cmdline (press esc immediately after âBooting: nvme 0â) or via grubby.
See offloading [Wiki] for details.
1 Like
Is using grubby generally preferred to configuration files in modprobe.d?
Downgrading wpa_supplicant to version 2.10-10.fc40 fixed things for me (MBP M1 Pro).
Setting brcmfmac.feature_disable=0x82000 did not help, in fact it made things worse. Before adding the parameter, I was able to try a WPA3 network and then switch to an unsecured network, but after adding it, I wasnât even able to see available networks after the first failed connection attempt.
Adding âbrcmfmac.feature_disable=0x82000â to the kernel command line âŚ
Thanks, it worked for me.
This worked for me!
Glad to see Iâm not alone.
It seems that is now working with the last upgrade of the kernel and the wpa_supplicant:
wpa_supplicant-1:2.11-2.fc40.aarch64
3 Likes
Temporary downgrade of wpa_supplicant performed with âsudo dnf downgrade wpa_supplicantâ works for me!
It seems that is now working with the last upgrade of the kernel and the wpa_supplicant:
wpa_supplicant-1:2.11-2.fc40.aarch64
This doesnât work for me!
@andrea-p wpa_supplicant-1:2.11-2.fc40.aarch64 will only work if you do not have brcmfmac.feature_disable=0x82000 in your kernel parameters for kernel="/boot/vmlinuz-6.9.12-401.asahi.fc40.aarch64+16k" in GRUB2 menu.
You can find your GRUB settings with the following:
$ sudo grubby --default-kernel
/boot/vmlinuz-6.9.12-401.asahi.fc40.aarch64+16k
$ sudo grubby --info /boot/vmlinuz-6.9.12-401.asahi.fc40.aarch64+16k
index=0
kernel="/boot/vmlinuz-6.9.12-401.asahi.fc40.aarch64+16k"
args="ro rootflags=subvol=root rhgb quiet rootflags=subvol=root"
root="UUID=990d9cc0-4a80-45f1-ba19-72e86f580a57"
initrd="/boot/initramfs-6.9.12-401.asahi.fc40.aarch64+16k.img"
title="Fedora Linux Asahi Remix (6.9.12-401.asahi.fc40.aarch64+16k) 40 (KDE Plasma)"
id="f2fe3c44cc4640b8b7be44e46b5b7bfe-6.9.12-401.asahi.fc40.aarch64+16k"
In the args= line, if you added brcmfmac.feature_disable=0x82000, you can remove this setting with the following grubby command:
$ sudo grubby --remove-args="brcmfmac.feature_disable=0x82000" \
--update-kernel /boot/vmlinuz-6.9.12-401.asahi.fc40.aarch64+16k
The above assumes that you added the extra arg brcmfmac.*to the 6.9.12-401 kernel. Hope this helps!
Hello Peter,
I now realise that the tread is for Macs with arm processors. My Mac has Intel processor and obviously I donât use that kernel. With the last kernel and the -2 wpa version the wifi does not work even without the parameter brcmfmac.feature_disable=0x82000