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
You could perform the installation on an Ivy+ mac, replace Preboot's os.dmg once the Ivy machine stalls (No AVX-2 either), go through the setup assistant, and install the drive in the cMP once you reach the desktop
Whoever has MBP11,4 has AVX2, so it is a suitable candidate for installation except the GPU acceleration will be missing.
Check for AVX2:
Code:
sysctl machdep.cpu | grep -o AVX2
Code:
sysctl machdep.cpu | tr ' ' '\n' | grep AVX
Last edited:
Hi, first of all thank you very much for the information and for the link.
Sorry for the dumb question (if it is) but why Ivy bridge or newer?
Isn't sandy bridge ok since it supports avx1?
Because even my Sandy Brigde iMac using the same method and changes cannot boot into normal mode, I get Windowserver crashes even using a still supported Polaris dGPU (only safe mode boot works). Even after the initial (user) setup from safe mode rebooting into normal mode ends up with the same kind of Windowserver crashes.
On the other hand at least (OCLP) injected patches for BCM5701 Ethernet are still working, upgrades BT/WiFi BCM94360CD works, too.
Searching for AVX2 needs this command:
sysctl -a | grep machdep.cpu.leaf7_features | grep -o AVX2Note:
Would be interesting to see a successful boot into normal mode with an MacPro5,1/Sandy Bridge iMac using a supported Polaris+ dGPU.
Edit:
Booting the same disk on an iMac11,3 (Lynnfield X4370 + Polaris RX480)) and iMac10,1 (Wolfdale+R9 M370X) into safe mode gives me additional crashes with LoginWindow, logind, and many more. This comes closer to the observations made by @Jazzzny. Main difference is no AVX1 here. The older the CPU, the more different crashes...
Last edited:
Can’t get it to work on mine with Ventura so I’m removing cards and putting a fresh nvme ssd in it to start from scratch 🤔
Thanks for the good wishes.
As this EFI from @Jazzzny (post 11,095) is from an OCLP installation it's been a headache for me to determine what the purpose of several instructions is. I have never used OCLP. I have always stuck with CDF's instruction on Post 1 of this thread and it would be far better if I left it well alone rather than sending myself and others down the wrong track.
For example, the Jazzzny EFI is built on OC 0.8.0 - we are all up to 0.8.1. It's not using AVXpel but seems to me to be using NoAVXFSCompressionTypeZlib.kext instead. I'm not sure which version of Lilu or WhateverGreen it's using? I am already on the latest releases.
There are many other far more competent people on this thread who can examine what OCLP seems to have achieved and advise how to adapt our (from Post1) config.plist and which kexts to include.
TLDR: I believe that Ventura should boot with a "Clean" OpenCore install if two conditions are met:
1. The APFS hash patch is applied (Find this under Kernel -> Patch of the OCLP EFI)
2. A full spoof to the MacPro7,1 is applied
Everything else should be optional, but I suggest updating all of the Acidanthera kexts.
1. The APFS hash patch is applied (Find this under Kernel -> Patch of the OCLP EFI)
2. A full spoof to the MacPro7,1 is applied
Everything else should be optional, but I suggest updating all of the Acidanthera kexts.
Before proceeding with Ventura upgrade consider this:
github.com
macOS Ventura and OpenCore Legacy Patcher Support · Issue #998 · dortania/OpenCore-Legacy-Patcher
This page will be updated as we learn more about Ventura and the changes within. If you're not an active developer for legacy Macs, DO NOT INSTALL VENTURA. Even if you're bored, more random users i...
github.com
So I thought I'll post a follow-up of this question. Having nothing to do today I thought I might aswell give it a try and see if I brick my machine or if it works.Hello there, this is my first post here, I have followed the Facebook Group for Mac Pro and OpenCore for a while but so far never jumped to install OpenCore. Until now.
I want OpenCore and the latest supported operating system on my Mac Pro. It is a 4.1 flashed to 5.1 running Mojave in the latest version on a 580 8GB and I would like to update it.
I have read a comprehensive guide on the web which made it seem to be rather easy and some problems here on the last pages.
Can anybody of you who recently made something similar please point me in the right direction as to what to do how and when or which guide to follow? Especially will I lose my data? I am familiar with SIP and how to disable it, I have a backup graphics card which has an Apple boot rom and will show anything from the get go. Would be very nice.
I followed the easier version of Martin's guide to get a preconfigured OpenCore installation and followed his simple but absolutely sufficient YouTube video guides.
First I did the tripe NVRAM reset, then booted into recovery to disable SIP. Then I booted the machine normally, applied the changes to the EFI partition and rebooted. It already showed a boot selector and the boot screen.
For the installation of a newer OS I applied the two changes to the config.plist Martin points out in a YouTube video, restarted the machine, searched for updates and it began downloading and installing Monterey (my Mac Pro was vanilla before, except the Firmware update from 4.1 to 5.1 I did a long while back).
After some unsettling amount of times the progress bar just hang there either at "less than a minute…" or another point in the installation I thought I'll just leave it and don't do anything to it. That was a good decision because it managed to move on every time, installed everything correctly and finally booted into Monterey. So far the system seems to work normally and I am writing these lines on my freshly updated Mac Pro 4.1/5.1.
Thank you all so very much for your dedication, that will keep my old beast running for another while.
Fun fact: the OS installation of this machine is the original installation I had on my then newly purchased Mac Pro 3.1 which I bought in 2008 I think. That one got swapped out for this 4.1/5.1 in the mid 2010s and I carried the drive over. It survived numerous hardware updates and a clone to an SSD without ever being fully deleted or newly installed.
Just to add to this: I have an Atto H680 SAS Hostbus adapter with an HP Ultrium 6250 external tape drive in my Mac Pro and after installation of Monterey it first did not work. As I use tape backups regularly I tried to find a solution and found out that ATTO had new drivers even for these cards on their homepage. After installing it, the card works perfectly and I was even able to update the firmware.
Lightroom 6.14 works, too, but quite slow and with a few bugs. I hope that Serif soon launches an alternative to Lightroom like it did with Affinity Photo for Photoshop. So far so happy.
Lightroom 6.14 works, too, but quite slow and with a few bugs. I hope that Serif soon launches an alternative to Lightroom like it did with Affinity Photo for Photoshop. So far so happy.
Hi all! I got a Radeon Pro VII
The latest version of Mojave cannot use it with acceleration, although the graphics adapter ID is in the kext plist. Only in Catalina I was able to get a acceleration
My question is does anyone have any idea how to get acceleration in Mojave?
The latest version of Mojave cannot use it with acceleration, although the graphics adapter ID is in the kext plist. Only in Catalina I was able to get a acceleration
My question is does anyone have any idea how to get acceleration in Mojave?
a radeon VII is faster under mojave than in all systems after it.
are you also sure on 10.14.6 with 144.0.0.0.0 bootROM?
There you go bud, for your personal knowledge, techpowerup has a very good GPU database 👍
Specs for:
Radeon VII
AMD Radeon VII Specs
AMD Vega 20, 1750 MHz, 3840 Cores, 240 TMUs, 64 ROPs, 16384 MB HBM2, 1000 MHz, 4096 bit
Radeon Pro VII
AMD Radeon Pro VII Specs
AMD Vega 20, 1700 MHz, 3840 Cores, 240 TMUs, 64 ROPs, 16384 MB HBM2, 1000 MHz, 4096 bit
We Spoofed device-id to Radeon VII (0x66AF), but still it is identified as Vega card.
@h9826790 Can you please post your config file for Radeon VII with injected properties? Thanks.
Code:
<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>PP_PhmSoftPowerPlayTable</key>
<data>wgYLAALCBjQIAACkNQAAfAAJAAAAGr4AvgC+AAAAAAB2AAELAAAACQcAAG4EAADMAwAAzAMAAMwDAADoAwAAyQQAAG4EAABuBAAANAQAACoDAAAAAAAAAAAAAAAAAAAAAAAAAAAAALwCAABmAQAANgEAADYBAAA2AQAAXgEAACYCAABmAQAAZgEAAJMAAAAOAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAABDgAAAAEBAQEBAQEBAQABAQEBAAAAAAAAAAAAAAAAAAAAAAAAHQAAAJgIAACYCAAAmAgAANUDAACYCAAA1QMAAJgIAADVAwAAsAQAABQAAAAKDwAACg8AAF8AAABuAAAAAgAAAAAAAAABAAAAAQAAAAEAAABfAAAAZAAAAF8AAABkAAAAXwAAAGQAAABfAAAAZAAAAF8AAABkAAAAAAAAAAAAAAAAAAAAKAMAACgDAAAoAwAA4gIAACgDAADiAgAAKAMAAOICAABeAQAAFAAAAMIBAADCAQAAGQAAADIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABkAAAAUAAAAGQAAABQAAAAZAAAAFAAAABkAAAAUAAAAGQAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwAAAP/v9DkAAAAAvgAAAAAAAAAAAAAAAAAAAL4AAAAyAAAASgEAAGQAbgBeAHMAcwD///////8AAAAAAAAAAAEAcwAAAAAAAAAAAPAK8AqgD6APJgAAAAEBCQAAAAAAAAAAAFuxvz7sUfi+ZRlSPwABCABkO58/Ft6lvQAAAAAAAAAAAAAAAAABCAA1Xpo/jzYuPgAAAAAAAAAAAAAAAAABCABpb7A/SDMWPQAAAAAAAAAAAAAAAAABCADlYaE/EvdYvQAAAAAAAAAAAAAAAAABAwC1FYM/wt0ZPgAAAAAAAAAAAAAAAAABCACGOIY/Dr4wPgAAAAAAAAAAAAAAAAABCACDwFo/TaHzPQAAAAAAAAAAAAAAAAIBCAAAAAAAAAAAAKRwjT/kFIW/1ecyPwIBAwAAAAAAAAAAAAAAAAAAAAAA1ecyPwEBCAAAAIA/AAAAANGR/D4fhSu/Mnd1P7wCKANuBFwFCgaTBtUG7QYJBwAAAAAAAAAAAAAAAAAAZgHmAWsC9AJSA8wDbgRuBDYBkAEMAmsCqAL0AlIDzAM2AZABDAJrAqgC9AJSA8wDNgEMAjcCawKoAvQCUgPMA14BIANMBEwEJgJiArIC+AJmA8ADOATJBGYBxgE3AqgC9AJSA8wDbgRmAcYBNwKoAvQCUgPMA24EkwDyAFgB5AEVAqoDEwQ0BA4BHAIqAwAAAAAAAAAAAAAJB24EzAPMA8wD6ANuBG4ENAQqA8kEAADIACwBYAnwCigDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkHAQAAAAAAAAIGBlAANAEAAAAAAAAAAAAAAACQAZABkAGQAZABkAGQARQAVAtUCwoPUAAAAAACAAAAAAAAAAAAAQAAAAAAAFCNlzwK16M7AAAAAOqymDyHokA9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAABAAAAAAAAAKAAAAAIEAIQGgRMBOgD6APoA+gDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACGCyILVAsAAJABkAE4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=</data>
<key>model</key>
<string>AMD Radeon VII</string>
<key>ATY,EFIVersion</key>
<string>01.06.1604</string>
<key>ATY,EFIVersionB</key>
<string>113-D3600200-106</string>
</dict>
</dict>
<key>Delete</key>
<dict/>
</dict>If you want to spoof the GPU name, all you need is just
Code:
<key>model</key>
<string>AMD Radeon VII</string>Of course, you can make it
Code:
<key>model</key>
<string>AMD Radeon Pro VII</string>For info, it's better to keep the prefix
AMD, otherwise, some software (e.g. VideoProc) may not able to show the GPU ident properly.
Thanks. This is the SSDT for Radeon VII Pro (it attaches through 3 bridges to GFX0):
Code:
DefinitionBlock ("", "SSDT", 2, "DRTNIA", "AMDGPU", 0x00001000)
{
External (_SB_.PCI0.IOU0.PXS1, DeviceObj)
External (DTGP, MethodObj) // 5 Arguments
Scope (\_SB.PCI0.IOU0.PXS1)
{
Device (BRG0)
{
Name (_ADR, 0x00100000) // _ADR: Address
Device (BRG1)
{
Name (_ADR, Zero) // _ADR: Address
Device (BRG2)
{
Name (_ADR, Zero) // _ADR: Address
Device (GFX0)
{
Name (_ADR, Zero) // _ADR: Address
If (_OSI ("Darwin"))
{
Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
Local0 = Package (0x06)
{
"model",
Buffer (0x0F)
{
"AMD Radeon VII"
},
"ATY,EFIVersion",
Buffer (0x0A)
{
/* 0000 */ 0x30, 0x31, 0x2E, 0x30, 0x36, 0x2E, 0x31, 0x36, // 01.06.16
/* 0008 */ 0x30, 0x34 // 04
},
"ATY,EFIVersionB",
Buffer (0x10)
{
/* 0000 */ 0x31, 0x31, 0x33, 0x2D, 0x44, 0x33, 0x36, 0x30, // 113-D360
/* 0008 */ 0x30, 0x32, 0x30, 0x30, 0x2D, 0x31, 0x30, 0x36 // 0200-106
}
}
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}
}
}
}
}
}
}
}
Will opencore support to MacOS Ventura on trash-can Mac Pro 6,1 shortly? Or somebody has already been working it? Because Mac Pro 6,1 is about to die soon in this fall.... And I would like to get one and I would like to see its potential. Will it be just as good as Mac Pro 5,1 with Opencore...
Sure don't copy the PowerPlay table. Even another Radeon VII should test that settings before inject via OpenCore.
