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

[ScreenSavers]

Power Nap is not supported with MP5,1 firmware. First Mac Pro to support it is late 2013 Mac Pro.

Mac User Guide

Learn what’s new in macOS, how to get started with your Mac and use it with your Apple devices, and how to control privacy and security on macOS.

support.apple.com

Btw, PowerNap does just what you don't want.

Exactly. And it will heat your room by 10° if you manage to get it to work.

 

[TECK]

Btw, PowerNap does just what you don't want.

Thanks, I thought the option is missing because OC and the Power Nap is acting as being enabled by default.

You can achieve this by disabling "Wake for network access."

Thanks, I'm going to disable the option.

 

[ECJ]

I setup OpenCore 0.5.8, and it has been working great. Thanks to this great thread. I was able to disable the Boot Picker, add HW acceleration, show my NVME drives as internal, and set the boot background color to black. The only issue I have is the EFI still shows when I hold option key upon boot, and the Catalina partition won't boot if I select it. If I select the EFI drive or if I let it boot without intervention, it boots Catalina just fine. Mojave and Catalina each have their own 2TB NVME. My System is below. Any help would be great.

2009 4,1 flashed to 5,1
2x 3.3Ghz Xeons
96GB 1333 Mhz DDR3
Radeon RX 580 8GB Flashed for boot screen
Syba I/O Crest SI-PEX40129 NVME card (Slot 2)
2x 2TB Sabrent Rocket NVME blades

 

[cdf]

The only issue I have is the EFI still shows when I hold option key upon boot, and the Catalina partition won't boot if I select it. If I select the EFI drive or if I let it boot without intervention, it boots Catalina just fine.

That's absolutely normal. Because you have a flashed card, when you hold the Option key, you get the original boot picker, and because Catalina is unsupported, it needs to boot through OpenCore, which is the "EFI Boot" option.

 

[ECJ]

That's absolutely normal. Because you have a flashed card, when you hold the Option key, you get the original boot picker, and because Catalina is unsupported, it needs to boot through OpenCore, which is the "EFI Boot" option.

Thanks. That makes sense. More of a feature than a bug. lol

 

[joevt]

The only issue I have is the EFI still shows when I hold option key upon boot, and the Catalina partition won't boot if I select it.

You could try using the bless command to give OpenCore a different label other than "EFI Boot" but that might not work for old Macs.
sudo bless --folder "/Volumes/EFI/EFI/BOOT" --label "OpenCore"
This creates invisible .disk_label and .disk_label_2x files in the folder containing bootx64.efi. Double check that those exist (press Command-Shift-Period to show/hide invisible files).

If that doesn't work, you could put OpenCore on an HFS+ partition but I don't know if OpenCore works from an HFS+ partition. For one thing, it won't be able to write files to the HFS+ partition, such as log or screenshots. Does OpenCore write logs? Does it write to the same volume as it's installed in or can it write to a different volume (any EFI or FAT partition will have write access in EFI)?

 

[startergo]

You could try using the bless command to give OpenCore a different label other than "EFI Boot" but that might not work for old Macs.
sudo bless --folder "/Volumes/EFI/EFI/BOOT" --label "OpenCore"
This creates invisible .disk_label and .disk_label_2x files in the folder containing bootx64.efi. Double check that those exist (press Command-Shift-Period to show/hide invisible files).

If that doesn't work, you could put OpenCore on an HFS+ partition but I don't know if OpenCore works from an HFS+ partition. For one thing, it won't be able to write files to the HFS+ partition, such as log or screenshots. Does OpenCore write logs? Does it write to the same volume as it's installed in or can it write to a different volume (any EFI or FAT partition will have write access in EFI)?

It works from an HFS+ partition but does not save the log files there.

 

[Paolo-Sp]

Hello

To enabling Hardware Acceleration (PART II - Advanced Configuration) need only add kexts Lilu + WhateverGreen + AppleMCEReporter and add the device properties "PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)" or, need also iMacPro hybridization + clean the NVRAM?

 

[cdf]

To enabling Hardware Acceleration (PART II - Advanced Configuration) need only add kexts Lilu + WhateverGreen + AppleMCEReporter and add the device properties "PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)" or, need also iMacPro hybridization + clean the NVRAM?

As stated in the guide: hybridization is integral to successful hardware acceleration. You need it. And with it, you no longer need any boot arguments. So you can clean the NVRAM.

 

[Paolo-Sp]

Thanks @cdf

I make just config.plist and put al kexts in Kexts folder, all is as indicated in PART II but after restar KP!
If I deactivate UpdateSMBIOS "false" my Mac 5.1 start but no Hardware Acceleration.

I think I need your help.... attach my config

P.S. I have Radeon RX-850 with MacVidCards EFI

 

[startergo]

Thanks @cdf

I make just config.plist and put al kexts in Kexts folder, all is as indicated in PART II but after restar KP!
If I deactivate UpdateSMBIOS "false" my Mac 5.1 start but no Hardware Acceleration.

I think I need your help.... attach my config

<dict>
                <key>BundlePath</key>
                <string>AppleMCEReporterDisabler.kext</string>
                <key>Comment</key>
                <string>Disable AppleMCEReporter</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NightShiftEnabler</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>

This is a mess.

 

[Paolo-Sp]

Thanks @startergo
I correct the config.plist and let you know in a few hours

 

[Kenn2183]

My hardware on my cmp 5,1 imy BootROM is 144.0.0.0 duel 6 core CPUs @ 3.06 and Nvidia GTX 680 with boot screen support and Mac OS Mojave 10.15.6 in sata bay number one. My Mac OS Catalina install disk is on sonnet tempo duel 2.5 SSD with duel Samsung 860 EVO’S running in fusion drive formatted in APFS in pcie slot 4 on the logic board and my windows install disk is on 2.5 SSD on a pcie card on logic board in slot number 3 and I can’t get the config plist set up and to see Mac OS Mojave and Mac OS Catalina and windows 10 install with out losing opencore when I boot into windows and could some help me please set up a config plist to solve my problems thanks

 

[Paolo-Sp]

Thank you all.

I have correct my stupid erro in config and now Hardware Acceleration done.
I rebooted and suggested that I connect to this link

 

[kosiba]

First I want to give a huge "Thank You!" to everyone who has contributed to the OpenCore development and these forums,
It is amazing to be able to us this resource, and maintain the usefulness of older MacPros.

I have followed the updated instructions by CDF in Post #1, with OpenCore 0.5.8 and modified the config.plist file with the instructions outlined in PART 1 and PART 2.

I am running a dual X5690 processor Mac Pro 5,1, 144.0.0.0.0 firmware, with a Saphire Pulse RX580.
I have Mojave on an SSD in Drive Bay 1 and Catalina on an SSD in Drive Bay 2

I am having two issues that I am hoping someone could help me with.

1. I have H264 enabled and can not get HEVC enabled.

2. I have the OpenCanopy boot selector coming up but without any text labels on the drives. See images below.
When I press the space bar, the recovery partitions show each with a label but the Mojave & Catalina boot drives
do not have any text labels. I loaded the fonts and labels within the resource subdirectories but can't seem to get it
to display as shown in the top of Post #1 by CDF.

Thanks in advance for anyone who could provide advice or assistance.

 

[dataid]

First I want to give a huge "Thank You!" to everyone who has contributed to the OpenCore development and these forums,
It is amazing to be able to us this resource, and maintain the usefulness of older MacPros.

I have followed the updated instructions by CDF in Post #1, with OpenCore 0.5.8 and modified the config.plist file with the instructions outlined in PART 1 and PART 2.

I am running a dual X5690 processor Mac Pro 5,1, 144.0.0.0.0 firmware, with a Saphire Pulse RX580.
I have Mojave on an SSD in Drive Bay 1 and Catalina on an SSD in Drive Bay 2

I am having two issues that I am hoping someone could help me with.

1. I have H264 enabled and can not get HEVC enabled.

2. I have the OpenCanopy boot selector coming up but without any text labels on the drives. See images below.
When I press the space bar, the recovery partitions show each with a label but the Mojave & Catalina boot drives
do not have any text labels. I loaded the fonts and labels within the resource subdirectories but can't seem to get it
to display as shown in the top of Post #1 by CDF.

Thanks in advance for anyone who could provide advice or assistance.

You need to make sure you have the correct resources available for OpenCore.
Have a look at the instructions in giving OpenCore “A Beauty Treatment” below. Make certain you have the label resources in the correct folder and the folder structure is also correct.

Add GUI and Boot-chime · GitBook

dortania.github.io

 

[kosiba]

@dataid - Thank you for the quick response.
I had and then re-did the "Beauty Treatment" instructions and I have re-downloaded and placed the resources.
I am still having the same issues with no boot drive labels and no HEVC hardware acceleration.
I have attached a few screen captures of the file subdirectories and my config.plist file.
Any assistance is greatly appreciated.
Thanks Again!

 

[TECK]

I had and then re-did the "Beauty Treatment" instructions

What are Beauty Treatment instructions? I would only follow the simple to use official OpenCore instructions. Took me five minutes to enable OpenCanopy on top of @cdf's HWAccel setup (please use his precise instructions, for 100% success) and another five to disable it because there is an issue with Windows boot freezing all the time.

I need to find a bit of time to push into EFI the debug OC version and share the logs here, so we figure together why is this happening. @cdf was experiencing this issue also. but a lot less than me. I used VirtualBox EFI to install Windows with a fully formatted NTFS disk, not "halfandhalf." I like that name

 

[dataid]

What are Beauty Treatment instructions? I would only follow the simple to use official OpenCore instructions. Took me five minutes to enable OpenCanopy on top of @cdf's HWAccel setup (please use his precise instructions, for 100% success) and another five to disable it because there is an issue with Windows boot freezing all the time.

I need to find a bit of time to push into EFI the debug OC version and share the logs here, so we figure together why is this happening. @cdf was experiencing this issue also. but a lot less than me. I used VirtualBox EFI to install Windows with a fully formatted NTFS disk, not "halfandhalf." I like that name

Dortiana

What are Beauty Treatment instructions? I would only follow the simple to use official OpenCore instructions. Took me five minutes to enable OpenCanopy on top of @cdf's HWAccel setup (please use his precise instructions, for 100% success) and another five to disable it because there is an issue with Windows boot freezing all the time.

I need to find a bit of time to push into EFI the debug OC version and share the logs here, so we figure together why is this happening. @cdf was experiencing this issue also. but a lot less than me. I used VirtualBox EFI to install Windows with a fully formatted NTFS disk, not "halfandhalf." I like that name

Dortiana on Github has provided for OpenCore 0.5.8 explicit instructions the "Beauty Treatment" on how to set up OpenCanopy to display its GUI and provide an audio chime on boot up while using OpenCore. It also provides links to the digital resources for audio, fonts, images (icons) and labels which are not provided in either the release or developer versions of OpenCore. These are the Resources made available by the OpenCore developers themselves. As OpenCanopy is not yet official and the OpenCore documentation itself is written for developers and Hackintosh users, others have written instructions to simplify setting up the GUI and audio features for those wanting to use these features before their official release.

 

[Paolo-Sp]

Hallo Kosiba

After last just change, my Mac Pro 5.1 is perfect.
Test my EFI in your Mac but control your device video properties because maybe it's different from mine "PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)"

 

[dataid]

@kosiba
Here are the Boot settings in my config.plist for OpenCore 0.5.8/OpenCanopy which displays the labels.
I am not familiar with many other settings in your config.plist so I cannot comment on that.

 

[TECK]

Dortiana on Github has provided for OpenCore 0.5.8 explicit instructions the "Beauty Treatment" on how to set up OpenCanopy to display its GUI and provide an audio chime on boot up while using OpenCore.

That is some third party posting their solution. Why not use the actual OC documentation which is so easy to use and understand? I would not trust anything else. The goal is to learn what you put into your property list file, not just copy/paste values for a website. Best example is: what happens if the maintainers of these sites stop maintaining their guides?

@kosiba
Here are the Boot settings in my config.plist for OpenCore 0.5.8/OpenCanopy which displays the labels.
I am not familiar with many other settings in your config.plist so I cannot comment on that.


View attachment 917400

IMO, that is a perfect example what not to do, use pre-built tools which "fill" things for you.

 

[mangombia]

As stated in the guide: hybridization is integral to successful hardware acceleration. You need it. And with it, you no longer need any boot arguments. So you can clean the NVRAM.

Maybe that's my issue. I've correctly applied the Device Properties for my GPU, and implemented the hybridization parameters, but I never reset the NVRAM which had my boot-args. If I reset NVRAM do I need to re-bless the OC EFI?

 

[cdf]

If I reset NVRAM do I need to re-bless the OC EFI?

If you reset it by holding Option, Command, P and R before the boot chime, then yes.

 

[mangombia]

If you reset it by holding Option, Command, P and R before the boot chime, then yes.

If I reset via the NVRAM reset command from the OC picker, same result?