Sidebar Sidebar
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

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.
I was checking the Lilu 1.5.0 release and did not see any user space patching fixes.
 
hi- Opencore install as per the instructions went flawlessly for me, thanks for this. I have a Mac Pro 4,1/5,1, running Catalina and Windows 10 on separate SSDs. Opencore is installed to allow me to choose OSs, and also to give boot graphics on an installed RX580.

Is there any trick to getting a 3rd option, of Linux on a 3rd separate SSD for triple boot? I installed Ubuntu on a separate SSD, after I disconnected all other drives.
Ubuntu on its own (no other drives connected) boots straight away. But, if I power down, reattach my Catalina drive and restart, I dont get the OC loader; it just goes straight into Ubuntu. I've tried this with a couple of different versions of Ubuntu for testing.
If I then power down and disconnect Ubuntu, and restart, OC appears and I can boot Catalina.
So far, I've tried:
1) selecting the startup disk in preferences in Catalina, which didn't change anything
2)resetting the NVRAM. After 2 or 3 zaps, I could see a "NO NAME" additional entry in the boot picker, but this won't boot. It generates an error complaining that it has "failed to load MoklistRT: invalid parameter. Could not read \EFU\".
The fix for this seems to be to replace shimx64.efi with grubx64.efi in the Ubuntu EFI Partition. However, this hasn't worked for me and results in the system still complaining of failing to load MoklistRT on reboot.

Is triple boot possible?
 
sorry for the question. but is the new Big Sur update good to install?

edit: never mind. please delete my post. (why doesn't this forum have that feature?)
 
Hello everyone,
I installed OC 0.6.4 on my cMP 5.1 mit Mojave successfully. Yesterday, Software-Update offered a Safari- and Securityupdate for Mojave and i started the install, maybe a little premature. The mac restarted after downloading and ended with a black screen and the "not compatible"-sign (crossed crircle sign) white on black screen and rebooted. Then I got the Bootpickerscreen, with an macinstaller added to my mojave-installation. Booting with the installer leads to crossed-circle. Booting with mojave ist fine. So I assume, the Installer hangs somewhere, but I don't know, how to fix that.

For the future: Is it advised to install bigger updates for existing OS within OC? Or better deinstall OC and then starting the update?

Thanks in advance and thanks for the immense help and knowledge shared in this thread
Lightspeed
 
Lightspeed65 said:
Booting with the installer leads to crossed-circle. Booting with mojave ist fine. So I assume, the Installer hangs somewhere, but I don't know, how to fix that.
Click to expand...
Did you change the VMM flag? See Instructions on page 1 here for update OS info.
 
paalb said:
Did you change the VMM flag? See Instructions on page 1 here for update OS info.
Click to expand...
No, I didn't. Understood the instructions on page 1 that this is only important when upgrading to Catalina or higher. Wrong? Is it necessary too when upgrading within the existing Mojave-Installation? So setting the VMM flag in an alternative config.sys should help?
 
Lightspeed65 said:
No, I didn't. Understood the instructions on page 1 that this is only important when upgrading to Catalina or higher. Wrong? Is it necessary too when upgrading within the existing Mojave-Installation? So setting the VMM flag in an alternative config.sys should help?
Click to expand...
It will block/unblock any OS update as far as I know. I do it manually to get to know OpenCore. But of course you could have two alternative config.plist and write/copy over current. Remember to reboot.
 
paalb said:
It will block/unblock any OS update as far as I know. I do it manually to get to know OpenCore. But of course you could have two alternative config.plist and write/copy over current. Remember to reboot.
Click to expand...
On cMP5,1 Mojave and earlier OS's are supported and VMM flag is not needed. VMM is only needed for upgrading to/ updating Catalina.
 
startergo said:
On cMP5,1 Mojave and earlier OS's are supported and VMM flag is not needed. VMM is only needed for upgrading to/ updating Catalina.
Click to expand...
That's how I understood VMM flag. Now I regret not using a usb stick for OC. My idea now: deinstalling OC, reboot, upgrading Mojave to latest Sec-Update. Then reinstall OC. Anyone who denies or supports this?
 
Lightspeed65 said:
That's how I understood VMM flag. Now I regret not using a usb stick for OC. My idea now: deinstalling OC, reboot, upgrading Mojave to latest Sec-Update. Then reinstall OC. Anyone who denies or supports this?
Click to expand...
Of course you can do that, but in general, disable SMBIOS spoofing is enough to fix the problem.
 
  • Like
Reactions: Lightspeed65
Lightspeed65 said:
That's how I understood VMM flag. Now I regret not using a usb stick for OC. My idea now: deinstalling OC, reboot, upgrading Mojave to latest Sec-Update. Then reinstall OC. Anyone who denies or supports this?
Click to expand...
I stand corrected. Just tried it out on my mac. Security update 006 went without a hitch with OpenCore installed and VMM set to OFF on Mojave. And with no SMBIOS spoofing. Continuing with Security update 007 now.

Edit: Security update 007 went well.
 
Last edited:
Using OC 0.6.4. Is there a config variable to prevent NVRAM from being permanently changed? It keeps clearing my boot-args="-no_compat_check" which I use to boot Catalina and Big Sur bypassing OC, when needed.
I have looked but not seen a reference.
I have:
<key>AllowNvramReset</key>
<false/>
and
<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<dict>
<key>UIScale</key>
<data>AQ==</data>
<key>DefaultBackgroundColor</key>
<data>AAAAAA==</data>
</dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-lilubetaall -wegbeta agdpmod=pikera shikigva=80 mbasd=1 -wegtree -no_compat_check no32exec=0</string>
<key>csr-active-config</key>
<data>dwgAAA==</data>
<key>run-efi-updater</key>
<string>No</string>
</dict>
</dict>
<key>Delete</key>
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<array>
<string>UIScale</string>
<string>DefaultBackgroundColor</string>
</array>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
<string>csr-active-config</string>
</array>
</dict>
<key>LegacyEnable</key>
<false/>
<key>LegacyOverwrite</key>
<false/>
<key>LegacySchema</key>
<dict/>
<key>WriteFlash</key>
<false/>
</dict>
But that does not seem to prevent it from being cleared of the boot-arg.
 
KingKongUser said:
How did you update? I checked on mine and it said no update was available and 11.0.1 was the latest
Click to expand...
As per cdf's finding, I keep the following code in the config plist to get Big Sur support.
Code: 
<key>SMBIOS</key>
        <dict>
            <key>FirmwareFeatures</key>
            <data>A1QM4A==</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/w==</data>
        </dict>
 
I was able to update to Big Sur 11.1 with OC 0.6.4 with the correct VMM flag, but the Catalina Security Update did not show on System Update. The downloaded version refused to install. Has anybody had better luck?
 
haralds said:
Is there a config variable to prevent NVRAM from being permanently changed? It keeps clearing my boot-args="-no_compat_check" which I use to boot Catalina and Big Sur bypassing OC, when needed.
Click to expand...
Not currently possible to set things up such that you have one set of boot args when using OpenCore and another set for when not. It is either/or.

Will be looking at option for doing this when chain-loading via RefindPlus.
 
H2SO4 said:
Will give that look sometime tomorrow, work isn't giving me much playtime at the moment.
Thankyou for the pointer.
Click to expand...
Hullo again, so just so I' heading in the right direction I headed to 'MyTools' and ran FetchEFI. Now this places a folder called MyBootMgrOld in your /Users/Shared folder.
It appears to be a replica of a folder that's already in there - that's fine at this stage I want to go through what the deal is and be sure before anything gets messed with.

It appears then that I need to edit config.plist that resides in two locations, (/Users/Shared/MyBootMgr/EFI/OC and /Users/Shared/MyBootMgr/EFI/OC_ALT)?
 
cdf said:
Things are iffy at the moment with Big Sur. There are problems with DRM, Night Shift and USB. Even more concerning are the obviously unwanted firmware updates that cannot be blocked as before.

While BlacklistAppleUpdate helps, it cannot block all firmware updates:

github.com

run-efi-updater flag no longer works in macOS 11, Big Sur · Issue #1255 · acidanthera/bugtracker

With macOS Big Sur, it seems that even though the NVRAM variable is set macOS will still bless the firmware update during both install and update processes: 15:835 00:005 OCB: Perform boot EFI to d...
github.com github.com

The new RestrictEvents kext also helps:

github.com

GitHub - acidanthera/RestrictEvents

Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.
github.com github.com

But by blocking some processes, this kext prevents a clean install of Big Sur on the 5,1 Mac Pro.

Now installing Big Sur without trying to block firmware updates will likely still work, but this might happen:

forums.macrumors.com

OpenCore on the Mac Pro

Flash back your reconstructed dump. Most of the variables on your nvram -xp are about EFI payloads, for firmware upgrades.
forums.macrumors.com forums.macrumors.com

So until things get sorted out and more testing is done, post #1 cannot include steps for installing Big Sur.
Click to expand...

RestrictEvents is now viable for installs because it no longer blocks firmware updaters:

github.com

Do not restrict firmware updaters as they break macOS updates · acidanthera/RestrictEvents@5f5f4bf

Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.
github.com github.com
 
  • Like
Reactions: TECK, tsialex, h9826790 and 1 other person
Lightspeed65 said:
Hello everyone,
I installed OC 0.6.4 on my cMP 5.1 mit Mojave successfully. Yesterday, Software-Update offered a Safari- and Securityupdate for Mojave and i started the install, maybe a little premature. The mac restarted after downloading and ended with a black screen and the "not compatible"-sign (crossed crircle sign) white on black screen and rebooted. Then I got the Bootpickerscreen, with an macinstaller added to my mojave-installation. Booting with the installer leads to crossed-circle. Booting with mojave ist fine. So I assume, the Installer hangs somewhere, but I don't know, how to fix that.

For the future: Is it advised to install bigger updates for existing OS within OC? Or better deinstall OC and then starting the update?

Thanks in advance and thanks for the immense help and knowledge shared in this thread
Lightspeed
Click to expand...
you can also try removing oc, then try running the update then reinstall oc. i got mojave to upgrade to 10.14.6 no problems but i also have an efi flashed 480 in my mp 5.1
 
Last edited:
  • Like
Reactions: Lightspeed65
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back