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
With the new updated design I finished yesterday, there are no more end-user errors. By default, we have a list of all settings used in OpenCore. Then the end-user create a small compact file, containing only the settings he/she wants to update. This results in a very compact config file, easy to follow and understand. You can set for example what kexts you use and the installer will configure everything for you:
Code:
kexts = [
{
'project': 'Lilu',
'repo': 'acidanthera',
'version': '1.4.9'
},
{
'project': 'NightShiftEnabler',
'repo': 'cdf',
'version': '1.0.0'
},
{
'project': 'WhateverGreen',
'repo': 'acidanthera',
'version': '1.4.4'
}
]@startergo @cdf @h9826790 Please take a look at Big Sur setup.py to see what I mean. BTW, please let me know if there are any wrong keys that I forgot to remove or have wrong values.
For someone who does not have any experience with OC, all you need to do is pass a setup.py file, knowing there will be no errors whatsoever when he/she implements/updates the OC package into his/her Mac.I will definitely need @cdf's precious help to revise the wiki documentation.
Last edited:
With the new updated design I finished yesterday, there are no more end-user errors. By default, we have a list of all settings used in OpenCore. Then the end-user create a small compact file, containing only the settings he/she wants to update. This results in a very compact config file, easy to follow and understand. You can set for example what kexts you use and the installer will configure everything for you:
Code:kexts = [ { 'project': 'Lilu', 'repo': 'acidanthera', 'version': '1.4.9' }, { 'project': 'NightShiftEnabler', 'repo': 'cdf', 'version': '1.0.0' }, { 'project': 'WhateverGreen', 'repo': 'acidanthera', 'version': '1.4.4' } ]
@startergo @cdf @h9826790 Please take a look at Big Sur setup.py to see what I mean. BTW, please let me know if there are any wrong keys that I forgot to remove or have wrong values.setup.pyfile, knowing there will be no errors whatsoever when he/she implements/updates the OC package into his/her Mac.
I will definitely need @cdf's precious help to revise the wiki documentation.
Code:
python /Users/g5/Downloads/opencore-master/setup.py
* OpenCore 0.6.3
- downloading component... OK
- building files structure... OK
- cleaning directory... OK
- installing AppleMCEReporterDisabler...
Traceback (most recent call last):
File "/Users/g5/Downloads/opencore-master/setup.py", line 73, in <module>
build.write_tree(kexts)
File "/Users/g5/Downloads/opencore-master/opencore/build.py", line 412, in write_tree
self.install_opencore(self.version)
File "/Users/g5/Downloads/opencore-master/opencore/build.py", line 342, in install_opencore
self.copy_tree(source, destination)
File "/Users/g5/Downloads/opencore-master/opencore/build.py", line 266, in copy_tree
for item in listdir(source):
OSError: [Errno 2] No such file or directory: 'files/AppleMCEReporterDisabler.kext'You need to run this inside the repo, it will not work otherwise. Also, you need to do a git pull, downloading the package will not work because is linked to OcBinaryData repo.
Code:
floren@zeus ~]$ cd github
[floren@zeus github]$ rm -rf opencore
[floren@zeus github]$ git clone https://github.com/axivo/opencore.git
Cloning into 'opencore'...
remote: Enumerating objects: 77, done.
remote: Counting objects: 100% (77/77), done.
remote: Compressing objects: 100% (52/52), done.
remote: Total 183 (delta 42), reused 35 (delta 20), pack-reused 106
Receiving objects: 100% (183/183), 531.20 KiB | 2.03 MiB/s, done.
Resolving deltas: 100% (94/94), done.
[floren@zeus github]$ cd opencore
[floren@zeus opencore]$ vi setup.py
[floren@zeus opencore]$
[floren@zeus opencore]$ python setup.py
* OpenCore 0.6.3
- downloading component... OK
- building files structure... OK
- cleaning directory... OK
- installing AppleMCEReporterDisabler... OK
- copying OcBinaryData files...Submodule 'files/OcBinaryData' (https://github.com/acidanthera/OcBinaryData.git) registered for path 'files/OcBinaryData'
Cloning into '/Users/floren/github/opencore/files/OcBinaryData'...
OK
* Lilu 1.4.9
- downloading component... OK
- building files structure... OK
* NightShiftEnabler 1.0.0
- downloading component... OK
- building files structure... OK
* WhateverGreen 1.4.4
- downloading component... OK
- building files structure... OK
* OpenCore Configuration
- generating config.plist... OK
* Miscellaneous
- fixing file permissions... OK
[floren@zeus opencore]$The beauty of this setup is that all you have to do is pass the setup.py file and the user will have your identical setup.
Are the NVRAM settings unchanged, for Big Sur?
Code:
<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<dict>
<key>DefaultBackgroundColor</key>
<data>
AAAAAA==
</data>
<key>UIScale</key>
<data>
AQ==
</data>
</dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>run-efi-updater</key>
<string>No</string>
</dict>
</dict>
<key>Delete</key>
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<array>
<string>DefaultBackgroundColor</string>
<string>UIScale</string>
</array>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>run-efi-updater</string>
</array>
</dict>
<key>LegacyEnable</key>
<false/>
<key>LegacyOverwrite</key>
<false/>
<key>LegacySchema</key>
<dict>
</dict>
<key>WriteFlash</key>
<false/>
</dict>
Last edited:
Hello
Firstly, thank you to everyone that has contributed to the community, I have a 4,1>5,1 cMP kitted out very nicely now & running opencore 6.3 & Catalina. thank you for making this as easy as possible.
I followed the instructions above and now i have my old Mojave installation on a spare SSD im no longer using. I am wanting to erase it and use it for WIP media storage. Is it safe for me to erase the mojave OS now that I have catalina & opencore installed on a new SSD or are there OC links that might be broken if i erase it?
cheers!
Firstly, thank you to everyone that has contributed to the community, I have a 4,1>5,1 cMP kitted out very nicely now & running opencore 6.3 & Catalina. thank you for making this as easy as possible.
I followed the instructions above and now i have my old Mojave installation on a spare SSD im no longer using. I am wanting to erase it and use it for WIP media storage. Is it safe for me to erase the mojave OS now that I have catalina & opencore installed on a new SSD or are there OC links that might be broken if i erase it?
cheers!
can you please show where exactly in the example config file to put this?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
Stock IO80211Family kext from Mojave already works in Catalina, but there were kernel panics when entering recovery because of collission with Catalina's version. Big Sur did not even boot as Big Sur's version is already preloaded in prelinked kernel and trying to inject Mojave version results in kernel panic too.
Patched IO80211Family kext above does not collide with system versions so original Broadcom card now works in Catalina's recovery and even in Big Sur without any system partition modifications!
XML:<dict> <key>Comment</key> <string></string> <key>PlistPath</key> <string>Contents/Info.plist</string> <key>Enabled</key> <true/> <key>MaxKernel</key> <string>20.99.99</string> <key>MinKernel</key> <string>19.0.0</string> <key>ExecutablePath</key> <string>Contents/MacOS/IO80211Mojave</string> <key>Arch</key> <string>Any</string> <key>BundlePath</key> <string>IO80211Mojave.kext</string> </dict> <dict> <key>Comment</key> <string></string> <key>PlistPath</key> <string>Contents/Info.plist</string> <key>Enabled</key> <true/> <key>MaxKernel</key> <string>20.99.99</string> <key>MinKernel</key> <string>19.0.0</string> <key>ExecutablePath</key> <string>Contents/MacOS/AirPortBrcm4331</string> <key>Arch</key> <string>Any</string> <key>BundlePath</key> <string>IO80211Mojave.kext/Contents/PlugIns/AirPortBrcm4331.kext</string> </dict>
@cdf It might be a good idea to add this into the wiki post after more testing is done
The Mo
Your Mojave OS is your safety net in case the OC partition fails for some reason. Remove it and keep it safe. Use another disk for whatever. Without OpenCore Catalina will not boot.
ok, so does that mean I can delete my old mojave user files and then CCC the Mojave install to a smaller ssd & leave that permanantly mounted in the old superdrive cage? (i have the owc 2.5" adapter) or will changing the location of the mojave install break opencore links?
Cheers
You don't need to have Mojave installed. Just have a Mojave USB installer on hand and you'll be able to rectify whatever issues you may have with OC later on.
You should put them under the:
<key>Kernel</key>
<dict>
<key>Add</key>
<array>
#### put them here
</array>
Same place with Lilu and WEG
Thanks. sadly didn't work. wifi doesn't get enabled. I'm in Big Sur.
Another question, is Lilu and Whatevergreen not working with Big Sur? I get crash reports upon reboot.
also nightshift enable doesn't seem to work.
To get it working correctly for Big Sur.
Disable VMM, Disable Lilu, NightshiftEnabler, and WhateverGreen. Not needed. Also you can remove the DeviceProperties data. Then change the SMBIOS to MacPro7,1.
Only problem is an annoying error message upon boot that memory is incorrectly blah blah, just close it and after that no problems so far. Works much better then previous OS and settings.
Disable VMM, Disable Lilu, NightshiftEnabler, and WhateverGreen. Not needed. Also you can remove the DeviceProperties data. Then change the SMBIOS to MacPro7,1.
Only problem is an annoying error message upon boot that memory is incorrectly blah blah, just close it and after that no problems so far. Works much better then previous OS and settings.
Attachments
Maybe setting Windows as startup using Startup Disk preferences panel doesn't work with OpenCore? Are you trying to boot Windows using EFI or legacy BIOS mode? If legacy BIOS mode, then you need to use Startup Manager (if you have Mac compatible boot screen) or RefindPlus.
I have been using Big Sur right from the day after it was released. After different failures to Install in my cMPro 4,1 to 5,1 I could do a fresh install from Mojave only when I put in my config.plst:
VMM on
UpdateSMBIOS changed to "false"
With that, I am running my Big Sur with no issues at all (Including Bluetooth-wifi). System works very smooth. No hardware acceleration no NightShift, of course. No error messages so far.
With UpdateSMBIOS changed to "true" -which is default-, I get a failure in the middle of the starting process and restarting again in a loop.
Last edited:
What wifi card do you have? The original or updated wifi ac one?
And you have hardware acceleration enabled this way?
Also, having VMM enabled slows the system down. There is no need for VMM with the proper SMBIOS settings, hardware acceleration works. I wouldn't use this system without UpdateSMBIOS to "true", on any OS other than Mojave.
Attachments
Last edited:
Into SMBIOS config.plist, have you put string "SystemProductName = MacPro7,1"?
Yes, or you can you OpenCore Configurator and add it manually per the picture above.
I also add MacPro7,1 to Board Version but it doesn't seem to make any difference. Its SystemProductName NightShift is looking for. Also most important as well is the Firmware Mask and Firmware Features. Without these set you will run into issues installing Big Sur and say that your system requires a firmware update or Mac OS journaled blah blah.
<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string></string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string></string>
<key>BoardAssetTag</key>
<string></string>
<key>BoardLocationInChassis</key>
<string></string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-27AD2F918AE68F61</string>
<key>BoardSerialNumber</key>
<string></string>
<key>BoardType</key>
<integer>0</integer>
<key>BoardVersion</key>
<string>MacPro7,1</string>
<key>ChassisAssetTag</key>
<string></string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string></string>
<key>ChassisType</key>
<integer>0</integer>
<key>ChassisVersion</key>
<string></string>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
<key>PlatformFeature</key>
<integer>0</integer>
<key>ProcessorType</key>
<integer>0</integer>
<key>SmcVersion</key>
<data></data>
<key>SystemFamily</key>
<string></string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string>MacPro7,1</string>
<key>SystemSKUNumber</key>
<string></string>
<key>SystemSerialNumber</key>
<string></string>
<key>SystemUUID</key>
<string></string>
<key>SystemVersion</key>
<string></string>
</dict>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>