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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Last edited:
Excuse me, but as I said earlier, this manual and provided config file doesn't work for me. And there is no link to the previous versions of config. So I decided to try to understand and make my own instead.
Why my config is unrelated to the thread? Can you explain please.
Can you please start from scratch and follow the step by step instructions posted into OP by @cdf? You will have great success, just make sure you follow to the letter the guide.
@startergo I did that. The resultant output is what I posted. There are a lot of entries in the list and am unsure as to which one is actually the GPU.
Last edited:
POST 1 => Advanced Configuration => Enabling Hardware Acceleration => Spoiler: More Details
A bit puzzled as to why you need that though. (Seems like a potential XY Problem situation)
If using MyBootMgr, GPU Acceleration would be enabled if you select the option. If you are not getting the expected outcome, changing the implementation method would not fix this.
If you do want to use device properties for GPU Acceleration, make sure you disable GPU Acceleration in MyBootMgr first so that you don't have two potentially conflicting attempts.
A note considering other queries you have made is that GPU Acceleration is not related to getting disks to identify as internal.
Would there be a benefit to doing having the Mac Pro 7,1 ID in there by default since we are all running Mac Pro's and not iMac's?
Not really, My package is to aim for providing HWAccel, which include Mojave (the last macOS that natively supported for cMP).
However, Mac Pro 7,1 is not supported in Mojave. If I put the 7,1 board ID into my public config as default. Then only the cMP running Catalina or newer can use HWAccel.
Before Big Sur, we can use the "board-id to board-ix" patch to fix that black screen issue. However, since Big Sur break user space patching. Therefore, we need to use the 7,1 board ID. This is a Big Sur specific issue (so far).
If the OC / Lilu / WEG team find out a way to fix this issue, then we may able to keep using the iMac Pro board ID to activate HWAccel with no downside.
Hmm how come I don't have a black screen with iMacpro spoofing? Is it because of the Orinoco?
I see, thank you for explaining. So if I run Big Sur it would be better to put in the 7,1 ID?
Hi Martin,
I try today your new 0.6.6 OpenCore package with the actual Build of 10.15.7 - all works so far but I lost my audio output and I have no idea what happen.
This is your opencore 0.6.5 package:
This is your opencore 0.6.6 package:
Internal Speaker, Line-Out and Digital-Out are gone.
Any idea? Let me know if I can help with any information.
I try today your new 0.6.6 OpenCore package with the actual Build of 10.15.7 - all works so far but I lost my audio output and I have no idea what happen.
This is your opencore 0.6.5 package:
This is your opencore 0.6.6 package:
Internal Speaker, Line-Out and Digital-Out are gone.
Any idea? Let me know if I can help with any information.
Possible. So, all ports on your RX580 still works with iMac Pro board ID, correct?
If you downgrade back to 0.6.5, then all audio options come back straight away?
It looks like you are also affected. But just because you only need one DP, and you are using the “correct” port. Therefore, it looks like you are not affected.
If setup correctly, both DP ports should work.
I have 3DP and I use 2 of them. I need to inject the framebuffer for the 3rd DP or is there another way?
iMac Pro board ID here with no Orinoco. All ports working.
Mea culpa - mea maxima culpa.
I take everything back and claim the opposite. Note: If you read a lot, you can make a lot of mistakes.
I just wanted to reactivate my graphics card name in your package and have modified the corresponding places (DeviceProperties). Unfortunately, when looking through the config.plist, I found the entry <DeviceProperties> true / false in the <ProtocolOverrides> and "thought" it must also be activated. That was my fault. I have now set this value back to <false> and have my graphics card name and my audio ports are active again.
Much smoke about nothing ... sorry.
Hi Dayo. GPU acceleration is indeed functional. My inquiry is more of a cosmetic issue when it comes to VideoProc. This is the post in reference: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29451348
I just wanted to identify the Vega 64 and append the initials 'AMD' before it. That way, VideoProc also sees the GPU in its status screen. Like I said - merely cosmetic as GPU acceleration is in fact working.
Now the problem I'm running into after following these instructions:
Is that I get a very long list of items and I'm unsure as to which is the Vega card.
This patch is applied using the kernel patcher, so it should be fine.
Update: I just tested the patch (in Big Sur) by disabling it. As a result, only one port works. Thus the patch is OK. So something else is causing the issue...
Use
gfxutil -f display
Last edited: