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

[MacForumsUser]

You can, but it will make Windows the default startup. If you have Bootcamp on the Windows side you can use that to boot back to macOS. Otherwise, you'll have to press"ESC" at boot to choose macOS again.

Gotcha. So if I'm using OC, can I install Windows 10 using Boot Camp? I thought it must be UEFI mode?

 

[nobullone1964]

Gotcha. So if I'm using OC, can I install Windows 10 using Boot Camp? I thought it must be UEFI mode?

It has to be UEFI in order for OpenCore to show it in BootPicker. If it is Legacy (installed via DVD) OpenCore won't see it, but it will be functional if selected in startup disk under system Preferences. There is a way to boot Legacy and with that I'd point you to @Dayo for his instructions.

 

[eVasilis]

One thing that puzzles me is that occasionally when I boot my mac pro, the screen stays black, no desktop. The boot process is complete as I can hear the alert sounds when I press certain keys on the keyboard. The only thing I can do is turn it off and then reboot. Any ideas? This happened with both 0.6.6 and 0.6.7 and big sur.

Thanks

 

[TECK]

before do all this step, i want understand all that i will do.

Please read the first post carefully and consult also the OpenCore documentation, if needed. When I started using OC, all I had to do is read the first post, many times I might add. Then, everything came together clear.

To get you started, you should have your Mac running latest unpatched Mojave macOS on a Sata1 disk (safest way for BootROM refresh, etc.). Mojave is the last supported macOS, for a 5,1 Mac. From there, you can follow the guide step by step.

When I started first, I've chosen to remove all disks and install High Sierra fresh into Sata1 SSD, then I upgraded to Mojave with a metal supported GPU, in my case I used a RX580. All upgrade details are linked into first post.

 

[MacForumsUser]

One thing that puzzles me is that occasionally when I boot my mac pro, the screen stays black, no desktop. The boot process is complete as I can hear the alert sounds when I press certain keys on the keyboard. The only thing I can do is turn it off and then reboot. Any ideas? This happened with both 0.6.6 and 0.6.7 and big sur.

Thanks

What happens if you turn your monitor off and back on? Have you tried connecting it via a different method: HDMI, DisplayPort, DVI (if available)?

 

[eVasilis]

What happens if you turn your monitor off and back on? Have you tried connecting it via a different method: HDMI, DisplayPort, DVI (if available)?

Turning monitor on/off does nothing. I cannot try HDMI as the monitor does not have such a post, it only has DP. As for DVI I did not try in as I do not have a cable for it.

Thanks

 

[hwojtek]

Turning monitor on/off does nothing. I cannot try HDMI as the monitor does not have such a post, it only has DP. As for DVI I did not try in as I do not have a cable for it.

Similar thing happens when my R9 280X doesn't initialize one of the DP ports correctly. I have two screens connected and sometimes (most often if I booted to Windows and gamed) a random DP port doesn't light up on warm reboot. It's always just one of two, so the other screen works. A simple solution is to unplug both displays and plug them back in. Try this.

 

[Dewdman42]

I have been getting weird problems like that with my rx580 when I have both a dp and dvi monitor connected and when I go to Mojave recovery mode or boot the Mojave install media from usb. Turning off my dp monitor makes the desktop appear on the dvi monitor and the turning the dp monitor back on brings the desktop over to the dp screen again. Strange stuff. It was not always doing that, something changed recently but not sure what.

Mojave and Catalina both boot up normally though with both screens when booting up into the full operating system.

 

[eVasilis]

Similar thing happens when my R9 280X doesn't initialize one of the DP ports correctly. I have two screens connected and sometimes (most often if I booted to Windows and gamed) a random DP port doesn't light up on warm reboot. It's always just one of two, so the other screen works. A simple solution is to unplug both displays and plug them back in. Try this.

Thanks, I'll try that.

 

[anarchi]

I'm fairly sure that this has been answered before and I apologise, but I can't find it.

How do I reset the nvram without unblessing OpenCore?

If I reset the nvram in the normal way (cmd+opt+p+r) it unblesses OpenCore and I have to spend half an hour reinserting a sata disk and trying to get the recovery partition to boot. I do have a bootable version of Mojave in my 5,1 at all times, but it is on an SSD on a PCIe card and getting that one's recovery disk to boot is about a 1 in 10 chance.

Thanks for your patience.

 

[jrumball]

I'm fairly sure that this has been answered before and I apologise, but I can't find it.

How do I reset the nvram without unblessing OpenCore?

If I reset the nvram in the normal way (cmd+opt+p+r) it unblesses OpenCore and I have to spend half an hour reinserting a sata disk and trying to get the recovery partition to boot. I do have a bootable version of Mojave in my 5,1 at all times, but it is on an SSD on a PCIe card and getting that one's recovery disk to boot is about a 1 in 10 chance.

Thanks for your patience.

Use Cmd+r to boot into the Mojave recovery partition, disable SIP and bless the EFI partition again....

 

[anarchi]

Use Cmd+r to boot into the Mojave recovery partition, disable SIP and bless the EFI partition again....

Thanks. Yes I know that's the normal way of doing it, but I'd like to try to avoid the whole unblessing and rebooting outside of OpenCore, if there is a way to do this.

 

[startergo]

I'm fairly sure that this has been answered before and I apologise, but I can't find it.

How do I reset the nvram without unblessing OpenCore?

If I reset the nvram in the normal way (cmd+opt+p+r) it unblesses OpenCore and I have to spend half an hour reinserting a sata disk and trying to get the recovery partition to boot. I do have a bootable version of Mojave in my 5,1 at all times, but it is on an SSD on a PCIe card and getting that one's recovery disk to boot is about a 1 in 10 chance.

Thanks for your patience.

There is a tool in OC Nvram reset. It only resets variables outside of OC.

 

[anarchi]

There is a tool in OC Nvram reset. It only resets variables outside of OC.

That sounds perfect. Where…? How…?

 

[startergo]

That sounds perfect. Where…? How…?

8.5 Security Properties​

1. AllowNvramReset
   Type: plist boolean
   Failsafe: false
   Description: Allow CMD+OPT+P+R handling and enable showing NVRAM Reset entry in OpenCore picker.
   Note 1: It is known that some Lenovo laptops have a firmware bug, which makes them unbootable after performing NVRAM reset. See acidanthera/bugtracker#995 for more details.
   Note 2: Resetting NVRAM will also erase any boot options not backed up using the bless command. For example, Linux installations to custom locations not specified in BlessOverride

 

[anarchi]

And there it is in the Config.plist. Thanks for this. I'll investigate it further.

 

[MacForumsUser]

You can, but it will make Windows the default startup. If you have Bootcamp on the Windows side you can use that to boot back to macOS. Otherwise, you'll have to press"ESC" at boot to choose macOS again.

So just FYI, I decided to bite the bullet and try setting my startup disk to Windows 10 from with Big Sur > Preferences > Startup Disk. When I selected it and clicked Restart, I received an error:

Unable to set startup disk

An error occurred while setting “Windows” as the startup disk: The operation couldn’t be completed. (SDErrorDomain error 104.)

I clicked "Dismiss," and restarted normally and held Esc.

 

[nobullone1964]

So just FYI, I decided to bite the bullet and try setting my startup disk to Windows 10 from with Big Sur > Preferences > Startup Disk. When I selected it and clicked Restart, I received an error:

Unable to set startup disk

An error occurred while setting “Windows” as the startup disk: The operation couldn’t be completed. (SDErrorDomain error 104.)

I clicked "Dismiss," and restarted normally and held Esc.

Is your Windows UEFI or Legacy?

 

[cdf]

So just FYI, I decided to bite the bullet and try setting my startup disk to Windows 10 from with Big Sur > Preferences > Startup Disk. When I selected it and clicked Restart, I received an error:

Unable to set startup disk

An error occurred while setting “Windows” as the startup disk: The operation couldn’t be completed. (SDErrorDomain error 104.)

I clicked "Dismiss," and restarted normally and held Esc.

This is a know issue in Big Sur.

 

[juliovg]

Please read the first post carefully and consult also the OpenCore documentation, if needed. When I started using OC, all I had to do is read the first post, many times I might add. Then, everything came together clear.

To get you started, you should have your Mac running latest unpatched Mojave macOS on a Sata1 disk (safest way for BootROM refresh, etc.). Mojave is the last supported macOS, for a 5,1 Mac. From there, you can follow the guide step by step.

When I started first, I've chosen to remove all disks and install High Sierra fresh into Sata1 SSD, then I upgraded to Mojave with a metal supported GPU, in my case I used a RX580. All upgrade details are linked into first post.

Thanks so much @TECK
after reading the post 3 times (really) and i decide start.

my first question is ... :

for the image attached

Both disk must be SSD 2.5?
Could Disk A be HDD 3.5 or USB ... ?
the EFI disk must be internal?
all the time for ever and ever will connected to mac pro 5.1?

Regards

 

[cdf]

after reading the post 3 times (really) and i decide start.

my first question is ... :

for the image attached

Both disk must be SSD 2.5?
Could Disk A be HDD 3.5 or USB ... ?
the EFI disk must be internal?
all the time for ever and ever will connected to mac pro 5.1?

Regards

It shouldn't really matter, as long as the disks are bootable.

 

[Weisswurstsepp]

GPU Video Acceleration & DRM Support Not Working

I've spent most of the day reading through a number of threads but I'm stuck and would appreciate some help.

I"ve got a MP5,1 (Mid 2010) single processor with 3.33GHz 6-core XEON, 64GB RAM, a MVC Radeon RX580 8GB gfx card, a Micron 9200 NVMe SSD, upgraded WiFi+BT which thanks to OC runs Catalina. Most of the installation of OC was pretty straight forward, however the one thing I'm struggling with is video acceleration and DRM playback (Apple TV+). So far I've upgraded OC to 0.67, added the Lilu 1.5.1 and WhateverGreen 1.4.8 kextx to the OC/Kext folder and modified the config.plist as per instructions on the first page.

Gfxutil comes up with the following:
05:00.0 1002:67df /PCI0@0/IOU0@3/GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)

I changed the address in the config.plist accordingly.

However I still get no video acceleration nor can I stream Apple DRM content. VideoProc (latest Trial) also shows both H264 and HEVC as unavailable.

I attached the config.plist to this post, it would be nice if someone could have a look at it and maybe let me know what's wrong.

Another thing: once I get video acceleration and DRM playback to work I intend to upgrade to Big Sur. Can I assume that video acceleration and DRM would work there, too?

 

[PeterHolbrook]

Sleep issues

Is there any kind of consensus as to sleep reliability of a Mac Pro 5,1 running OC 0.6.7 and the latest release of Big Sur? Are there any recommended config.plist keys that should be used to make computer sleep possible in a reliable manner? I'm not sure why right now, but my Energy Savings only has one slider, for Display (in other words, my computer NEVER goes to sleep). I guess this is due to some setting(s) in my config.plist. Should one or more particular ACPI binaries be included? As of now, I only have one ACPI binary for my Titan-Ridge Thunderbolt 3 card, but I suppose there might be others I need to include.

 

[amstel78]

Sleep issues

Is there any kind of consensus as to sleep reliability of a Mac Pro 5,1 running OC 0.6.7 and the latest release of Big Sur? Are there any recommended config.plist keys that should be used to make computer sleep possible in a reliable manner? I'm not sure why right now, but my Energy Savings only has one slider, for Display (in other words, my computer NEVER goes to sleep). I guess this is due to some setting(s) in my config.plist. Should one or more particular ACPI binaries be included? As of now, I only have one ACPI binary for my Titan-Ridge Thunderbolt 3 card, but I suppose there might be others I need to include.

No issues with sleep on my cMP5,1 running OC v0.6.7 and BS 11.2.3. Everything works perfectly. No complaints at all. I'm honestly very surprised at how well BS runs on this Mac. It's almost as if it was a fully supported vanilla install. All thanks goes to @Dayo though for his RP/OC package which includes ConfigFactory. It makes configuring the config.plist file easy as 1, 2, 3.

In terminal, type: pmset -g or pmset -g assertions (for a better breakdown) to determine what's keeping your Mac awake.

 

[startergo]

Sleep issues

Is there any kind of consensus as to sleep reliability of a Mac Pro 5,1 running OC 0.6.7 and the latest release of Big Sur? Are there any recommended config.plist keys that should be used to make computer sleep possible in a reliable manner? I'm not sure why right now, but my Energy Savings only has one slider, for Display (in other words, my computer NEVER goes to sleep). I guess this is due to some setting(s) in my config.plist. Should one or more particular ACPI binaries be included? As of now, I only have one ACPI binary for my Titan-Ridge Thunderbolt 3 card, but I suppose there might be others I need to include.

You can always boot BS directly with -no_compat_check set and compare the results. But I think it is your titan-ridge which is breaking sleep especially if you have USB device connected to it.