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

[cdf]

When's "OC: The GUI" due?

I'm not sure what you're referring to. Like a configurator app? I think OCLP has something like that by now.

General FA question: if you don't have OC EFI on any connected hard drives and you boot with a usb with OC on it - will the cMP will boot using that OC?

Not necessarily. Without a Mac EFI graphics card, the only way to boot something on demand is with a CD by holding C (see Maintenance for how to create an OpenCore rescue CD).

 

[superparati]

Have you been around Sidecar with BigSur?
I have an error -501 and tried different kind of things

SideCar do not work with my Mac Pro BigSur and OpenCore 0.7.6 (Vega RX 56).

Turn off and on my iCloud account on both machine
Turn off and on BT on both machine
tried to usb cable
reboot both machines.


Any suggestion?

I've a MBP 16 with Catalina and no use using a cable.

 

[prefuse07]

You only need to "update" the NVRAM firmware features (see Complete your setup). This is for macOS updates and installations. But for that to work, you also need to set SecureBootModel to Default (see macOS); you have it set to Disabled.

Now if you absolutely wanted to "update" the SMBIOS firmware features, you could (but there's no known reason to), and the value you have there is correct. I've explained this in another post, commenting on the discrepancy between the NVRAM and SMBIOS values.


To my knowledge, ocvalidate won't check for boot-arg or device property correctness.


For the setup described in post #1, boot-args aren't needed at all. In my opinion, boot-args should be reserved for temporary testing (or for exceptional cases where device properties can't be set).


Yes. Before you can mix and match from various approaches, you really need to be sure of the settings. Otherwise, it's best to stick to one approach.

Good luck!

Ok, I went through my config and page 1 instructions again, starting from the top and going through -- line by line in textedit, removed all the boot args I had before (except -no_compat_check, since I do plan on booting into Mojave from time to time).

Added my GPU in DeviceProperties and added some of the boot args
unfairvga = 1
shikigva = 80

SecureBootModel = Default

UpdateNvram = true


First I was getting a red screen when trying to launch amazon prime video -- research says this is a DRM issue, so I went back into config and added all of the previous boot-args I had in NVRAM to DeviceProperties -- and now get an error when trying to launch amazon video -- it won't even play. Probably still having some DRM issues...

I read on here that shikigva=80 was no longer necessary, but then why am I getting these DRM errors (and I wasn't having any issues when I was running Martin's package, with the code inside boot-args)?


Furthermore, I am still only seeing the verbose/BuiltIn text-only OC boot picker.

Really don't know what to do about getting the icons back -- I even tried setting PickerVariant to "Acidanthera/GoldenGate" but STILL, getting the damn verbose/BuiltIn/text-only boot picker.

Manually configured (per the instructions) config is attached -- would really appreciate your feedback if you have some time.

Thanks again for your expertise!

 

[cdf]

Furthermore, I am still only seeing the verbose/BuiltIn text-only OC boot picker.

Really don't know what to do about getting the icons back -- I even tried setting PickerVariant to "Acidanthera/GoldenGate" but STILL, getting the damn verbose/BuiltIn/text-only boot picker.

This shouldn't happen. I would try recreating a fresh setup by following the instructions in Basic setup. Make sure to redownload all the files and use the basic config in post #1 without any modifications. Once you get the boot menu working properly, you can move on to customizing your config.

Manually configured (per the instructions) config is attached -- would really appreciate your feedback if you have some time.

Some comments and recommendations:

1. agdpmod device property isn't necessary when spoofing Mac-27AD2F918AE68F61
2. double check the path of your graphics card with gfxutil (this might explain your issues with DRM)
3. use device properties to make your PCIe drives internal (if you have any) and remove the IONVMeFamily patch and set ExternalDiskIcons to false (these patches can be considered deprecated)
4. unless you plan on booting macOS 11.3–12.0.1, you can remove SurPlus
5. set PollAppleHotKeys to true
6. processor type can be set to 0 for automatic detection
7. set GraphicsInputMirroring to false
8. playchime should be disabled on Macs
9. TimerResolution is 100000 on Macs

 

[prefuse07]

This shouldn't happen. I would try recreating a fresh setup by following the instructions in Basic setup. Make sure to redownload all the files and use the basic config in post #1 without any modifications. Once you get the boot menu working properly, you can move on to customizing your config.


Some comments and recommendations:

1. agdpmod device property isn't necessary when spoofing Mac-27AD2F918AE68F61
2. double check the path of your graphics card with gfxutil (this might explain your issues with DRM)
3. use device properties to make your PCIe drives internal (if you have any) and remove the IONVMeFamily patch and set ExternalDiskIcons to false (these patches can be considered deprecated)
4. unless you plan on booting macOS 11.3–12.0.1, you can remove SurPlus
5. set PollAppleHotKeys to true
6. processor type can be set to 0 for automatic detection
7. set GraphicsInputMirroring to false
8. playchime should be disabled on Macs
9. TimerResolution is 100000 on Macs

Ok, going to try again from scratch as you've instructed -- also thanks for the pointers on all of the above.

Quick question:

./gfxutil -f display | sed 's|. *= ||' returns the following path:

% /PCI0@0/IOU0@3/PXS1@0/pci-bridge@0/display@PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)

Therefore, the address: Pci(0x3,0x0)/Pci(0x0,0x0), is the path of my GPU, right? (PCIe slot 1)

 

[cdf]

./gfxutil -f display | sed 's|. *= ||' returns the following path:

You have a space before the *. Remove it to get the properly formatted path, which seems to be
PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)

 

[prefuse07]

You have a space before the *. Remove it to get the properly formatted path, which seems to be
PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)

Ok, from absolute scratch, literally followed the guide down to a 'T'

got a brand new config file, from page 1, all OC and associated files downloaded directly per the links you posted on the guide (which takes me to Acidanthera's github repo for each kext etc...).

My system seems a lot snappier during boot (perhaps because now I am using DeviceProperties instead of Patching with the IONVME as you recommended) -- thanks for this!

In any case..... STILL, the damn Verbose/BuiltIn/Text-only boot picker.

Also, still getting red screen when trying to watch amazon prime video (DRM thing still seems to be happening). I took got rid of agdpmod as recommended.

Keeping SurPlus because I am running 11.6.2

New OC file is attached, I am dumbfounded on why I keep getting the text-only picker...

 

[kkinto]

I'm not sure what you're referring to. Like a configurator app? I think OCLP has something like that by now.

Yes, but just kidding really - would be great to just tick all required 'features' and click 'build Opencore' and it just created the config for you - sort of like OCLP but without the patching

 

[cdf]

Also, still getting red screen when trying to watch amazon prime video (DRM thing still seems to be happening). I took got rid of agdpmod as recommended.

Let's address this one first.

Unfortunately, you seem to be dealing with one of the exceptional cases where your GPU lacks the necessary acpi-path property for adding other properties. The quickest solution for now is just to use boot-args. In your config, remove

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>rebuild-device-tree</key>
<integer>0</integer>
<key>unfairgva</key>
<integer>1</integer>
<key>shikigva</key>
<integer>80</integer>
</dict>

and replace

<string>-no_compat_check</string>

by

<string>-no_compat_check wegtree=1 unfairgva=1 shikigva=80</string>

Now with these changes, check that DRM works.

 

[cdf]

Have you been around Sidecar with BigSur?
I have an error -501 and tried different kind of things

SideCar do not work with my Mac Pro BigSur and OpenCore 0.7.6 (Vega RX 56).

Turn off and on my iCloud account on both machine
Turn off and on BT on both machine
tried to usb cable
reboot both machines.


Any suggestion?

I've a MBP 16 with Catalina and no use using a cable.

Unfortunately, even if "unlocked", Sidecar will not work on MacPro5,1.

 

[Dewdman42]

just out of curiosity, what is the reason it won't work?

 

[cdf]

just out of curiosity, what is the reason it won't work?

Lack of integrated graphics.

 

[startergo]

Lack of integrated graphics.

Or T2 right? Either or.

 

[prefuse07]

Let's address this one first.

Unfortunately, you seem to be dealing with one of the exceptional cases where your GPU lacks the necessary acpi-path property for adding other properties. The quickest solution for now is just to use boot-args. In your config, remove

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>rebuild-device-tree</key>
<integer>0</integer>
<key>unfairgva</key>
<integer>1</integer>
<key>shikigva</key>
<integer>80</integer>
</dict>

and replace

<string>-no_compat_check</string>

by

<string>-no_compat_check wegtree=1 unfairgva=1 shikigva=80</string>

Now with these changes, check that DRM works.

Thanks for your patience and help, really appreciate it! I got it fixed.

First I added to DeviceProperties:

<key>wegtree</key>
<integer>1</integer>

I rebooted into recovery with the text-picker and disabled SIP and rebooted again (text-picker still showing up); I then chose recovery and reblessed using terminal (as per guide instructions) and rebooted

OC graphical boot picker now works!

Now I have another question for you -- How can I get custom boot icons to work? (again)

I had them working when I was running Martin's package on 0.7.5, and all I did was replace the files in EFI/OC/Resources/Image/Acidanthera/GoldenGate

Replaced HardDrive.icns with a custom one I made, same name: HardDrive.icns

Same thing for Windows.icns.

I tried doing the same on my current config with 0.7.7, but @ boot, I get the OC text picker. Any ideas?

Googling the subject is all over the place, so that's why I am asking you (in case you got custom icons working on 0.7.7)

Other than that -- thank you for everything, 0.7.7 seems to be running really smoothly on my machine, haven't experienced any KPs or issues yet, but will see if this stability persists (I am loving it!)

 

[cdf]

Thanks for your patience and help, really appreciate it! I got it fixed.

Great! But...

First I added to DeviceProperties:

<key>wegtree</key>
<integer>1</integer>

This doesn't do anything. The property is "rebuild-device-tree".

I rebooted into recovery with the text-picker and disabled SIP and rebooted again (text-picker still showing up); I then chose recovery and reblessed using terminal (as per guide instructions) and rebooted

OC graphical boot picker now works!

Seems random. SIP doesn't have to be disabled.

Now I have another question for you -- How can I get custom boot icons to work? (again)

You can create your own icon set and place it in any directory in EFI/OC/Resources/Image. Then set PickerVariant to that directory in your config.

Other than that -- thank you for everything, 0.7.7 seems to be running really smoothly on my machine, haven't experienced any KPs or issues yet, but will see if this stability persists (I am loving it!)

Again, this is great, but what you're describing indicates that something is off. The fact that reblessing fixes the graphical boot menu is strange. I wonder if you're not dealing with multiple OC installations. Try mounting all your EFI partitions and verifying their contents. There should only be one that contains the OC files.

You might also want to try the debug version of OC. It generates a log that can give us a better idea of what is going on. The section Maintenance in post #1 explains how to set this up.

 

[prefuse07]

Great! But...


This doesn't do anything. The property is "rebuild-device-tree".

Ah, gotcha

Seems random. SIP doesn't have to be disabled.


You can create your own icon set and place it in any directory in EFI/OC/Resources/Image. Then set PickerVariant to that directory in your config.


Again, this is great, but what you're describing indicates that something is off. The fact that reblessing fixes the graphical boot menu is strange. I wonder if you're not dealing with multiple OC installations. Try mounting all your EFI partitions and verifying their contents. There should only be one that contains the OC files.

You might also want to try the debug version of OC. It generates a log that can give us a better idea of what is going on. The section Maintenance in post #1 explains how to set this up.

I only have 1 drive with macOS on it, the other one is Windows 11, and then a Time Machine HDD, but I'll check all of them just in case. Thanks for the heads up.

 

[cdf]

So I don't need wegtree then?

Not as a device property, because there is no such property. There are three possibilities to enable DRM. In order of preference:

1. rebuild-device-tree device property (with any value)
2. wegtree=1 boot-arg
3. -wegtree deprecated boot-arg

All three do the same thing.

 

[toomanyairmiles]

I have an MSI Radeon 5700 XT Mech card and this doesn't appear to be compatible with Lilu and WhateverGreen. All that appears in About This Mac is 'Display 31Mb', it does boot and work in some kind of basic mode though.

Is there some kind of work around that is card specific?

 

[tsialex]

I have an MSI Radeon 5700 XT Mech card and this doesn't appear to be compatible with Lilu and WhateverGreen. All that appears in About This Mac is 'Display 31Mb', it does boot and work in some kind of basic mode though.

Is there some kind of work around that is card specific?

Apple started to support NAVI 1x cards with Catalina 10.15.1, what macOS version you are running?

Btw, the NAVI driver support RX 5700XT with device ID 731F, 'Display 31Mb' show that your card is not being recognized.

 

[toomanyairmiles]

Apple started to support NAVI 1x cards with Catalina 10.15.1, what macOS version you are running?

Btw, the NAVI driver support RX 5700XT with device ID 731F, 'Display 31Mb' show that your card is not being recognized.

At the moment, Mojave because it crashes each time I upgrade, but that turns out to be an issue with the card too.

About to test a fix, hopefully the issue will go away with the OS upgrade.

 

[tsialex]

At the moment, Mojave because it crashes each time I upgrade, but that turns out to be an issue with the card too.

About to text a fix, hopefully the issue will go away with the OS upgrade.

Mojave knows nothing about your GPU, that's the reason for the 'Display 31Mb' with AboutMyMac. You only have a display working right now because the EFI driver fallback / OC support of GOP cards.

 

[DigitaLife]

You need to download Windows 10 AND Windows 11 installers from Microsoft. Prepare an exFAT USB bootable pen drive with the Windows 11 installer. Rename the file appraisers.dll in the Windows 11 /sources folder to something like _appraisers.dll. Copy the file appraisers.dll in the Windows 10 /sources folder and paste it in the same folder of the Windows 11 installer. Now, follow @cdf's tutorial. Everything should work.

I followed your instructions but when the installation of Windows 11 starts, a message pops up saying ".... cannot install Windows 11 on this PC because it does not have the requirements..."
Can you please help me? Thanks in advance!

 

[prefuse07]

I followed your instructions but when the installation of Windows 11 starts, a message pops up saying ".... cannot install Windows 11 on this PC because it does not have the requirements..."
Can you please help me? Thanks in advance!

Didn't read my post to you, did you?

 

[toomanyairmiles]

MacOS Could Not Be Installed On Your Computer

Very frustrated with this build, clean install of Opencore on a MacPro 4,1 with hacked firmware and a RX580. No matter what OS I've tried to install on it, I end up with the above message, and I've tried El Cap to Catalina along with the Catalina Patcher build.

Googling the error provides an endless stream of clickbait listicles most of which claim the issue is the system date being incorrect, the clock is correct.

Any thoughts appreciated.

 

[cdf]

MacOS Could Not Be Installed On Your Computer

You need to enable the VMM flag to install Catalina.