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

h9826790 · Jul 24, 2022

startergo said:
I have a MacMini 2018 with 5700 EGPU and the performance I worst than on a MacBook Pro 2018 with internal 580 GPU.

Even we can work out the Thunderbolt bandwidth, but Thunderbolt itself is a different technology, and eGPU isn't that mature yet. That may also cost some difference apart from the available bandwidth.

amarmot · Jul 30, 2022

Hey all. This has grown into such a long thread it is difficult to keep track of the latest updates! Are users having good luck with Monterey 12.5 on classic mac pro 5,1 using Martin's package?

~~One thing I found is that custom ACLs on external drives seem messed up after upgrading to Monterey 12.5.~~ (This was a migration assistant problem, not a Monterey issue). I am wondering if there are any other problems others have run into.

amarmot · Aug 2, 2022

albertyy said:
No ! not on my Stock Mac Pro 5.1 !! All the time I have used the OC Legacy Patcher (also Vers. 0.49) there is no HWAcc but Bluetooth support and everything else - that's fine, except just hardware support for the graphics card. That´s right. With the Package (OC 0.80) from h9826790, I have HWAcc on my Radeon RX580. But no Bluetooth and WIFI. Until now I always have to swap the two OC folders, depending on the need. That's superfluous and actually unnecessary. I hoped to get a solution from you that both works. If you want to test it... As a photographer, a always use the DXO Software and export a RAW file with Noise reduction DEEP PRIME. And there is a very very very huge difference with or without the HWAcc with the GraphicCard. I tried the tips from h9826790, th change some settings in the config, plist to activate Bluetooth , but it is not working. And the other fraction with the OCLP 0.49. doesn't seem to have the right settings in their patcher for the Radeon RX580 so I can use the card's hardware support.

I recommend upgrading the wifi. As added bonus it’s blazing fast if your home/office has 1G.

MoerBoer · Aug 2, 2022

amarmot said:
Hey all. This has grown into such a long thread it is difficult to keep track of the latest updates! Are users having good luck with Monterey 12.5 on classic mac pro 5,1 using Martin's package?

One thing I found is that custom ACLs on external drives seem messed up after upgrading to Monterey 12.5. I am wondering if there are any other problems others have run into.

I've updated to 12.5 on 5.1 without any issues with the latest package and config.plist from Martin. I haven't experienced any issues.

amarmot · Aug 3, 2022

I spoke too soon! After installing Monterey 12.5, I am having trouble turning off the VMM flag ~~and resuming SMBios spoofing~~. After installing (with VMM on and SMBios spoofing off), I can reboot through OpenCore to Monterey with no issues. But if I reset ~~UpdateSMBios to true and~~ Cpuid1Mask to all A's, and then reboot to Monterey, it crashes after the boot screen with "Your computer restarted because of a problem. Press a key or wait a few seconds to continue starting up." If I then turn on the VMM flag ~~and turn off SMBios spoofing~~, it can reboot to Monterey.

ssj92 · Aug 3, 2022

Sorry to have started a war but let me add a few details.

This isn't exclusive to final cut pro x. Even a single video in the timeline has this issue. using quicktime to play the video has this issue.

PCIe 2.0 x16 is not the issue. I have many nVidia cards running in PCIe 3.0 x8 and even tried PCIe 3.0 x4 and they can play the video fine.

SSD should not be an issue either. I am using a PCIe adapter that converts PCIe 2.0 x8 to PCIe 3.0 x4. my SSD is running the same speed as a native machine with NVMe PCI 3.0 x4 slot.

Playing this HVEC 8K video on my laptop with RTX 2060 uses 20% of its power. I would find it hard to believe a latest gen AMD card can't even keep up with nVidia's previous GPU in HVEC playback.

I will try davinci resolve and see what happens. If it has same issue, I'll move the RX6800 to my EVGA SR-2 build with dual X5675s (almost same specs as my Mac Pro) and run windows and see if issue is there.

If it's not then maybe something is up macos.

Playback is perfect on my M1 Pro 16" macbook pro.

amarmot · Aug 3, 2022

amarmot said:
I spoke too soon! After installing Monterey 12.5, I am having trouble turning off the VMM flag and resuming SMBios spoofing. After installing (with VMM on and SMBios spoofing off), I can reboot through OpenCore to Monterey with no issues. But if I reset UpdateSMBios to true and Cpuid1Mask to all A's, and then reboot to Monterey, it crashes after the boot screen with "Your computer restarted because of a problem. Press a key or wait a few seconds to continue starting up." If restart and select Windows 10, no problem. If I select Mojave, it gives the "Your computer restarted" error, but then boots. If I then turn on the VMM flag and turn off SMBios spoofing, it can reboot to Monterey.

Update: It seems to be the VMM flag. If I re-enable SMBios spoofing, but leave the VMM flag on, it boots. The problem is when I reset Cpuid1Mask to all A's, it crashes. Thoughts?

czs · Aug 3, 2022

Has anyone experienced an issue where the system will boot fine from a power-on but hangs on reboot?

I am running cMP5,1 + Clover 0.8.0 + High Sierra (10.13.6) + RX 580 Pulse 8GB

amarmot · Aug 3, 2022

czs said:
Has anyone experienced an issue where the system will boot fine from a power-on but hangs on reboot?

I am running cMP5,1 + Clover 0.8.0 + High Sierra (10.13.6) + RX 580 Pulse 8GB

I (and many others) have reported issues with large hard drives in SATA 2 bays not mounting on warm reboot (even though they mount fine with a power-on restart). I assume you are on a SSD though. Is it PCIe or SATA?

czs · Aug 3, 2022

amarmot said:
I (and many others) have reported issues with large hard drives in SATA 2 bays not mounting on warm reboot (even though they mount fine with a power-on restart). I assume you are on a SSD though. Is it PCIe or SATA?

@amarmot: Thanks for responding. This is my first wade into OC so I am doing testing before going full-commit. With that in mind, all testing is being done using a WD gold 4TB SATA spindle drive; in fact I have 2x of these drives installed.

Should I (a) remove one of the drives or even (b) use a smaller drive? If "B", any suggestion as how low I should go?

jameslmoser · Aug 3, 2022

czs said:
@amarmot: Thanks for responding. This is my first wade into OC so I am doing testing before going full-commit. With that in mind, all testing is being done using a WD gold 4TB SATA spindle drive; in fact I have 2x of these drives installed.

Should I (a) remove one of the drives or even (b) use a smaller drive? If "B", any suggestion as how low I should go?

I actually have an 8TB WD drive in one of mine with OpenCore 0.8.0 and have had no issues, but that one is still running Big Sur. The other one I have running Monterey, same OC config, with two 3 TB drives without a problem. I'm not booting from any of them... I have NVME drives for the boot drives.

amarmot · Aug 3, 2022

czs said:
@amarmot: Thanks for responding. This is my first wade into OC so I am doing testing before going full-commit. With that in mind, all testing is being done using a WD gold 4TB SATA spindle drive; in fact I have 2x of these drives installed.

Should I (a) remove one of the drives or even (b) use a smaller drive? If "B", any suggestion as how low I should go?

I guess it depends on your ultimate goal. If you are eventually installing SSDs in SATA bays or PCIe slots, I wouldn't worry about it. It's not a OC issue - it's a general problem with Mac Pros and HDDs. Also, I think you could have other problems with Big Sur and Monterey on HDDs. These newer OSs are designed around APFS, which can have problems on HDDs.

If you are just testing, I might suggest getting a small low-speed SATA SSD, which are very cheap now. You can plug into optical bay or get a sled from OWC.

Sandleford · Aug 4, 2022

Using the prepackaged open core for cMP, system froze and had to hold down the button. When it came back there was no menu bar. Next made the mistake of resetting pram. Now trying to bless the OC partition with the little automator app in Mojave but it does not bless it. I think I was in Catalina when I used it 1st. Was going to boot into recovery mode and reinstall OS 12, but forgot what I was supposed to be doing! I did not see a recovery partition for it in Mac picker, is it hidden?

Is there a terminal command to get it blessed? Anyway, iwhats with mac efi getting corrupt file structure?

h9826790 · Aug 4, 2022

Sandleford said:
Using the prepackaged open core for cMP, system froze and had to hold down the button. When it came back there was no menu bar. Next made the mistake of resetting pram. Now trying to bless the OC partition with the little automator app in Mojave but it does not bless it. I think I was in Catalina when I used it 1st. Was going to boot into recovery mode and reinstall OS 12, but forgot what I was supposed to be doing! I did not see a recovery partition for it in Mac picker, is it hidden?

Is there a terminal command to get it blessed? Anyway, iwhats with mac efi getting corrupt file structure?

Disable SIP in recovery partition, otherwise that little automator app won't work.

In recovery partition, the bless command is

Code:

bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi

(you should mount the EFI partition, and check BOOTx64.efi is there before you run this command)

In general, NVRAM reset should not disable OpenCore. However, that's not 100% guarantee, especially if OC is installed on PCIe SSD.

Since you should able to boot to Mojave without OC. The easiest way for you should be hold Command + R to boot to the Mojave recovery partition -> Disable SIP -> boot back to Mojave, mount the EFI partition -> run the bless app.

Of course, if you are happy to use terminal command, you can do everything in the Mojave recovery partition. That's your choice.

Sandleford · Aug 4, 2022

3

h9826790 said:
Disable SIP in recovery partition, otherwise that little automator app won't work.

In recovery partition, the bless command is

Code:

bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi

(you should mount the EFI partition, and check BOOTx64.efi is there before you run this command)

In general, NVRAM reset should not disable OpenCore. However, that's not 100% guarantee, especially if OC is installed on PCIe SSD.

Since you should able to boot to Mojave without OC. The easiest way for you should be hold Command + R to boot to the Mojave recovery partition -> Disable SIP -> boot back to Mojave, mount the EFI partition -> run the bless app.

Of course, if you are happy to use terminal command, you can do everything in the Mojave recovery partition. That's your choice.

Good to have the command, it comes in handy. The OC efi I dont keep on the PCIe but made sure and got the double chime. A bit of a pain to fix up but not bad. Thanks for putting the package together it's kind of nice to just kick back for the most part and take it easy and enjoy it.

Then I will work on the PC OC rig after some rest.

But a little fooling with some things. Updated to 12.5. Did not notice in the video on updating Catalina/Monterey about reversing the alterations to the config when through with the updates. What effects does it have?

I tried enabling sip and saw 3 alert boxes with no dialog on each login. Have you heard of it?

Did not know DOSdude had an app running before, never used SIP. Never really affected anything that it seemed. "patcherupdaterd"

VertexWolf · Aug 4, 2022

iMac 21" Late 2013 iMac13,1 (NVidia GT 640M)
Monterey 12.5 Install
OpenCore Legacy Patcher 0.4.9

When installing the post-install patches for Kepler and Intel, it bricks the startup where it gets stuck in some error loop.
Reading up on Github, it says that 12.5 dropped some metal and graphic frameworks and to not upgrade to 12.5 if you have an Nvidia graphics card.

Apparently, if you have an Intel card, it will work.

You can't file bug reports on Github, so if anyone knows anyone over at Dortania, please forward them this information.

h9826790 · Aug 4, 2022

Sandleford said:
What effects does it have?

Enable HWAccel and CPU power management (including Turbo Boost)

amarmot · Aug 5, 2022

czs said:
@amarmot: Thanks for responding. This is my first wade into OC so I am doing testing before going full-commit. With that in mind, all testing is being done using a WD gold 4TB SATA spindle drive; in fact I have 2x of these drives installed.

Should I (a) remove one of the drives or even (b) use a smaller drive? If "B", any suggestion as how low I should go?

ps. you might want to check out the forum where the problem about warm restart was discussed. A number of folks tested specific drives and reported which seemed immune:

https://forums.macrumors.com/threads/macpro-5-1-high-capacity-hard-drives.1971809/page-2

William4673 · Aug 5, 2022

Hi all,

Last night I installed stock macOS 12.5 Monterey on a separate SSD from my open core blessed drive, which includes Mojave on it. I made sure to use the cpu Id .Plist edit as well as the smbios. These are now both back to the original setting as per the video tutorial.

My config is Martins 0.8.0, i have a 5,1 dual processor and an rx580 pulse with a new upgraded Bluetooth card (4.0 wifi) that is compatible with the modern operating systems.

So far, everything works fine. I’ve tested basic functionality. iMessage works as well as other apps, no kernel panics yet. But I’m curious about a couple things.

Is 12.5 able to corrupt the rest of the drive it’s stored on? I remember reading that it was taking over machines and blocking the boot picker from seeing any other OSes older than it.

My Bluetooth is not able to be turned on. Where in the plist do I need to edit to reenable this? as I would like to continue using continuity features.

What are some steps to take, and optimizations to make to keep my NVRAM healthy (avoiding KPs) , make it run smooth, and not trash my machine? What are the risks and potential negative effects of running it under 0.8.0, and what can I do to mitigate them?

Thank you all so much for your time. The knowledge this community has is truly stunning. Take care

-W

czs · Aug 6, 2022

amarmot said:
ps. you might want to check out the forum where the problem about warm restart was discussed. A number of folks tested specific drives and reported which seemed immune:

https://forums.macrumors.com/threads/macpro-5-1-high-capacity-hard-drives.1971809/page-2

Thanks @amarmot - that is a great thread...

Unfortunately, I had thought this was just an issue when using large drives as the boot-device but I am finding that neither of my WD Gold 4TB drives show up at all with a warm-boot - only at power-on. And now I have a secondary issue in that the Samsung EVO 870s also exhibit the exact same behavior - not seen on warm-reboot.

Would so love to send Jobs an email that simply read "No dude - sometimes it don't Just Work".

Good times !!!!

Krisz · Aug 7, 2022

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

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 and newer macOS 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 optimized for your setup (e.g. I haven'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 optimization 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:

Boot screen (via GOP for unflashed card, including some Nvidia card)

Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)

HWAccel (H264 / HEVC hardware decode + encode in Mojave and newer macOS)

ability to watch DRM streaming content (Mojave and newer macOS)

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)

NVMe and SATA drives on PCIe card show up as internal

Support for Apple USB SuperDrive

TRIM (regardless trimforce status)

Ability to run non-GUI 32bit software in Catalina

~~Ability to reset NVRAM in boot picker~~ (disabled at this moment to align with the native Apple boot manager)

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]

Ability to boot Catalina / Big Sur / Monterey and the associated Recovery Partition [SurPlus (credit to Syncretic) is included and enabled by default to fix the racing condition in macOS 11.3 or later][MonteRand is also included. another credit to Syncretic][ASPP-Override is included for macOS 12.3, credit to dortania]

Sleep should work (tested on my cMP, but I can't guarantee it also work with your hardware)

Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)

Enable HDMI Audio for some graphic cards

Ability to monitor modern AMD GPU's temperature (by using the attached RadeonGadget. Credit to Aluveitie)

It's impossible for me (and other voluntary helpers) 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, credit to Dosdude, password "rom")

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, analysis shows that depends on hard drives config. It's hard to explain which exact scenario may hit this bug. So, please avoid to install this package on NVMe. You can install this package on ANY SATA drive with virtually no performance lost, 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 packages 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.

I tried to make the installation as simple as possible. However, I still demand you to learn some very basic skills. Those skills are very useful in the recovery process if something goes wrong. Anyway, here is what you need to do

[Optional] 3x NVRAM reset to avoid some unknown issues.

Disable SIP (must do, especially if you performed step 1)

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.)

Follow the steps in this video (please turn on and read the subtitle)

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

Reboot

For existing OpenCore users, you may follow the step in this video to update OpenCore [For those who installed OC onto the Windows drive, please make sure you only replace the OC files, but not the whole EFI folder]

Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this. [Depreciated in 0.7.6, which Retina should be enabled automatically on 4K monitor]

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, ~~Big Sur~~ and Monterey, please follow the steps in this video. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]

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: To enable legacy BT support in the latest unsupported OS, you may turn on both BlueToolFixUp and BlueTooth-Spoof kext.

Additional option 6: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's defaulted to be disabled. If you want to re-enable SIP, please follow the steps in this video. (please turn on the English subtitle when you watch this video, some useful info at there)

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:298 Apr 2022, OpenCore 0.8.0, Lilu 1.6.0, WhateverGreen 1.5.8, RadeonSensor 0.3.1, AppleALC 1.6.9, FeatureUnlock 1.0.6, SurPlus, MonteRand, ASPP-Override]

Hi! A new version will not be uploaded?

h9826790 · Aug 7, 2022

Krisz said:
Hi! A new version will not be uploaded?

Most likely not for this two months, because I will move to another country soon.

If there is anything that need urgent update (e.g. need some new patch for latest macOS), then I will see if I can release a new config for the existing 0.8.0 package first (this is relatively simple and safe).

If must use a newer version of OC, I will need more time to do that.

mode11 · Aug 7, 2022

@h9826790 If I reset my NVRAM, will I need to re-bless OC (running your 0.8.0)?

I have OC on my Windows SSD, which sits in Bay 1. My Mac defaults to bay 1 after an NVRAM reset, and I seem to recall that OC would self-bless on first boot. Or is this wrong?

Krisz · Aug 7, 2022

h9826790 said:
Most likely not for this two months, because I will move to another country soon.

If there is anything that need urgent update (e.g. need some new patch for latest macOS), then I will see if I can release a new config for the existing 0.8.0 package first (this is relatively simple and safe).

If must use a newer version of OC, I will need more time to do that.

Ok, thanks for your reply
now I use the opencore 0.8.0 plist file for o.c 0.8.2, unfortunately I don't understand the config

I'll wait until you get over the move.
Good luck with your new home!

h9826790 · Aug 7, 2022

mode11 said:
@h9826790 If I reset my NVRAM, will I need to re-bless OC (running your 0.8.0)?

I have OC on my Windows SSD, which sits in Bay 1. My Mac defaults to bay 1 after an NVRAM reset, and I seem to recall that OC would self-bless on first boot. Or is this wrong?

It depends on the users hard drive config.

In your case, OC should remain blessed even you perform a NVRAM reset.

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

macrumors P6

macrumors member

macrumors member

macrumors regular

macrumors member

macrumors regular

macrumors member

macrumors newbie

macrumors member

macrumors newbie

macrumors 6502a

macrumors member

macrumors member

macrumors P6

macrumors member

macrumors newbie

macrumors P6

macrumors member

macrumors newbie

macrumors newbie

macrumors member

macrumors P6

macrumors 68000

macrumors member

macrumors P6

Our Staff