Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Delete the EFI folder and try my EFI.

try this EFI and don't change anything in it

for RX 580 you can use my EFI folder do not delete or change anything in it

Hmm... The config in your EFI presents some questionable settings. It uses WEG without any pertinent boot arguments or device properties. It uses AppleALC, which the RX580 doesn't need. It also updates the SMBIOS with just some BootROM version and release date, a puzzling choice... Perhaps you could elaborate on these settings.
 
Interesting, are you using monitors that enforce DRM? Are you using HDMI inputs? Displayport?
I am using converters. Display ports-->DVI-->Monitor Input on both monitors.
Also how did you force the Orinoco buffer type? What advantage does it confer?
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>@0,name</key>
                <data>QVRZLE9yaW5vY28=</data>
                <key>ATY,EFIVersion</key>
                <data>MDEuMDEuMTgz</data>
                <key>CFG,CFG_FB_LIMIT</key>
                <data>BA==</data>
                <key>CFG,CFG_PTPL2_TBL</key>
                <data>ggAAAHwAAAB2AAAAcAAAAGoAAABkAAAAXgAAAFgAAABSAAAATAAAAEYAAABAAAAAOgAAADQAAAAuAAAAKAAAAA==</data>
                <key>PP,PP_PowerPlayEnabled</key>
                <data>AQAAAA==</data>
                <key>PP,PP_WorkLoadPolicyMask</key>
                <data>CA==</data>
                <key>agdpmod</key>
                <data>cGlrZXJhAA==</data>
                <key>model</key>
                <data>QU1EIFJhZGVvbiBSWCA1ODA=</data>
                <key>rebuild-device-tree</key>
                <data>AA==</data>
                <key>shikigva</key>
                <data>kA==</data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <array>
                <string>ATY,EFIVersion</string>
            </array>
        </dict>
    </dict>
</dict>
</plist>
The advantages are mainly in increased GB5 score, better handling by the OS X overall and the boot process. I have 4 video outputs hence
Code:
<key>CFG,CFG_FB_LIMIT</key>
                <data>BA==</data>
BA== is 04 in HEX, so if you have 5 you will have to set BQ== there etc.
 
Hmm... The config in your EFI presents some questionable settings. It uses WEG without any pertinent boot arguments or device properties. It uses AppleALC, which the RX580 doesn't need. It also updates the SMBIOS with just some BootROM version and release date, a puzzling choice... Perhaps you could elaborate on these settings.
without AppleALC there will be no HDMI sound
 
Hi
i want to use OpenCore with Fusion Drive.
Dose OC support Fusion Drive? If it is, what drive should i Bless?
If it isn't, should i Bless the Windows SSD?
Thank you.
 
OpenCore on Legacy Apple Hardware

This guide explains how to use the excellent OpenCore bootloader on a classic Mac Pro to install, run and update macOS Catalina, resulting in a clean, unpatched operating system no different than on a supported Mac.

Why OpenCore?

There are several advantages to using OpenCore on a classic Mac Pro:

Boot picker screen (even with a standard graphics card)
View attachment 916024
Software Update (just like on a supported Mac)
View attachment 882160
Hardware acceleration (and DRM for Netflix on Safari)View attachment 919405
Requirements

Mac Pro modelEarly 2009 with MacPro5,1 firmware,* Mid 2010 or Mid 2012
Processor architectureWestmere (E56xx, L56xx, X56xx) / Gulftown (W36xx)
Boot ROM version144.0.0.0.0*
GraphicsEFI (flashed) or standard UEFI card with Metal support

* Need to upgrade? See the upgrade instructions.

PART I
Basic Installation




PART II
Advanced Configuration





PART III
Maintenance





APPENDIX




Acknowledgements

A big thank you to @vit9696 and the other talented developers of Acidanthera for making all of this possible. Special gratitude goes to @h9826790 for spearheading the hardware acceleration study and @startergo for the relentless testing that led to boot screen support. And thanks to all those that have contributed to this thread!

Stuck on Step 3, my Mac can't put to recovery mode
 
macOS Big Sur?
No. I'm on Mojave 14.6. But, if it works now it should work 2 OSs up. Remember that you're playing with beta software. They may have not added the driver back, yet.


edit: Just completed my Catalina installation. RX500 works OOB.
 
Last edited:
Correct, does it need to be configurable?
@jackluke is trying to boot patched systems in BigSur.

Patched BigSur already worked, I'd need also patched BaseSystem.dmg (or any custom Ramdisk DMG) to load from OpenCore , also using csr-active-config /w8AAA== is not suffice (there is some other OpenCore.efi subcheck on DMG structure validation), getting this output message:
Code:
DMG has been altered
OCB: LoadImage failed - Unsupported
Halting on critical error

@vit9696 could you make this configurable ?

Thanks
 
Last edited:
Is there any reason why a MP with OC won't boot Catalina 10.15.6 from a clone backup on a USB hard drive? I recently made a clone with CCC, formatting the drive as APFS (unencrypted) beforehand. When I select the drive in the boot picker it begins booting then stops almost immediately, displaying an icon with a line through it, before returning to the picker.
 
Last edited:
Ok, so I've read about 110 pages of this thread now to try and understand the DRM and hardware acceleration issue. Wondering if the community could answer one or two questions.

Some background however.
My system is as follows:
-Xeon X5690 3.46Ghz
-Sapphire RX580 8Gb unflashed
-SSD with Mojave in Bay 1
-SSD with Catalina 10.15.6 and Opencore in Bay 2
-I currently have the VMM flag turned off

I've thus far just performed the basic Opencore 0.59 install from the Wiki coupled with the OpenCanopy installation.
It is currently set to display the boot picker and will then progress to the Catalina OS. I have signed into iCloud and all my data has been pulled down without issue.

Bar the TV app, everything else in Catalina appears to be working. If I download a purchased movie, then it will play but it will not let me stream a purchased movie. Apple TV + content streams fine.

I've gone back to the Mojave installation and the behaviour is the same. It will not stream a purchased movie (it did before Opencore) but it will play a downloaded purchased movie.

I am able to access Netflix in the Catalina installation via Chrome.
One thing I have noticed is that my monitor will occasionally just go black for a few seconds during random actions and then display signal again with no intervention from me.

*************************
Ok so having read through this thread from the start, my understanding is that in the early days full spoofing of iMac Pro was used and this was deemed unsafe for the Mac Pro in case it messed with the firmware.

It would appear now though that a few months back it was deemed safe to use the UpdateSMBIOS key for iMacPro hybridisation in order to enable hardware acceleration as per the Wiki. Once hardware acceleration is enabled, then the UpdateSMBIOS is set as "True" and this can be left on without any issues. As long as the VMM is turned off, then updates will not occur and my Mac Pro will not be screwed by an update.

If I wished to update however, then I would need to change UpdateSMBIOS to "false" and turn the VMM "on" before checking for an update. Once, I've updated, I then set SMBIOS as "True" again and turn the VMM "Off".

Is this a correct understanding of the current state of affairs?

Also, given my issues with streaming TV app content, am I correct in my assumption that enabling the hardware acceleration as per the Wiki will resolve the issue?
 
I'm new to using OC, but when I updated from 10.15.5 to 10.15.6 I only temporarily set VMM to On (during the update) - I didn't touch anything to do with SMBIOS. I don't use TV app, but the free VideoProc app shows I've got hardware h264/265 encode and decode enabled.
 
Is there any reason why a MP with OC won't boot Catalina 10.15.6 from a clone backup on a USB hard drive? I recently made a clone with CCC, formatting the drive as APFS (unencrypted) beforehand. When I select the drive in the boot picker it begins booting then stops almost immediately, displaying an icon with a line through it, before returning to the picker.

the drive must plugged in one of the onboard USB2.0 connections
you can‘t boot from a USB3.x card
 
Thanks IndioX, I was using one of the front USB 2.0 ports.

I thought I'd run CCC again on the drive in case it helped, and noticed that the clone partition with the system on wasn't mounting. CCC advised to run First Aid on it, which I did and it's now mounting fine. I'm running a quick differential backup and will then test again. It'll probably work fine now but I'll report back.

Edit: still not booting off the cloned disk. CCC's blog has some discussion of issues with creating a new bootable backup when starting from 10.15.5+: https://bombich.com/kb/ccc5/macos-catalina-known-issues. I've submitted a ticket, so will see what they say.

It seems like due to changes with Catalina, the partition you're cloning to must be formatted APFS non-encrypted. You can then boot into the clone and turn File Vault on. I presume I can then reboot into my regular install, leave the USB drive plugged in, and FV will continue encrypting in the background? Don't really want to have to remain booted from the USB drive until 500GB is encrypted over USB 2. Could leave it overnight though if I must.
 
Last edited:
If I wished to update however, then I would need to change UpdateSMBIOS to "false" and turn the VMM "on" before checking for an update. Once, I've updated, I then set SMBIOS as "True" again and turn the VMM "Off".

Is this a correct understanding of the current state of affairs?

For updates, you can keep hybridization enabled; you just need to turn on the VMM flag.

Also, given my issues with streaming TV app content, am I correct in my assumption that enabling the hardware acceleration as per the Wiki will resolve the issue?

Without enabling hardware acceleration (hybridization and WEG), you will not have DRM for Netflix in Safari. Things may be different for other apps and services. I would enable hardware acceleration and check. Make sure to let us know if it works.
 
Hi everyone!

I'm using the installation of Open Core from @h9826790 (thanks for that!) here: https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-28255048

Things seem fine, but I have two questions:

1. I currently have Catalina 10.15.5 working and would like to update to 10.15.6, but I can't find anything above 10.15.5 in System Preferences -> Software Update. It just thinks my Mac is up to date with 10.15.5. I've tried the to do the changes to the config.plist as done here to no avail:
What's the best way for me to upgrade to Catalina 10.15.6 you think?

2. Any ideas why my drive with Catalina is called ”T3” in the Open Core boot picker? It's called ”MacOS” in the Finder once booted into it. I think it could be because I once used a Samsung T3 drive to clone my install back to my internal drive, but I don't understand where Open Core would get that name from.

For item 1 - you need to set the VMM flag. See the section "Toggle the VMM flag" in the first post.
 
  • Like
Reactions: star-affinity
Patched BigSur already worked, I'd need also patched BaseSystem.dmg (or any custom Ramdisk DMG) to load from OpenCore
You can try loading from rEFInd. Place these EFI Drivers in the drivers directory and modify the attached nsh startup script to your needs and place it next to your shell.efi tool. Start shell.efi (if your text mode does not work use the attached rEFInd version) and it should load whatever is requested in the startup.nsh script.
 

Attachments

  • Drivers.zip
    42 KB · Views: 130
  • startup.nsh.zip
    874 bytes · Views: 178
  • C06_RefindGOP_x64.efi.zip
    131.8 KB · Views: 129
  • Like
Reactions: jackluke
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.