I am still in Mojave. My plan was simply to install OpenCore and upgrade from Mojave to Catalina via Software Upgrade. I made a CCC copy to a disk that I put out of the machine before I started, just to be safe...
Last edited:
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 have Mojave installed on two disks? I see what you mean, you edited the previous post. You cannot upgrade to Catalina, it will ask you to upgrade to Big Sur. If you need Catalina, you can download the installer, but it will erase the target disk.
Yes, right now I have only 1 disk in my machine, I thought I install opencore and upgrade to Catalina then, was that wrong?
The guide tells you to have 2 disks present in your Mac, one for Mojave (default) and one for OC Catalina/Big Sur.
First, you don't have the suggested initial setup:
You did not followed OP setup, as described. Second, if you follow the setup, your (OC Mojave) Software Update will offer you an upgrade to Big Sur, not Catalina.
Last edited:
You have a valid point, the guide is there for a reason, if people would follow it to the letter, there should be less confusion and easier troubleshooting...
Now, in this particular pagraph, the real reason to have two disks in a real mac, is to be able to actually allow OC to run. The EFI on the orginal disk is the Apple one and I very much doubt you can replace that folder and have the system running on one disk. (well, you might be able to replace the folder, but I doubt you will be able to boot into recovery. And if you managed to do so, the good old Apple EFI will be back in charge)
The B to A disk trick keeps Apple at bay
Everything works for me perfectly following the guide. I also did a clean installation of Big Sur (in another ssd) from a butable pendrive with: sudo / Applications / Install \ macOS \ Big \ Sur.app/Contents/Resources/createinstallmedia --volume / Volumes / MyVolume, I installed OC in this Pendrive and everything perfect, from there I was able to bless the EFI of the SSD with BigS. It is another method and it also works.
you don't need to have another disk with a supported os on your Mac.You have a valid point, the guide is there for a reason, if people would follow it to the letter, there should be less confusion and easier troubleshooting...
Now, in this particular pagraph, the real reason to have two disks in a real mac, is to be able to actually allow OC to run. The EFI on the orginal disk is the Apple one and I very much doubt you can replace that folder and have the system running on one disk. (well, you might be able to replace the folder, but I doubt you will be able to boot into recovery. And if you managed to do so, the good old Apple EFI will be back in charge)
The B to A disk trick keeps Apple at bay
in fact, you can bless the OC boot loader simply from an USB installer of any Mac OS version.
if the original code to bless OC didn't work try the alternative code, but I found that you need to run it without the verbose option, like this:Yes I did it exactly as mentioned in part 1 and I did not get any error message before
nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102
as answer to
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi
this one always works for me where the original suggested code always fails me. but be sure to mount the correct partition.
That is because you know what you are doing. Not everyone does. And I personally do not want to fiddle with USB drives if my OC setup breaks. Is a matter of choice, that is why @cdf presented the safest way to setup your Mac. The guide will evolve soon (he is busy with work until beginning of December) and be merged with the plistlib generator I created a while ago, so we take out of equation the mistakes made by people while copying files, configuration, etc.
I never disable SIP, when I bless the EFI partition and I never use the long bless command. I do however shutdown the Mac for 15s, instead restarting it directly. I did tried before a simple reboot and it worked but I rather use the @cdf purist approach for your hardware.
Hi, I've searched this thread multiple ways but am out of search ideas.. I believe a few months ago I saw a post about someone finding some software that would not run on the 5,1 macpro due to it being the only known software that needed an instruction set from newer cpus that is not in our favorite 6 core xeons. Does that ring a bell for anyone which software that might be? An audio guy is asking me... Thanks!
Native Instruments Massive X was the first to require AVX, others followed.
@cdf @h9826790 @startergo I started the documentation (scroll up to see the actual configuration file), it will be easy for users to understand and implement OC settings, assuming they refer to Acidanthera documentation. On the other hand, passing the
setup.py file will allow another user to replicate a consistent setup, with all dependencies properly installed.
Last edited:
Yes but does that really explain my problem? 😬 I am confused now - why does it make a difference? Right n
thx a lot everybody. I ended up doing it as mentioned, installed Catalina on the empty disk and using migration manager, everything works now 😍
I have tested OC on MBP15,1 and to make my Thunderbolt PCIE external drive appear as internal only this helped:
OpenCore on the Mac Pro
Here is how I did it: Patch Arch x86_64 Base Comment IONVMeFamily Patch#External Count 0 Enabled...
forums.macrumors.com
Last edited:
After not hearing back about my reboot problems with Big Sur, I figured that this was not a OS 11 problem, so I went back to recode my Opencore partition. I found my mistake right away, redid the XML file and everything was fine. After using 3 SSDs for the 3 OSs, I wanted to fit everything on 2 drives. I never had luck using the same drive for Mojave and Catalina, but with Catalina holding the OpenCore EFI on the NVMe drive, I was able to put both Mojave and Big Sur on a SATA SSD. Since neither SuperDuper or CCC will clone a Big Sur volume, I had to make a new installation and then migrate the full install. Everything seems to be working well on both the 6 and 8-core. I‘d like to thank everyone involved in this endeavor. While I’m still an ignorant novice, I have learned a lot from this experience and appreciate everyone’s help. Thanks.
Outface has got his install working. But the discussion here has left me wondering. Is this correct? An Apple installer will never erase a target disk containing a MacOS as far as I know. It will upgrade. Is there a setting in default OpenCore settings we start with from page one that overrides the default way MacOS installers work?
A couple of months ago I found two references suggesting there was some kext able to emulate AVX/AVX2 for vintage processors like our Xeons. Is this true? If such a kext exists or can be compiled, will it run on OpenCore?
Last edited:
If you are referencing posts written long ago by me and others, it was a talk about how could it be done, AFAIK this not have been implemented in any way that I know of.
To enable Night Shift, again here but in another forum, I found this link
forums.macrumors.com
Post 2,493
What do you think? I believe it can be done ....
macOS 11 Big Sur on Unsupported Macs Thread
I have the same problem as you, I can't fix the wifi because of that. Please help
forums.macrumors.com
Post 2,493
What do you think? I believe it can be done ....
Show me your setup.py, I’ll let you know where is the issue. If you don't have a setup.py, give me your Device Path for the disk you want to hide.
Last edited: