Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
After giving up on the cheap cards and getting some confirmed working RX550 Biostar cards my work machines are chugging along happily. Now I'm playing with OpenCore on my home machine (Mac Pro 4,1->5,1, dual x5690, R9 Fury Nano - Mojave) and just like the freebie cards I had at work - I get no bootpicker. I can toss in the old Nvidia GT120 and see the boot picker - so am I just up a creek with my Nano - does it not do GOP either? Also, I don't seem to be getting any hardware acceleration out of it although I've followed the guide. Hit me with your words of wisdom!

Danke for the help in advance!
 
After giving up on the cheap cards and getting some confirmed working RX550 Biostar cards my work machines are chugging along happily. Now I'm playing with OpenCore on my home machine (Mac Pro 4,1->5,1, dual x5690, R9 Fury Nano - Mojave) and just like the freebie cards I had at work - I get no bootpicker. I can toss in the old Nvidia GT120 and see the boot picker - so am I just up a creek with my Nano - does it not do GOP either? Also, I don't seem to be getting any hardware acceleration out of it although I've followed the guide. Hit me with your words of wisdom!

Danke for the help in advance!
BIOS provided by AMD to add UEFI support
 
Is there some alternate way of installing windows other than what’s outlined in post 1?
I can't really vouch for it, since I tried it once and didn't work for me, although it might well have been my fault, and my hunch is it should work. Provided you install Windows in legacy mode (i.e., unmodified Boot Camp) on its own disk (partitioned as GPT+MBR and formatted as exFAT or NTFS, the latter being recommended), you can easily convert it to UEFI mode using Winclone 8. There are a couple of menu options to toggle between legacy and UEFI. If you already have Winclone 8 (and if you don't, you should probably get it), I suggest that you install legacy Windows and then use Winclone to convert it to UEFI mode. Let us know if that works for you.
 
The path is most likely correct, the way you put it in your config.plist isn't.

Can you show us how you did it?

This is how the part looks like with my graphics card and PCI ahci drive:

Code:
<key>DeviceProperties</key>
<dict>
    <key>Add</key>
    <dict>

        <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)</key>
        <dict>
            <key>built-in</key>
            <data>
            AA==
            </data>
        </dict>

        <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
        <dict>
            <key>agdpmod</key>
            <data>
            cGlrZXJhAA==
            </data>
            <key>rebuild-device-tree</key>
            <data>
            AA==
            </data>
            <key>shikigva</key>
            <data>
            UA==
            </data>
        </dict>

    </dict>

    <key>Delete</key>
    <dict/>
</dict>

It looks similar, I juste have them the other way around:

Code:
    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>agdpmod</key>
                <data>
                cGlrZXJhAA==
                </data>
                <key>rebuild-device-tree</key>
                <data>
                AA==
                </data>
                <key>shikigva</key>
                <data>
                UA==
                </data>
            </dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>built-in</key>
                <data>AA==</data>
            </dict>

    </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>
 
It looks similar, I juste have them the other way around
The order doesn't matter, the fact that you closed the dictionary too soon does ;)

Here's the corrected bit:

Code:
<key>DeviceProperties</key>
<dict>
    <key>Add</key>
    <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>agdpmod</key>
                <data>
                cGlrZXJhAA==
                </data>
                <key>rebuild-device-tree</key>
                <data>
                AA==
                </data>
                <key>shikigva</key>
                <data>
                UA==
                </data>
            </dict>
            <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>built-in</key>
                <data>AA==</data>
            </dict>
    </dict>
    <key>Delete</key>
    <dict/>
</dict>
 
A question to all:

Wouldn't it be a good idea to specify the screen resolution (WxH@bpp) in UEFI > Output > Resolution ?

Instead of putting it to "Max" or failsafe empty string?

I can't test it, since my card shows bootpicker and boot screen on all outputs, but would it possibly make a difference for peeps who only got bootpicker on a specific output?

Just replaced Max with 2560x1440@24, same result as Max setting...
 
You are a gentleman and a scholar. Now - additional wisdom requested. Is there a VBIOS patching tool for Mac or what's the method of doing this. Only ones I've ever patched were Nvidia cards that I did in Windows.
There is a UEFI version of AMD flasher on that site, which let's you flash the firmware from UEFI shell. You might need the GT-120 for the boot screen for this purpose.
 
Is there some alternate way of installing windows other than what’s outlined in post 1? I want to use my own iso but it does not have install.wim it only has boot.wim. Its a custom installer with office integrated and updates slipstreamed in among other things. im stuck on
  • Apply the install image by entering: dism /apply-image /imagefile:install.wim /index:1 /applydir:C:\ /compact /EA
Edit: no big deal if not just wanted to save some time on updates and configurations.
 
Is there some alternate way of installing windows other than what’s outlined in post 1?
Same process as @startergo posted just with images and stuff:
 
If you've followed the guide, then this should be the result. You can verify it by entering the following in terminal: ioreg -l | grep agdpmod. You should see "agdpmod" = <"pikera">.
Infact, is as you told me. The command returns:

Code:
Pro-di-Donato:~ donnie$ ioreg -l | grep agdpmod
    | |   |   | |   "agdpmod" = <"pikera">
    | |   |     |   "agdpmod" = <"pikera">
Pro-di-Donato:~ donnie$

Why my VGA don't boot from display port?

Here my config.plist.

Thank you so much.
 

Attachments

  • config.plist.zip
    3 KB · Views: 79
What do you mean by this? VGA stands for Video Graphics Array connector.
Sorry, I used wrong word. I would to say my Mac Pro, if attached to display port, is always in a black screen. Seems to be with no signal. If attach the hadmi port I can see all done, from boot to the desktop of Catalina.
Thx.
 
Last edited:
Sorry, I used wrong word. I would to say my Mac Pro, if attached to display port, is always in a black screen. Seems to be with no signal. If attach the hadmi port I can see all done, from boot to the desktop of Catalina.
Thx.
Is your pulse RX580 100% genuine, no bios mods?

If you care to try:
replace Resolution : Max with the actual resolution of your monitor...

Code:
<key>Output</key>
        <dict>
            <key>ClearScreenOnModeSwitch</key>
            <false/>
            <key>ConsoleMode</key>
            <string></string>
            <key>DirectGopRendering</key>
            <false/>
            <key>IgnoreTextInGraphics</key>
            <false/>
            <key>ProvideConsoleGop</key>
            <true/>
            <key>ReconnectOnResChange</key>
            <false/>
            <key>ReplaceTabWithSpace</key>
            <false/>
            <key>Resolution</key>
            <string>Max</string>
            <key>SanitiseClearScreen</key>
            <false/>
            <key>TextRenderer</key>
            <string>BuiltinGraphics</string>
            <key>UgaPassThrough</key>
            <false/>
        </dict>
 
Already did a batch of my work Mac Pro 4,1->5,1 with Catalina, however we have a few users that need access to 32-bit apps, so I'm doing a handful with Mojave also. I'm on one of those machines currently and see that the CPUs are detected as a pair of i3 cpus instead of the stock 2.26ghz Xeons. Didn't seem to happen on the Catalina boxes - although I'm not using identical config.plist files - I just did this one from scratch.

Thoughts?
 
Already did a batch of my work Mac Pro 4,1->5,1 with Catalina, however we have a few users that need access to 32-bit apps, so I'm doing a handful with Mojave also. I'm on one of those machines currently and see that the CPUs are detected as a pair of i3 cpus instead of the stock 2.26ghz Xeons. Didn't seem to happen on the Catalina boxes - although I'm not using identical config.plist files - I just did this one from scratch.

Thoughts?
Dual CPU Mac Pros that have Nehalem Xeons are supported up to High Sierra. With Mojave, 2009 dual CPU Mac Pros have several sleep and audio problems and both single/dual CPU 2009 Mac Pros with the original Xeons don't have Apple Hypervisor support - no VMM support.

The best course of action is to upgrade to a Westmere Xeon.
 
Is your pulse RX580 100% genuine, no bios mods?

If you care to try:
replace Resolution : Max with the actual resolution of your monitor...

Code:
<key>Output</key>
        <dict>
            <key>ClearScreenOnModeSwitch</key>
            <false/>
            <key>ConsoleMode</key>
            <string></string>
            <key>DirectGopRendering</key>
            <false/>
            <key>IgnoreTextInGraphics</key>
            <false/>
            <key>ProvideConsoleGop</key>
            <true/>
            <key>ReconnectOnResChange</key>
            <false/>
            <key>ReplaceTabWithSpace</key>
            <false/>
            <key>Resolution</key>
            <string>Max</string>
            <key>SanitiseClearScreen</key>
            <false/>
            <key>TextRenderer</key>
            <string>BuiltinGraphics</string>
            <key>UgaPassThrough</key>
            <false/>
        </dict>
I’m not sure if graphic card has a genuine software. There is a way to see if is it?

Change max to my 4K monitor risolution help me for black screen on display port?
Thx.
 
I’m not sure if graphic card has a genuine software. There is a way to see if is it?

Change max to my 4K monitor risolution help me for black screen on display port?
Thx.
If the previous owner has tampered with the bios, there's no way of telling =(

Replacing Max with 3840x2160 could work, maybe start with half the reolution (1920x1080)... won't hurt to try...
 
does anybody have a problem with apple cinema display 24 with display port on a radeon 580 ? i can see the boot but the the screen is black . works well with windows 10
 
im sure this has been talked about but not sure which page number, trying to upgrade to Os Big Sur and im getting an error. whats the trick?
Edit: is Board ID Spoofing still a requirement? I'm going back reading trying to see what tools to use to accomplish this.
Screen Shot 2020-10-28 at 4.27.05 PM.png
 
Last edited:
Is there some alternate way of installing windows other than what’s outlined in post 1? I want to use my own iso but it does not have install.wim it only has boot.wim. Its a custom installer with office integrated and updates slipstreamed in among other things. im stuck on
  • Apply the install image by entering: dism /apply-image /imagefile:install.wim /index:1 /applydir:C:\ /compact /EA
Edit: no big deal if not just wanted to save some time on updates and configurations.

Did you try the command with boot.wim?

Sorry, I used wrong word. I would to say my Mac Pro, if attached to display port, is always in a black screen. Seems to be with no signal. If attach the hadmi port I can see all done, from boot to the desktop of Catalina.
Thx.

Perhaps you can try going back to the standard configuration from Part I to confirm that you can get an output (including the basic boot picker) on the DisplayPort.

im sure this has been talked about but not sure which page number, trying to upgrade to Os Big Sur and im getting an error. whats the trick?
Edit: is Board ID Spoofing still a requirement? I'm going back reading trying to see what tools to use to accomplish this.

Did you try the minimal spoofing described in Post #4,212?
 
Did you try the command with boot.wim?
No I instead used a standard ISO direct for Microsoft and have been doing the extra configurations manually almost done just need to install office 2019 now and ill be finished.

Did you try the minimal spoofing described in Post #4,212?
No I have not, Thank you for adding the post#. Ill look into trying again later tonight.
 
  • Like
Reactions: cdf
Perhaps you can try going back to the standard configuration from Part I to confirm that you can get an output (including the basic boot picker) on the DisplayPort.
At the end of Part I, my system were ok. I saw basic boot picker in the left top corner and I was attached to display port. Only after Part II there was a problem.
Thx.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.