Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

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.
ALF07 said:
Hi all

I'm on a Mac pro 4,1>5,1, with radeon VII on Mojave.

Currently trying to move up to Monterey or even just Catalina using Martin Lo's OpenCore 0.8.9 package.

I followed the video with the edits made in the code and downloaded Monterey from the app store, went to install and it told me i didn't have the correct firmware.

I can't figure out why and for some reason i can't download Catalina from the Appstore

any idea?

Thanks
Click to expand...
There are two parameters need to be changed.

1) enable VMM by changing that A to C
2) disable SMBIOS spoofing by changing the true to false

It seems you only did 1 but not 2.
 
  • Like
Reactions: ALF07
blauesliebe7 said:
I have recently conducted a transcode process on a 300 seconds-long 4K H264 video file, and the output was successfully converted to High-Efficiency Video Codec (HEVC) without any noticeable rendering delays or system degradation issues. Although I did not encounter any rendering lags during the transcoding process, I do unfortunately experience major performance degradation when utilizing resource-intensive software such as Final Cut Pro X, Adobe Premiere, or Topaz AI Enhancer during the rendering process. I guess it's just me.
Click to expand...
Thanks for the test and report. So, we now know your issue is not directly HWAccel related, but something else.

The first suspect would be some updated kext inside in the new package.
 
  • Like
Reactions: blauesliebe7
Sandleford said:
I used this and had the machine running well. Wifi one day was not working so rebooted and now its touchy with usb somehow more than it was before. USB seemed a little off before. Meaning it will go half way through the verbose then reboot with usb items plugged in then with usb unplugged it will make to desktop. Did the ASD and showed no problem. Wifi does not work in windows either and windows will often not make it to desktop ending in bluescreen. But its not always the case with USB sometimes get makes it to desktop... Could be motherboard or something usb related?

Update I really dont know, now it seems a little better. Tried zapping the Pram but not much change at least the hardware monitor app is not giving notification of taking too long to start up and there may be a hardware problem.
Still can take a couple times to get to the desktop, reboots, but finally does. Wifi still not working, ordered another as it was only selling for nine bucks, been using the 94360
Click to expand...
The USB problem can be quite intermittent indeed. However, usually it won't stop the machine to boot to desktop, but just disabled the internal BT.

Anyway, apart from NVRAM reset, please also try SMC reset. I know some cases the cMP can't boot to desktop, which actually fixed by SMC reset, but not NVRAM reset.
 
  • Like
Reactions: Dayo
@h9826790 in the 0.9.0 config file the lines 658, 659 repeat the exact same <key>ProvideCurrentCpuInfo</key> from the two lines before.

Stumbled over this while comparing my currently installed 0.8.8 to your latest 0.9.0 config.plist to copy over some adjustments from my running configuration before updating.

Is this an intended hack or something that can be cleaned out while I'm on it without breaking anything?

I am on a cMP dual X5690 and dual boot Monterey/Win10.
 
matmilano said:
@h9826790 in the 0.9.0 config file the lines 658, 659 repeat the exact same <key>ProvideCurrentCpuInfo</key> from the two lines before.

Stumbled over this while comparing my currently installed 0.8.8 to your latest 0.9.0 config.plist to copy over some adjustments from my running configuration before updating.

Is this an intended hack or something that can be cleaned out while I'm on it without breaking anything?

I am on a cMP dual X5690 and dual boot Monterey/Win10.
Click to expand...
Thanks for the report, will fix that on the next release. Interesting that ocvalidat tool doesn't count this an error.
 
h9826790 said:
Thanks for the report, will fix that on the next release. Interesting that ocvalidat tool doesn't count this an error.
Click to expand...
Also interesting is that PlistEdit Pro app that I always use, automatically fixes the duplication error :
Screenshot 2023-03-17 at 00.57.59.png

I've been using this App for a long time and never had issues with bad formatting. It takes care of all formatting has always produced valid plist files and so so easy to use. The App focuses the user on the content and not worry about formatting (like <true/>, ,key>, </dict>, etc, etc) as all that is done for you.

All I did was open you config.plist file in PlistEdit Pr App, simply saved it as config-pro.plist and re-opened in BBEdit App and the duplication was gone.
 
  • Like
Reactions: h9826790
Mid-2011 27" iMac with 3.4ghz i7, a 250gb SSD, and an AMD Radeon HD6970M 2GB VRAM card. Currently running OCL v0.6.1 (latest) enabling MacOS Mojave in an HFS+ volume. Everything appears in order, except that hardware-acceleration (i.e., OpenGL) is turned off. Is there a quick way to enable it?

(I have multiple backups, external boot volumes, know how to use Terminal, etc. Fire away.)
 
Minghold said:
Mid-2011 27" iMac with 3.4ghz i7, a 250gb SSD, and an AMD Radeon HD6970M 2GB VRAM card. Currently running OCL v0.6.1 (latest) enabling MacOS Mojave in an HFS+ volume. Everything appears in order, except that hardware-acceleration (i.e., OpenGL) is turned off. Is there a quick way to enable it?

(I have multiple backups, external boot volumes, know how to use Terminal, etc. Fire away.)
Click to expand...
First, OpenGL have absolutely nothing to do with the VideoToolbox API.

Second, only Polaris and newer GPUs have the ASICs that are required by VideoToolBox API for hardware assistance of video conversion/compression/decoding/grading/pixel transfer, what is called here AMD Hardware Acceleration.

How you gonna enable something that your hardware do not have?
 
  • Like
Reactions: 0134168 and h9826790
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.9.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 (for mounting the EFI partition only, please do NOT use it to edit the OpenCore config) 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:
  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 and newer macOS)
  4. ability to watch DRM streaming content (Mojave and newer macOS)
  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 / 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][AVXPel is also included. another credit to Syncretic][ASPP-Override is included for macOS 12.3, credit to dortania]
  13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your setup)
  14. Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)
  15. Enable HDMI Audio for some graphic cards
  16. 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
  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 (if the newer package has compatibility issue. You may download the older package, same installation procedures.)
  4. Follow the steps in this video (please turn on and read the subtitle)
  5. 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.
  6. 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:7 Mar 2023, OpenCore 0.8.9, Lilu 1.6.4, WhateverGreen 1.6.4, RadeonSensor 0.3.1, AppleALC 1.7.8, FeatureUnlock 1.1.3, SurPlus, AVXpel, ASPP-Override]
Click to expand...


It had no affect on my Adobe Premiere H264 Export. A 10min export of 1080p video was still taking the same amount of time as before. Using Vega 56 card. There no encoder acceleration.

Specs:
OS Mojave 10.14.6
Mac Pro 2010 (5'1) -
2 x 2.66 GHz 6-Core Intel Xeon
96 GB 1333 MHz DDR3
NVME boot 2TB and NMVE footage drive 2TB -
Boot Rom 144.0
 
royaltimetv said:
It had no affect on my Adobe Premiere H264 Export. A 10min export of 1080p video was still taking the same amount of time as before. Using Vega 56 card. There no encoder acceleration.

Specs:
OS Mojave 10.14.6
Mac Pro 2010 (5'1) -
2 x 2.66 GHz 6-Core Intel Xeon
96 GB 1333 MHz DDR3
NVME boot 2TB and NMVE footage drive 2TB -
Boot Rom 144.0
Click to expand...
As far I can recall, back in Mojave days, Adobe never used OpenCL or Metal to accelerate encoding/decoding...they were a CUDA house (i.e. NVIDIA). So it not a surprise.

If you have access to FCPX, you will notice the speed of encode/decode done via the AMD GPU.
 
is the Lilu kext going into "user/Library/Extensions" or system/Library/Extensions ?. There is no extension folder in the user/library, so I had to create it.
 
royaltimetv said:
It had no affect on my Adobe Premiere H264 Export. A 10min export of 1080p video was still taking the same amount of time as before. Using Vega 56 card. There no encoder acceleration.

Specs:
OS Mojave 10.14.6
Mac Pro 2010 (5'1) -
2 x 2.66 GHz 6-Core Intel Xeon
96 GB 1333 MHz DDR3
NVME boot 2TB and NMVE footage drive 2TB -
Boot Rom 144.0
Click to expand...
Did you check if H264 / HEVC HWAccel is correctly activated?

It seems you use the depreciated kext method, but not by installing OpenCore. Am I correct?
 
Stu Forbes said:
Hey guys just a quick question, I'm running the 0.8.6. oc package on my 4,1->5,1 running monterey no problem with the wifi bluetooth upgrade, the only issue i have it that if i go the the about this mac section the serial number says unavailable anyone know why?
Click to expand...
@Macschrauber was 100% right the board did not have a serial number. I used the Blank Board Serializer and flashed the serial number that was on the sticker on the back of my Mac Pro and now it shows up correctly
 
Hi guys I just finished Installing Opencore on my cMP 5,1. I have boot screen Menu, everything works fine but I have just H264 HW/A no HEVC , I saw systems like my mac pro even lower that they could activate HEVC


Screen Shot 2023-03-29 at 3.32.01 AM.png



Screen Shot 2023-03-29 at 3.47.50 AM.png




it should be like this


Screen Shot 2023-03-29 at 3.46.00 AM.png



what should I do to get this?
 
h9826790 said:
Did you try the little circular arrow on the right hand side to refresh the HWAccel status?
Click to expand...
yes for both of them but in HEVC there is no action, and I used this version of open core :
Screen Shot 2023-03-29 at 5.06.22 AM.png


ohh my god , after booting to my second drive which is high sierra and go back I double check if it is active! It became active, then when I double refresh the circle it became inactive again!!
 
MapleGreen said:
yes for both of them but in HEVC there is no action, and I used this version of open core :
View attachment 2180400

ohh my god , after booting to my second drive which is high sierra and go back I double check if it is active! It became active, then when I double refresh the circle it became inactive again!!
Click to expand...
You haven't mod anything in the OpenCore config plist, and never patch any system files, install extra GPU related kext etc?
 
h9826790 said:
You haven't mod anything in the OpenCore config plist, and never patch any system files, install extra GPU related kext etc?
Click to expand...
No I just 3xNVRAM reset then disable sip - copy efi from open core to efi/efi then bless it , then restart , everything is fine except HEVC
 
h9826790 said:
The package in post #1314 should take care all required spoofing and kext injection.

Of course, you can still follow the discussions in older post to enable HWAccel.
Click to expand...
thanks again I Installed Catalina in "Opencored Mojave" (that didn't gave me HEVC support).
finally I have everything working without even re-installing Opencore in Catalina , but I need it (HEVC) to work on Mojave because my Avid Mbox Pro Sound card and M-Audio midi keyboard don't have 64bit drivers so I have to work in Mojave. Could you please help a musician here and figure out a way to make HEVC work in Mojave?
I want to start my youtube music channel. so I'll be doing a lot of encoding/decoding.
maybe I need to Change something in config.plist to be able to have HEVC in Mojave
regards

Screen Shot 2023-03-30 at 6.44.24 AM.jpg


but in Mojave Still :

Screen Shot 2023-03-29 at 3.32.01 AM.png
 
MapleGreen said:
thanks again I Installed Catalina in "Opencored Mojave" (that didn't gave me HEVC support).
finally I have everything working without even re-installing Opencore in Catalina , but I need it (HEVC) to work on Mojave because my Avid Mbox Pro Sound card and M-Audio midi keyboard don't have 64bit drivers so I have to work in Mojave. Could you please help a musician here and figure out a way to make HEVC work in Mojave?
I want to start my youtube music channel. so I'll be doing a lot of encoding/decoding.
maybe I need to Change something in config.plist to be able to have HEVC in Mojave
regards

View attachment 2181046

but in Mojave Still :

View attachment 2181047
Click to expand...
I suggest you try re-installing Mojave first (just cover on top of your existing Mojave, no need to remove any user data). This can effectively unpatch / recover all system kexts (if any).

Your Catalina test suggest you did the correct steps and the OC package is functioning correctly.

So, if doen't work in Mojave, most likely due to Mojave itself has issue.

If still doesn't work, then the next test will be get a spare drive to install a clean Mojave. And see if you can get full HWAccel in that clean Mojave.
 
h9826790 said:
I suggest you try re-installing Mojave first (just cover on top of your existing Mojave, no need to remove any user data). This can effectively unpatch / recover all system kexts (if any).

Your Catalina test suggest you did the correct steps and the OC package is functioning correctly.

So, if doen't work in Mojave, most likely due to Mojave itself has issue.

If still doesn't work, then the next test will be get a spare drive to install a clean Mojave. And see if you can get full HWAccel in that clean Mojave.
Click to expand...
Ok I will install mojave again, I don’t have any important files or user data in my mojave it is fresh install, should I install new Mojave while I’m in Mojave OS or it’s better to Install it while I am in Catalina that showed no Problem?
I have 3 separate bootable ssd’s now
high sierra
mojave
Catalina
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back