Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
The problem is, the kext does not exist, it was removed as described earlier:
Code:
% ls -lah /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext
ls: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext: No such file or directory

% ls -lah /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns                
total 0
drwxr-xr-x  4 root  wheel   128B  1 Jan  2020 .
drwxr-xr-x  7 root  wheel   224B  1 Jan  2020 ..
drwxr-xr-x  3 root  wheel    96B  1 Jan  2020 AirPortBrcmNIC.kext
drwxr-xr-x  3 root  wheel    96B  1 Jan  2020 IO80211NetBooter.kext

I'm wondering what is the fix? If Wifi works, it means the card is visible by system, since that card produces both Wifi and Bluetooth.
 
Last edited:
The problem is, the kext does not exist, it was removed as described earlier:
Code:
% ls -lah /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext
ls: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext: No such file or directory

% ls -lah /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns               
total 0
drwxr-xr-x  4 root  wheel   128B  1 Jan  2020 .
drwxr-xr-x  7 root  wheel   224B  1 Jan  2020 ..
drwxr-xr-x  3 root  wheel    96B  1 Jan  2020 AirPortBrcmNIC.kext
drwxr-xr-x  3 root  wheel    96B  1 Jan  2020 IO80211NetBooter.kext

I'm wondering what is the fix? If Wifi works, it means the card is visible by system, since that card produces both Wifi and Bluetooth.
If I remove the USB dongle my Bluetooth is not recognized, but in Catalina macOS 10.15.7 (19H2):
Code:
ls -lah /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/
total 0
drwxr-xr-x  7 root  wheel   224B Nov 11 16:10 .
drwxr-xr-x  7 root  wheel   224B Sep 21 17:05 ..
drwxr-xr-x  3 root  wheel    96B Nov 11 16:10 AirPortAtheros40.kext
drwxr-xr-x  3 root  wheel    96B Nov 11 16:10 AirPortBrcm4331.kext
drwxr-xr-x  3 root  wheel    96B Sep  1 01:07 AirPortBrcm4360.kext
drwxr-xr-x  3 root  wheel    96B Sep  1 01:21 AirPortBrcmNIC.kext
drwxr-xr-x  3 root  wheel    96B Sep  1 01:22 IO80211NetBooter.kext
It could be that the power is not delivered to my internal bluetooth.
 
  • Like
Reactions: TECK
If I remove the USB dongle my Bluetooth is not recognized, but in Catalina macOS 10.15.7 (19H2)
Same thing, does anyone else has the same problem? I’m wondering if other Big Sur users have the 4360 kext missing but the Bluetooth functional. Otherwise, could OC add the missing kext so the issue is solved?

I created a separate thread, to avoid highjacking
 
Last edited:
I upgraded the stock card to BCM943602CDPAX in order to get Bluetooth 4.2 and continuity, it was fine in Mojave/Catalina, now invisible in Big Sur. Here are my details in Mojave:

View attachment 1666641

@startergo @h9826790 @cdf if you have any suggestions where it might be the issue, please let me know.
You may try BrcmPatchRAM3.kext + BrcmFirmwareData.kext + BrcmBluetoothInjector.kext
 
I upgraded the stock card to BCM943602CDPAX in order to get Bluetooth 4.2 and continuity, it was fine in Mojave/Catalina, now invisible in Big Sur. Here are my details in Mojave:

View attachment 1666641

@startergo @h9826790 @cdf if you have any suggestions where it might be the issue, please let me know.
Here are some BigSur screen shots for comparison if it helps. WiFi/BT4.0 card and on the WiFi page the card is using the AirportDriverBrcmNIC.kext which is a plugin of the IO80211Family.kext which resides in SLE for BigSur. There is no AirPortBrcm4360.kext but the card does not need to use it. In fact if I remember correctly the card was using BrcmNIC.kext in Catalina as well. This may be a reason why it seems to work for me.

Screenshot 2020-11-14 at 21.35.18.png
Screenshot 2020-11-14 at 21.36.01.png
 
  • Like
Reactions: TECK
I have dual E5520 2.26 Ghz xeons in my 4,1->5,1 Mac Pro, I want to install Opencore to get Boot picker but not Catalina or Big Sur, still on 10.14.3 because sound stuttering.

Will I have problems if I install Opencore?
 
I am contemplating whether to go Open Core with my MP5,1 and would appreciate some clarifications from experts here...

My machine specs: 2010 MP5,1, 12 core@ 3.46ghz, 128gb ram, airport extreme BT upgrade from osxwifi.com, RX580 video, several other important PCI cards.

In no particular order of importance:

  1. Am i understanding correctly that Open Core will need to be installed on my primary boot drive so that it will be found first when powering on the machine? If I choose to boot from a different drive using System Preferences, will that then bypass OpenCore or does the Mac always look on that primary drive during initial boot up, etc. I am just trying to decide how I can safely "experiment" with trying Open Core in a way that I could easily go back to my standard Apple Mojave setup that I have now.

  2. I do not plan to experiment with any spoofing at all, I want vanilla completely. Is it reasonably safe to assume, after reading through all the scary posts on this thread, that my firmware is not at risk of being brick-walled if I use the config file that is in the first post of this thread, and/or follow the hardware acceleration instructions?
  3. Eventually I would like to also have a dual boot to Windows 10. Actually even initially I'd like to be able to have Mojave, Catalina and BigSug all bootable, and eventually Windows10 too. I read some things here that in some cases Windows has been bricking MP5,1's when installed this way. Is that still that case that its a possibility? what do I need to make sure to do to avoid that?

  4. The Open Core config settings as indicated in the first post of this thread...those same settings will apply to all versions of OSX and Windows, or is it necessary to have a different OpenCore setup for each intended OS version I plan to run?

  5. My MP5,1 has updated airport extreme with BT4.2 from osxwifi.com. Anyone know if this is working 100% in this OpenCore vanilla setup?

  6. Do I understand correctly that with this OpenCore setup, each time I want to get updates from Apple I will need to go into the OpenCore configuration, enable the VM stuff long enough to run the update, and then turn it back off after. each time? Has anyone made an app or AppleScript thing to make that more convenient and reliable?

  7. Any issues with memory? I have 128gb in this box. What I have should work completely with this OpenCore setup?

  8. Any issues with dual CPU's or special things i need to do?

  9. After all of that, is there anything at all that doesn't work 100%? I understand that I will need to do some KEXT hacking as explained in post#1 to get complete hardware acceleration. After doing that, is there anything that doesn't work 100% with Catalina? Handoff, continuity, etc.? Anything?

  10. Too early to ask about Big Sur probably, but anyway, same question as above.

  11. What about Windows 10 in this configuration. Does anything not work?
 
Blutooth is working, WiFi is working.
I believe that the main issue for having "continuity" is the enable "Continuity Support" in: /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist, which as fas as I know, is not possible since the system files are read-only.
Any suggestions?
 
  • Like
Reactions: Dewdman42
Blutooth is working, WiFi is working.
I believe that the main issue for having "continuity" is the enable "Continuity Support" in: /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist, which as fas as I know, is not possible since the system files are read-only.
Any suggestions?
No extra patch is required. As long as we have the iMac Pro board ID injected via OpenCore, all those functions should be enabled automatically in Big Sur.

I tested that in a 100% clean installed Big Sur.
 
  • Like
Reactions: TECK
No extra patch is required. As long as we have the iMac Pro board ID injected via OpenCore, all those functions should be enabled automatically in Big Sur.

I tested that in a 100% clean installed Big Sur.
Would you be kind enough to share your config.plist file which works
 
Would you be kind enough to share your config.plist file which works
Here
 
Did you downloaded the image from Microsoft? Do not use any other images except the downloaded one, as it worked for me as described into @cdf instructions. Post the exact commands, including the exact image name you got, the naming listed by @cdf is used as example, you need to use your own outputs.

You should use the plistlib generator to prepare your package, it will make sure all deps are set the right way for Windows.
What is the plistlib generator? What are the deps?

The USB is now bootable. I used it to boot a windows computer.

However, it will still not boot the SSD on the Mac Pro set up for Windows.
 
Same thing, does anyone else has the same problem? I’m wondering if other Big Sur users have the 4360 kext missing but the Bluetooth functional. Otherwise, could OC add the missing kext so the issue is solved?

I created a separate thread, to avoid highjacking
I had this problem. I restarted and did an NVRAM reset. When it rebooted, it worked fine.
 
Questions for anyone that knows the answers. I'm trying to understand exactly how the boot loader and NVRAM works so that I can try out OpenCore and I want to understand how I would rollback to non-OpenCore if it doesn't work out for me, and to understand exactly what i need to avoid to avoid bricking my NVRAM.


OpenCore is stored only on the EFI partition of your disk, nothing in the BootROM/logicboard/whatever.

Thank you for clarifying, sorry for simple questions...

Clover is the boot loader that can't be used and damage the Mac Pro NVRAM. OpenCore was designed to be used on Macs from the ground up and don't cause adverse effects.

Right so I interpret that to mean that Clover can and will write into the NVRAM, which is the BootROM (which is not on any disk), and that is how NVRAM can get corrupted that people have described on this forum thread. But you believe OpenCore should not make those kinds of mistakes in corrupting the NVRAM, so should be ok to try it out without too much concern about corrupting the NVRAM.

Does that include when I boot to MSWIndows? I read some post on one of these threads that there was some situations with MS Windows where it might have overwritten past some buffer limits in NVRAM or something and possibly corrupted it, even using OpenCore EFI windows install?

NVRAM is part of the BootROM, you can only backup it dumping the full firmware image from the SPI flash memory, using flashrom/ROMTools.

Thank you.

So a few more questions to help me figure out the best workflow to attempt this stuff... I need to understand exactly what the proper procedure would be to rollback out of OpenCore if I decide its not working for me.

So I think you're saying that if NVRAM gets corrupted because of a stupid boot loader (Clover), then might have to get some tricky software or maybe even hardware-level tools to restore the NVRAM back to a state where the machine can even be booted at all...ie...bricked. I'm not prepared to deal with that, and I definitely won't use Clover, so hopefully NVRAM wouldn't get corrupted any other way. If that is unlikely scenario with OpenCore, then I won't worry about it right now.

However, one other question.. Let's say I want to try OpenCore... Assume my system has 3 or 4 SSD's installed, any of which could be used for booting if I choose. Ok, so I have normal non-OpenCore Mojave installed on my primary drive. let's say I setup a completely separate drive with the OpenCore boot loader and install Catalina. Fine so far. And in those steps the NVRAM is changed (I think) to indicate that the mac should boot with OpenCore Bootloader which is on only one of the drives in the computer.

Alright, so I do that, I get it all working and play with it a while, but then for whatever the reason I want to pull it out and go back to my old non-OpenCore Mojave boot. I presume in that case I could not just pull out the OpenCore drive and boot up the machine, I would need to also configure the NVRAM to now look back to the original drive with non-OpenCore Mojave on it...then I'd be good to go back and could remove the OpenCore drive entirely and boot up with original Mojave, right?

what would happen if I pulled out the open core drive without reconfiguring NVRAM (if I have that right) to look back for the original Mojave non-OpenCore bootable volume? That's not really completely a brick because I could put the OpenCore drive back in, fix it and move on, but I just want to understand the ramifications of rollback before I try anything.

I think ultimately I will want the drive in drive bay #1 to have the open core boot loader and Mojave, and then I will have various other drives or partitions with Catalina, BigSur and Windows10, maybe even linux later. Sounds like rolling it back would simply be remove the bootloader and reconfigure the NVRAM and reboot, then it would be back to normal MacOS approach. yea?

And also, is there any reason to believe that my Mojave boot volume would act funny while booting under OpenCore...would it require hardware acceleration hacks and what not like is required for Catalina and Big Sur?
 
Last edited:
I had this problem. I restarted and did an NVRAM reset. When it rebooted, it worked fine.
Are you using the standard first post package created by @cdf? Did you applied post #4,399 to your config? Do you mind sharing your config file so I see what you have inside?
 
No extra patch is required. As long as we have the iMac Pro board ID injected via OpenCore, all those functions should be enabled automatically in Big Sur.

I tested that in a 100% clean installed Big Sur.

hmm. I am not interested in spoofing the id of my MP5,1. So you're saying those things only work if I spoof it as an iMac?
 
BCM943602CDP in my 5,1 natively/unpatched on Big Sur fine, no different to Catalina.

Including handoff/watch unlock, continuity etc

That's the same airport extreme card I have. Are you having to spoof your MP5,1 as an iMac in order for it to work?
 
My card is a BCM943602CDPAX, I hope the card is not the culprit, so it must be a config setting. Are you using the @h9826790 package or the standard @cdf package?
Mine is based on CDF's package with pretty much all of the additions in the guide. Including the iMac Pro board ID fixes in the thread for native Big Sur installation.
 
Last edited:
Did you copied the OcBinaryData legacy USB driver? It is probably not showing because the driver is missing. Not sure what else could be the issue.
The Samsung EVO 860 1 Tb drive named Drive 1 (the primary hard drive is a Hitachi 2 Tb HDD which has Mojave), has an EFI partition. The EFI partition has an EFI folder.

In the EFI folder are two folders: Boot and OC.

In OC is a drivers folder. In the drivers folder is ExFatDxeLegacy.efi.

Should the OpenCore.efi be in the drivers folder in OC or should it be (as it now is) in with several folders and the updated config.plist.

The folders are: ACPI (appears to be an empty folder), Bootstrap, Drivers, Kexts, Resources, Tools.

The Kexts folder has: AppleMCReporterDisabler.kext, the Lilu.kext (and the dict for it comes first as it is supposed to and the AppleMCReporterDisabler.kext comes second to last, since it didn't seem to like being last (I got a not OK when it was that way)), and the WhateverGreen.kext is also in that folder.

To the best of my knowledge the config.plist has been correctly modified with 0.6.3.

I would be glad to send you a copy of the config.plist since a second set of eyes would be worthwhile to make sure that I have not made a mistake.

By the way, the lastest AppleMCEReporterDisabler does not seem to provide a .kext, just an info.plist. So I used the previous AppleMCEReporterDisabler.kext that I had downloaded.
 
Mine is based on CDF's package with pretty much all of the additions in the guide.

Thanks a lot. that is definitely what I want to try first. So no spoofing for you to iMac and everything works. Great. Big Sur too? even better.

Is there any chance you have also installed Windows10 using this boot loader config? Just curious if there is anything I need to watch out for if I setup a multi-boot scenario...I want Mojave, Catalina, BigSur and Windows10....
 
Are you using the standard first post package created by @cdf? Did you applied post #4,399 to your config? Do you mind sharing your config file so I see what you have inside?
Yes to all of the questions. Used 0.6.3 package by @h9826790. I am away from the computer now. Will post the plist soonest.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.