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 am on the Windows insider program and get Win 11 upgrades very frequently. They no longer overwrite the BOOTx64.efi in the EFI folder. I have rEFInd disguised as a BOOTx64.efi there and it never stopped working. From rEFInd I select OC or Windows (I like to run Windows natively as this machine is not a cMP5.1 with a problematic NVRAM).
Well, because post #1 here covers the installation of both Windows 10 and 11 on the Mac Pro 5,1, and because the potential for an unwanted file replacement is always there, my recommendation stands. At the very least, given the fragility of the Mac Pro’s BootROM, I think it is very important to be aware of the situation.
Thanks this does clarify a lot, going to try moving the microsoft folder to my windows drives efi and remove its boot folder, and it should just be empty from what I understand. microsoft drive / efi folder / microsoft folder (nothing in it) but the windows drive has no efi folder as of now… hmmm do I create a efi folder? As stated before No efi folder = NO EFI
Last edited:
Be careful with this. The Microsoft folder should not be empty. In particular, the file \EFI\Microsoft\Boot\bootmgfw.efi is what gets picked up automatically by OC to boot Windows. There are two different Boot folders here: The one inside the Microsoft folder (just mentioned) is necessary, whereas the one outside is bad (well, any non-OC one is bad; the OC one should be kept!).
If you want to experiment with this post-installation, make sure to have a backup of the EFI files. Also be ready to recreate these files using bcdboot with the installer (as described in the appendix of post #1).
Hello, I have searched everywhere and can not find an answer. If I install open core on my Mac Pro mid 2010 does it overwrite my current mojave system and can only be installed on a clean formatted drive or will it just update my current of MacOS Mojave? I am curious if I'll lose all of my info. Also, if I back up my system, which I do regularly, if open core can only be installed on a clean HD, will I be able to do a System Restore once open core is installed to get back all of m y information BUT on an updated OS?
Installing OpenCore won't affect your current installation of Mojave. After you install it and properly configure it (and most importantly understand some of the basics), you'll be able to update Mojave to a more current version of macOS. If you prefer, you can also do a clean install and move your data over using Migration Assistant.
You don't have to install OpenCore on a clean HD; you will be accessing a partition on your existing disk that is normally hidden, and adding the OpenCore files to that. I'm not sure what you're proposing in the rest of that sentence; you seem to be saying that you want to have all of your information available on an updated (later version) OS? That is certainly possible. My recommendation would be that you have a second disk available for that later OS; you would get OpenCore working with your Mojave disk and get comfortable with how to make changes in the file that controls how it works (config.plist). Then you download and run the installer for the later OS, specifying the second clean disk as the target; OpenCore makes this possible (you aren't blocked by Apple's compatibility checking). Then, as @cdf suggests, you run Migration Assistant to transfer your Mojave files over to the disk with the later OS.
Yes, lots of backups are a good idea in case something goes wrong. I would recommend having several full disk backups (made by Carbon Copy Cloner and/or SuperDuper!); I would never depend on a single Time Machine backup for an important job like this.
This morning's update to macOS Monterey 12.6.3 went without issues.
Do heed the recommendation in the first post to keep a copy of Mojave available - either on a drive separate from the drive that has the OC EFI folder or on a external drive - so you still have a natively supported version of macOS to boot from if you have issues with OC updates, etc. in the future. This is an invaluable safety net.
You'll have to use OpenCore Legacy Patcher and use root patches to get your GPU working. Polaris, Vega and others are supported with patching. Navi (RX5000 and RX6000 series) will not work yet.
This isn't the support page for OpenCore Legacy Patcher. Their discord may be more of help. Keep in mind you cannot use Migration Assistant as its broken on root-patched systems. Make a backup before you do anything, its your only ticket back
Last edited:
Based on their documentation yes Kepler is supported. I didn't bother checking that section since I upgraded my GPU to Navi. Best to check your setup specs to see is everything will be supported for you
I've been following OCLP's development for several weeks now. Interesting as it is, I wouldn't like this thread to become "infected" with notions about root patching and the like. Those interested should go to the relevant thread, and leave this one for a more "unpatched" experience. Hopefully, things will be better in the coming weeks if/when AVX/AVX2 emulation is achieved and we have some reliable internal USB hub solution to make our old machines compatible with Bluetooth à la Ventura, which sounds kind of funny in Spanish.
Agreed
To be honest, I don't see much incentive at this point for someone to work on an emulation layer when root patching can be considered "good enough" or even possibly provide better performance than emulation for such things.
For me though, I'd like to see it as theres beginning to become a slew of applications that require AVX and AVX2, even on Windows. I'm keeping my fingers crossed some sort of emulation will be achieved, but I have some realistic expectations. Looking at Intel's documentation on AVX just gives me a headache as to why they made it the way they did.
Yea, I've seen the thread. They're a very talented individual and so is everyone else here working to make our Mac's more useful
It eventually installed but at every restart I had the forbidden symbol. I had to turn off the computer and turn it on again to continue the install.
Once that process was done install completed and 12.6.3 runs fine.
Anyone with a IMAC 13,1 have a solution to no sound/speakers being found when running OCLP/Ventura.
Yeah, that's a bummer. Migration Assistant doesn't work, so I can't really do a time machine restore? Want to see how many folks have taken the plunge and upgraded to Ventura yet.
My opinion is that running ventura on a macpro with processors that do not support AVX is just a waste of time, since we cannot use all the benefits:
programs with avx support work worse for us,
the processor compiles shaders somehow slowly and inefficiently - even all cores are not involved,
the video card renders well, but worse than in macro 7.1
we do not use all the capabilities of video cards,
memory buses are slow
What is supposed to be done on macpro in ventura with outdated video cards? surf the internet?
- somehow very expensive in terms of energy consumption - about how to mine on macpro
NVIDIA: legacy cards work, but CUDA is not supported,
AI based plugins therefore don't work on mac
even if ventura will work in the future on AMD 6xxx or even on 7xxx - which seem to support AI - anyway, the memory is slow, the processor does not support AI at all
my opinion - I will not even try to run Ventura on 5.1 - I will have to buy 7.1 - especially if Apple add support for amd 7xxx
But i have a practical question:
I'm afraid to experiment in OCPL, because after installation the system will be patched and will no longer be native with many minuses and limitations,
I was convinced from my own experience - after the experiments I had to reinstall the system
Someone from the guru can explain:
support for old bluetooth has been added to the ocpl - in that case, atheros.
I think it's just some kind of kext added?
Is there any hope in the minimum cdf configuration to add this?
programs with avx support work worse for us,
the processor compiles shaders somehow slowly and inefficiently - even all cores are not involved,
the video card renders well, but worse than in macro 7.1
we do not use all the capabilities of video cards,
memory buses are slow
What is supposed to be done on macpro in ventura with outdated video cards? surf the internet?
- somehow very expensive in terms of energy consumption - about how to mine on macpro
NVIDIA: legacy cards work, but CUDA is not supported,
AI based plugins therefore don't work on mac
even if ventura will work in the future on AMD 6xxx or even on 7xxx - which seem to support AI - anyway, the memory is slow, the processor does not support AI at all
my opinion - I will not even try to run Ventura on 5.1 - I will have to buy 7.1 - especially if Apple add support for amd 7xxx
But i have a practical question:
I'm afraid to experiment in OCPL, because after installation the system will be patched and will no longer be native with many minuses and limitations,
I was convinced from my own experience - after the experiments I had to reinstall the system
Someone from the guru can explain:
support for old bluetooth has been added to the ocpl - in that case, atheros.
I think it's just some kind of kext added?
Is there any hope in the minimum cdf configuration to add this?
Last edited: