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

[fzJNotIBOxgnbqejSeVCvJScL]

Sorry, now I'm really confused. I already followed Martin's pre-configured package.

Yes, you do need SurPlus and have to add the appropriate edits to the Config.plist. Honestly if it seems too much, the easist thing to do is use Martin's pre-configured package. Its just a matter of drag and drop and he has tutorial videos. You can find his link at the way beginning of the guide.

Which one's the latest? I see a lot of stuff from 2020, want to make sure I'm taking the most direct path to the latest version of Big Sur.

 

[14dcutaneo]

Is that not enough? The only option right now is Mac OS 12 Monterrey. Can't pull Big Sur from App store either.

If all you did is Martin Lo’s package you’re already set. It includes surplus and everything needed. You can see so on the bottom of his post where he says what’s included in the patcher. To download Big Sur, you can visit apples website to get the link to install the latest version of Big Sur

How to download and install macOS - Apple Support

Download and install current or previous versions of the Mac operating system on compatible Mac computers.

support.apple.com

 

[imrazor]

@cdf Well things got a bit weird. If I leave the older versions of WEG and Lilu in the /Libraries/Extensions folder on my Mojave volume, AND set the boot-args specified in the AMD HWAccel thread, acceleration works fine. But when I tried using those older versions in Monterey along with with specified boot-args, the video wouldn't initialize and left me with a black screen. So for now I'm stuck in Mojave.

Can you tell me what the difference between "-wegtree unfairgva=1" and "shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94" is? I've also noticed that in Mojave even though the name of the device is PXS1 (*not* GFX0), encoding acceleration still works. In which OS version did naming the GPU GFX0 become a requirement? If necessary I'll just install Catalina or Big Sur to sidestep the issue.

 

[anarchi]

Hi,

I’ve developed a routine with OC that works for me each time I update the OC package (usually each month). However, I would just like to check with all of you whether each of the things I do are still necessary for my setup (see the signature at the bottom).

I start with Martin Lo’s package (thank you for this), which has just about everything already set up (SurPlus, MonteRand, etc.). Then using cdf’s (and thank you) guide in post #1 I add the following:

1. Disable the special GOP renderer (I have an RX580).

2. Enable Night Shift (in Martin’s 0.7.5 package that simply means setting the variable to ‘true),

3. Add the device properties for the GPU (the actual path to my GPU is identical to the example one given in cdf’s guide).

4. Add the Windows 10 ExFatDxeLegacy driver and argument (I used this initially to set up a Windows drive and I still add it each time as I dual boot into the Windows nvme drive).

I intend to update to Monterey, but probably not make any other major changes to the setup in the near future (other than updating OC each month or so). This is my main home work computer and has been since August 2010 (with upgrades along the way) and I’d like to keep it going for a while longer.

Thanks for any help or comments.

 

[sfalatko]

That's fine. Big Sur booted with OpenCore was the test setup for the creating the CD. This is how the CD should appear in Finder:

View attachment 1903266

I wonder if there are differences to account for depending on what media is used. I've been testing this with a DVD+RW...

@cdf - success. Redid the process and I now have a working rescue CD. Thanks for your help.

 

[cdf]

Can you tell me what the difference between "-wegtree unfairgva=1" and "shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94" is?

The two sets of boot-args can't really be compared. Here's what each boot-arg is for:

• wegtree is for the renaming
• unfairgva is for DRM in Big Sur and later
• shikigva is for DRM in Catalina and earlier (we've found that the best value is 80)
• shiki-id is for changing the board ID only for select processes (this local change has proven insufficient, so we use a global change via OC)

I've also noticed that in Mojave even though the name of the device is PXS1 (*not* GFX0), encoding acceleration still works. In which OS version did naming the GPU GFX0 become a requirement? If necessary I'll just install Catalina or Big Sur to sidestep the issue.

But not decoding. The requirement predates Mojave.

 

[cdf]

4. Add the Windows 10 ExFatDxeLegacy driver and argument (I used this initially to set up a Windows drive and I still add it each time as I dual boot into the Windows nvme drive).

The ExFAT driver is actually only needed for booting the USB installer, so you can skip that part if you want.

 

[anarchi]

The ExFAT driver is actually only needed for booting the USB installer, so you can skip that part if you want.

Thanks, I suspected that might be the case, but I wasn't sure.

 

[cdf]

I followed your guide on page 1 to the "T", but the Windows installer USB will not show up on the OpenCore boot selector.... I've tried playing around with my config.plist, to see if that may change anything, but still no luck.

I've got Big Sur running on my machine successfully with OC, and I have my Windows SSD Formatted to ExFAT (GUID partition), with a Windows 10 USB Stick plugged in and ready (following your rsync -r ....) instructions.

In the rsync command, don't forget the "/" after the name of the Windows ISO. I've added a note in the guide.

 

[fzJNotIBOxgnbqejSeVCvJScL]

If all you did is Martin Lo’s package you’re already set. It includes surplus and everything needed. You can see so on the bottom of his post where he says what’s included in the patcher. To download Big Sur, you can visit apples website to get the link to install the latest version of Big Sur

How to download and install macOS - Apple Support

Download and install current or previous versions of the Mac operating system on compatible Mac computers.

support.apple.com

OK, got it upgraded to 11.6.1 Besides enabling Night Shift. What else do you recommend?

 

[imrazor]

@cdf I do seem to be making progress, but still do not have hardware encoding support. I found that under Monterey the GPU (as well as the SATA controller) has a different PCI identifier than under Mojave. When originally building the config.plist file under Mojave the device looked as you have described in the first post:

PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

but under Monterey looks more like this:

PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

(This is not exact because I do not have my cMP in front of me ATM.) Once the new PCI address was put in place, GFX0 was visible in ioreg. A similar thing happened with the SATA controller, and once the controller was correctly identified in config.plist, the SSD showed up as an 'internal' device.

I also found that I needed to set 'rebuild-device-tree' to 1 in config.plist AND put -wegtree in the boot-args to move past a black boot screen.

However none of this has enabled hardware assisted encoding. Even adding the 'pikera' parameter to boot-args did not enable acceleration. So it seems like I am closer to my destination, but still have not arrived yet.

 

[Charmandrigo]

@cdf I do seem to be making progress, but still do not have hardware encoding support. I found that under Monterey the GPU (as well as the SATA controller) has a different PCI identifier than under Mojave. When originally building the config.plist file under Mojave the device looked as you have described in the first post:

PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

but under Monterey looks more like this:

PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

(This is not exact because I do not have my cMP in front of me ATM.) Once the new PCI address was put in place, GFX0 was visible in ioreg. A similar thing happened with the SATA controller, and once the controller was correctly identified in config.plist, the SSD showed up as an 'internal' device.

I also found that I needed to set 'rebuild-device-tree' to 1 in config.plist AND put -wegtree in the boot-args to move past a black boot screen.

However none of this has enabled hardware assisted encoding. Even adding the 'pikera' parameter to boot-args did not enable acceleration. So it seems like I am closer to my destination, but still have not arrived yet.

I noticed this same thing when trying to do the process to make my nvme drive internal instead of external, I put that longer string anyways on the config.plist, the converting command showed it was OK but it didn't worked, my nvme boot drive still shows as external

 

[imrazor]

I noticed this same thing when trying to do the process to make my nvme drive internal instead of external, I put that longer string anyways on the config.plist, the converting command showed it was OK but it didn't worked, my nvme boot drive still shows as external

Putting the longer identifier *did* make my SATA SSD (on a PCIe controller card) appear as an internal drive. It also renamed my GPU to GFX0 as intended, but did not achieve my goal of enabling hardware acceleration. I'm not sure if that longer ID is part of the issue of acceleration not turning on, or if there's some other issue lurking in the weeds...

 

[MacToby]

I need help, I can't get any further.

So. I wanted to do a clean install of macOS Monterey on OpenCore 0.7.5. For this I deleted my SSD where I wanted to install Monterey and OpenCore. I then successfully installed OC on the SSD.

So far, so good. With the help of the guide, I then also made settings in the Config and made my cMP Monterey ready. However, when I then wanted to restart my Mac so that the new settings in the Config are applied, my Mac now no longer boots - no display output. Nothing. When I press the power button again, the Mac turns off immediately. I have checked the Config several times and have also checked it with the terminal.
The only change that differs from the normal guide here in my config is that I used the FeatureUnlock Kext instead of the NightShiftEnabler Kext. I have never had a bad experience with this one.

Does anyone have any ideas or know what I did wrong? I attach my config.

 

[Cfreak]

I am running Martin Lo's OC package. I am having some sudden crashes & understand my next step is to test my RAM.
System information says the RAM modules "Pass".
I tried to boot into my AHT USB for the 5,1; my USB was on the OC boot picker, but, selecting it didn't boot from it.
I tried to boot from a MemTest CD I made years ago, no luck.

This also raised a lot of questions in my mind about, even if it would boot, how would I get an image since I have an RX580 installed... would I need to re-install my original GPU?

Any suggestions on how to (easily) test my RAM modules on my soup'd up 5,1?

Thank you!

 

[MacNB2]

I am running Martin Lo's OC package. I am having some sudden crashes & understand my next step is to test my RAM.
System information says the RAM modules "Pass".
I tried to boot into my AHT USB for the 5,1; my USB was on the OC boot picker, but, selecting it didn't boot from it.
I tried to boot from a MemTest CD I made years ago, no luck.

This also raised a lot of questions in my mind about, even if it would boot, how would I get an image since I have an RX580 installed... would I need to re-install my original GPU?

Any suggestions on how to (easily) test my RAM modules on my soup'd up 5,1?

Thank you!

AHT needs Mac's original GPU.
If you have working Hight Sierra or Mojave, you can install the .diagnostic (hidden) folder into one of those OC's. Then with the original Mac GPU, power on while holding the d key on the keyboard. That will boot into the AHT be able to run the Ram tests, etc.
Google Apple .diagnostic folder as I am not sure I am allowed to post Apple software here.

Alternatively, if you do not have the original Mac flashed GPU, you can use Opencore to run Memtest86 from Opencore's boot picker. Installing it is a bit involved (but simple) but I guess I am are going off topic here. Could write a separate thread guide.

 

[cdf]

Putting the longer identifier *did* make my SATA SSD (on a PCIe controller card) appear as an internal drive. It also renamed my GPU to GFX0 as intended, but did not achieve my goal of enabling hardware acceleration. I'm not sure if that longer ID is part of the issue of acceleration not turning on, or if there's some other issue lurking in the weeds...

With the rename done, hardware acceleration should work provided that hybridization is applied.

So far, so good. With the help of the guide, I then also made settings in the Config and made my cMP Monterey ready. However, when I then wanted to restart my Mac so that the new settings in the Config are applied, my Mac now no longer boots - no display output. Nothing. When I press the power button again, the Mac turns off immediately. I have checked the Config several times and have also checked it with the terminal.

The problem is not your config. Your Mac suddenly shutting down on startup indicates that it's trying to start Monterey natively (or any version of macOS for which it's unsupported). In other words, OC has become unblessed (perhaps by an NVRAM reset). You can easily rebless it if you've prepared an OC rescue CD. Otherwise:

1. shut down and remove all disks except for one with Mojave
2. boot into Mojave, and use Startup Disk to bless the disk
3. shut down and reinsert your disk with Monterey
4. boot into Mojave, and bless OC with the First boot procedure

 

[MacToby]

With the rename done, hardware acceleration should work provided that hybridization is applied.


The problem is not your config. Your Mac suddenly shutting down on startup indicates that it's trying to start Monterey natively (or any version of macOS for which it's unsupported). In other words, OC has become unblessed (perhaps by an NVRAM reset). You can easily rebless it if you've prepared an OC rescue CD. Otherwise:

1. shut down and remove all disks except for one with Mojave
2. boot into Mojave, and use Startup Disk to bless the disk
3. shut down and reinsert your disk with Monterey
4. boot into Mojave, and bless OC with the First boot procedure

Sorry! I had forgotten to mention that. Monterey is not yet installed on the disk, only OC. But I can't boot anything with it.

EDIT:
I have configured the config file in Mojave. I can't boot Mojave and other macOS versions/installers when the OC disk is in the Mac.

 

[MacNB2]

I need help, I can't get any further.

So. I wanted to do a clean install of macOS Monterey on OpenCore 0.7.5. For this I deleted my SSD where I wanted to install Monterey and OpenCore. I then successfully installed OC on the SSD.

So far, so good. With the help of the guide, I then also made settings in the Config and made my cMP Monterey ready. However, when I then wanted to restart my Mac so that the new settings in the Config are applied, my Mac now no longer boots - no display output. Nothing. When I press the power button again, the Mac turns off immediately. I have checked the Config several times and have also checked it with the terminal.
The only change that differs from the normal guide here in my config is that I used the FeatureUnlock Kext instead of the NightShiftEnabler Kext. I have never had a bad experience with this one.

Does anyone have any ideas or know what I did wrong? I attach my config.

Your config.plist file is broken.
Whenever you upgrade OpenCore and/or change the config.plist file, always check that file with OpenCore's ocvalidate utility for that specific version of OpenCore before booting it.

This is what I get when I run ocvalidate (from OpenCore 0.7.5) against your config.plist:

MacNB@MacBook-Pro ocvalidate % ./ocvalidate /Users/MacNB/Downloads/mactoby-config.plist   
OCS: No schema for Base at 1 index, context <Patch>!
OCS: No schema for MaxKernel at 9 index, context <Patch>!
OCS: No schema for MinKernel at 10 index, context <Patch>!
OCS: No schema for Base at 1 index, context <Patch>!
OCS: No schema for MaxKernel at 9 index, context <Patch>!
OCS: No schema for MinKernel at 10 index, context <Patch>!
OCS: No schema for Base at 1 index, context <Patch>!
OCS: No schema for MaxKernel at 9 index, context <Patch>!
OCS: No schema for MinKernel at 10 index, context <Patch>!
OCS: No schema for Base at 1 index, context <Patch>!
OCS: No schema for MaxKernel at 9 index, context <Patch>!
OCS: No schema for MinKernel at 10 index, context <Patch>!
Serialisation returns 12 errors!

Booter->Patch[0]->Identifier contains illegal character!
Booter->Patch[1]->Identifier contains illegal character!
Booter->Patch[2]->Identifier contains illegal character!
Booter->Patch[3]->Identifier contains illegal character!
CheckBooter returns 4 errors!

Completed validating /Users/MacNB/Downloads/mactoby-config.plist in 2 ms. Found 16 issues requiring attention.
MacNB@MacBook-Pro ocvalidate %

Basically, you added the SurPlus & MonteRand patches in the wrong place (Booter>>Patch) instead of Kernel>>Patch.

 

[cdf]

Sorry! I had forgotten to mention that. Monterey is not yet installed on the disk, only OC. But I can't boot anything with it.

Interesting. I should have checked your config. I wasn't aware that a borked config could lead to your Mac suddenly shutting down like that. Usually that's a dead give-away for your Mac trying to boot something natively that it can't!

 

[MacNB2]

Interesting. I should have checked your config. I wasn't aware that a borked config could lead to your Mac suddenly shutting down like that. Usually that's a dead give-away for your Mac trying to boot something natively that it can't!

OpenCore halts the CPU when it finds errors in the config.plist and cannot/should not boot.
Only way out is to press the power button to switch off the system.

With the Debug version of OpenCore and with the right debug settings, you can view where it halts.

 

[cdf]

OpenCore halts the CPU when it finds errors in the config.plist and cannot/should not boot.
Only way out is to press the power button to switch off the system.

Right. But the Mac shutting down on its own (immediately, as described in the post) is a different thing. Anyways, thanks for actually looking at the config.

 

[MacToby]

So do you guys have any ideas why it's causing that?

 

[cdf]

So do you guys have any ideas why it's causing that?

Maybe there are concurrent issues. Is your Mac still shutting down with the config fixed?

 

[MacToby]

Maybe there are concurrent issues. Is your Mac still shutting down with the config fixed?

Sorry! I over read the fix. I’ll try it later and will report how it went!