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 Manually Configured OpenCore on the Mac Pro

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.
paalb said:
I still have a question to the wiki post: What is the reasons for “Making External Drives Internal”? Need no long explanation, just some keywords for Google.
Click to expand...
1) cosmetic, if you display external drives on the desktop, having your operating system disk in between then is simply odd
2) safety, if you make an external disk internal, the eject option is no longer there

Personally, I also prevent volumes from other operating systems from auto-mounting, but that's got nothing to do with OpenCore...
 
  • Like
Reactions: paalb
The Spirit said:
did it work?
Click to expand...
If it is me you are asking? It did work. I did struggle with the XML but using the plutil -convert xml1 config.plist && plutil config.plist I did manage to get an OK at last.

Looks like this
XML: 
<key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x10,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>built-in</key>
                <data>
                AA==
                </data>
            </dict>
            <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x11,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>built-in</key>
                <data>
                AA==
                </data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict/>
    </dict>
 
Hello everyone and thx for your good job for this and other guides.
I'm from Milan, and now I ask help for a problem.
I followed PART I and PART II of the guide, but now when I start my Mac Pro, I'm in a black screen.

After PART I the system started regular, all seems to be done.
After reboot at the end of PART II, the system has gone in a black screen.

My setup:
Mac Pro 4,1 upgraded to 5,1
VGA: Sapphire RX 580 Pulse

I have 4 ports: 2 hdmi and 2 display port. On the display port I'm in a black screen, on the hdmi nope. Hdmi is only in 30Hrz in 4K and I would to go on display port.

Thank you all in advance.
 
OneyedK said:
Next time I'm bored with this perfectly working mac, I'll read the manual of OpenCore o_O
Click to expand...
Not entirely your fault indeed. Even you read the OpenCore manual, you won't find anything about this.

This is about the integrity / operational condition of UEFI GOP. Not really part of the OpenCore. Therefore, the OpenCore manual won't mention that.
 
  • Like
Reactions: cdf
saltarob said:
I did some testing with ScanPolicy and Vault with the EFI package installed on an external USB drive. And it worked well.
But now as I moved the EFI package to an internal drive suddenly both features are not working anymore.

When the EFI is on the internal drive the NVMe PCI device shows only up with ScanPolicy 0 whereas with the EFI on the USB drive it showed up with ScanPolicy 0x10F0103 (17,760,515):

View attachment 969994

Why is the EFI behaving differently on an internal drive then on an external drive? Any ideas?

Same with the Vault. With the EFI on the external drive the signing was very easy and reliable. But as soon as I moved it to the internal drive the EFI didn't boot with the signing applied.

What could be wrong?
Thank you so much for your help.
Click to expand...
It was a bug and it is fixed with the a9af4ab commit.
 
  • Like
Reactions: Dayo
Hi Folks!
Is there any particular configuration for the ethernet with OpenCore? Since I installed it my ethernet ports on cMP are not working anymore.
Does anyone know where to take a look at?
Thanks.
 
RickyHunter said:
Hi Folks!
Is there any particular configuration for the ethernet with OpenCore? Since I installed it my ethernet ports on cMP are not working anymore.
Does anyone know where to take a look at?
Thanks.
Click to expand...

OpenCore should not cause any issues with ethernet. Is your installation of macOS unpatched?
 
paalb said:
I still have a question to the wiki post: What is the reasons for “Making External Drives Internal”? Need no long explanation, just some keywords for Google.
Click to expand...
There are few reasons. E.g. SWAP can only be used when the boot drive ident as internal.

Let’s say you boot from NVMe, and that’s and external drive. MacOS can’t use SWAP when you are running out of memory.
 
Last edited:
  • Like
Reactions: roobarb! and paalb
Hi,

I followed your guide on a flashed and updated 4.1 (3.46, 48GB, 2TB SSD NVME, Nitro+ RX580).
Great guide, thank you for your efforts on that.

I have a question however. Catalina is installed my PCI NVME. After the installation this drive appears 3 times in Disk Utility. Once with the normal name and once with "-Data" behind it. Is this normal? I didn't find any reference to this in the guide? Because of this I don't want to execute the part to get it to show as internal for now.

Disks.png


Thanks !
 
OneyedK said:
Physically remove Disk A, reset smc, now you should be able to boot from Disk B.
Click to expand...
Thx OneyedK. I'm able to boot also from disk A where I installed Catalina by OpenCore, but only on hdmi. The principal problem is that I'm not able to boot from the two display port.
 
Might have been asked here before, but is there any way to change which monitor the boot menu and boot screen show on? I use one monitor connected by DisplayPort and the other connected by HDMI, OpenCore always uses the DisplayPort monitor. Anyway to make it use the HDMI one instead?
 
Ieziebie said:
Hi,

I followed your guide on a flashed and updated 4.1 (3.46, 48GB, 2TB SSD NVME, Nitro+ RX580).
Great guide, thank you for your efforts on that.

I have a question however. Catalina is installed my PCI NVME. After the installation this drive appears 3 times in Disk Utility. Once with the normal name and once with "-Data" behind it. Is this normal? I didn't find any reference to this in the guide? Because of this I don't want to execute the part to get it to show as internal for now.

View attachment 974819

Thanks !
Click to expand...

Normally there should be two volumes, one for the OS and the other for your data. Does the diskutil in terminal also list two "- Data" volumes? In any case, making the disk internal should not break anything.

donchan said:
Thx OneyedK. I'm able to boot also from disk A where I installed Catalina by OpenCore, but only on hdmi. The principal problem is that I'm not able to boot from the two display port.
Click to expand...

This sounds like agdpmod is not properly enabled. Recheck your steps for enabling hardware acceleration.

thewoolysheep08 said:
Might have been asked here before, but is there any way to change which monitor the boot menu and boot screen show on? I use one monitor connected by DisplayPort and the other connected by HDMI, OpenCore always uses the DisplayPort monitor. Anyway to make it use the HDMI one instead?
Click to expand...

This is a great question. I'd be interested in knowing this as well.
 
  • Like
Reactions: Stefano85
donchan said:
I have to set agdpmod=pikera ?

Thx.
Click to expand...

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">.
 
It does show two as well. I did follow the guide twice, but I fully formatted the disk before starting over again.

1603818314295.png


Is there any way to get rid of this? Sounds a bit OCD-ish but it's mentally bothering me :)
 
Ieziebie said:
It does show two as well. I did follow the guide twice, but I fully formatted the disk before starting over again.

View attachment 975001

Is there any way to get rid of this? Sounds a bit OCD-ish but it's mentally bothering me :)
Click to expand...
If you change the name of the main volume the corresponding DATA volume will automatically change. This way you will find out, which is the third volume and you can rename it to anything you want.
 
  • Like
Reactions: JedNZ, OneyedK, cdf and 1 other person
Actually, when trying to make the drive internal, I have to find out the device root and that gives me the following result: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)

And that's too much.... when checking the plist it says only one device is allowed. Now...... which one do I pick there? How can I find out which one is the correct one?

Thanks for all the help !
 
Ieziebie said:
PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)
Click to expand...
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>
 
Last edited:
cdf said:
OpenCore on Legacy Apple Hardware

This guide explains how to use the excellent OpenCore bootloader on a classic Mac Pro to install, run and update macOS Catalina, resulting in a clean, unpatched operating system no different than on a supported Mac.

Why OpenCore?

There are several advantages to using OpenCore on a classic Mac Pro:

Boot picker screen (even with a standard graphics card)
View attachment 916024
Software Update (just like on a supported Mac)
View attachment 882160
Hardware acceleration (and DRM for Netflix on Safari)View attachment 919405
Requirements

Mac Pro modelEarly 2009 with MacPro5,1 firmware,* Mid 2010 or Mid 2012
Processor architectureWestmere (E56xx, L56xx, X56xx) / Gulftown (W36xx)
Boot ROM version144.0.0.0.0*
GraphicsCatalina supported GPU**, EFI (flashed) or a standard UEFI card (PC GPU)

* Need to upgrade? See the upgrade instructions.
** Several GPUs that are supported with High Sierra had support removed from Mojave and Catalina, like any non-Kepler generation NVIDIA GPUs or AMD GPUs earlier than HD 7950. Several HD 78xx GPUs (Pitcairn) were rebadged as R9 2xx and are not supported anymore by Mojave/Catalina drivers. All Mac Pro factory GPUs had support removed with Mojave.

PART I
Basic Installation




PART II
Advanced Configuration




PART III
Maintenance




APPENDIX​




Acknowledgements

A big thank you to @vit9696 and the other talented developers of Acidanthera for making all of this possible. Special gratitude goes to @h9826790 for spearheading the hardware acceleration study and @startergo for the relentless testing that led to boot screen support. And thanks to all those that have contributed to this thread!
Click to expand...
I have followed the Appendix guide to a T with regards to installing Windows 10 in UEFI mode on a separate drive in my Mac Pro, I currently do not want Catalina and I am happy with Mojave which is booting from an NVme 1TB drive in a PCie slot. This method works for a while and then Windows slows to a crawl and then becomes unbootable. Should I try to install an older version of Windows 10 and not update it? I just want to play a few games and have a nice selectable menu for booting into Windows. I also like the hardware acceleration for H.264 and HVEC on the Mac side of things. Can anyone point to a method with using the APPENDIX method that will stick and not send Windows into an unbootable state?
 
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.
 
Last edited:
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