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
I had not used ocvalidate nor OpenCore Configurator in setting up OC. I was curious by your post so tried them. ocvalidate indicated >50 missing keys with my functioning 0.6.1. Made a copy and opened in Configurator. Made no changes just saved it and indeed ocvalidate shows all good. All the empty keys are now in the copy. Seems a bit pointless - agree about the NVRAM empty parameters.
It boots but just without a boot screen - correct. Power up and hold Alt+Com+P+R and hang on through at least two boot chimes then let go.
Goodmorning, hope to not go OT since I have a problem on a beta OS (big sur PB6)
I recently changed the Sapphire Nitro+ RX590 on my Mac Pro 5,1 in signature with a Sapphire Pulse BE RX5600XT card.
I've had to update the device part of the OC config.plist but now on Catalina 10.15.6 both HDMI and Display ports are working just fine. The problem is on BigSur PB6 where (with the same OC 0.6.0 configuration) it works only if I connect the monitor to HDMI ports on the back (on display port I have black screen after boot).
I have updated both lilu and wethevergreen kexts to latest available version but I have the same behaviour.
I'll send you later my OC config for troubleshooting (now I'm at work
Thank you by now for your support!
Have a nice day
EDIT: Attached currently OC config.plist
hey man. Do you have your PCI and power supply fans revving up with your Pulse 5600xt BE?
I downgraded from a Radeon VII and I had nothing but problems with Navi. Now I returned that GPU and got a 5700xt reference and it still the MacPro revs up the pci and ps fans. Did you have any similar issues on your MacPro?
AirOut: A solution to the racing fan bug
Introduction The racing fan bug is a well known issue that affects certain cMP systems with upgraded video cards, particularly systems with SMC version 1.39f5. On these systems the PCI, PS, and booster fans spin abnormally fast at idle, causing unnecessary noise. Although the issue appears to...
forums.macrumors.com
AirOut: A solution to the racing fan bug
Introduction The racing fan bug is a well known issue that affects certain cMP systems with upgraded video cards, particularly systems with SMC version 1.39f5. On these systems the PCI, PS, and booster fans spin abnormally fast at idle, causing unnecessary noise. Although the issue appears to...
Thank you @h9826790 that is what I am using right now. I was just wondering if it happens to other people or just me. Also I read it might be my smc version which is 1.39f5. Is there anyway to change smc version? Is there another solution? Thank you!
I am already regretting selling my Radeon VII. It worked perfect with my MacPro. The 5700xt not so much
I updated the Python OC installer, these are the config differences between 0.6.0 and 0.6.1.
Prior 0.6.1, we removed the NVRAM '7C436110-AB2A-4BBB-A880-FE41995C9F82' entries with HWA changes. I see that you added back the 'run-efi-updater' on NVRAM '7C436110-AB2A-4BBB-A880-FE41995C9F82', can you please let me know why?
Last edited:
swapped my config.plist to spoof an iMac pro and run the cmds to unenroll
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll
and then re enroll in the dev program
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed
checked software update and dev beta 7 popped up and installed without a hitch. Once back on the desktop swapped my config.plist back to the Macpro 5.1 not booting
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll
and then re enroll in the dev program
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed
checked software update and dev beta 7 popped up and installed without a hitch. Once back on the desktop swapped my config.plist back to the Macpro 5.1 not booting
Last edited:
Use MFC to customise a fan profile for the PCIe and PSU fan.
e.g. PCIe fan base on PCIe ambient, min 35°C, max 55°C.
PSU fan base on PSU component 2 temperature, min 35°C, max 55°C
Of course, you can vary these numbers a bit to make it fit your own need.
swapped my config.plist to spoof an iMac pro and run the cmds to unenroll sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll
and re enroll in the dev program, checked software update and dev beta 7 popped up and installed without a hitch. Once back on the desktop swapped my config.plist back to the Macpro 5.1 and will not boot, only boots with the iMac pro config spoof
and re enroll in the dev program, checked software update and dev beta 7 popped up and installed without a hitch. Once back on the desktop swapped my config.plist back to the Macpro 5.1 and will not boot, only boots with the iMac pro config spoof
Do you have imacpro board-id in your config? "will not boot" is a vague term. Provide a debug boot log as a minimum.
Actually, that change came with 0.6.0. It's an extra precaution against firmware updates, which is especially important when spoofing.
Hi thanks everybody for the good work.
I have bootscreen with your 0.6.1 package, thanks.
But something weird : My SSD and HD partition clone (pre open core ) appears with the same name :
Mac Pro SSD instead of first , ok
and the second name should be DEF CLONE CATALINA 2 (as name in finder, recognized by disk utility).
I can choose the second one and boot to the HDD clone, so it is a progress.
The Graphic acceleration isn't seen by Videoproc. What should I do please ?
Edit : For that I got it reading agin on the first post, I do not have a required Westmere (E56xx, L56xx, X56xx) / Gulftown (W36xx) processor but a Bloomfield one.
Remain the mystery of the boot picker 😂
Last edited:
I am at the next snag.
I had a Windows 10 installation on a separate SSD that is sitting in the place of one of the optical bays (MacPro 5.1 6 core 3.4 2010).
I tried to do the change from mbr to EFI and it looked like it was fine (I did this with only the windows drive in the machine).
Now when I have both Windows and Mac OS drives in, OC isn't coming on and it simply goes to Windows.
To note, my Catalina is on an NVME in a PCIe slot.
Any help would be greatly appreciated.
I had a Windows 10 installation on a separate SSD that is sitting in the place of one of the optical bays (MacPro 5.1 6 core 3.4 2010).
I tried to do the change from mbr to EFI and it looked like it was fine (I did this with only the windows drive in the machine).
Now when I have both Windows and Mac OS drives in, OC isn't coming on and it simply goes to Windows.
To note, my Catalina is on an NVME in a PCIe slot.
Any help would be greatly appreciated.
Hey folks, been out of this for a while and just took the opportunity to update to 0.6.1 using the first post instructions. However, I’m finding myself looping around back to the simple boot picker. OpenCore sees Mojave and Catalina, but when choosing either I don’t see the Apple logo and wind up back at the simple boot picker again.
Any clues? NVRAM reset puts me back into Mojave with no issues, followed instructions, including SMC reset and bless from recovery.
Any clues? NVRAM reset puts me back into Mojave with no issues, followed instructions, including SMC reset and bless from recovery.
Same thing happened to me. I went back to 0.6.0 from an EFI backup. Then I redid the 0.6.1 setup from post #1. Worked fine the second time so clearly I messed something up. When enabling nightshift I had a weird feeling that I may have copied lilu entry a second time. Also, I am uncertain the hardware acceleration kexts were properly copied over. Regardless of where I screwed up, just starting fresh and doing it carefully again fixed it.
If I am reading this right, the OC EFI is on the NVME? I could not get that to work. I put OC on another SATA HDD and blessed it there. Has been working fine since.
Okay, I'll give it another whirl. I'm on 0.5.6 at the moment which has been flawless since February, but I find myself with sufficient time and enthusiasm to re-investigate this evening.
Sorry I should have been clearer, but you did get it right. I think it's got to do with how the Mac goes to look for boot drives, IIRC?
I'd rather not do that, though, any other suggestions?
Okay, I'll give it another whirl. I'm on 0.5.6 at the moment which has been flawless since February, but I find myself with sufficient time and enthusiasm to re-investigate this evening.
Nuts. Same thing. And when I look at the number of changes in the config.plist file compared to mine... where's that enthusiasm gone!
Now, noting @6DecadesLater's post above I'm also running this from an NVME drive on a 7101A carrier. Version 0.5.6 is working just fine from there, but maybe something has changed that breaks this? Then again, it is starting...
Only thing I did notice is hitting <SPACE> and choosing the recovery partition for Mojave did get me an Apple logo, but the boot never completed - just sat at a black screen.
Last edited:
Guys, I need some help reinstalling Mojave. The disk B where Mojave was running just died, Catalina is running fine on Disk A. I replaced the detective disk with an SSD mounted in Slot 1 and formatted the SSD to ATFS:
What is the proper way to install Mojave into selected disk from an OpecCore setup?
Edit: I created an USB installer and removed all drives except the new Mojave SSD, you need a Metal card to install Mojave. I let the installer go through no boot screen, until the install screen showed.
What is the proper way to install Mojave into selected disk from an OpecCore setup?
Edit: I created an USB installer and removed all drives except the new Mojave SSD, you need a Metal card to install Mojave. I let the installer go through no boot screen, until the install screen showed.
Last edited: