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
Is this why I was running great with OC 0.6.9 switching between Mojave and Mt. Lion with boot picker working great. Then all of a sudden boot picker disappeared and automatically booted and I checked status when I was in Mojave and saw this. (VMM flag). <<<<<
Alex I'm going to PM you bud.
Thank You! very helpful, my CmP Dual had almost 17000 of free space, now after the 5th chime procedure has 51000
I have been working my way through this process since getting my hands on a Mac Pro 5,1. It came with a metal compatible GPU, so I didn't have to deal with that headache.
I want to thank everyone that has figured out all of the hard work and providing detailed instructions. Catalina and the latest version of Windows are running stably. BigSur 11.3 was already out, and I am not touching that hot mess at the moment since 11.23 is not available. Besides, staying at 11.23 means no security updates.
This machine was largely an a production machine. I've been checking the VSS store from the beginning and after using it for couple of weeks, and it is still within the health range for a dual processor machine with all 8 memory slots filled, so I assume the garbage collection is doing it's job.
The one snag I have run into is that I can't get the install process to work for Linux. The USB installer that is made in the process doesn't show up in the boot picker on reboot. I found the combination of using a FAT volume with an Apple Partition scheme to be a bit strange, but I assume that is needed for the install drive to show up in the boot picker.
I've already tried repeating all of the steps and carefully checking everything, but no dice
Getting Linux installed is not misson critical. It would be nice to have. At the moment, I am giving it a try under VirtualBox to see if I want to spend more time on getting installed on actual hardware.
Edit- I did check the USB installer I made under the Linux virtual machine I made with Virtual box, and it mounts and appears to be an install disk. Wonder what it keeping it from showing up in the boot picker? I did install the ext4_x64.efi driver and edited the plist file as instructed.
I want to thank everyone that has figured out all of the hard work and providing detailed instructions. Catalina and the latest version of Windows are running stably. BigSur 11.3 was already out, and I am not touching that hot mess at the moment since 11.23 is not available. Besides, staying at 11.23 means no security updates.
This machine was largely an a production machine. I've been checking the VSS store from the beginning and after using it for couple of weeks, and it is still within the health range for a dual processor machine with all 8 memory slots filled, so I assume the garbage collection is doing it's job.
The one snag I have run into is that I can't get the install process to work for Linux. The USB installer that is made in the process doesn't show up in the boot picker on reboot. I found the combination of using a FAT volume with an Apple Partition scheme to be a bit strange, but I assume that is needed for the install drive to show up in the boot picker.
I've already tried repeating all of the steps and carefully checking everything, but no dice
Getting Linux installed is not misson critical. It would be nice to have. At the moment, I am giving it a try under VirtualBox to see if I want to spend more time on getting installed on actual hardware.
Edit- I did check the USB installer I made under the Linux virtual machine I made with Virtual box, and it mounts and appears to be an install disk. Wonder what it keeping it from showing up in the boot picker? I did install the ext4_x64.efi driver and edited the plist file as instructed.
Thought I'd update everyone on my progress with running an RX 5700XT in Big Sur and newer on a Penryn based Mac Pro 2008. Apparently the issue was entirely SSE4,2 dependant as once Syncretic was able to resolve Big Sur support within MouSSE, my MacPro3,1 was able to boot beautifully in both Big Sur and even Monterey where I was previously limited to Catalina.
If anyone else has an RX 5700XT (or any Navi based GPU) and a 2008 Penryn Mac Pro lying around, it is in fact possible to boot.
Specs for those curious:
If anyone else has an RX 5700XT (or any Navi based GPU) and a 2008 Penryn Mac Pro lying around, it is in fact possible to boot.
Specs for those curious:
Code:
MODEL: MacPro3,1 - Early-2008
CPU: Dual Xeon X5482 Quad Core (8c8t)
RAM: 16GB DDR2 667Mhz (4GBx4)
GPU: AMD RX 5700XT 8GBI want to install High Sierra on my cMP (5,1 with Mojave, Catalina, and Windows 10), but with the latest ROM firmware and OpenCore, the computer tells me that I can't do that. It says that High Sierra is too old to install.
I set the date and time back to December 2017 and disconnected the internet. Then tried it again. Same results.
Do I need to remove OpenCore, downgrade the firmware, install High Sierra, and then go back to square one of installing OpenCore and upgrading the ROM firmware?
If that's what I need to do, I will do it.
Thanks for any information.
P.S. I tried putting a stand alone drive in the cMP with two partitions. On one partition is the installer for High Sierra, a bootable dmg. The other partition is set up to have High Sierra installed on it.
I did that sort of thing with 10.5.8 on my G4 Mac to install Leopard. It worked. So I thought I would try it on the cMP. The computer boots, but it never opens the High Sierra dmg. Is the ROM not letting it work?
I set the date and time back to December 2017 and disconnected the internet. Then tried it again. Same results.
Do I need to remove OpenCore, downgrade the firmware, install High Sierra, and then go back to square one of installing OpenCore and upgrading the ROM firmware?
If that's what I need to do, I will do it.
Thanks for any information.
P.S. I tried putting a stand alone drive in the cMP with two partitions. On one partition is the installer for High Sierra, a bootable dmg. The other partition is set up to have High Sierra installed on it.
I did that sort of thing with 10.5.8 on my G4 Mac to install Leopard. It worked. So I thought I would try it on the cMP. The computer boots, but it never opens the High Sierra dmg. Is the ROM not letting it work?
I reset the NVRAM on my 2009 cMP earlier today and couldn't get it to reboot. After removing all drives other than my NVME boot drive, I was up and running. I put the other drives back in and again, it wouldn't boot. I eventually realized it was being caused by the drive that I have in Bay 3 (a Seagate 1TB 2.5" SATA HD).
The only thing I can think of, is that while trying to install Catalina a while ago, I was having issues so kept having to go back and forth between Mojave and Catalina. I only had one flash drive so eventually, put the Mojave installer on the drive so I had it n case I needed to make another install USB. Could that be the culprit? It was never an issue before today.
The only thing I can think of, is that while trying to install Catalina a while ago, I was having issues so kept having to go back and forth between Mojave and Catalina. I only had one flash drive so eventually, put the Mojave installer on the drive so I had it n case I needed to make another install USB. Could that be the culprit? It was never an issue before today.
It's Open Core Spoofing a Mac Pro 7,1.
A Mac Pro 7,1 is not High Sierra compatible so spoofing does its job well.
Install without OpenCore, Firmware is backwards compatible, the latest firmware can run the oldest OS.
The approach in the guide (first post of this thread) uses iMac Pro, which makes High Sierra possible. I suspect that the issue here is with running the installer from Mojave or Catalina.
A High Sierra bootable USB installer should do the trick provided that you're not spoofing an unsupported model as pointed out above.
I put the drive back in it's original enclosure so I could connect it via USB after booting. Everything mounted properly but when I tried to reboot with it connected, the same thing happened. I was thinking it could've been something with the drive being mounted internally but that's not the case. What could be causing this drive to keep the computer from booting?
Resetting the NVRAM when using OpenCore can be problematic. It's possible that your Mac is now always defaulting to boot the offending drive. You need to re-bless OC from a natively-booted recovery environment.
Have you looked at the problematic drive - does it have opencore in the EFI partition?
It doesn't have open core on the partition but there is a file called "BOOTLOG" with the EFI. I've never seen that before. Is that the issue?
I can't help with that. I thought you might have multiple copies of Opencore on your system and if so that would cause a conflict.
Come to think of it, I think I do actually have multiple copies of OpenCore on my system. One on my Mojave drive and one on my Catalina drive. Should I uninstall one?
Yes. Also, you should try blessing Mojave outside of OpenCore (this can be done, for example, by selecting Mojave in Startup Disk with RequestBootVarRouting disabled), booting Mojave natively (you know this is happening when you have no bootscreen, provided that OC gave you one in the first place), and verifying that the offending disk is no longer problematic. If the problem persists, then the issue is not with OC.
So I did everything as suggested and still couldn’t boot with that disk connected. However, I removed the Catalina drive, re-enabled RequestBootVarRouting and everything booted up. In the bootscreen I had Mojave, the Mojave recovery but then also a “Recovery 10.7.5”. Does this shed any light on the situation?
OpenCore is not the problem then.
Perhaps a broken leftover Lion recovery partition is causing the issue. You might want to try identifying this partition with diskutil.
Alright! Got the recovery partition deleted so everything starts up again. You said I should get rid of one of the two copies of OpenCore that I have on my system. Does it make a difference as to which I keep? I’m typically booting into Catalina but also have the Mojave drive as well for the few times I need 32-bit support. I need to dig deeper into OpenCore. Every time I think I’m beginning to understand, I’m immediately reminded of how little I know. Lol. Thank you for all of your help!
Last edited:
Me again. Since updating from 0.6.8 to 0.7.0 I seem to have lost the ability to hot plug/cold boot my TB3 Apollo x8. I made the change thunderbolt 3 in config.plist that should correct this but still haven't had any luck. Has anyone else had this issue? If so, is going back to 0.6.8 as simple as replacing OC/BOOT in the EFI like when updating or is this a big no-no?
Hey, so second day of the Big Sur upgrade, just noticed when I went to use my VNC phone app to control the Mac Pro (yes sometimes I’m that lazy), it connects, but all I see is a black screen. Same with screen sharing from all my other macs. It’s not a huge deal but if anyone knows why this is happening and if it’s an easy fix id appreciate it.
I checked all the accessibility and screen sharing settings and nothing is available to “check”.
Also the Mac Pro is able to see all the other Mac screens.
I checked all the accessibility and screen sharing settings and nothing is available to “check”.
Also the Mac Pro is able to see all the other Mac screens.
I would have a clean (no Opencore) Mojave drive so you can always boot without OC in a natively supported operating system.