MP 1,1-5,1 Activate AMD hardware acceleration

[Stex]

If you still have Mojave, pull out the Big Sur drive, then your cMP should boot to Mojave automatically.

Then you can boot to the recovery partition, disable SIP, and re-install OC etc.

Or you can swap in your original GPU, hold option to boot, and select EFI from there. That should be your OpenCore. And then you can boot to Big Sur again, and mount the EFI partition, and re-bless OC.

Thanks for the immediate reply, much appreciated.

I have a CCC clone of the original boot drive with Mojave. The OC EFI is currently on another SSD, not on the Big Sur SSD. Should I remove both of those drives or only the Big Sur drive?

 

[h9826790]

Thanks for the immediate reply, much appreciated.

I have a CCC clone of the original boot drive with Mojave. The OC EFI is currently on another SSD, not on the Big Sur SSD. Should I remove both of those drives or only the Big Sur drive?

Just the Big Sur drive should be good enough.

OC itself is good, the problem is that your setup is now bypassed OC, but try to load Big Sur directly.

Simply swap in the Mojave drive should allow you to perform all necessary recovery actions easily.

 

[Stex]

Just the Big Sur drive should be good enough.

OC itself is good, the problem is that your setup is now bypassed OC, but try to load Big Sur directly.

Simply swap in the Mojave drive should allow you to perform all necessary recovery actions easily.

Followed the above instructions and was able to fix the issue as you expected. Thanks very much h9826790!

Big Sur is running fine so far (screenshot attached), but I need to test more applications etc. For what it's worth, ran Geekbench 5 with Big Sur and, compared to Mojave, got very similar results for CPU and a better result (+10%) for Metal.

The only issues I encountered so far (all previously reported in this thread):

1- The boot screen works well, but only shows names for recovery partitions and not for the actual OS partitions. I have several backups/clones (1 High Sierra, 2 Mojaves, 1 Big Sur) so it can be a bit confusing when switching boot drives without the text reference. Will review mor carefully previous posts with instructions on how to inject the names, although it sounded a bit intimidating to me!

2- I can confirm that the RX580 own fans are running at faster speed than with Mojave. Not sure if others have found a solution for this at this time. Or maybe it's just the nature of the upgrade, this being a more GPU-intensive OS?

3- I still have the original cMP 4,1 Wifi-Bluetooth internal card. I did not have to edit the plist to activate it (as shown on the video) - it was active and functional from the first launch of Big Sur. On the other hand, a Hideez 4.0 Bluetooth external dongle that I used with Mojave does not work at this time in Big Sur. The manufacturer states that there are issues with Big Sur. I might finally look into replacing the old card once and for all!

 

[h9826790]

Followed the above instructions and was able to fix the issue as you expected. Thanks very much h9826790!

Big Sur is running fine so far (screenshot attached), but I need to test more applications etc. For what it's worth, ran Geekbench 5 with Big Sur and, compared to Mojave, got very similar results for CPU and a better result (+10%) for Metal.

The only issues I encountered so far (all previously reported in this thread):

1- The boot screen works well, but only shows names for recovery partitions and not for the actual OS partitions. I have several backups/clones (1 High Sierra, 2 Mojaves, 1 Big Sur) so it can be a bit confusing when switching boot drives without the text reference. Will review mor carefully previous posts with instructions on how to inject the names, although it sounded a bit intimidating to me!

2- I can confirm that the RX580 own fans are running at faster speed than with Mojave. Not sure if others have found a solution for this at this time. Or maybe it's just the nature of the upgrade, this being a more GPU-intensive OS?

3- I still have the original cMP 4,1 Wifi-Bluetooth internal card. I did not have to edit the plist to activate it (as shown on the video) - it was active and functional from the first launch of Big Sur. On the other hand, a Hideez 4.0 Bluetooth external dongle that I used with Mojave does not work at this time in Big Sur. The manufacturer states that there are issues with Big Sur. I might finally look into replacing the old card once and for all!



View attachment 1715270

1) You can press F10 (you may need to press Fn + F10, depends on your keyboard) to capture the boot picker. Then the screen capture will be stored in the EFI partition.

Please post the picture here, so that easier to understand your problem.

2) My RX580 is in the box now (may be I should sell it now, the price seems quite high ), and I never use it in Big Sur. However, from memory, you are not the only one to report this issue. May be driver related.

 

[Stex]

1) You can press F10 (you may need to press Fn + F10, depends on your keyboard) to capture the boot picker. Then the screen capture will be stored in the EFI partition.

Please post the picture here, so that easier to understand your problem.

2) My RX580 is in the box now (may be I should sell it now, the price seems quite high ), and I never use it in Big Sur. However, from memory, you are not the only one to report this issue. May be driver related.

Screen capture of Boot Picker attached here.

I also just found out that audio over Displayport is not working. I have two monitors connected via Displayports. Should I to try the multiscreen suggestion from your video in post #1314 to see if it fixes the audio issue?

 

[h9826790]

Screen capture of Boot Picker attached here.

I also just found out that audio over Displayport is not working. I have two monitors connected via Displayports. Should I to try the multiscreen suggestion from your video in post #1314 to see if it fixes the audio issue?

View attachment 1715330

Please try the following steps and see if it helps to fix the boot drive's ident.

1) Keep your Mojave drive in the cMP

2) Follow the steps in this video to properly uninstall OpenCore

3) Reboot to Mojave natively without OC (make sure SIP is still disabled, if not, please do that)

4) Follow the steps in post #1314 again to install the latest 0.6.5 DRM fix version

Activate AMD hardware acceleration

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.7.9] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...

forums.macrumors.com

Let's see if the boot picker will able to show the correct disk name.

If not, then we may need to use the disklabel tool. That may be considered more complicated for most users.

OpenCore on the Mac Pro

Download the OpenCore package: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true 1. Open terminal and type: disklabel disklabel: usage: One of -status -create [-msize=] [owner-uid=] [owner-gid=] [dev-name=] [owner-mode=] [other-property=] -destroy...

forums.macrumors.com

 

[h9826790]

I also just found out that audio over Displayport is not working. I have two monitors connected via Displayports. Should I to try the multiscreen suggestion from your video in post #1314 to see if it fixes the audio issue?

You mean the DisplayPort audio option isn't avail at here?

Can you see if the driver is loaded for your graphic card?

As long as you are running Big Sur, you are free to try that multi-monitor fix mod. But once you do that, you will lost HWAccel in Mojave (of course, you can always revert the changes when you need it).

 

[star-affinity]

I have a question about your @h9826790 latest ”0.6.5 DRM fix” – coming from the 0.6.4 package I can no longer use the mouse to change which drive or partition to start from in the OpenCore boot picker. This is a problem when using a Bluetooth keyboard since it doesn't work there. Is this perhaps something that can be enabled and disabled in the config.plist for OpenCore?

 

[IceHouse]

I have a question about your @h9826790 latest ”0.6.5 DRM fix” – coming from the 0.6.4 package I can no longer use the mouse to change which drive or partition to start from in the OpenCore boot picker. This is a problem when using a Bluetooth keyboard since it doesn't work there. Is this perhaps something that can be enabled and disabled in the config.plist for OpenCore?

Take a look a few comments ago: Reactivate Mouse Pointer in OpenCanopy

 

[h9826790]

I have a question about your @h9826790 latest ”0.6.5 DRM fix” – coming from the 0.6.4 package I can no longer use the mouse to change which drive or partition to start from in the OpenCore boot picker. This is a problem when using a Bluetooth keyboard since it doesn't work there. Is this perhaps something that can be enabled and disabled in the config.plist for OpenCore?

That's a known issue, and will be fixed in the next release.

Activate AMD hardware acceleration

Thanks for the report, I will make picker attribute = 19 as default in the future package release.

forums.macrumors.com

 

[cageytiger]

I've ran into an odd problem - everything boots fine using the prepared package, but my Titan Ridge card only works in about 1 in 5 boots. The card is visible in system, but connecting anything/drives (TB3 or USB) just won't mount. I have to restart until it shows up, once it's there, it works great until I shut down.

Have I missed something?

 

[h9826790]

I've ran into an odd problem - everything boots fine using the prepared package, but my Titan Ridge card only works in about 1 in 5 boots. The card is visible in system, but connecting anything/drives (TB3 or USB) just won't mount. I have to restart until it shows up, once it's there, it works great until I shut down.

Have I missed something?

Is that a flashed card?

 

[cageytiger]

Is that a flashed card?

Yes - I flashed it myself. It shows up in System profiler as 40GB/s, FW 23.0, would it work at all if I made a mistake in flashing? I have a TB3 only drive so the TB is 100% working, when it works.

 

[DigitaLife]

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package already updated to 0.6.5]

For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina for dual processor cMP.

I don't mind you guys discuss anything about this package, but I have no plan to provide any explanation about OpenCore at here. If you want to know more, please join cdf's OpenCore thread. For new joiners, please make sure read through the FAQ in post #1 before you ask anything.

The attached packaged included Clover Configurator and a complete preconfigured OpenCore. All credits goes to the developer teams. If you want to show your support, please give them donation (declaration of interest： I am NOT in any of their developer teams)

For Clover Configurator and OpenCore developers teams, please let me know if you want me to remove the associated software inside my attachment in this post.

This is a "one package fit all" solution. So, it's designed to fit as much setup as possible, which may not be optimised for your setup (e.g. I did't provide HiDPI boot screen, for those who are running 4K screen, the Apple logo may be quite small during boot). You have to do the optimisation by yourself (details in the OpenCore manual, some info also available in cdf's OpenCore thread).

Anyway, for those who have RX 460 or newer AMD GPU, this package should gives you:

1. Boot screen (via GOP for unflashed card, including some Nvidia card)
2. Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
3. HWAccel (H264 / HEVC hardware decode + encode in Mojave or later)
4. ability to watch DRM streaming content (Mojave and later)
5. Boot picker (only support EFI systems, tested with Apple wired keyboard, Magic Mouse, and Magic Keyboard, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
6. NVMe and SATA drives on PCIe card show up as internal
7. Support for Apple USB SuperDrive
8. TRIM (regardless trimforce status)
9. Ability to run non-GUI 32bit software in Catalina
10. Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
11. Ability to run any natively supported ancient OSX with modern graphic card e.g. Radeon VII in 10.6.8 (only can display, no acceleration) [Update 5th May 2020: Sierra and High Sierra may not fully supported yet. Thanks for pierrox's report]
12. Ability to boot Catalina / Big Sur Recovery Partition
13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your hardware)

It's impossible for me to test every single function in all situations. So, as usual, use at your own risk. But you are welcome to report back if there is any problem / error.

Pre-installation:

• Recommend to backup your BootROM between step 1 and 2 (e.g. by using ROMTool)
• If you want to test OpenCore, you can install this package onto a bootable USB thumb drive.
• Quite a few users reported that can't boot OpenCore from NVMe, please avoid to install this package on NVMe. You can install this package on ANY SATA drive, not necessary your boot drive.
• If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then remove BOOT and OC folders inside the EFI folder on EFI partition.
• If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
• For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
• If you installed Lilu for whatever reason (e.g. because of innie), or applied my previous non-OpenCore HWAccel mod, please remove them or revert them. For Lilu + WEG, that means delete Lilu.kext in /Library/Extensions/ and reboot (caution: these kexts may be installed in System/Library/Extensions/ as well). For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework. Warning: My package already have Lilu and WEG included, "double installation" of these kexts will cause macOS boot failure.
• For PULSE RX580, users reported that only can see boot screen when boot from gaming mode. There may be no UEFI GOP in the compute mode's ROM.

Anyway, I tried to make the installation as simple as possible. Here is what you need to do

1. [Optional] 3x NVRAM reset to avoid some unknown issues.
2. Disable SIP (must do, especially if you performed step 1)
3. Download the attachment in this post (Some users reported 0.6.1 package has compatibility issue. You may download the 0.5.9 package if you prefer that, same installation procedures)
4. Follow the steps in this video
   
5. Spoiler: Multi monitors fix for Big Sur

   For Big Sur only, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
   
6. Reboot

For existing OpenCore users, you may follow the step in this video to update OpenCore

Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this.

Additional option 2: If you have a flashed Thunderbolt 3 card, you can install that in slot 4, then enable Thunderbolt 3 support by doing this.

Additional option 3: If you want to enable the ability to install / update Catalina [Update: Thanks for cdf's finding. If you are with the 0.6.3 (and newer) package, and want to install Big Sur, your 5,1 should able to do that "natively". No need to touch the VMM flag etc]

Additional option 4: If you have legacy wifi card, you may try the follow steps to re-activate the old wifi card in Big Sur (only avail in my 0.6.4 package or above)

Additional option 5: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's default to be disabled. If you want to re-enable SIP, please follow the steps in this video.

For FCP(X) users, if you want to export HEVC video by using HWAccel, you will need Compressor.
[N.B. The setting MUST identical to the one that I show in the video. Otherwise, HEVC hardware encoding may not work]

If you want to completely uninstall my OpenCore package, please follow the steps in this video.

N.B. Unflashed graphic card means "the ROM is never modified". For those who bought used card, and can't see the boot screen, most likely the last user flashed the card with modified ROM (e.g. downvolt for mining). In this case, you can go to TechPowerUp to find a ROM that fit your own card, and flash it.

P.S. If you want to support my work, please donate via the following link. Million thanks in advance! https://www.paypal.com/paypalme/martinlo420

[Last update: 7 Jan 2021, OC 0.6.5, Lilu 1.5.1 MASTER, WEG 1.4.7 MASTER]

Hi, I just moved Catalina to an NVMe SSD (on HighPoint SSD7101A-1), leaving Mojave on a SATA SSD (Bay #1) and installed OC on the EFI volume in a SATA SSD (Bay #2).
I installed your OC 0.6.5 package (I have a Radeon VII) but I don't understand why, after installing the HighPoint NVMe Controller Driver, the NVMe disks are seen (icons) as external disks.
Could you please help solve this little problem?
Thanks in advance!

 

[amstel78]

Hi, I just moved Catalina to an NVMe SSD (on HighPoint SSD7101A-1), leaving Mojave on a SATA SSD (Bay #1) and installed OC on the EFI volume in a SATA SSD (Bay #2).
I installed your OC 0.6.5 package (I have a Radeon VII) but I don't understand why, after installing the HighPoint NVMe Controller Driver, the NVMe disks are seen (icons) as external disks.
Could you please help solve this little problem?
Thanks in advance!

You can use Innie to get NVME drives to appear as internal. This happened to my 5,1 running Mojave with two OWC PCIe Accelsior SSD cards installed. I believe anything that's not connected directly to the SATA 3g drive bays are considered external devices by OSX.

Innie: A fix for PCI drives seen as external

It is well known that macOS sees PCI drives in a cMP as external. In the past, there have been several attempts to fix this annoyance, typically through codeless kexts and driver patches. However, these approaches are far from perfect. Codeless kexts affect the properties of all (even non-PCI)...

r.tapatalk.com

 

[DigitaLife]

You can use Innie to get NVME drives to appear as internal. This happened to my 5,1 running Mojave with two OWC PCIe Accelsior SSD cards installed. I believe anything that's not connected directly to the SATA 3g drive bays are considered external devices by OSX.

Innie: A fix for PCI drives seen as external

It is well known that macOS sees PCI drives in a cMP as external. In the past, there have been several attempts to fix this annoyance, typically through codeless kexts and driver patches. However, these approaches are far from perfect. Codeless kexts affect the properties of all (even non-PCI)...

r.tapatalk.com

I have tried several times to install Innie 1.3.0 following the guide but without success!
I have tried with both Catalina and Mojave but nothing!
Any suggestions on how I can fix this problem?
Thanks in advance!

 

[amstel78]

I have tried several times to install Innie 1.3.0 following the guide but without success!
I have tried with both Catalina and Mojave but nothing!
Any suggestions on how I can fix this problem?
Thanks in advance!

Sorry, I can't assist further. I installed Innie using MyBootManager via RefindPlus. I suggest you ping the author of the post I linked to, or drop a line via GitHub.

 

[nigel1210]

I've installed Open Core 0.65 DRM Fix but using the check in videoproc it says that video acceleration isn't working.

I've tried to get it working following the steps in the hardware acceleration thread on mac rumours but I get to step 14 and get this error - nvram: Error setting variable - 'boot-args': (iokit/common) general error

I was under the impression that video acceleration should just work after using that install of open core. I'm currently using an unflashed RX580 on a 2009 >2010 dual Cpu.

Any ideas why this is happening and how to fix it?

 

[h9826790]

I've installed Open Core 0.65 DRM Fix but using the check in videoproc it says that video acceleration isn't working.

I've tried to get it working following the steps in the hardware acceleration thread on mac rumours but I get to step 14 and get this error - nvram: Error setting variable - 'boot-args': (iokit/common) general error

I was under the impression that video acceleration should just work after using that install of open core. I'm currently using an unflashed RX580 on a 2009 >2010 dual Cpu.

Any ideas why this is happening and how to fix it?

As per the discussion on Facebook. You should not mix use the method in post #1 and post #1314.

What you should do is just download the package and follow the steps in post #1314.

Post #1 is mainly the FAQ (you should read all that).

 

[star-affinity]

Just went to System Preferences -> Software Update and found the Big Sur 10.2 update that showed as being over 3.5 GB.

I clicked to do the update, but instead of downloading it my computer restarted directly and when I got to the OpenCore boot picker I could see "Macintosh HD" there which I didn't have before (my drive with macOS is called "MacOS"). My Window 10 drive was highlighted as the one too boot from and I also couldn't use my wired keyboard to switch between drives, do now it seems I can only startup in Windows 10.

Any ideas why I can't switch between drives and partitions too boot from in the boot picker all of a sudden?

Forget it – my keyboard wasn't connected on the other end. 😆
Not possible to delete posts? 🤔

 

[Stex]

Please try the following steps and see if it helps to fix the boot drive's ident. [...]

Thanks for these suggestions. I had to wait on trying them as I had several deadlines and did not want to risk unexpected problems. Will try these steps in the next days to see if the boot screen shows the proper names for each drive.

As far as your answer to my question about the Displayport audio issue I had - sometimes after startup (cold boot I think it is referred as?) that option is not present at all under sound-system preferences. But when I do an immediate restart (warm boot?) the Displayport option shows correctly and works properly. Not quite sure why, but the restart seems to make it available.

Quick new question - I wonder if the process of updating to Big Sur 11.2 requires us to simply go through the regular software update process or do we need to take some special steps?

 

[cdf]

I wonder if the process of updating to Big Sur 11.2 requires us to simply go through the regular software update process or do we need to take some special steps?

No extra steps are necessary with an appropriate configuration.

 

[whackit]

Quick new question - I wonder if the process of updating to Big Sur 11.2 requires us to simply go through the regular software update process or do we need to take some special steps?

I upgraded to 11.2 with no apparent issue. Running 0.6.5 in standard form. Process was: Kick off upgrade from system preferences, on first reboot select "Mac Installer" if using bootpicker although would probably just self select if you didn't. After next reboot select your boot drive. Wait for machine to do it's thing through a few rebots and dark screens and Voila. 11.2.

 

[Stex]

Thank you both for the quick replies.

I currently still have SIP disabled. Would that be an issue? And... I wonder what is a best procedure, to re-enable it after successfully running OC via the (wonderful) package from h9826790?

 

[LFO8]

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package already updated to 0.6.6]

For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina for dual processor cMP.

I don't mind you guys discuss anything about this package, but I have no plan to provide any explanation about OpenCore at here. If you want to know more, please join cdf's OpenCore thread. For new joiners, please make sure read through the FAQ in post #1 before you ask anything.

The attached packaged included Clover Configurator and a complete preconfigured OpenCore. All credits goes to the developer teams. If you want to show your support, please give them donation (declaration of interest： I am NOT in any of their developer teams)

For Clover Configurator and OpenCore developers teams, please let me know if you want me to remove the associated software inside my attachment in this post.

This is a "one package fit all" solution. So, it's designed to fit as much setup as possible, which may not be optimised for your setup (e.g. I did't provide HiDPI boot screen, for those who are running 4K screen, the Apple logo may be quite small during boot). You have to do the optimisation by yourself (details in the OpenCore manual, some info also available in cdf's OpenCore thread).

Anyway, for those who have RX 460 or newer AMD GPU, this package should gives you:

1. Boot screen (via GOP for unflashed card, including some Nvidia card)
2. Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
3. HWAccel (H264 / HEVC hardware decode + encode in Mojave or later)
4. ability to watch DRM streaming content (Mojave and later)
5. Boot picker (only support EFI systems, tested with Apple wired keyboard, Magic Mouse, and Magic Keyboard, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
6. NVMe and SATA drives on PCIe card show up as internal
7. Support for Apple USB SuperDrive
8. TRIM (regardless trimforce status)
9. Ability to run non-GUI 32bit software in Catalina
10. Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
11. Ability to run any natively supported ancient OSX with modern graphic card e.g. Radeon VII in 10.6.8 (only can display, no acceleration) [Update 5th May 2020: Sierra and High Sierra may not fully supported yet. Thanks for pierrox's report]
12. Ability to boot Catalina / Big Sur Recovery Partition
13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your hardware)
14. Possible to run 8x32GB RAM in macOS

It's impossible for me to test every single function in all situations. So, as usual, use at your own risk. But you are welcome to report back if there is any problem / error.

Pre-installation:

• Recommend to backup your BootROM between step 1 and 2 (e.g. by using ROMTool)
• If you want to test OpenCore, you can install this package onto a bootable USB thumb drive.
• Quite a few users reported that can't boot OpenCore from NVMe, please avoid to install this package on NVMe. You can install this package on ANY SATA drive, not necessary your boot drive.
• If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then remove BOOT and OC folders inside the EFI folder on EFI partition.
• If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
• For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
• If you installed Lilu for whatever reason (e.g. because of innie), or applied my previous non-OpenCore HWAccel mod, please remove them or revert them. For Lilu + WEG, that means delete Lilu.kext in /Library/Extensions/ and reboot (caution: these kexts may be installed in System/Library/Extensions/ as well). For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework. Warning: My package already have Lilu and WEG included, "double installation" of these kexts will cause macOS boot failure.
• For PULSE RX580, users reported that only can see boot screen when boot from gaming mode. There may be no UEFI GOP in the compute mode's ROM.

Anyway, I tried to make the installation as simple as possible. Here is what you need to do

1. [Optional] 3x NVRAM reset to avoid some unknown issues.
2. Disable SIP (must do, especially if you performed step 1)
3. Download the attachment in this post (Some users reported 0.6.1 package has compatibility issue. You may download the 0.5.9 package if you prefer that, same installation procedures)
4. Follow the steps in this video
   
5. Spoiler: Multi monitors fix for Big Sur

   For Big Sur only, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
   
6. Reboot

For existing OpenCore users, you may follow the step in this video to update OpenCore

Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this.

Additional option 2: If you have a flashed Thunderbolt 3 card, you can install that in slot 4, then enable Thunderbolt 3 support by doing this.

Additional option 3: If you want to enable the ability to install / update Catalina [Update: Thanks for cdf's finding. If you are with the 0.6.3 (and newer) package, and want to install Big Sur, your 5,1 should able to do that "natively". No need to touch the VMM flag etc]

Additional option 4: If you have legacy wifi card, you may try the follow steps to re-activate the old wifi card in Big Sur (only avail in my 0.6.4 package or above)

Additional option 5: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's default to be disabled. If you want to re-enable SIP, please follow the steps in this video.

For FCP(X) users, if you want to export HEVC video by using HWAccel, you will need Compressor.
[N.B. The setting MUST identical to the one that I show in the video. Otherwise, HEVC hardware encoding may not work]

If you want to completely uninstall my OpenCore package, please follow the steps in this video.

N.B. Unflashed graphic card means "the ROM is never modified". For those who bought used card, and can't see the boot screen, most likely the last user flashed the card with modified ROM (e.g. downvolt for mining). In this case, you can go to TechPowerUp to find a ROM that fit your own card, and flash it.

P.S. If you want to support my work, please donate via the following link. Million thanks in advance! https://www.paypal.com/paypalme/martinlo420

[Last update: 3 Feb 2021, OC 0.6.6, Lilu 1.5.1, WEG 1.4.7]

Hi Martin, I am currently running your OC 0.6.3 package with wifi fix to run Big Sur on my 5,1 MP. Thanks!!

So thinking about updating to OC 0.6.6 Can I just replace the BOOT and OC folders with the ones from your 0.6.6 package to update or will that run me into wifi (or other) problems?