Well, if you added "no_compat_check" to your bootargs and have a working Mojave installation, you already know what you have to add to your config.plist.
On two partitions, yes.
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 there going to be a delay in the release of OC 0.8.5? If so, would this be related to Ventura's imminent release?
there is first step to ventura
github.com
GitHub - acidanthera/CryptexFixup: Various patches to install Rosetta Cryptex
Various patches to install Rosetta Cryptex. Contribute to acidanthera/CryptexFixup development by creating an account on GitHub.
github.com
This is a very neat plugin. I got it to work on a clean install of Ventura from Monterey with
-cryptbeta.That being said, we should really temper our expectations with regards to Ventura: Power management remains broken and “supported” graphics cards (≥ Polaris, to which many of us have upgraded) present a major hurdle. Even with the Rosetta cryptex, the graphics drivers remain dependent on AVX 2.0, and while root patching allows for downgrading, just getting through the Ventura install is very painful (ironically enough, without an “unsupported”, albeit Mac EFI, graphics card)…
It's Polaris and newer, so, Polaris/VEGA/NAVI. All AMD graphics drivers with Ventura require AVX2.0.
Best case scenario: it’ll be the same situation.
As I understand it, a processor without avx will still affect the inability to load GPU drivers?
but I won't be too upset as long as the Monterey with W6800 GPU works perfect for me
Currently you can't run Ventura AMD graphics drivers without a AVX2.0 supported processor. OCLP solution to have graphics acceleration is to downgrade the drivers to the Monterey versions, via root patching.
Interesting enough, because the AVX2.0 requirement, seems easier to get a NVIDIA Kepler GPU like GTX 680 working with Ventura again than a Polaris/VEGA/NAVI.
@tsialex - interesting so to use Ventura it may be better to go back to my GTX 680? Root patching in any event.
Looks like the community is pushing the limits of keeping our cMPs alive.
OCLP devs got Kepler NVIDIA GPUs working long before Polaris and newer AMD GPUs - no VideoToolbox hardware assistance for video decoding/compression/grading/conversion/etc with NVIDIA GPUs tho.
The real issue is that Ventura right now is a utter mess with anything earlier than Haswell CPUs and stable/production root patching will take a long time to arrive, like was said by OCLP devs back on day one. Said that, I bet that lot's of people will try to run Ventura on day one just to have borked systems. Remember how much time was needed to get Big Sur stability, with Ventura things are a lot more complex.
One thing to notice from the commits, the effort on supporting Ventura is also improving BigSur and Monterey support, lot's of bugs are being addressed and real improvements are being made everywhere. So, even if we won't have MacPro5,1 running Ventura right now, we are still reaping benefits.
The guide has been updated to OpenCore version 0.8.5. For this version, you can just reuse your config from 0.8.4. Happy updating!
Hi - I have been having problems recently and I thought a new OC with latest version might help (no wake from sleep, no shutdown). I was using Martin Lo's old 0.8.0 config basically.
But I cannot follow this guide and succeed as I cannot get my mac to boot by following the guide to end of 'Basic setup' section. Vanilla config downloaded here will work OK, but once I add some of the 'compatible' changes suggested then it will not work anymore - boots to recovery only.
I have made some of the changes where it says "a few possibilities" but once that is done and copied to EFI I am screwed, even though it said "config.plist OK". When I reboot as instructed in final step of that section after copying config back to EFI then mac will no longer boot Mojave and reboots recovery. If I undo those changes and go back to downloaded config.plist then it will boot again but it is very time consuming to do this over and over every time (zapping NVRAM etc) so I have stopped now after 6 tries. I am pretty convinced I am following the instructions.
I did not even get to try the "complete your setup" section.
I have had to go back to original EFI folder (Martin Lo 0.8.0) I was using in order to continue with the same problems as before back again unfortunately.
But I cannot follow this guide and succeed as I cannot get my mac to boot by following the guide to end of 'Basic setup' section. Vanilla config downloaded here will work OK, but once I add some of the 'compatible' changes suggested then it will not work anymore - boots to recovery only.
I have made some of the changes where it says "a few possibilities" but once that is done and copied to EFI I am screwed, even though it said "config.plist OK". When I reboot as instructed in final step of that section after copying config back to EFI then mac will no longer boot Mojave and reboots recovery. If I undo those changes and go back to downloaded config.plist then it will boot again but it is very time consuming to do this over and over every time (zapping NVRAM etc) so I have stopped now after 6 tries. I am pretty convinced I am following the instructions.
I did not even get to try the "complete your setup" section.
I have had to go back to original EFI folder (Martin Lo 0.8.0) I was using in order to continue with the same problems as before back again unfortunately.
Try keeping SecureBootModel=Disabled for Mojave. Once you have updated to Big Sur or later (using the VMM flag), you can switch to SecureBootModel=Default.
Edit: Guide updated to reflect this nuance.
Last edited:
@kkinto: Booting Mojave using OC is hardly necessary. I might be mistaken, but, depending on the spoofing level you use, booting Mojave via OpenCore might not be possible at all, unless you reinstall Mojave itself via OpenCore. But if you do that, Mojave will no longer boot natively (i.e., without OpenCore).
Just a clarification: Spoofing can indeed affect the bootability of Mojave (for example, using the iMac Pro board ID will work, but not 2019 Mac Pro board ID), but this can always be circumvented by using -no_compat_check (or holding Command-C-Minus at the OpenCore boot menu) and setting SecureBootModel=Disabled. Still, Mojave can always be booted natively whether or not it was installed through OpenCore (with no hard patching).
Hi Community!
After previously being a tiny bit involved I now got back running my Mac Pro as my daily driver. however ist the first time actually running (or booting for that matter) Monterey on that machine. I myself now ran into a weird issue which I suspect is DRM related. I don't have any audio when using the Apple TV app, while other DRM restricted sources like amazon prime (web as well as app) work just fine. Video works fine in all cases, including Apple TV. for now I actually resorted to streaming Apple TV via AirPlay from my iPhone to said Mac Pro, which works just fine.
The reason I suspect it's a DRM issue is, 'cause it's a somewhat know Apple TV problem on other platforms, that certain audio streams fail to decode due to some DRM hiccups. At least according to a quick web-search.
That said it might also be related to my old Nahlem CPUs, which according to the guide are unsupported. (I get no audio stuttering like it has been know on Mojave using those CPUs on dual-socketed machines, however – using airplay and DP-audio only, though.) I might upgrade those down the line, but I don't know yet, as apart for said issue everything "just works".
If anyone got any insides or even better a potential fix for the issue, that'd be great.
After previously being a tiny bit involved I now got back running my Mac Pro as my daily driver. however ist the first time actually running (or booting for that matter) Monterey on that machine. I myself now ran into a weird issue which I suspect is DRM related. I don't have any audio when using the Apple TV app, while other DRM restricted sources like amazon prime (web as well as app) work just fine. Video works fine in all cases, including Apple TV. for now I actually resorted to streaming Apple TV via AirPlay from my iPhone to said Mac Pro, which works just fine.
The reason I suspect it's a DRM issue is, 'cause it's a somewhat know Apple TV problem on other platforms, that certain audio streams fail to decode due to some DRM hiccups. At least according to a quick web-search.
That said it might also be related to my old Nahlem CPUs, which according to the guide are unsupported. (I get no audio stuttering like it has been know on Mojave using those CPUs on dual-socketed machines, however – using airplay and DP-audio only, though.) I might upgrade those down the line, but I don't know yet, as apart for said issue everything "just works".
If anyone got any insides or even better a potential fix for the issue, that'd be great.
Thanks for the response. I didn't have the opportunity to get anywhere near any spoofing or anything else - I just could not finish the 'Basic settings' section last reboot without getting into a no boot scenario and ending up with the recovery version of Mojave.
I didnt particularly want to boot Mojave but the instructions began with:
"✓ The first step is to boot into macOS natively (no patched installs, no third-party boot loaders).
On MacPro5,1, the last natively bootable version of macOS is Mojave.
⚠️ It is important to always have a disk with a natively bootable installation of macOS. That way, you can always boot if something goes wrong."
Right. So just keep SecureBootModel=Disabled in the config and you will be able to boot Mojave. Let us know how it goes.
The problem might indeed be related to your Nehalem CPUs, because I've had no issue using Apple TV with my Westmeres. Note that DRM requires WEG and a few settings as described in the guide.
Sorry for the late reply: do I have to reboot the system after deleting the EFI?
WEG is successfully loading according to kextstat. So it indeed might be CPU bound. Too bad 'cause otherwise there does not seem to be anything keeping those old Macs with stock CPU from running.
BTW.: Why is Westmere a requirement anyway? 'Cause of the audio stuttering within Mojave (and possibly other releases)?
Last edited:
The device properties
rebuild-device-tree and unfairgva are also important. Note that for some graphics cards, it’s not possible to add these properties, so you have to resort to the corresponding boot-args.That’s right (if I remember correctly). You might also want to confirm that power management is working.