mbp-fedora-kernel
mbp-fedora-kernel copied to clipboard
mikeeq
WiFi issues
Hello everyone,
As many of us have problems with running WiFi under Linux on new Macs, I want to make a list of already compatible models/wifi chips here and track all issues in one thread. Sorry for closing other ones.
Compatible models:
- Macbook Pro 15,2 i5
- BCM4364/3 (P-maui-X3_M-HRPN_V-u__m-7.5.txt)
How correct Broadcom fw load should look like in dmesg:
➜ dmesg | grep brcmfmac
[ 13.351387] usbcore: registered new interface driver brcmfmac
[ 13.351570] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[ 13.454664] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[ 14.545924] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[ 14.578324] 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
[ 14.658688] brcmfmac 0000:01:00.0 wlp1s0: renamed from wlan0
modprobe -r brcmfmac; modprobe brcmfmac rambase_addr=0x160000
#/etc/default/grub
GRUB_CMDLINE_LINUX="rhgb quiet efi=noruntime pcie_ports=compat modprobe.blacklist=thunderbolt systemd.unified_cgroup_hierarchy=0 brcmfmac.rambase_addr=0x160000"
Please post here all WiFi related issues.
Related issues in other projects:
- https://github.com/Dunedan/mbp-2016-linux/issues/71
- https://github.com/Dunedan/mbp-2016-linux/issues/112
Historic issues:
- https://github.com/mikeeq/mbp-fedora-kernel/issues/1
- https://github.com/mikeeq/mbp-fedora-kernel/issues/2
- https://github.com/mikeeq/mbp-fedora/issues/8
Imcompatible models:
- Macbook Pro 15,2 i5
- BCM4364/3 (P-maui-X2_M-HRPN_V-u__m-7.5.txt)
Wrong Broadcom fw load message:
[ 7.140063] usbcore: registered new interface driver brcmfmac
[ 7.140311] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[ 7.245941] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[ 9.624439] brcmfmac 0000:01:00.0: brcmf_pcie_download_fw_nvram: FW failed to initialize
@zhewang95 Your revision of WiFi chip probably uses different rambase address (https://github.com/Dunedan/mbp-2016-linux/issues/112#issuecomment-570008233) than my one. Are you able to recompile the kernel by yourself and check if removing that line fixes the issue for you?
https://github.com/mikeeq/mbp-fedora-kernel/blob/v5.4-f31/patches/wifi.patch#L21
Also you can check if it will be printed in dmesg after adding brcmfmac.debug=2097150 to kernel arguments, like here:
[ 4.170427] brcmfmac: brcmf_chip_get_raminfo RAM: base=0x160000 size=1310720 (0x140000) sr=0 (0x0)
Imcompatible models:
MacbookAir 8,2 i5 BCM4355/12 (P-hawaii-X0_M-YSBC_V-u__m-4.3.txt) Wrong Broadcom fw load message:
[ 7.140063] usbcore: registered new interface driver brcmfmac
[ 7.140311] brcmfmac 0000:02:00.0: enabling device (0000 -> 0002)
[ 7.245941] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4355-pcie for chip BCM4355/12
[ 7.778035] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2
[ 7.778037] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found
[ 9.624439] brcmfmac 0000:02:00.0: brcmf_pcie_download_fw_nvram: FW failed to initialize
A couple of notes... Here is what I named each file (MacOSX -> Fedora)
C-4355__s-C1/hawaii.trx -> /lib/firmware/brcm/brcmfmac4355-pcie.bin C-4355__s-C1/hawaii-X0.clmb -> /lib/firmware/brcm/brcmfmac4355-pcie.clm_blob C-4355__s-C1/P-hawaii-X0_M-YSBC_V-u__m-4.3.txt -> "/lib/firmware/brcm/brcmfmac4355-pcie.Apple Inc.-MacBookAir8,2.txt"
I have used the latest ISO listed here: https://github.com/mikeeq/mbp-fedora
Per these comments: https://github.com/Dunedan/mbp-2016-linux/issues/112#issuecomment-523730513 and https://github.com/Dunedan/mbp-2016-linux/issues/112#issuecomment-523483504 People have been successful in loading wifi on the MacBookAir8,2 and the BCM4355 driver. The particular kernel patch they are referencing was this: https://github.com/ppaulweber/linux-mba/commit/80f9698fad2b0e7e7de1bca1076085bb715f5968. Unfortunately I am not quite skilled enough to recompile the linux kernel myself and apply this patch to see if it works. But I looked through the patches posted on this repository and saw that the wifi kernel patches seem pretty similar.
The only conclusion I can reach is that I am doing something wrong but I cannot for the life of me figure out what I am doing wrong. Any help would be greatly appreciated!
@ktb92677 Please check brcmf_chip_get_raminfo size in dmesg after adding brcmfmac.debug=2097150 to kernel args (in grub).
@mikeeq Hey, I am having trouble getting the CRTL+SHIFT+F10 trick to work on my mac... any other way to edit kernel args?
EDIT: okay I got to the screen with CTRL_SHIFT+F10. I edited the kernel parameters but now I can't hit CTRL+X to save it!
FURTHER EDIT: Doesn't hitting F10 boot with the modifications made in the grub interface? If so I hit F10 after making the modification and when it booted there was no reference to brcmf_chip_get_raminfo inside of dmesg.... I assume F10 means "disregard the changes and boot"
LAST EDIT (I promise... read from here): Okay so you hit CTRL+SHIFT+F10 to get grub to take the kernel parameter. Got it. I can confirm via dmesg that the kernel parameter "brcmfmac.debug=2097150" was taken. However there is still no reference to "brcmf_chip_get_raminfo" inside of dmesg... what do I do from here?
@mikeeq Thanks a lot for this project :+1:
Incompatible model:
- Macbook Pro 15,2 i5
- BCM4364/3 (P-maui-X3_M-HRPN_V-m__m-7.7.txt)
dmesg | grep brcmfmac:
[ 5.500453] usbcore: registered new interface driver brcmfmac
[ 5.500664] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[ 5.607914] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[ 7.987068] brcmfmac 0000:01:00.0: brcmf_pcie_download_fw_nvram: FW failed to initialize
I also tried adding brcmfmac.debug=2097150 as kernel argument, but there was no change in the dmesg output...
BTW: modprobe -r brcmfmac; modprobe brcmfmac debug=2097150 should also work without the need to edit kernel arguments...
Thanks @geovie on the suggestion. I tried adding "debug=2097150" after modprobe like you suggested with no changes for me as well.
Same FW failed to initialize problem here with a 4364 on a 15,3. I have tried every possible baseaddr in that file: 0x160000, 0x180000, 0x198000, 0x200000. None of them works.
We need to find a solution to load brcmfmac module with debug parameter to find out baseaddr for most wifi chips revisions, so I can make several versions of kernel so everyone will be able to download kernel with his wifi.patch backed into the kernel.
@mikeeq Is modprobe -r brcmfmac; modprobe brcmfmac debug=2097150working for you?
I tried it on my current setup (when FW is loading correctly) and I don't have any additional logs in dmesg, i don't have time to test it further at the moment.
Same
FW failed to initializeproblem here with a 4364 on a 15,3. I have tried every possible baseaddr in that file: 0x160000, 0x180000, 0x198000, 0x200000. None of them works.
@Xinkai @ktb92677 accordingly to one of the first issues the firmware loading address 0x160000 should be fine for BRCM 4355 and 4364 chips.
At the beginning I had a similar problem as reported above:
[ 5.607914] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[ 7.987068] brcmfmac 0000:01:00.0: brcmf_pcie_download_fw_nvram: FW failed to initialize
I recommend to check the following locations in the patch of the brcmfmac driver if you have correctly patched those location as well: https://github.com/ppaulweber/linux-mba/blob/master/patch-linux-brcmfmac.diff Check especially the mapping at the end of the patch because the device id and hw id differs from the chip name!
- https://github.com/ppaulweber/linux-mba/blob/master/patch-linux-brcmfmac.diff#L86
- https://github.com/ppaulweber/linux-mba/blob/master/patch-linux-brcmfmac.diff#L94
Just to check, here is my firmware listing:
-rw-r--r-- 1 root root 655611 2019-08-17 19:53 /lib/firmware/brcm/brcmfmac4355-pcie.bin
-rw-r--r-- 1 root root 3039828 2019-08-17 21:22 /lib/firmware/brcm/brcmfmac4355-pcie.hexdump
-rw-r--r-- 1 root root 607 2019-08-17 19:53 /lib/firmware/brcm/brcmfmac4355-pcie.txcb
-rw-r--r-- 1 root root 5093 2019-08-21 16:18 '/lib/firmware/brcm/brcmfmac4355-pcie.Apple Inc.-MacBookAir8,1.txt'
-rw-r--r-- 1 root root 14241 2019-08-17 19:54 /lib/firmware/brcm/brcmfmac4355-pcie.clm_blob
And my dmesg output (I'm reloading the brcmfmac and iwd at every system start-up):
[ 43.124844] usbcore: deregistering interface driver brcmfmac
[ 43.346802] usbcore: registered new interface driver brcmfmac
[ 43.457090] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4355-pcie for chip BCM4355/12
[ 43.904065] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4355-pcie for chip BCM4355/12
[ 43.928037] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4355/12 wl0: Mar 28 2019 19:57:32 version 9.137.9.0.32.6.33 FWID 01-c5e1774f
@ppaulweber so here's the wifi patch that @mikeeq was using: https://github.com/mikeeq/mbp-fedora-kernel/blob/d8f5578d4fd9c9ee01c2a125dae30237aefcf391/patches/wifi.patch. I've taken a look at that and compared it to the wifi patch you posted (also carefully looking at those lines that you specified) and the patch seems pretty okay to me.
One difference I did immediately notice though was that on my system I only copied over the .txt, clm_blob, and bin. Are the hexdump and txcb files required as well for this to work?
@ktb92677 but accordingly to this patch from @mikeeq the BRCM_CC_4355_CHIP_ID redirects (switch case fall-through) to tcm_rambase value 0x180000 and not 0x160000.
https://github.com/mikeeq/mbp-fedora-kernel/blob/d8f5578d4fd9c9ee01c2a125dae30237aefcf391/patches/wifi.patch#L7-L24
One difference I did immediately notice though was that on my system I only copied over the .txt, clm_blob, and bin. Are the hexdump and txcb files required as well for this to work?
no, I forgot to strip them, sry about that
@ppaulweber Okay, with my very limited knowledge of this I am trying to recompile the kernel with that patch included... If you have any suggestions on how I might test to see if this is what is causing my problems short of rebuilding the kernel that would be appreciated.
@mikeeq any chance you could include this fix into your repository sometime soon? Also instructions on how to build this from home. (e.g. do I just run the build.sh script on a Fedora machine?)
okay great! @mikeeq I am currently running a "sh build.sh" over here. As soon as the new kernel-5.4.8-200.mbp.fc31.x86_64.rpm file pops out I'll go ahead and install it to my mba8,2 and I'll let you know what happens
@mikeeq okay well I just finally built it all and installed everything... for some reason my system doesn't get past the following screen:
BCMDHD_ExitBootService: ENTER dhd_os_wifi_platofrm_set_power: Setting wl_reg_on to 0 succeeded dhd_os_wifi_platform_set_power: Setting wl_reg_on to 1 succeeded
What have I done wrong..
EDIT: SO hitting return a bunch of times makes the thing boot at that screen. Anyways I got the same exact error after the kernel update (I verified that the new kernel is running via uname -a). The error is "FW failed to initialize". Not exactly sure what else to check here.. Did I also mention my mouse and keyboard don't work after the kernel upgrade?
Hello, i have tested this update with mbp 15,2 i5 maui-x3. have same issue as in previous kernel
brcmf_pcie_download_fw_nvram: FW failed to initialize
trying to set debug options but without any good results.
@ktkd the fix mentioned above addresses only the MBA8,2 issues from @ktb92677
@ktb92677 seems that UEFI has an incorrect firmware setting, just reboot to your system into Mac OS X, ignore the system error report dialog, and reboot back to your bootloader (grub etc.) and boot your Linux again.
@ppaulweber reboot to MacOSX? I over wrote MacOSX already though. Do I need to re-install it?
@ktb92677 I hope you didn't erased the EFI partition of your internal storage, otherwise you have no proper Apple firmware installed and the Apple UEFI uses this to setup etc. the device.
@ppaulweber I do not believe that I erased the EFI partition. I used the following repo to install linux on my Mac: https://github.com/mikeeq/mbp-fedora.
So what are you suggesting? Should I go through the Apple recovery process and re-install MacOSX right now and then try to install Fedora again ontop of it?
EDIT: And just as I was trying to use the new mbp-fedora image posted on https://github.com/mikeeq/mbp-fedora with the new kernel patch and it doesn't get past the spinning wheel screen on Fedora... https://github.com/mikeeq/mbp-fedora/issues/13
@ktb92677 but README doesn't mention that you should remove all partitions :D
You can always split your main macOS partition and then use left free space for other partitions ;)
And yes I recommend to install macOS, i.e. for EFI/iBridge updates.
Cheers
@mikeeq Okay cool, well I am re-installing MacOSX right now. Looks like the recovery portion of MacOSX stayed in tact through all this hacking.
Still not sure why the ISO wasn't booting though. Also how do you know that the ISO will boot after I re-install MacOSX?
I don't know if ISO will boot after you reinstall macOS (it shouldn't be related), I was testing it only on a VM. I will test it in a minute on my Macbook Pro 15,2 ;)
EDIT: It's booting correctly for me.
Imcompatible models:
- Macbook Pro 15,1 i7-8750H
- BCM4364/3 (P-kauai-X0_M-HRPN_V-m__m-7.7.txt)
MACOS 10.15
ioreg -l | grep C-4364
images" = {"C-4364__s-B2/P-kauai-X0_M-HRPN_V-m__m-7.7.txt"={"imagetype"="NVRAM","required"=Yes,"imagename"="C-4364__s-B2/P-kauai-X0_M-HRPN_V-m__m-7.7.txt"},"C-4364__s-B2/kauai-X0.txcb"={"imagetype"="TxCap","required"=No,"imagename"="C-4364__
s-B2/kauai-X0.txcb"},"C-4364__s-B2/kauai-X0.clmb"={"imagetype"="Regulatory","required"=Yes,"imagename"="C-4364__s-B2/kauai-X0.clmb"},"C-4364__s-B2/kauai.trx"={"imagetype"="Firmware","required"=Yes,"imagename"="C-4364__s-B2/kauai.trx"}}
Kernel Version
uname -a
Linux localhost.localdomain 5.4.8-200.mbp.fc31.x86_64 #1 SMP Wed Jan 8 11:08:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
No kernel driver in use.
lspci -vnn -d 14e4:
03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4364 802.11ac Wireless Network Adapter [14e4:4464] (rev 03)
Subsystem: Apple Inc. Device [106b:07bf]
Flags: fast devsel, IRQ 16
Memory at 81400000 (64-bit, non-prefetchable) [size=32K]
Memory at 81000000 (64-bit, non-prefetchable) [size=4M]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/16 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 <?>
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number a2-ed-98-ff-ff-34-f0-18
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [220] Resizable BAR <?>
Capabilities: [240] L1 PM Substates
Kernel modules: brcmfmac
brcmf_pcie_download_fw_nvram: Invalid shared RAM address 0x00081001
dmesg -T |grep brcmf
[Sat Jan 11 15:51:28 2020] Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.4.8-200.mbp.fc31.x86_64 root=UUID=eb984862-4b96-4949-aeef-d387c25d8a7f ro rhgb quiet efi=noruntime pcie_ports=compat modprobe.blacklist=thunderbolt brcmfmac.debug=2097150
[Sat Jan 11 15:51:28 2020] Kernel command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.4.8-200.mbp.fc31.x86_64 root=UUID=eb984862-4b96-4949-aeef-d387c25d8a7f ro rhgb quiet efi=noruntime pcie_ports=compat modprobe.blacklist=thunderbolt brcmfmac.debug=2097150
[Sat Jan 11 15:51:31 2020] usbcore: registered new interface driver brcmfmac
[Sat Jan 11 15:51:31 2020] brcmfmac 0000:03:00.0: enabling device (0000 -> 0002)
[Sat Jan 11 15:51:31 2020] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364-pcie for chip BCM4364/3
[Sat Jan 11 15:51:32 2020] brcmfmac 0000:03:00.0: brcmf_pcie_download_fw_nvram: Invalid shared RAM address 0x00081001
[Sat Jan 11 15:51:32 2020] Modules linked in: intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi ghash_clmulni_intel brcmfmac iTCO_wdt mei_hdcp iTCO_vendor_support hci_uart btqca applesmc intel_cstate input_polldev brcmutil snd_hda_intel ses enclosure btrtl snd_intel_dspcfg btbcm snd_hda_codec scsi_transport_sas btintel intel_uncore cfg80211 bluetooth intel_rapl_perf snd_hda_core mei_me snd_hwdep mmc_core pcspkr ecdh_generic snd_pcm idma64 i2c_i801 mei rfkill sbs ecc joydev apple_gmux sbshc acpi_tad intel_pch_thermal apple_bl ip_tables amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper drm nvme crc32c_intel nvme_core video rndis_host uas cdc_ether usb_storage usbnet mii pkcs8_key_parser fuse snd_seq snd_timer snd_seq_device snd soundcore bcm5974 hid_apple apple_ib_als(OE) apple_ib_tb(OE) apple_ibridge(OE) industrialio_triggered_buffer kfifo_buf industrialio
[Sat Jan 11 15:51:32 2020] brcmf_fweh_detach+0x15/0x60 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_detach+0x5d/0xe0 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_pcie_remove+0x58/0xf0 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_pcie_setup+0x38/0xb80 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_fw_request_done+0x65/0xe0 [brcmfmac]
[Sat Jan 11 15:51:32 2020] WARNING: CPU: 4 PID: 193 at drivers/net/wireless/broadcom/brcm80211/brcmfmac/fweh.c:309 brcmf_fweh_detach+0x5b/0x60 [brcmfmac]
[Sat Jan 11 15:51:32 2020] Modules linked in: intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi ghash_clmulni_intel brcmfmac iTCO_wdt mei_hdcp iTCO_vendor_support hci_uart btqca applesmc intel_cstate input_polldev brcmutil snd_hda_intel ses enclosure btrtl snd_intel_dspcfg btbcm snd_hda_codec scsi_transport_sas btintel intel_uncore cfg80211 bluetooth intel_rapl_perf snd_hda_core mei_me snd_hwdep mmc_core pcspkr ecdh_generic snd_pcm idma64 i2c_i801 mei rfkill sbs ecc joydev apple_gmux sbshc acpi_tad intel_pch_thermal apple_bl ip_tables amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper drm nvme crc32c_intel nvme_core video rndis_host uas cdc_ether usb_storage usbnet mii pkcs8_key_parser fuse snd_seq snd_timer snd_seq_device snd soundcore bcm5974 hid_apple apple_ib_als(OE) apple_ib_tb(OE) apple_ibridge(OE) industrialio_triggered_buffer kfifo_buf industrialio
[Sat Jan 11 15:51:32 2020] RIP: 0010:brcmf_fweh_detach+0x5b/0x60 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_detach+0x5d/0xe0 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_pcie_remove+0x58/0xf0 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_pcie_setup+0x38/0xb80 [brcmfmac]
[Sat Jan 11 15:51:32 2020] brcmf_fw_request_done+0x65/0xe0 [brcmfmac]
Any idea ?
@mikeeq okay so I did manage to get the latest fedora ISO you posted to boot. I installed it fully. It included the patch from @ppaulweber.
Unfortunately... I am STILL getting the "FW failed to initialize" error.
What else could I look for?
So I was looking at @jhohisel comment (who so far is the only person I can find with a MacBookAir8,2 who has gotten wifi to work) https://github.com/Dunedan/mbp-2016-linux/issues/112#issuecomment-522253748 and he made a mention of removing the txt file and seeing the difference in dmesg. Well I tried removing the .txt file and dmesg did indeed reflect that that file was missing! Don't know if that's good news at all.
I still have a feeling that the wifi patch that @mikeeq is using isn't quite up to date with @ppaulweber kernel patch.