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
Two questions...
* Is there a risk of bricking a MacPro5,1 when setting up / configuring OpenCore?
* I have a dedicated BootCamp SSD (EFI Windows 10) - can that be easily integrated into OpenCore, or left alone and accessed by the Option key method (with macOS Catalina handled by OpenCore)
* Is there a risk of bricking a MacPro5,1 when setting up / configuring OpenCore?
* I have a dedicated BootCamp SSD (EFI Windows 10) - can that be easily integrated into OpenCore, or left alone and accessed by the Option key method (with macOS Catalina handled by OpenCore)
We’ve been able to spoof the 7,1 but can’t get 32GB’s working. Is there any changes to the OC config file you’ve done to get the 32GB’s working?This is what I run in my MacPro have a look here too #4,648
For the memory config I followed the Apple MacPro 2019 scheme -> https://support.apple.com/en-us/HT210103
8 DIMMs is the one we need, note still shows 12 slots. I have configured it on 12 slots scheme because I did not want to see the notification, which as no incidence whatsoever. You would put 1.5TB memory config that it would not change anything.
However when I tried the set the 8 slots according to the supported configuration I would get the error notification. So I reverted back to 12 slots configuration even though we only have 8 slots and the error's gone.
I guess that in the near future if IOIIIO works on the kext notification disabler, that we can properly set the memory config to reflect the true memory configuration of our MacPro5,1.
I preferred to set it that way so 1 less .kext in the driver folder.
I would love to have it configured this way which reflect the true config but then you get error and orange check, which I don't like
View attachment 1661007
View attachment 1660972
I want to update the plistlib generator with the changes you suggest. If you have time today PM me, so we can work on the release together.
I was using a 32 Gb Kingston Traveler 3.0 USB.
The Kingston USB showed up on the desktop in Mojave.
I did not know - it was not explained - that you should not use 3.0 USB's.
So I am replacing the 32 Gb Kingston Traveler 3.0 USB with a 16 Gb PNY 2.0 USB.
In the mean time, from the time I started on this project, the install routine changed from 6.2 to 6.3 and I was not finished with the 6.2 install when it changed to 6.3. So I am going back to the start and updating all of the stuff, such as the config.plist to the new version.
Thank you for your help.
The Kingston USB showed up on the desktop in Mojave.
I did not know - it was not explained - that you should not use 3.0 USB's.
So I am replacing the 32 Gb Kingston Traveler 3.0 USB with a 16 Gb PNY 2.0 USB.
In the mean time, from the time I started on this project, the install routine changed from 6.2 to 6.3 and I was not finished with the 6.2 install when it changed to 6.3. So I am going back to the start and updating all of the stuff, such as the config.plist to the new version.
Thank you for your help.
Let me know if that works for you.
@cdf, I cannot download Big Sur directly. I will try with gibMacOS, never used it before.
Edit, cannot download Big Sur with gibMacOS neither (works fine with Catalina), I get:
Probably Apple servers related.
Last edited:
This is what I run in my MacPro have a look here too #4,648
For the memory config I followed the Apple MacPro 2019 scheme -> https://support.apple.com/en-us/HT210103
8 DIMMs is the one we need, note still shows 12 slots. I have configured it on 12 slots scheme because I did not want to see the notification, which as no incidence whatsoever. You would put 1.5TB memory config that it would not change anything.
However when I tried the set the 8 slots according to the supported configuration I would get the error notification. So I reverted back to 12 slots configuration even though we only have 8 slots and the error's gone.
I guess that in the near future if IOIIIO works on the kext notification disabler, that we can properly set the memory config to reflect the true memory configuration of our MacPro5,1.
I preferred to set it that way so 1 less .kext in the driver folder.
I would love to have it configured this way which reflect the true config but then you get error and orange check, which I don't like
View attachment 1661007
View attachment 1660972
Everything working normally? Any errors? Did you run geekbench?
Code:
curl: (22) The requested URL returned error: 403 Forbidden
Could not replicate http://swcdn.apple.com/content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg: Command '[u'/usr/bin/curl', u'-fL', u'--create-dirs', u'-o', u'./content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg', 'http://swcdn.apple.com/content/downloads/50/49/001-79699-A_93OMDU5KFG/dkjnjkq9eax1n2wpf8rik5agns2z43ikqu/InstallAssistant.pkg']' returned non-zero exit status 22I have one question here. Would i be possible to have a 3rd party person do the Opencore configuration for my MacPro 5.1, and just send me the IMG file, and i flash it to a USB, and then i have opencore preconfigured?
That is if i provide all the info needed about my setup.
I am looking to run opencore because i wanna run Windows10 on NVME SSD full speed. And dualboot with bigsur and catalina.
That means i have to make the PCI SSD NVME look internal before install i guess.
Anyone know if possible to "hire" the expertise to do this? And just send me the .img?
(if i cant do it myself)
thanks
//GF
That is if i provide all the info needed about my setup.
I am looking to run opencore because i wanna run Windows10 on NVME SSD full speed. And dualboot with bigsur and catalina.
That means i have to make the PCI SSD NVME look internal before install i guess.
Anyone know if possible to "hire" the expertise to do this? And just send me the .img?
(if i cant do it myself)
thanks
//GF
Did not work.
Booted and gave two options: Mojave and Catalina. No option to install Windows.
It looks like the USB is still not bootable.
I need help.
Thanks.
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.
The image from Microsoft is: CCCOMA_X64FRE_EN-US_DV9
I used: rsync -r /Volumes/CCCOMA_X64FRE_EN-US_DV9/ /Volumes/Untitled
Untitled was the name of the USB on the Disk Utility program and on the Terminal.
I used the checking routine on the plist.config each time to make sure that everything was OK.
I used: rsync -r /Volumes/CCCOMA_X64FRE_EN-US_DV9/ /Volumes/Untitled
Untitled was the name of the USB on the Disk Utility program and on the Terminal.
I used the checking routine on the plist.config each time to make sure that everything was OK.
TL;DR
I had Big Sur up and running on my "5.1" but after some cross pollination of .kext editing instructions (and admittedly some complacency on my side) the MacPro now reboots to a crossed over circle with directions to Apple Support: meaning "MacOS found, but it's not compatible with your Mac Pro, please reinstall".
I'm guessing the issue is some removed keys from the config.plist that resides in EFI-->OC....
I have a copy of the "original" .plist that was working previously in my Home folder. Is there a clean way to get that file into the EFI-->OC folder via the Recovery option I get on boot, or is there a better way to "reset" Open Core?
I had Big Sur up and running on my "5.1" but after some cross pollination of .kext editing instructions (and admittedly some complacency on my side) the MacPro now reboots to a crossed over circle with directions to Apple Support: meaning "MacOS found, but it's not compatible with your Mac Pro, please reinstall".
I'm guessing the issue is some removed keys from the config.plist that resides in EFI-->OC....
I have a copy of the "original" .plist that was working previously in my Home folder. Is there a clean way to get that file into the EFI-->OC folder via the Recovery option I get on boot, or is there a better way to "reset" Open Core?
Another huge step in getting BCM4322 to work in Catalina and Big Sur
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!
@cdf It might be a good idea to add this into the wiki post after more testing is done
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
Last edited:
I have this upper question too.
OpenCore needs to block EFIwin not to write to bootrom.
Does it block this automatically or is there a setting for it?
Is it explained somewhere how OC works?
(I'm not savvy enough just to "read the source"...)
The setting for this is ProtectSecureBoot, which is already enabled in the config provided in the wiki. For further details, see the OpenCore manual.