The problem is, I also don’t know what you’ve done wrong.
We need to clarify a few things in order to solve the issue.
So, there is only one OC installed? And that’s 0.6.6 on the Windows drive EFI partiton?
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
We need to clarify a few things in order to solve the issue.
So, there is only one OC installed? And that’s 0.6.6 on the Windows drive EFI partiton?
Yes, only OC 0.6.6 is installed on an EFI partition of a SATA drive (not on the Windows drive).
I haven't checked yet if I can see the Windows volume as a startup disk from System Preferences.
I tried to select Windows volume in the startup disk but nothing, in the boot picker of OC there is not the Windows icon!
Attachments
As long as the Microsoft folder is untouched.
Please try re-install OC and BOOT folder to the Windows drive’s EFI partition. And bless it.
I tried as you suggest me but nothing! In the boot picker of OC there is not the Windows icon!
I pulled out all the drives leaving only the Windows drive but unfortunately, after the boot sound, only one of the two monitors appears in gray without boot picker (no icon)!
This sounds strange.
If it happen with your 0.6.6 backup. Which means not OC related.
So far, it points to your Windows is damaged.
Since you haven’t touch the Microsoft folder on the EFI partition. That means, very likely some system files on the main partition is damaged.
But if all you did was just replace the 0.6.6 files by 0.6.7, that shouldn’t happen.
If it happen with your 0.6.6 backup. Which means not OC related.
So far, it points to your Windows is damaged.
Since you haven’t touch the Microsoft folder on the EFI partition. That means, very likely some system files on the main partition is damaged.
But if all you did was just replace the 0.6.6 files by 0.6.7, that shouldn’t happen.
I don't think that's the only solution, but most likely the quickest way to fix this issue. Especially we don't know what's the root cause of the issue at this moment. It will take much more time to diagnosis than just re-install Windows (not necessary a clean one, you may able to keep your existing files /setup if you install Windows on your existing broken Windows).
Thank you very much for your availability and for your patience and for your precious help!
But if I install on existing Windows, do I still have to follow all the steps described in APPENDIX of post # 1 of cdf?
Thanks in advance!
Hi again,
i have a little Problem with the Update to OC 0.6.7 (i think so, but i can't reveal it for 100%, perhaps AppleTV+ doesn't worked for me in the past too).
I want to use my Apple TV+ with my "new" 30"Apple Cinema Display and every time when i start a Film, it goes Fullscreen and instantly g back to normal view and doesn't start the film.
I have a GTX680 in my Mac Pro and use your Config (with the only change for activating my AirPort Card).
Is it not possible to view AppleTV+ with my Screen? I Thought, the DRM Fix is for this issue.
Many thanks for your work and stay healthy.
EDIT: okay, with Chrome it is working, but i thought the fix is for the AppleTV+ App in BigSur?
i have a little Problem with the Update to OC 0.6.7 (i think so, but i can't reveal it for 100%, perhaps AppleTV+ doesn't worked for me in the past too).
I want to use my Apple TV+ with my "new" 30"Apple Cinema Display and every time when i start a Film, it goes Fullscreen and instantly g back to normal view and doesn't start the film.
I have a GTX680 in my Mac Pro and use your Config (with the only change for activating my AirPort Card).
Is it not possible to view AppleTV+ with my Screen? I Thought, the DRM Fix is for this issue.
Many thanks for your work and stay healthy.
EDIT: okay, with Chrome it is working, but i thought the fix is for the AppleTV+ App in BigSur?
Last edited:
Edited: I did not realize that I started at the opencore thread, opened Martin's link and wound up here, an entirely different thread. Glad I caught it before the grumpy thread police got all up in bunches.
Last edited:
Mike Richardson
macrumors regular
Can someone direct me to the hex edit instructions for Mojave? I have a MacPro5,1 with a "MacVidCards" RX 580 and just want to enable hardware video codecs (H.264/H.265). I have no plans to upgrade to Crapalina.
(Yes I know there is search but this thread is huge and sometimes has information that is outdated on one page and updated on a later page. I don't want to use outdated instructions.)
(Yes I know there is search but this thread is huge and sometimes has information that is outdated on one page and updated on a later page. I don't want to use outdated instructions.)
Last edited:
Activate AMD hardware acceleration
I‘d happy to know more about it as well. As I often have to rely on PRAM reset to allow me to boot into windows again to activate my TB3 devices, from there I have to warmboot into macOS. So the benefit of having it fixed would be obvious.. Thanks so far.
forums.macrumors.com
I wonder what are - if any - the benefits of using Board ID iMacPro1,1 versus Board ID Mac Pro7,1 for this particular OC package? I found one brief question/answer about this in the general OC thread that had to do with the 7,1 possible being more reliable for ports on some GPUs, but I wonder if anyone would not mind to share a bit more details of the pros/cons. Thanks!
iMac Pro board ID works in Mojave, the 7,1 board ID does not.
Since this thread aim at provide HWAccel. Therefore, the package default to use the iMac Pro board ID, which can provide HWAccel on more macOS.
Thanks for the clarification, Martin. I might try to test the 7,1 Board ID to check what appears to be a replicable bug in my system. In addition to loosing BT when I boot Big Sur right after Mojave (a known bug), I also loose the following:
1) Audio from one of the DP ports on the RX580 (I use the 2 DP ports and only one looses audio)
2) Sonnet Fusion Dual 2.5-inch SSD RAID on PCIe 4 does not load.
BT regularly comes back on a subsequent (second) Big Sur reboot as reported by other users, but the other two issues usually need a third Big Sur reboot to show up. At that point everything works perfectly, even if i shutdown/restart on a daily basis.
But in order to test the 7,1 Board ID to troubleshoot the above -- I would have to change the Board ID while booted on Mojave and just before rebooting into Big Sur... correct?
From a simple thread search with the keyword FileVault: https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-29605219
Going to sound dumb but does HWA in OC affect Windows 10 at all? Having instability with Windows (during gaming) and I'm trying to track down what it is, but I don't think so myself....