MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[hwojtek]

For extra backup (and in case of some installer hickups) you may go like this:
1. Clone your current (nvme) disk to sata ssd with CCC or SuperDuper
2. Remove the sata ssd
3. Install OC to nvme → reboot → upgrade to Monterey

Since you don't have OC yet, I assume you have a supported (Apple boot picker) GPU. So in case a total failure of #3 just power down, insert the SATA clone, hold option on power on, select the SATA clone to boot from, clean the nvme, clone SATA to nvme, power down and repeat from #2.

 

[fatespawn]

For extra backup (and in case of some installer hickups) you may go like this:
1. Clone your current (nvme) disk to sata ssd with CCC or SuperDuper
2. Remove the sata ssd
3. Install OC to nvme → reboot → upgrade to Monterey

Since you don't have OC yet, I assume you have a supported (Apple boot picker) GPU. So in case a total failure of #3 just power down, insert the SATA clone, hold option on power on, select the SATA clone to boot from, clean the nvme, clone SATA to nvme, power down and repeat from #2.

I have a regular unflashed RX580 Sapphire Pulse. And I also have my GT120 in a desk drawer somewhere.

 

[fatespawn]

I have a regular unflashed RX580 Sapphire Pulse

 

[hwojtek]

OK, so no boot screens for 'ya. Get this GT120 and install as a second card, just in case you needed the Apple boot screen (I don't think you will need it, but better safe than sorry).

 

[6DecadesLater]

No.


What for? What are you trying to accomplish? Dual boot?
Install OC on your NVME ssd efi partition, reboot, upgrade to Monterey, job done.

When I first installed OC many versions ago (0.6.2?) I had some issues installing the OC efi on the NVME ssd. This was resolved by putting the OC efi on one of the spare SATA data disks while keeping the upgraded OS on the NVME. This may not be the issue now but if you have problems with the OC efi on the NVME try it on a SATA (not your Mojave backup). I installed recently OC efi/Monterey on a 4,1->5,1 on a SATA ssd. That works fine.

 

[hwojtek]

When I first installed OC many versions ago (0.6.2?) I had some issues installing the OC efi on the NVME ssd.

If the NVME ssd boots (as in: you have updated the Mac Pro 5,1 to 144.0.0 firmware) a supported OS, there is no way it won't boot OC.

 

[6DecadesLater]

If the NVME ssd boots (as in: you have updated the Mac Pro 5,1 to 144.0.0 firmware) a supported OS, there is no way it won't boot OC.

That install was on a 5,1. I can only tell you OC bootpicker was flaky until I moved the blessed efi off the NVME. As I said, it works fine on the 4,1->5,1 SATA ssd.

 

[Macschrauber]

quick question about this:



So I am actually using RefindPlus as a chain booter, the BOOTx64.efi actually first loads RefindPlus...and then later RefindPlus will load OC if I choose it to do so.

So I can't just copy and replace the entire BOOT dir over from OC download, I need to actually copy over just whatever new files are needed for this issue...which I do not understand exactly what is being done. Since RefindPlus is loading OC if and when I select it, should the .contentVisibility file continue to be located in the BOOT folder in order for OC to work correctly? Is it still going to solve the problem since I am not using the standard BOOTx64.efi boot loader?

or perhaps I don't even need this hidden file since I'm not using the OC version of BOOTx64?

Dont forget to set LauncherOption from Full to Disabled. Or OC sets itself as the first bootloader in the NVRAM and RP will not start again.

Whats good for OpenCore allone is bad for chainloading OC.

 

[fatespawn]

If the NVME ssd boots (as in: you have updated the Mac Pro 5,1 to 144.0.0 firmware) a supported OS, there is no way it won't boot OC.

Well... I dove in with fingers crossed.

I used Martin Lo's package to install OpenCore 0.8.7. It worked just fine on my NVME drive.

Ironically... I now know where I saw the comment about NVME drives - In Martin's instructions.

Quite a few users reported that can't boot OpenCore from NVMe, analysis shows that depends on hard drives config. It's hard to explain which exact scenario may hit this bug. So, please avoid to install this package on NVMe. You can install this package on ANY SATA drive with virtually no performance lost, not necessary your boot drive.

Activate AMD hardware acceleration

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.7.9] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...

forums.macrumors.com

Anyway, it's working since I now show a boot picker and System Preferences now offers Ventura as an upgrade option (I know cMP's can't do Ventura.) Maybe I got lucky installing it on NVME?

So, I'd like to move forward with installing Monterey. I noticed he did a Youtube video with some instructions for installing Monterey... unfortunately Subtitles aren't working for me. I can see in the video where he modifies a few lines in the config.plist file.

How do I edit the config.plist file?

If you want to install Catalina (and Monterey), please follow the steps in this video to turn ON the VMM flag, and turn OFF SMBIOS spoofing. This will allow you to install Catalina (and Monterey) after reboot. Once you finished the macOS installation, please turn OFF the VMM flag, and switch ON SMBIOS spoofing in other to restore all hardware functions with max performance.

Apparently I need to turn on the VMM flag and turn off SMBIOS spoofing during the install.

Suggestions?

 

[paalb]

How do I edit the config.plist file?

The instructions are in the first post here.

 

[fatespawn]

The instructions are in the first post here.

Thanks. read them and edited in notepad

 

[hwojtek]

Ironically... I now know where I saw the comment about NVME drives - In Martin's instructions.

Never had to use Martin's package. Installed all my OC for past couple of years on various NVME ssds on both "dumb" and PCIe switched controllers, never had any issue. As I said: if a ssd is bootable in an Apple computer (never mind the OS), it will boot OC.
The problem with pre-packaged OC setups is that while they are a labour of love and a lot of time of their creators and they do solve a lot of issues for certain configurations, they may have (again: never seen Martin's config, so it is not personal in any way) a lot of less-than-perfectly documented small changes which might create more problems and are not easily solved with #1 post and cryptic OC handbook as a guide.
That's why I prefer the vanilla OC approach (as outlined perfectly in post #1 of this thread) but suggest OCLP for those who want an automated solution.

How do I edit the config.plist file?

Mount the EFI partition of the ssd, edit /EFI/OC/config.plist with a decent editor (actually even Text Edit will do, but you may find a programmers' editor more handy), save, reboot.

Apparently I need to turn on the VMM flag and turn off SMBIOS spoofing during the install.

I don't remember changing my config.plist when I was installing Monterey and I don't have either of these, but your mileage may vary and VMM during installation will not hurt.
Make sure you do it exactly as post #1 says (you will find the values in "Complete your setup" → VMM flag).

 

[mateo14]

The second question was if the first question was a "yes". Thanks. I just wanted to make sure I didn't waste time troubleshooting an installation.

I'm planning to switch from Catalina to Big Sur on Mac Pro 2012 in March, and I starting to worry about my High Sierra installation. I read somewhere that booting to High Sierra can destroy Big Sur. I don't want to take out my hard drive with Big Sur when I want to use High Sierra.

My Mac Mini Server from 2010 with High Sierra isn't a powerful machine.

How can I solve this issue?

 

[fatespawn]

Never had to use Martin's package. Installed all my OC for past couple of years on various NVME ssds on both "dumb" and PCIe switched controllers, never had any issue. As I said: if a ssd is bootable in an Apple computer (never mind the OS), it will boot OC.

hwojtek,

Thanks for all the suggestions.

I did use the vanilla method on my wife's 4,1 a couple of months ago. It went well.

This time I used martin's package and went ahead with installing OC on the NVME. There were a couple of extra config.plist changes I had to make to install Monterey, but all went smoothly. It hung at "less than a minute remaining" for about an hour, but patience was rewarded and 12.6.2 is running fine.

One thing I read about installing OC on NVME.... a few people seem to think that the next time the nvram is reset, there may be an issue if OC is not installed on a SATA drive. Have you (or anyone) run across that issue?

I'm happy with both OC installations on both of my Mac Pro's.

 

[Dewdman42]

Dont forget to set LauncherOption from Full to Disabled. Or OC sets itself as the first bootloader in the NVRAM and RP will not start again.

Whats good for OpenCore allone is bad for chainloading OC.

Thanks. It seems to be working ok....and EFI is not showing up in the OC boot picker...so I guess its all working with the hidden file...and I don't have time to check right now, but presumably I have LauncherOption set appropriately since chain loading is working as before.

I did find that after recent MacOS update, my NVRAM was clogged with a lot of stuff and I had to do an NVRAM reset to get back to the OC boot picker menu remembering which volume to boot by default from system preferences.

Seems all good now though.

 

[Macschrauber]

My dumper has a line for reporting LauncherOption:Full - as it's sometimes tricky to get it away.

https://forums.macrumors.com/threads/healthy-nvram-normal-behaviour-on-4-1-5-1-machines.2333460/post-31857693

 

[dr.mav]

Hello everyone.

I'm facing the issue with the DP. I have next setup:

I have black screen during the boot. Doesn't matter if I'm using DP or HDMI. I'm using a Legacy Patcher to build the OC. Can someone help me to figure out what can be wrong?

 

[anarchi]

One thing I read about installing OC on NVME.... a few people seem to think that the next time the nvram is reset, there may be an issue if OC is not installed on a SATA drive. Have you (or anyone) run across that issue?

I've had OC set up on an NVME for quite a while. Resetting the nvram means that the next start OC is disabled and the computer tries to boot natively. I get around this by going straight from the nvram reset to booting from the OC rescue CD (see page 1) and then reblessing the OC on the NVME.

 

[sfalatko]

Hello everyone.

I'm facing the issue with the DP. I have next setup:

View attachment 2137728

I have black screen during the boot. Doesn't matter if I'm using DP or HDMI. I'm using a Legacy Patcher to build the OC. Can someone help me to figure out what can be wrong?

If you are using OCLP then I would suggest you try the OCLP Discord server - this forum is focused on manually installing OC using the method in the first post.

 

[fatespawn]

I've had OC set up on an NVME for quite a while. Resetting the nvram means that the next start OC is disabled and the computer tries to boot natively. I get around this by going straight from the nvram reset to booting from the OC rescue CD (see page 1) and then reblessing the OC on the NVME.

Thanks, makes sense.

I have two Mojave clones I made before upgrading my NVME to Monterey. After a nvram reset, I know I wont' have a boot picker (RX580 unflashed) but can I boot into recovery mode and set the startup disk to Mojave. Then boot normally into mojave, rebless the OC on the NVME and restart? One of my MacPro's is lacking a DVD drive so I'm looking for options.

 

[dr.mav]

If you are using OCLP then I would suggest you try the OCLP Discord server - this forum is focused on manually installing OC using the method in the first post.

Last night I tried Martin’s package and it’s end up with the same problem, but without boot partition lost.
I even looked into register and don’t see the problem with a port’s type identification.

 

[h9826790]

Last night I tried Martin’s package and it’s end up with the same problem, but without boot partition lost.
I even looked into register and don’t see the problem with a port’s type identification.

If you tried all the ports, none of them can display the UEFI GOP boot screen via OpenCore (but all ports works inside MacOS). Then the UEFI GOP may be broken. This often happen on used cards (the previous modded the card’s ROM).

You may backup the existing ROM, then go to TechPowerUp, download a factory ROM for your card and flash it. This usually can bring the UEFI GOP boot screen back.

 

[SpatialZebra]

Hi guys, I am new to macrumors, and trying to run Monterey on my 2008 Mac Pro 3,1.
I had great success with an EVGA GeForce GTX 680 2GB Mac Edition (gives boot screen and everything), and I was also able to get the OCLP boot picker and progress bar with an MSI Radeon RX 580 8GB.

You may think this is a stupid idea since I already have an RX 580, but I am trying to run an Asus Direct CU II Radeon HD 7970 3GB in my Mac Pro. Power requirements aside, since for now I am using an external cooler master PSU, I am unable to get the OCLP boot picker and progress bar at boot. macOS Monterey ends up loading and giving me an image, but it must be conflicting with some kets injected by OCLP, as I completely lose both audio and wifi support. Metal works perfectly and the card is recognized in macOS

So basically I would like to restore audio and wifi support + get OCLP boot loader to recognize the card and show boot picker.

EDIT: I enabled AMD GOP injection in developper settings of OCLP and that entirely fixed it. So for anyone experiencing the same issue just do that.

 

[PeterHolbrook]

@SpatialZebra: It's great if you've solved your issue. In any case, be aware that this is NOT an OCLP support forum. This thread is devoted to the MANUAL installation of OC, not OCLP, as taught in message #1. The majority of readers of this thread know next to nothing about OCLP.

 

[lewnworxx]

@cdf :

Does anyone have a copy of the 0.8.6 -> 0.8.7 Update Instructions?

Is there any way to get to the maintenance section from 0.8.6 > 0.8.7? I got buried in other stuff and didn't get a chance to do that update before @cdf posted the new 0.8.7 to 0.8.8 and would like to do that update rather than recreate from scratch. I tried the net wayback machine to see if I could get that, but the last trawl was in September.

There were significant changes from 0.8.6 to 0.8.7 with the bootkicker stuff etc, but it wasn't nearly as much work as a full on recreate from scratch. It'd save a mess of time.

Thanks. In the future I just need to make a re-occuring calendar entry to do a copy paste and stuff those in notes some place.