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
Okay, so I screwed something up and had to start from scratch again. I followed the initial setup guide, dropped in the default config.plist, put in the OG GPU and selected the EFI partition to boot, and it worked. However, the change isn’t keeping when I reboot again, so it isn’t booting off OpenCore. What might be going on? This didn’t happen the first time I did the initial setup.
I was missing a very simple step, when selecting the EFI partition, I forgot to hold down control when I hit enter. Mundane detail, as Michael Bolton would say.
The guide has been updated to OpenCore version 0.8.6.
What would make a cMP Ventura-compatible would be AVX2 emulation or AVX2-free GPU drivers (and working drivers for some other hardware like wifi or bluetooth, too). Neither is an element of the "core" Open Core.
Pertinent changes include improvements to emulated NVRAM (in particular, a fix for the wake from sleep issue). Regarding Ventura, as mentioned by @hwojtek, fixes for getting it to run on the classic Mac Pro are not really on the OpenCore issue radar...
There are people claiming successful upgrades to 13.0 using OCLP 0.5.x on cMPs, and there are those who even claim that their computer is more responsive than in Monterey! I might try that on a backup volume and see how it goes, but I suspect that, sooner or later, in the current situation, Ventura will cause frequent kernel panics on our aging hardware.
This is valid only for NVIDIA Kepler GPUs, where there is no requirement of AVX2.0, since it's Big Sur drivers hacked to work with Ventura. No DRM working and a long list of small issues:
Legacy Metal Graphics Support and macOS Ventura - Sequoia · Issue #1008 · dortania/OpenCore-Legacy-Patcher
With the forth coming release of OpenCore Legacy Patcher v0.5.0, systems with legacy Metal GPUs will finally be able to achieve graphics acceleration in macOS Ventura! Reminder: These patches are s...
github.com
You might be surprised. Yesterday I saw this (not my computer):This is valid only for NVIDIA Kepler GPUs, where there is no requirement of AVX2.0, since it's Big Sur drivers hacked to work with Ventura. No DRM working and a long list of small issues:
Legacy Metal Graphics Support and macOS Ventura - Sequoia · Issue #1008 · dortania/OpenCore-Legacy-Patcher
With the forth coming release of OpenCore Legacy Patcher v0.5.0, systems with legacy Metal GPUs will finally be able to achieve graphics acceleration in macOS Ventura! Reminder: These patches are s...
This fellow claims that everything is working for him, except Bluetooth! My hunch would be that his Mac Pro 5,1 must have panicked a few minutes after his screenshot, but, who knows?
AMD HD 7950 is a legacy GCN1-3 card with Monterey drivers hacked to work with Ventura, that also doesn't require AVX2.0. Like NVIDIA Kepler, no DRM support and no H.264 acceleration, see the list of issues.
Legacy GCN drivers currently have a lot more issues than NVIDIA Kepler drivers.
Last edited:
Wow, thanks for this comment, I was plagged with slow boot for months, and it gaves me a clue about the issue.
After disabling TRIM on OpenCore config (SetApfsTrimTimeout=0) I have fast boot again (I'm running OpenCore 0.8.4 with OCLP 0.4.10 and 12.6) !
My question now is, is it OK to keep TRIM disabled and to just run it with big timeout from time to time as a "maintenance" task ?
I looked into it a bit further. As per Dortania, with OS 12 and above one cannot change the trim timeout; thus there is no change in booting times whether one uses -1 or 4294967295 as values in the said parameter.
Sadly been getting my butt kicked with OCLP recently. Going to have to try a vanilla build again on my 5,1. Absolutely unable to boot into newer installers, keep getting kicked at the same spot (using Verbose)
I have tried various things such as remove all extra accessories, extra drives, even changed what media I was using to boot into the installer and OCLP. Keep getting stopped at the same place. Mojave is a bit too old on this system, hoping I could have done a leapfrog to Monterey, but no luck as of yet. Can't even boot the Big Sur installer either
.
Code:
<Error>: Failed to bootstrap path: Path = /Library/Apple/System/Library/LaunchDaemons, error = 2: No such file or directoryI have tried various things such as remove all extra accessories, extra drives, even changed what media I was using to boot into the installer and OCLP. Keep getting stopped at the same place. Mojave is a bit too old on this system, hoping I could have done a leapfrog to Monterey, but no luck as of yet. Can't even boot the Big Sur installer either
.
0 disables trim altogether but I do not thing it will be good for your ssd in the long run.
That's a bit confusing. The OC manual state this
Code:
Trim operations are only affected at booting phase when the startup volume is mounted. Either specifying timeout, or completely disabling trim with 0, will not affect normal macOS running.I don't know how often the OS will TRIM the SSD, and I personally haven't monitor it. But one of the OpenCore user told me that he did observed TRIM operation 2-3 days after boot (with SetApfsTrimTimeout=0). Assuming he know what he was doing. And he did that correctly. Then SetApfsTrimTimeout=0 shouldn't cause too many extra wear to the SSD.
So what does it mean when you manage to get to the boot screen, and after selecting your MacOS partition you get a black screen with Ø ? I’m a bit baffled since I’m reusing a config file that worked before but I had to reformat and reinstall. I think I did all the same setup as before. The default config works fine, so I’m doing something wrong.
That is the prohibited boot screen - means your OS is unsupported. You would see that for example if you spoofed a MacPro7,1 and tried to boot Mojave since Mojave is not supported by the MacPro7,1.
What OS are you trying to boot? What computer are you spoofing?