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.
star-affinity said:
Having some trouble with video on one display after updating from macOS 11.5.1 to 11.5.2 with @h9826790's OpenCore package from this thread, currently using the the 0.7.2 version.

On my RX 5700 XT graphics card I have a DVI display connected via a DisplayPort to DVI adapter and a TV connected via HDMI. What happens is that I get the Apple logo with the progress bar that loads to about the middle and when the logins screen loads the DVI display turns blank and video is only displayed on my TV – it's as if the DisplayPort connected display wasn't connected at all.

I notice this is the same no matter which of my macOS partitions I attempt to start up from (Except for my main with Big Sur I have one with High Sierra and one with Catalina).

Any ideas?
Click to expand...
agdpmod=vit9696 or agdpmod=pikera, try both by adding to the boot-args
 
Ausdauersportler said:
agdpmod=vit9696 or agdpmod=pikera, try both by adding to the boot-args
Click to expand...
Thanks for the suggestion. :)

Tried changing from ”pikera” to ”vit9696” bit that gave me the forbidden sign on startup. :(

Is it possible to alter the congfig file from the startup picker and then restart? Would be handy since I otherwise have to take out my drive with OpenCore and connect it to another computer to revert the setting.

Or maybe I can reach the EFI partition from within Windows 10? 🤔
 
Last edited:
star-affinity said:
Thanks for the suggestion. :)

Tried changing from ”pikera” to ”vit9696” bit that gave me the forbidden sign on startup. :(

Is it possible to alter the congfig file from the startup picker and then restart? Would be handy since I otherwise have to take out my drive with OpenCore and connect it to another computer to revert the setting.

Or maybe I can reach the EFI partition from within Windows 10? 🤔
Click to expand...
No, unfortunately not. You need another bootable system to access the EFI and config.plist. You possibly just added an minor error to the plist. Always check in advance, there are tools.
 
I'm on 11.2.3 and tried updating to 11.5.2 with Open core running smooth. It just hangs halfway through the process. I read somewhere someone had the same hing happened. Can't find the resolve, have to find it.
 
basslik said:
I'm on 11.2.3 and tried updating to 11.5.2 with Open core running smooth. It just hangs halfway through the process. I read somewhere someone had the same hing happened. Can't find the resolve, have to find it.
Click to expand...
Did you make sure latebloom is enabled? Martin included it but it is NOT enabled by default - the config section entry says "Enable" but underneath it says "false" - that must be changed to "true".
 
star-affinity said:
I was quite careful… But thanks! Do you recommend any specific tool? :)
Click to expand...
Check the first post of this thread…. it covers the handmade approach of creating a valid OC config in detail.

Getting a black screen with displayport connections can sometimes be cured by updating the GOP part of the vBIOS, by changing the OC config as I described or by changing cables and adapters, especially when you are using a bunch old ones.
 
star-affinity said:
Having some trouble with video on one display after updating from macOS 11.5.1 to 11.5.2 with @h9826790's OpenCore package from this thread, currently using the the 0.7.2 version.

On my RX 5700 XT graphics card I have a DVI display connected via a DisplayPort to DVI adapter and a TV connected via HDMI. What happens is that I get the Apple logo with the progress bar that loads to about the middle and when the logins screen loads the DVI display turns blank and video is only displayed on my TV – it's as if the DisplayPort connected display wasn't connected at all.

I notice this is the same no matter which of my macOS partitions I attempt to start up from (Except for my main with Big Sur I have one with High Sierra and one with Catalina).

Any ideas?
Click to expand...
Try this
 
  • Like
Reactions: star-affinity
h9826790 said:
Try this
Click to expand...
Thanks – that worked! :)👍

Now, I'm just curios about this trouble with starting up into macOS that sometimes happen with recent Big Sur updates. Is that what's called the ”race condition” which ”latebloom” can mitigate? Is that something I should try to use? Doesn't feel to good having to hard restart several times when trying to get into macOS.

I can't see anything about ”latebloom” in the config.plist from your 0.7.2 package of OpenCore. Does that mean you have no trouble with this? 🤔
 
kkinto said:
Did you make sure latebloom is enabled? Martin included it but it is NOT enabled by default - the config section entry says "Enable" but underneath it says "false" - that must be changed to "true".
Click to expand...
I don't know where that is. Been reading so much I lost my way. Please guide me, thanks.
 
basslik said:
I don't know where that is. Been reading so much I lost my way. Please guide me, thanks.
Click to expand...
In the /EFI/OC/Config.plist file, look for the entry for latebloom (<string>PCI delay for BS/Monterey</string>). Underneath there is a line <key>Enabled</key> and under that (by default per Martin's file) it says <false/> - edit that to be <true/> and then save the config .

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>latebloom.kext</string>
<key>Comment</key>
<string>PCI delay for BS/Monterey</string>
<key>Enabled</key>
<false/> <<<----- change this to <true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/latebloom</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>20.4.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
 
star-affinity said:
Now, I'm just curios about this trouble with starting up into macOS that sometimes happen with recent Big Sur updates. Is that what's called the ”race condition” which ”latebloom” can mitigate? Is that something I should try to use? Doesn't feel to good having to hard restart several times when trying to get into macOS.

I can't see anything about ”latebloom” in the config.plist from your 0.7.2 package of OpenCore. Does that mean you have no trouble with this? 🤔
Click to expand...
There is another thread all about latebloom - its better you start there. But if you want to try it, Martin's config includes it (and the relevant kext) in his OC package - just see my answer above to @basslik to activate it using Martin's config file. But always better you also read more about it and its settings/options/issues in the latebloom thread.
 
  • Like
Reactions: star-affinity
dtsisdead said:
Could it possibly be due to using HDMI instead of DP? It is not the end of the world, as I definitely have hardware acceleration, etc. working... But it would be nice to be able to choose a USB or other drive at boot.
Click to expand...
Huzzah! It was, indeed, due to using HDMI instead of DP. I switched over to a DP cable and am now getting the boot screen and picker screen! Might be worth noting that the picker and boot screens operate only when using the first DP port on a reference RX 480 8GB.
 
dtsisdead said:
Huzzah! It was, indeed, due to using HDMI instead of DP. I switched over to a DP cable and am now getting the boot screen and picker screen! Might be worth noting that the picker and boot screens operate only when using the first DP port on a reference RX 480 8GB.
Click to expand...
Strange. I've exactly the opposite behaviour with my MacPro and RX580 Nitro+. In my case picker won't show using DP cable, but shows with DVI and HDMI.
 
borgo1971 said:
Strange. I've exactly the opposite behaviour with my MacPro and RX580 Nitro+. In my case picker won't show using DP cable, but shows with DVI and HDMI.
Click to expand...
This is not strange, it reflects only how the particular vBIOS has been programmed to use external ports.
 
Ausdauersportler said:
This is not strange, it reflects only how the particular vBIOS has been programmed to use external ports.
Click to expand...
Thus why I specified the card and port... I highly doubt the card's previous owner was running a custom vBIOS... so logically, these reference 480s seem to need to have the first DP port used in order to see the picker and boot screens.
 
  • Like
Reactions: Ausdauersportler
h9826790 said:
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package already updated to 0.7.2]

[...]

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: 15 Aug 2021, OC 0.7.2, Lilu 1.5.5, WhateverGreen 1.5.2]
Click to expand...

This was by far the easiest installation of OpenCore I've ever done. Thank you. Check your PayPal.
 
  • Like
Reactions: h9826790, dtsisdead and 0134168
borgo1971 said:
Strange. I've exactly the opposite behaviour with my MacPro and RX580 Nitro+. In my case picker won't show using DP cable, but shows with DVI and HDMI.
Click to expand...
Correction, will show on HDMI and not DVI.
 
Last edited:
What's the best way to update OC to 0.7.2?

I installed your package when it was 0.6.8.

Do I need to do the OC Plistlib Generator? It seems it requires a lot of settings to be configured depending on current setup; since I used your package, I'm not at all familiar with what settings need to be used if I use that update method...
 
cdf said:
If you used Martin's package and didn't do any modifications to it, then just replace the files.
Click to expand...

Are you saying that I simply mount the EFI partition and copy all files from the 0.7.2 OC EFI folder?

I am in the process of setting up OC to install Windows 10, so I've just mucked with the config.plist file as well as copying over the ExFatDxeLegacy.efi driver. I assume I would retain copies of those and move them back into the EFI partition once I copy over the 0.7.2 files, yes?
 
Auggie said:
Are you saying that I simply mount the EFI partition and copy all files from the 0.7.2 OC EFI folder?
Click to expand...
That's how it works if you haven't customized your setup.

I am in the process of setting up OC to install Windows 10, so I've just mucked with the config.plist file as well as copying over the ExFatDxeLegacy.efi driver. I assume I would retain copies of those and move them back into the EFI partition once I copy over the 0.7.2 files, yes?
Click to expand...
Yes. You'll also need to repeat the necessary edits to your new configuration file.
 
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