Good to know, I was reading the 0.6.4 changelog. I’m going to try it again today with a fresh download from Store instead of gibMacOS.
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Wonderful, it's working as expected !Another huge step in getting BCM4322 to work in Catalina and Big Sur
GitHub - khronokernel/IO80211-Patches: Repo for patched IO80211Family Kexts
Repo for patched IO80211Family Kexts. Contribute to khronokernel/IO80211-Patches development by creating an account on GitHub.github.com
I see.
Despite OpenCore is written for both PC and Mac, but the behaviour can be slightly different.
Since our Mac can run OSX / macOS by default. Sometimes, we can do a bit more than OpenCore provided to PC.
In fact, then the 1st Big Sur beta came out, I can easily install and run Big Sur just by spoofing the SMBIOS. Regardless Lilu and WhateverGreen not really functioning at that moment, but Big Sur still working as expected on my cMP. But a normal PC user can't quite do that, at least not that simple.
Mac Mini late 2012 is compatible with Catalina. Use IO80211Catalina instead of Mojave's version. Bluetooth is natively supported.
As BCM4331 is natively supported in Big Sur, you do not even need that Catalina kernel extension, just simply replace card device-id with BA430000.
Last edited:
Many thanks for the heads-up. Correct me if I'm wrong, but my interpretation is that your CoreBrightness solution involves creating a patched installer that is used to install Big Sur itself. Along with most OpenCore users that own a Mac Pro 5,1, I am interested in a post-install patch, or a patch updater, if you will, similar to that of dosdude1's Catalina Patcher. As far as I've been able to detect, an unmodified Big Sur installer works flawlessly on a Mac Pro 5,1 (posing as an iMac Pro 1,1), provided it is booted via Open Core. If such a post-install Night Shift patcher doesn't exist, can you easily create one?
Making a stock BigSur createinstallmedia , then applying my "BaseSystem legacy USB fix" to that USB Installer, even if you already have a BigSur installation, it behaves as a kind of post install patcher.
Only issue is that after you patched a kext or framework, the OTA update aren't more detected, but simply reinstalling BigSur (keeping Data) will remove any patches.
Moreover if you have an apple GPU that can detect the "apple startup manager", you can boot this "BaseSystem fix Installer" directly with alt-option key, or from any opencore setup or refind or any bootloader that supports HFS+ .
I was able to perform a clean install. However, to my big surprise, AirPortBrcm4360 class was removed from Big Sur, so now I'm Bluetooth less. Do you have by any chance the new AirportBrcmFixup configuration I need to apply into OC to fix this? I have the Broadcom BCM943602CDPAX installed in my cMP.
Well, you can manually replace system CoreBrightness with the patched one using this guide
https://medium.com/@andv/making-wif...d-macs-with-failed-with-66-error-36c98e3f7965
@jackluke Better temporary solution ( Before Lilu userspace patching is resolved ) would be to patch that custom CoreBrightness so it will not collide with system versions just like this
GitHub - khronokernel/IO80211-Patches: Repo for patched IO80211Family Kexts
Repo for patched IO80211Family Kexts. Contribute to khronokernel/IO80211-Patches development by creating an account on GitHub.
Through pikeralpha method I patched the CoreBrightness binary exec, but to use patched frameworks you need also to Disable Library Validation or AMFI disabled, that I already included in my BaseSystem fix.
I haven't tested if a framework exec can be used as kext exec through OpenCore, while for Extensions this works I guess for Frameworks won't work, framework loading from BigSur kernel is enough different from kernel extension.
My patched CoreBrightness doesn't collide because is installed only on BigSur (without opencore) and it's simply copied in this path /PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness
(I used this for 11.0.1 https://github.com/jacklukem/BigSurfixes/blob/master/BigSur 19H2 patched CoreBrightness.zip)
on BigSur all the frameworks exec are embedded here: /System/Library/dyld/dyld_shared_cache_x86_64
so simply removing that CoreBrightness patched file the stock BigSur CoreBrightness is used that is embedded unmodified on that dyld shared cache.
Last edited:
Sorry for big nonsense I wrote, NighShift patching kext and CoreBrightness framework merged in my mind for a second. No CoreBrightness can't be injected using OpenCore as it is a not kernel extension
I don't exclude that opencore developers could be able to inject frameworks exec as kext, but currently for patching BigSur need to handle : sealed snapshot booting, BootKernelExtensions.kc (KernelCollections) and frameworks exec embedded only in dyld shared cache (they are not in their /Name.framework/Versions/A/ folder as for Catalina and previous macOS).
Found your comment in different thread, these steps should still work? Even easier by adding AMFI as a OC boot-arg and disabling SIP using it too.
Last edited:
I have the same issue in Big Sur.
Unfortunately there does not seem to be a way to write the system files anymore. Any helps would be greatly appreciated.
Last edited:
Not sure what is going on here. My cMP 5.1 upgraded to BigSur with no issues (apart from no DRM streaming which is a known problem for now). BCM94360CD working fine with full continuity, watch unlock etc. Here is the system preferences:
AirPort Extreme (0x14E4, 0x111)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1669)
I am using OC6.3 with efi on a NVME and just completed an OTA upgrade from Catalina (also on the NVME) and installed over Catalina. Luckily, update was seamless for me.
Yes, but I upgraded my wifi/bluetooth to 802.11/BT 4.0 hardware... Can be done for about $50 if you have soldering skills to make a custom power cable. or spend about $200 for a premade kit. Then it works natively for me on any of the last 3 OSs.
To skip AMFI as OC boot-arg, from BigSur terminal this ASentientBot method :
Code:
sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool truethen from another macOS environment (not directly from BigSur because it's locked with snapshot and frameworks are constantly in use), simply adding that CoreBrightness patched through making a new snapshot, then Night Shift on Display prefpane should work also on MacPro.
Yes it worked for me with stock HDD with Mojave and a NVME for opencore/catalina. Be sure ur pci adapter and NVME are fully compatible, there another thread about hardware.
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:
@startergo @h9826790 @cdf if you have any suggestions where it might be the issue, please let me know.
I guess you need patched Wifi driver for AirPortBrcmNIC or AirPortBrcm4360 , that is the stock IO80211Family.kext from Mojave or Catalina , but to install them on BigSur you need to make a new snapshot.
Maybe try this: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29228715
even if I guess that OpenCore can't inject kext already present on KernelCollections.
When I purchased the card, I was not aware of this OC thread and in Catalina I was told to run:
Code:
sudo mount -uw /
sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" \
/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist
sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F221BEC8\0\0\0\0\0\0\0\0/" \
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360
cd /System/Library/Extensions
sudo touch .
Last edited:
I had a very similar issue with my upgraded bluetooth from iMac17,1. It stopped working at some point and I installed this USB dongle to fix it.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Everything still works fine in Mojave and Windows, only in Big Sur is not recognized:
Wifi works properly.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
A stock BigSur install has a locked System Volume so can't use "sudo mount -uw /", but this is surely doable if you disable snapshot booting or delete snapshot or make a new snapshot with those modified files (this implies a kmutil kernelcollection rebuild), all these will break the OTA update feature.