MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[tsialex]

I do not recall having to disable CSR.

You can't dump or flash to the MacPro5,1 BootROM without SIP being disabled, unless you flashed from 10.9.

 

[MacNB2]

You can't dump or flash to the MacPro5,1 BootROM without SIP being disabled, unless you flashed from 10.9.

Well clearly I must have already had CSR disabled (probably from when I was flashing your Never-booted ROM).

In any case, instructions in Post #1 are clear and already do state that CSR needs to be disabled and so there's no need to add any new instructions.

 

[Macschrauber]

it's exactly "csr - allow untrusted kexts" to kextload DirectHw.kext for letting Flashrom dump and flash the spi chip what is needed.

the terminal command for recovery is:

csrutil enable --without kext

just tested it again with natively booted Mojave.

Works for the Dumper and DosDude's RomTool.

 

[Gustav Holdoff]

I do not argue - you are all gods here, but please explain for ordinary users
what macos is used during the flash procedure? really possible in monterey with opencore?-
of course not, with opencore I can boot into recovery, turn off the sip, turn off the computer
then take out my opencore disk, insert mojave instead and replace the video card with supported one
then turn on the computer and hold the button on to enter the flash mod
I'm not sure that these manipulations are correct (without opencore i can boot only mojave/highsierra and can't boot monterey)
Or is it still in Mojave/Haysierra - according to all the rules, as it recommends according to the classics, for example, Tsialex? with disconnection of all hdd and psi-e

 

[tsialex]

I do not argue - you are all gods here, but please explain for ordinary users
what macos is used during the flash procedure?

ROMTool is a GUI for DirectHW + flashrom and works from 10.9 to 12.6.8, except 10.10. I'd had a lot of issues with Ventura, I do not even try to flash from Ventura anymore.

Macschrauber dumper have a different version of DirectHW that is compatible with 10.10, tho.

really possible in monterey with opencore?

It's one of the things that while you can do, any careful person should really avoid. Since we can't say how you configured your Mac Pro, what you messed up with your config.plist, if the Mac Pro is stable and etc, the recommendation is always go to the basics and avoid all risks. If anything goes wrong, you have a boat anchor until you replace the SPI flash memory or install a MATT card.

If your Mac Pro ever crashed while running unsupported macOS releases, you should do not flash from it.

Or is it still in Mojave/Haysierra - according to all the rules, as it recommends according to the classics, for example, Tsialex? with disconnection of all hdd and psi-e

It's up to you. For people with MATT cards, it's a no-brainer, but for others, it's a risk assessment that you should err on the side of caution.

 

[cybercylon]

I've been following along with the discussion about the EnableGop option. I was gifted with a cMP a few years ago that mostly ran Windows 7 under legacy mode, and I think the highest macOS version run on it was high Sierra.

When it got into my hands, the first thing that I did was the old reboot five times and then dumped an image of the Rom. The free space available under VSS Store is around what is expected for a dual processor machine and all dimm slots filled. I periodically flash with that image.

I assume the safest starting point is with a reconstructed rom image though before even attempting to use the EnableGop option. I don't want to make a boat anchor. Thanks.

 

[Madr]

I got a Mac pro 5,1 flashed to 144 with an unflashed XFX ghost 7950. I used the normal opencore legacy patcher guide to install Monterey and used this extra chapter in the guide to get into the installer:

Note for Mac Pros/Xserves/iMacs with unflashed GPUs (which also links to this tread but it's huge)

After the install i get a black screen. I think i need to get into the USB and select the installation with the grey HD but have no idea how to get there because i get a black screen. And as far as i can see the guide doesn't mention this.

I got a 5770 though so i'll swap that in to get past the second part of the installer.

Anybody got any other tips?

I think that keeping the 7950 in the machine during the install will get it running. Because I had to install Sierra again with the 7950 in the machine and then work my way up to mojave to do the firmware and mojave install (tip: my machine switched from dvi to hdmi and was doing the install first with the dvi but didn't give screen)

Thank you!

 

[Madr]

I got a Mac pro 5,1 flashed to 144 with an unflashed XFX ghost 7950. I used the normal opencore legacy patcher guide to install Monterey and used this extra chapter in the guide to get into the installer:

Note for Mac Pros/Xserves/iMacs with unflashed GPUs (which also links to this tread but it's huge)

After the install i get a black screen. I think i need to get into the USB and select the installation with the grey HD but have no idea how to get there because i get a black screen. And as far as i can see the guide doesn't mention this.

I got a 5770 though so i'll swap that in to get past the second part of the installer.

Anybody got any other tips?

I think that keeping the 7950 in the machine during the install will get it running. Because I had to install Sierra again with the 7950 in the machine and then work my way up to mojave to do the firmware and mojave install (tip: my machine switched from dvi to hdmi and was doing the install first with the dvi but didn't give screen)

Thank you!

Didn't work. Used the 5770 for the second part of install and build the system and wrote to internal hd but after that with 7950 it would not give a screen after even 5 minutes.

I think if i go back the 5770 it will work but i only have 2 6 pin power cables and when i run the 5770 with the 7950 i need 3. And i'm too afraid to run with only 2 because i once destroyed a video card some years ago.

Nor have i done any root patching yet. Only removed the bootpicker and rebuild OC and write to internal disk.

Guide said something about safe mode when you get a black screen but not sure it is for my problem. Not sure how to get into safe mode without a bootscreen using the 7950.

oh edit: i think i did a root patching before i build to the the internal disk the first time. I think it selected the 5770 video drivers and wifi.

Maybe i need to add the 7950 drivers manually while using the 5770 and then restart with the 7950 in it.

 

[hwojtek]

I am not sure there is a thing like "7950 drivers". Been a long time since I had a similar card (R9 280x, mind you, a fancier 7970) but I believe yours should work out of the box when directly replacing the 5770. I tinkered with my card a lot and there were numerous occasions when I had to modify it outside the Mac, so I was replacing cards a lot and never had to do anything within the Mac to make it work once inside. I don't know about current situation, though, moved on to a RX570 years ago and just recently to a RX6800 XT.
If everything is OK with your card, it should fire up without hesitation (though it is possible it will start putting out video only once the initial boot is finished, on the login screen). Even if your OS configuration would not support it, it would output video, just not hardware accelerated.
If you are worried about powering the GPUs, get a super cheap SATA to 6-pin PCIe adapter, hook it up to a spare SATA power port and power your 5770 with this adapter.
Also, there is a vast, well-documented thread with software tools to allow 7950 cards to be flashed with modified, Apple-friendly firmware. Once you have your 5770 powered and both cards recognized in System Profiler, you may find it easier to boot an officially supported OS (without OpenCore) from a spare hard drive, reflash the 7950 for native boot screens and go from there... Word of warning, though, when two cards are present and you want to reflash one of them, be double-cautious when typing commands.

 

[Madr]

I am not sure there is a thing like "7950 drivers". Been a long time since I had a similar card (R9 280x, mind you, a fancier 7970) but I believe yours should work out of the box when directly replacing the 5770. I tinkered with my card a lot and there were numerous occasions when I had to modify it outside the Mac, so I was replacing cards a lot and never had to do anything within the Mac to make it work once inside. I don't know about current situation, though, moved on to a RX570 years ago and just recently to a RX6800 XT.
If everything is OK with your card, it should fire up without hesitation (though it is possible it will start putting out video only once the initial boot is finished, on the login screen). Even if your OS configuration would not support it, it would output video, just not hardware accelerated.
If you are worried about powering the GPUs, get a super cheap SATA to 6-pin PCIe adapter, hook it up to a spare SATA power port and power your 5770 with this adapter.
Also, there is a vast, well-documented thread with software tools to allow 7950 cards to be flashed with modified, Apple-friendly firmware. Once you have your 5770 powered and both cards recognized in System Profiler, you may find it easier to boot an officially supported OS (without OpenCore) from a spare hard drive, reflash the 7950 for native boot screens and go from there... Word of warning, though, when two cards are present and you want to reflash one of them, be double-cautious when typing commands.

Thanks! The 7950 worked in my Sierra Hackintosh (tested this weekend again) and worked in Mojave with this machine. Maybe it switched output ports again? I don't have a display cable nor monitor. So i can only test hdmi and dvi. It changed from dvi to hdmi while i was going to Mojave.

And maybe i should wait a bit longer while booting. And I think i try to set the boot mount again like in the OCLP guide about unflashed GPU's. BTW the guide links to this tread but no idea how i can find it here with 500 pages. I think the guide is missing info on this when it restarts? But maybe i don't understand it correctly.

And about the power cables. What i mean is that when i use 7950 and 5770 together in 1 machine I need 3 times 6 pins power. And the Mac Pro only has 2. But maybe i don't understand you correctly.

Thanks again for the reply!

 

[hwojtek]

Thanks! The 7950 worked in my Sierra Hackintosh (tested this weekend again) and worked in Mojave with this machine. Maybe it switched output ports again? I don't have a display cable nor monitor. So i can only test hdmi and dvi. It changed from dvi to hdmi while i was going to Mojave.

Yes, not all outputs work in all situations. If I remember correctly, the DisplayPort output is the most reliable.

And about the power cables. What i mean is that when i use 7950 and 5770 together in 1 machine I need 3 times 6 pins power. And the Mac Pro only has 2. But maybe i don't understand you correctly.

Yes, it has two PCIe power outputs 75W each on the mainboard. But the adapter I linked allows you to power a PCIe card separately from empty SATA power ports. So you can hook up both motherboard ports to the 7950 and power your 5770 from SATA.
If you want to go for a reflash (the Hackintosh may come in handy), I believe all the files needed, including a readme, are in the ZIP attached below. I believe your card has dual EPROM, so make sure you don't play with the switch while installing and flash Mac-friendly firmware with the switch in one position, so you can recover from a borked reflash with the the switch in position 2. It may be, that the card has a standard (BIOS) firmware in position 1 and PC EFI firmware in position 2. Some cards have regular firmware in position 1 and overclocked firmware in position 2. You may find it helpful if you gave us the exact details of the card.

 

[Madr]

Yes, not all outputs work in all situations. If I remember correctly, the DisplayPort output is the most reliable.


Yes, it has two PCIe power outputs 75W each on the mainboard. But the adapter I linked allows you to power a PCIe card separately from empty SATA power ports. So you can hook up both motherboard ports to the 7950 and power your 5770 from SATA.
If you want to go for a reflash (the Hackintosh may come in handy), I believe all the files needed, including a readme, are in the ZIP attached below. I believe your card has dual EPROM, so make sure you don't play with the switch while installing and flash Mac-friendly firmware with the switch in one position, so you can recover from a borked reflash with the the switch in position 2. It may be, that the card has a standard (BIOS) firmware in position 1 and PC EFI firmware in position 2. Some cards have regular firmware in position 1 and overclocked firmware in position 2. You may find it helpful if you gave us the exact details of the card.

- Thank you! I ordered some active displayport to hdmi converters (1080p and 4k, so 2 versions) I think a monitor with displayport would be the best but i try to keep my spending low and a 4k with displayport will be on my list in the future. You think an adapter could give more problems than a direct to display cable?

- Cool thanks! I've read too fast. Sorry!

That is the best option! I will try and get a cable like that. Then i don't need to reflash my 7950

Also i think my XFX ghost hasn't got a bootflash 1 en 2 switch. I've checked and the solder pads for a switch are there but no switch. Also i rather not flash this card now as it's my main and best card i have for the moment. Also i read that opencore can use non flashed gpu cards and still have a boot picker. With that sata to 5770 power cable i think i'm there. But maybe flash the card in the future.

I once flashed a 5770 pc card but i think the flash was not target at the specific card i had and it wasn't cooling enough and now it doesn't give any screen at all.

I would like to try a flashing of the card if it's an adjusted version of the rom that is on my card now. But maybe you mean that and i'm not reading properly. AGAIN! Hahahaha

- I'm looking into getting a (Chinese) RX580. It's specs are a bit less than a normal 580 and there is still a debate about being an old mining card. I've found a Soyo but need to search on this forum if people used it on a mac pro. I only need Mojave and Monterey on this machine so i think a RX 580 can handle that is much more newer and fit for these OS-es. Have you seen anybody here using these cheap Chinese RX580's? I will search for some brand names like soyo here too to see what is up.

- Again thank you for your time and effort. Really appreciate it.

 

[teiki arii]

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.9.4]

../..

1. Spoiler: Multi monitors fix for Big Sur

   For Big Sur and Monterey, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
   
2. Reboot

Hello everyone,
thank you very much to the MacRumors' community members for the work they have done to make my MacPro 5.1 work so well with McOS Monterey. Before making up my mind to buy a M2 Studio Max, I tried the mod to update Monterey on cMP.
Nevertheless, after using OCLP 0.6.8 to install Monterey on my cMP, I had a first issue with DxO PhotoLab 6. My Sapphire RX580 8GB Pulse didn't work (even if compatibility seems to be ok) and it took me 18 minutes to export my file with DeepPRIME XD on. Actually, CPU worked instead of GPU.
Thanks to h9826790 and manually update via the attached package updated to 0.9.4, I succeeded in making the RX580 work on DxO PL6: instead of 18 minutes, I am able to export RAW files with DeepPRIME XD process into tiff files in 45s!!!
But, DP doesn't work anymore. I tried to change BordProduct id. 7BA5B2D9E42DDD94 to 27AD2F918AE68F61, DP issue is still there.
Is there a solution to get both the RX580 GPU (on DxO PL6) and DP output working on my cMP?
Best regards for your help.

 

[h9826790]

../..

Hello everyone,
thank you very much to the MacRumors' community members for the work they have done to make my MacPro 5.1 work so well with McOS Monterey. Before making up my mind to buy a M2 Studio Max, I tried the mod to update Monterey on cMP.
Nevertheless, after using OCLP 0.6.8 to install Monterey on my cMP, I had a first issue with DxO PhotoLab 6. My Sapphire RX580 8GB Pulse didn't work (even if compatibility seems to be ok) and it took me 18 minutes to export my file with DeepPRIME XD on. Actually, CPU worked instead of GPU.
Thanks to h9826790 and manually update via the attached package updated to 0.9.4, I succeeded in making the RX580 work on DxO PL6: instead of 18 minutes, I am able to export RAW files with DeepPRIME XD process into tiff files in 45s!!!
But, DP doesn't work anymore. I tried to change BordProduct id. 7BA5B2D9E42DDD94 to 27AD2F918AE68F61, DP issue is still there.
Is there a solution to get both the RX580 GPU (on DxO PL6) and DP output working on my cMP?
Best regards for your help.

There are TWO 7BA5B2D9E42DDD94 in the newer (e.g. 0.9.4) config.plist. Please change BOTH to 27AD2F918AE68F61

 

[teiki arii]

Hello Martin,
thank you very much for your prompt answer!
I'll try and let you know.
Best regards!

 

[teiki arii]

There are TWO 7BA5B2D9E42DDD94 in the newer (e.g. 0.9.4) config.plist. Please change BOTH to 27AD2F918AE68F61

Hi Martin,
actually, the 7BA5B2D9E42DDD94 Id doesn't exist anymore in the config.plist file. 27AD2F918AE68F61 id is three times repeated...

Spoiler: my config.plist

../..

<key>PlatformInfo</key>

<dict>

<key>Automatic</key>

<false/>

<key>CustomMemory</key>

<false/>

<key>DataHub</key>

<dict>

<key>ARTFrequency</key>

<integer>0</integer>

<key>BoardProduct</key>

<string>Mac-27AD2F918AE68F61</string>

<key>BoardRevision</key>

<data>

</data>

<key>DevicePathsSupported</key>

<integer>0</integer>

<key>FSBFrequency</key>

<integer>0</integer>

<key>InitialTSC</key>

<integer>0</integer>

<key>PlatformName</key>

<string></string>

<key>SmcBranch</key>

<data>

</data>

<key>SmcPlatform</key>

<data>

</data>

<key>SmcRevision</key>

<data>

</data>

<key>StartupPowerEvents</key>

<integer>0</integer>

<key>SystemProductName</key>

<string>MacPro5,1</string>

<key>SystemSerialNumber</key>

<string></string>

<key>SystemUUID</key>

<string></string>

</dict>

<key>Generic</key>

<dict>

<key>AdviseFeatures</key>

<true/>

<key>MLB</key>

<string></string>

<key>MaxBIOSVersion</key>

<true/>

<key>ProcessorType</key>

<integer>0</integer>

<key>ROM</key>

<data>

</data>

<key>SpoofVendor</key>

<true/>

<key>SystemMemoryStatus</key>

<string>Auto</string>

<key>SystemProductName</key>

<string></string>

<key>SystemSerialNumber</key>

<string></string>

<key>SystemUUID</key>

<string></string>

</dict>

<key>PlatformNVRAM</key>

<dict>

<key>BID</key>

<string>Mac-27AD2F918AE68F61</string>

<key>FirmwareFeatures</key>

<data>

A1Qc4Ag=

</data>

<key>FirmwareFeaturesMask</key>

<data>

A1Qc4Ag=

</data>

<key>MLB</key>

<string></string>

<key>ROM</key>

<data>

</data>

<key>SystemSerialNumber</key>

<string></string>

<key>SystemUUID</key>

<string></string>

</dict>

<key>SMBIOS</key>

<dict>

<key>BIOSReleaseDate</key>

<string></string>

<key>BIOSVendor</key>

<string></string>

<key>BIOSVersion</key>

<string>9999.999.999.999.999</string>

<key>BoardAssetTag</key>

<string></string>

<key>BoardLocationInChassis</key>

<string></string>

<key>BoardManufacturer</key>

<string></string>

<key>BoardProduct</key>

<string>Mac-27AD2F918AE68F61</string>

<key>BoardSerialNumber</key>

<string></string>

<key>BoardType</key>

<integer>0</integer>

<key>BoardVersion</key>

<string>MacPro5,1</string>

<key>ChassisAssetTag</key>

<string></string>

<key>ChassisManufacturer</key>

<string></string>

<key>ChassisSerialNumber</key>

<string></string>

<key>ChassisType</key>

<integer>0</integer>

<key>ChassisVersion</key>

<string></string>

<key>FirmwareFeatures</key>

<data>

A1Qc4Ag=

</data>

<key>FirmwareFeaturesMask</key>

<data>

A1Qc4Ag=

</data>

<key>PlatformFeature</key>

<integer>-1</integer>

<key>ProcessorType</key>

<integer>0</integer>

<key>SmcVersion</key>

<data>

</data>

<key>SystemFamily</key>

<string></string>

<key>SystemManufacturer</key>

<string></string>

<key>SystemProductName</key>

<string>MacPro5,1</string>

<key>SystemSKUNumber</key>

<string></string>

<key>SystemSerialNumber</key>

<string></string>

<key>SystemUUID</key>

<string></string>

<key>SystemVersion</key>

<string></string>

</dict>

../..

So, what is to be done?
Best regards.

PS: My Monitor only have DP input. Perhaps, I should try for adapter HDMI-->DP (USB supply)?

BENFEI HDMI to DisplayPort Adapter, HDMI Source to DisplayPort Monitor Compatible with PC Graphics Card Laptop PS5 Xbox One(360) Supporting 4K@60Hz 2K@144Hz 1080P@165Hz

BENFEI HDMI to DisplayPort Adapter, HDMI Source to DisplayPort Monitor Compatible with PC Graphics Card Laptop PS5 Xbox One(360) Supporting 4K@60Hz 2K@144Hz 1080P@165Hz

www.amazon.com

"But Unfortunately it (BENFEI adapter) doesn't seem to support extending the desktop to the dual monitors (it provides an extra desktop but shows the same thing on both screens), but even with turning one of those monitors off and extending to the single monitor, I have so much more space to work."

 

[hwojtek]

But Unfortunately it (BENFEI adapter) doesn't seem to support extending the desktop to the dual monitors (it provides an extra desktop but shows the same thing on both screens)

Just disable mirroring in "Displays" preference pane and set to "Extended Display".

Your config.plist (it's a mess). Change:

<key>PlatformNVRAM</key>
<dict>
<key>BID</key>
<string>Mac-27AD2F918AE68F61</string>
<key>FirmwareFeatures</key>

to

<key>PlatformNVRAM</key>
<dict>
<key>BID</key>
<string></string>
<key>FirmwareFeatures</key>

You accidentally pasted the string into a wrong place.

 

[startergo]

Legacy Windows boot through OC:

Implement legacy OS booting support by Goldfish64 · Pull Request #482 · acidanthera/OpenCorePkg

Adds support for booting of legacy OSes such as older versions of Windows or situations where legacy Windows must be used for proper functionality of hardware. Scope includes both Macs (via legacy ...

github.com

 

[teiki arii]

You accidentally pasted the string into a wrong place.

Hi hwojtek,
certainly (actually, I only have changed one number id instead of the two and it did what happened). So, I pasted the config.plist from open 0.9.4 to Boot Disk EFI again , changed the id (x2) as I should have done, and it work perfectly with two monitors, one with DP input, the other with HDMI input, both together.
Thank you very much for your support!
teiki.

PS: No Mac STUDIO Max anymore for the moment. Even if Studio is quite faster, as I mostly work on PS, LR and DxO PL, cMP opencore Monterey is quite enough for my needs... Best regards.

 

[cdf]

The guide has been updated to OpenCore version 0.9.5. This version of OC brings legacy boot support (great work by OC dev Goldfish64!). By adding the OpenLegacyBoot.efi driver, it is now possible to boot legacy/CSM Windows installations through OC. Happy updating!

 

[startergo]

The guide has been updated to OpenCore version 0.9.5. This version of OC brings legacy boot support (great work by OC dev Goldfish64!). By adding the OpenLegacyBoot.efi driver, it is now possible to boot legacy/CSM Windows installations through OC. Happy updating!

I have tried it and it does not boot the legacy Windows. Have you tried it yet?

 

[cdf]

Unfortunately, I don't have a legacy installation to test. Hmm... I suppose you don't have any problems with native legacy booting (possibly through EnableGop), right?

 

[sfalatko]

Unfortunately, I don't have a legacy installation to test. Hmm... I suppose you don't have any problems with native legacy booting (possibly through EnableGop), right?

@cdf - Looking at the differences file it says "Add OpenLegacyBoot.efi and also optionally (see below) OpenNtfsDxe.efi to the config.plist Drivers section."

I don't see that in the "Maintenance" section of the first post. It seems that there should be a modification to config.plist to enable the driver.

Regards,
sfalatko

 

[cdf]

I don't see that in the "Maintenance" section of the first post. It seems that there should be a modification to config.plist to enable the driver.

Indeed, legacy booting with OC requires the addition of a driver, but I've left this out of the guide for now. The reason is that the same functionality should already be available natively with EnableGop. I may add some details later once more testing gets done.

 

[sfalatko]

@cdf - Looking at the differences file it says "Add OpenLegacyBoot.efi and also optionally (see below) OpenNtfsDxe.efi to the config.plist Drivers section."

I don't see that in the "Maintenance" section of the first post. It seems that there should be a modification to config.plist to enable the driver.

Regards,
sfalatko

Follow up - I added the OpenLegacyBoot.efi to the UEFI > Drivers section of my config.plist and it works booting a legacy installation of Windows.

One issue I have - there are two entries titled "Legacy Boot(Windows)". One boots into my Win 10 install and one to the Microsoft "no OS found" screen. My guess is the driver is seeing my Win10 partition and the "System Reserved" partition and providing entries for both in the boot picker.

Here's the code I added -

<key>UEFI</key>
<dict>
⋮
<key>Drivers</key>
<dict>
⋮
<key>Arguments</key>
<string></string>
<key>Comment</key>
<string>OpenCore plugin for Booting Legacy OSs</string>
<key>Enabled</key>
<true/>
<key>LoadEarly</key>
<false/>
<key>Path</key>
<string>OpenLegacyBoot.efi</string>

⋮
</dict>
⋮
</dict>