For most cases, the card’s ROM was modified by the last owner.
In some cases, the factory ROM shipped with no GOP or broken GOP.
In some rare cases, the Amazon etc sell the buyer a returned card which was flashed by the previous buyer.
Got a tip for us?
Let us know
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
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
In some cases, the factory ROM shipped with no GOP or broken GOP.
In some rare cases, the Amazon etc sell the buyer a returned card which was flashed by the previous buyer.
Do this:
Go to this site and drop previously extracted with GPU-Z
vbios and drop the vbios in the GOPupd.bat:
Attachments
Ok just to report back, hoping it helps someone. I re-flashed the MSI Gaming X RX 580 4gb to the factory ROM, and I still don't get a boot screen. I swapped in my Sapphire Nitro+ Gold Edition RX 590 8GB and I get a boot screen.
Last question, how do I change the resolution of the boot screen to 2560x1440?
Last question, how do I change the resolution of the boot screen to 2560x1440?
Then there is a possibility that all that RX580 model form MSI has broken UEFI GOP.
You can open a ticket at MSI support, and ask for a UEFI GOP ROM for your card.
Another option is cross flash another RX580 4GB ROM onto your card. 99% it can work as well, but the fan curve / clock speed etc may be a bit different than your existing value. But since the Gaming model has better cooling solution and high clock speed than average. Therefore, flash it with a lower clock speed ROM should be very safe.
You may also follow the suggestion in post #2027 to make your own UEFI GOP ROM.
Actually, it turns out that when a GOP driver, a UEFI 2.x driver, is implemented according to the associated UEFI 2.x Specs, it does not work on Classic MacPros and that what works for us is what is actually the "Broken" UEFI GOP.
Basically, one of the first items in the UEFI 2.x Specs for a GOP driver is to check if the device is UEFI 2.x compliant and fail if it is not. Thus, any GOP driver that works out of the box on a Classic MacPro is clearly not following this and also has some other changes downstream.
Strict UEFI 2.x GOP implementation, as appears to be used by Nvidia in GPUs that are not "Mac Edition" GPUs for instance, does not activate on Classic MacPros as Classic MacPros are not UEFI 2.x devices but EFI 1.x devices to which Apple has added a chunk of, but not all of, the UEFI 2.x capabilities. AMD/ATI, perhaps because of association with Apple, does not appear typically to have such a strict implementation.
This info is thanks to investigation by @joevt, with support from @startergo and @Macschrauber, on providing bootscreen in RefindPlus for Nvidia GPUs. The fix which allows bootscreen on such GPUs, and carries over to OpenCore if chainloaded from RefindPlus, will appear in the next release of RefindPlus due early next month and which will be packaged with MyBootMgr. Will also look later on how to implement directly in OpenCore.
Last edited:
Hi all, I've installed OpenCore 0.6.3 from this thread and upgraded to Big Sur. It's so good to have a boot screen and boot picker back after all these years!
One problem tho. I've got an RX 560 4GB. H264 / HEVC hardware decode + encode both working but when running OpenCore my Metal benchmark on Geekbench is very low. Metal benchmark of 14357 when running OpenCore compared to 21292 when booting without OpenCore. Anything I can do to improve that?
One problem tho. I've got an RX 560 4GB. H264 / HEVC hardware decode + encode both working but when running OpenCore my Metal benchmark on Geekbench is very low. Metal benchmark of 14357 when running OpenCore compared to 21292 when booting without OpenCore. Anything I can do to improve that?
You mean when you boot to Big Sur without OpenCore, the GPU perform better?
So, I'm running Big Sur and I've copied @h9826790's 0.6.3 pack with its vanilla (as is from the package) config.plist.
My Mac Pro has got no hwaccel though, and the CPUs show up as 3.46 and not 3.5.
This hasn't been a clean install to a new drive, but it's an upgraded MacOS, but I've made sure there are no old .kexts in the Libraries.
At the end of the day I might end up going with a clean install, but is there something else I should look for? I've read that I might not need the entire 0.6.3 package since I'm Big Sur only. I wonder if slimming it down would make a change. I'm mostly curious to see if I can kick the tires hard enough to get it to work with less work.
My Mac Pro has got no hwaccel though, and the CPUs show up as 3.46 and not 3.5.
This hasn't been a clean install to a new drive, but it's an upgraded MacOS, but I've made sure there are no old .kexts in the Libraries.
At the end of the day I might end up going with a clean install, but is there something else I should look for? I've read that I might not need the entire 0.6.3 package since I'm Big Sur only. I wonder if slimming it down would make a change. I'm mostly curious to see if I can kick the tires hard enough to get it to work with less work.
Yep, performance is better without OpenCore. I did the comparisons on Catalina before I upgraded to Big Sur but still the same issue.
Catalina with DosDude1 patch:
Boot without OpenCore - Geekbench Metal Score of 21292
Boot with OpenCore - Geekbench Metal Score of 14357
Big Sur
Boot with OpenCore - Geekbench Metal Score of 13554
I haven't tried Big Sur without OpenCore. It's installed to an NVMe and last time I tried to boot without it my OS drive got corrupted. I've got OpenCore currently running on a USB stick. Not sure if the perforce gain had anything to do with the DosDude1 patch
I've also noticed the boot picker is running at only 1080p on my 4k display. The resolution is set to Max in the config and if I change it to 3840x2160 I just get a black screen on boot.
I will. But I think it is (I'm not at the computer now). Isn't that the way it's set in our package?
After my last round of trouble shooting I just copied over your patch 'as is'.
----------
EDIT: I wonder if I'm having some issue with the bless script. But would Big Sur boot up normally, if the basic Open Core config wasn't working?
Last edited:
Hi my mac pro 5,1 with opencore 0.6.4 running Big Sur with AMD RX 580 8GB GPU.
I do not have hardware acceleration activated?
I believe I have lilu and whatevergreen kexts in Opencore 0.6.4
My config file does not have the correct PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) path I think?
Do I copy this into the config file, any section?
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>shikigva</key>
<data>UA==</data>
<key>agdpmod</key>
<data>cGlrZXJhAA==</data>
<key>rebuild-device-tree</key>
<data>AA==</data>
</dict>
</dict>
Could it be due to this or do I need to do anything else with the config file?
Are there any side issues to enabling hardware acceleration.
Many Thanks in advance.
I do not have hardware acceleration activated?
I believe I have lilu and whatevergreen kexts in Opencore 0.6.4
My config file does not have the correct PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) path I think?
Do I copy this into the config file, any section?
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>shikigva</key>
<data>UA==</data>
<key>agdpmod</key>
<data>cGlrZXJhAA==</data>
<key>rebuild-device-tree</key>
<data>AA==</data>
</dict>
</dict>
Could it be due to this or do I need to do anything else with the config file?
Are there any side issues to enabling hardware acceleration.
Many Thanks in advance.
AFAIK, the cMP can still boot Big Sur if the no compat check boot argument still there. However, of course you won't see boot picker etc.
But if that's my package, the CPU clock speed should show 3.5GHz. So this is a sign that something is wrong.
Either OC isn't working, or the config is wrong.
Of course, rather then debug, it's usually faster to re-install the whole OC package.
For 0.6.4, you better go back to the OpenCore thread to discuss.
But Big Sur should activate HWAccel by default (as long as the board ID is correct), Lilu / WEG / all those property injection are not required.
Thanks for your work on this. I got Big Sur running on my 5,1 after upgrading directly from Catalina with your 0.6.3 set up. For cleanliness, I wonder if it would it be possible to create a Big Sur OC version without these kexts and config?
I am thinking to create a Big Sur package seriously. But most likely wait until 0.6.4
Well, the beauty of science and technology is, that the likelihood of a logical explanation is pretty big.
I decided to start eliminating things regardless of my assumptions and found a second OC install on a strictly media drive that I hadn't thought to check because it wasn't supposed to be there. I did a half start with Open Core months ago but decided against it at the time and had forgotten about it. And since the EFI folders are pretty well tucked away and I wanted to be lazy about it.... Lesson learned.
Today I exported a hardware accelerated HEVC video out of Resolve for the first time: cheers!
I think that is a great idea. The smaller the package and the fewer the mods, the easier it is to understand what everything does.
I'm not so sure that there even is such a thing as 'casual Open Core modding' (needless to say it's recommended to read the documents and learn it properly), but it seems it is what I'm attempting recently, since my primary focus (and Macs that I use most) is elsewhere.
You can remove all associated code, however, as long as there is no adverse effect now, you better keep it as is.
e.g. the iMac Pro board ID is used for activating HWAccel, but may be also used for activating Handoff etc.
So, if there is nothing wrong now, better not to "fix" it.
I removed my internal super drive. now, no idea for that. But I really doubt if that's related to HWAccel. I have HWAccel with the super drive for quite a few months, no issue until I finally decided to remove it (because use less than once a month).
DVD Fab isn't support Big Sur yet, according to their CS post, the upcoming version should be under QA. You better wait for next version before trying to fix it.
@h9826790
hey MartinLo - Been running your 0.5.4 since Feb on my 5,1 Mojave - all good - thanks! ...so now I need 10.15.6 Cat to use Compressor HEVC direct out of FCPX - but when go into the mounted EFI - mine 0.5.4 does not have a folder called APPLE shown in your update video? so should I go ahead and replace the OC and BOOT folders to jump from 0.5.4->0.6.3?
ok I replaced the OC and BOOT folders 0.5.4->0.6.3.2 (I don't have an APPLE folder in my EFI when mounted) ; then restarted my Mojave 5,1 and now I get a cool little pause at a boot screen! something I have not seen for a while - very cool. So next step Catalina or BigSur install.
If you have my 0.6.3 installed, I recommend you go direct to Big Sur. It works very well on my cMP (better than Catalina).