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
Can anyone confirm whether setting MaxKernel to 21.6.0 will work flawlessly for Monterey 12.5?
for me with syncretic patch
- with 21.5.0 - kernel panic
- with 21.6.0 - works fine- (now I'm testing in benchmarks with real programs running: blender, UE5, twinmotion and archicad)
EDITED
the archicad began to open the project more slowly, again there was a pause of half a minute before opening the project
- this was after the update to macOS 12.4 until I corrected the apfs structure on my nvme ssd.
now the activity monitor again shows that the archicad are not responding for these half a minute
EDETED
I found, that cdf for ASPP-Override.kext used
<key>MinKernel</key>
<string>21.4.0</string>
i changed it to >21.6.0<
is this right?
now archicad loads project without hanging
with all my configs:
syncretic patch- all 6 parts changed <string>21.6.0</string>
+ASPP-Override.kext changed <string>21.6.0</string>
OR
noAVX kext changed <string>21.6.0</string>
+ASPP-Override.kext changed <string>21.6.0</string>
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.2, mac os 12.5
Last edited:
I haven't tried it yet and we haven't heard from syncretic about it yet. What I can say is that the way the patching process works, the patcher looks for matching sequence of data bytes before applying the patch. So if the thing being p patched has been changed in 12.5 then the patch will still not happen even after updating MaxKernel. Its probably better to just wait until we hear more from Syncretic or CDF on this point. Its also always possible that Apple may have removed the problem from 12.5 and no hack is even needed any longer. Or perhaps the thing being patched is still the same binary and the current patches will work as expected.
For now, the system has not panic'd on me yet, without the patch. But I think there is probably some use case that if I try to do it, it might panic. I'm not sure what that would be right now.
For now, the system has not panic'd on me yet, without the patch. But I think there is probably some use case that if I try to do it, it might panic. I'm not sure what that would be right now.
I confirm that in my Mac Pro 4,1->5,1 a clean 12.5 install with OCLP 0.4.9, and then use Migration Assistant from 12.4 is working like a charm. Been using the mac some hours and no problem till now.
Last edited:
My Mac Pro 2010 12 cores with Opencore 080 updated 12.5 from 12.4 works great
Hello, i have the following problem:
to install ReFindPlus would need to disable SIP on Mojave,
but when i boot into Recovery Mode via OpenCore (selecting the Recovery Partition @StartupPicker) i get only black screen and no visible output (RX 570, unflashed).
The recovery mode for the 2 other partitions (Monterey and ML) do work fine, but i need to disable SIP on Mojave, for ReFindPlus installation, thanks.
EDIT: got into recovery with the help of another GraphicsCard (EFI-Bootscreen), but every attempt to disable SIP, seems to fail. It says in recovery, "SIP has been disabled, you must restart for changes to effect" but after restart back to square one with "System Integrity Protection status: enabled?
to install ReFindPlus would need to disable SIP on Mojave,
but when i boot into Recovery Mode via OpenCore (selecting the Recovery Partition @StartupPicker) i get only black screen and no visible output (RX 570, unflashed).
The recovery mode for the 2 other partitions (Monterey and ML) do work fine, but i need to disable SIP on Mojave, for ReFindPlus installation, thanks.
Code:
System Integrity Protection status: enabled (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: enabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.EDIT: got into recovery with the help of another GraphicsCard (EFI-Bootscreen), but every attempt to disable SIP, seems to fail. It says in recovery, "SIP has been disabled, you must restart for changes to effect" but after restart back to square one with "System Integrity Protection status: enabled?
Last edited:
Is MaxKernel you need to change or simply remove it from config. What happens if you remove the patch completely?
If I were you, I would change the latest relevant patch entries in config.plist as
<key>MaxKernel</key>
<string></string>
I will experiment with this tonight
my situation is this:
martin's 0.8.0.1 config with syncretic patch with MaxKernel 21.5.0+ASPP kext 21.4.0 - kernel panic
cdf 0.8.2 config with patch -21.5.0 + ASPP kext -21.4.0 - kernel panic
cdf 0.8.2 config with noAVX kext-21.5.0 + ASPP kext-21.4.0 - work ok, but there are cloned processes mdsworker x 12 times, archicad does not correctly recognize addresses
cdf 0.8.2 config with noAVX kext or with syncretic patch with all settings 21.6.0
+ kext with settings 21.4.0 - work ok - archicad freezes
cdf 0.8.2 config with (syncretic patch or with noAVX kext) settings in all positions 21.6.0 -work ok, archicad OK
Check whether you have
csr-active-config in the NVRAM section of your config.plist as this is the NVRAM variable used by macOS to store current SIP settings, so if your OC setup is resetting it you will just see what OC sets on every reboot. (If you are using OCLP or equivalent patching - i.e. adding back OS files in place on the hard drive - then you will not want to remove these settings, however, as they enable the patches to work.)You can use the
AllowToggleSip option (OpenCore versions 0.7.0 to 0.8.0) or the ToggleSipEntry.efi driver (OpenCore 0.8.1 and up) to add a Toggle SIP entry in your menu (it's an auxiliary entry, so you may need to press space to show it).If you do have a custom
csr-active-config value set up in your OpenCore NVRAM section as mentioned above, then you need to select the Toggle SIP menu entry twice (once so that it shows 'SIP enabled' - don't boot with this if you are relying on patches - then once again so that it shows 'SIP disabled' again) - in order to be sure that SIP is fully disabled.
Last edited:
On my side, I'm running the following software (with no patch or kext related to AVX1.0):
Code:
build.kexts = [
{
'project': 'ASPP-Override',
'properties': {
'ExecutablePath': '',
'MinKernel': '21.4.0'
},
'repo': 'dortania',
'version': '1.0.1'
},
{
'project': 'Lilu',
'repo': 'acidanthera',
'version': '1.6.1'
},
{
'project': 'FeatureUnlock',
'repo': 'acidanthera',
'version': '1.0.9'
},
{
'project': 'WhateverGreen',
'repo': 'acidanthera',
'version': '1.6.0'
}
]In my books, defining a value for MaxKernel is irrelevant, as people will follow always one of two scenarios:
- Wait for others to validate if there are no issues with a new macOS release, then upgrade
- Test the upgrade themselves and change the MaxKernel value to 21.6.0, from 21.5.0
Last edited:
thanks, there is
dont know what to make of it.
besides, i tried to Toggle SIP Menu already, but then i left it alone, as it said "EXEC SIP disabled" or the likes, will try your tip with enabling and disabling, see if this does the trick.
EDIT: AllowToggleSip does not do the trick; i am using Version 0.8, OC installed on the same SSD as Mojave itself.
Last edited:
I disabled all parts of the patch,
the MacOS 12.5 loaded normally,
but it became uncomfortable to work with the programs:
archicad - norm,
blender not responding when loading files,
twinmotion loading scenes with not responding, in addition, the test scene load time was always about 1.5 minutes - now 2.06 minutes
- probably the programs are used incorrect memory addresses, and additional time is required,
in addition - MenuBar showed strange behaviour - simultaneously opened programs did not give the top menu when selected - file, edit, etc.
- only the menu bar for activity monitor.
I had to turn off all programs by force quit from activity monitor
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.2, mac os 12.5
That's good info for people building by hand the configuration. Not sure you were talking to me (since you quoted me), by default Plistlib Generator auto-updates the patch related values for me, I don't need to edit anything in my configuration:
Code:
properties = {
'Arch': 'x86_64',
'Base': '',
'Comment': '',
'Count': 1,
'Enabled': True,
'Find': b'',
'Identifier': '',
'Limit': 0,
'Mask': b'',
'MaxKernel': '',
'MinKernel': '',
'Replace': b'',
'ReplaceMask': b'',
'Skip': 0
}
Last edited:
If you want to disable temporarily the patch, simple set the
Enabled key to false:
Code:
<key>Enabled</key>
<false/>I took the tack of changing MaxKernel to 21.1.6 in the @Syncretic "patch" in my config.plist (built using the instructions in Post #1).
12.5 installed and is running fine.
12.5 installed and is running fine.
21.1.6? Do you mean 21.6.0? The 12.5 update hasn't worked for me. On the first boot my OC Picker selected macOS Installer, but then it stalled and rebooted by itself; on the second boot the Picker select Macintosh HD on its own and I'm back on 12.4. My MaxKernel lines are blank.
I am now using 12.5 with AVXpel MaxKernel set to 21.6.0. Seems to work so far. it was working fine without it too, but I didn't stress test AVX, I don't know how to.
@PeterHolbrook, that sounds to me like the upgrade procedure did not quite complete perhaps because you have something setup to not give you the boot menu. I used VMM, not sure if I needed to, but anyway, the first time the macOs Ibnstaller showed up on the boot menu...and I chose it...it went for a while and then rebooted itself..the second time in it seemed to go quite a long time also and seemed like it was even hanging, but eventually rebooted....and when it came back macOSInstaller no longer on the boot menu, but booting to the 12.5 volume caused another phase of the upgrade procedure to continue, before it finally booted into 12.5
@PeterHolbrook, that sounds to me like the upgrade procedure did not quite complete perhaps because you have something setup to not give you the boot menu. I used VMM, not sure if I needed to, but anyway, the first time the macOs Ibnstaller showed up on the boot menu...and I chose it...it went for a while and then rebooted itself..the second time in it seemed to go quite a long time also and seemed like it was even hanging, but eventually rebooted....and when it came back macOSInstaller no longer on the boot menu, but booting to the 12.5 volume caused another phase of the upgrade procedure to continue, before it finally booted into 12.5
Thanks, I'm not aware that I have anything out of the ordinary that will prevent macOS Installer from installing 12.5. It's surprising that, when it stalls and reboots, Macintosh HD (12.4) should be auto-selected.
I'm attaching my config.plist.
While updating remember to change to
<key>Cpuid1Data</key>
<data>AAAAAAAAAAAAAACAAAAAAA==</data>
<key>Cpuid1Mask</key>
<data>AAAAAAAAAAAAAACAAAAAAA==/data>
Also change <key>UpdateSMBIOS</key> to false while updating, and back to true after.
You are loading 'NoAVXFSCompressionTypeZlib.kext' and using 'AVXpel-patch' at the same time. Try disable each one of 'AVXpel - part 1 to 6', or just comment the whole part out with '<!--' and '-->'.
<!--
<dict>
...
</dict>
-->
I see you have <key>SetApfsTrimTimeout</key> to 9999999, I would set to 0.
I'm not at home so this is what I saw just with a quick look over your config.
for MacOS update I use Martin's config for OC 0.8.0.V2 with OC 0.8.0
but with two changes (V03 is compatible with 12.5)
https://forums.macrumors.com/.../config-plist-for-macos.../
Martin comments:
For those who want to run Monterey, please read the following carefully. This config is ready to "run" Monterey. However, NOT for Monterey "installation" (or update). You still need to turn on the VMM flag, and disable SMBIOS spoofing as per the steps in this video
https://www.youtube.com/watch?v=mrYFIpy9iqI
@Conzpiral & @Gustav Holdoff
Thank you for your advice. I'll look into that. Oddly enough, my current config.plist is the one that updated my system to Monterey 12.4 without any issues. The VMM flag has been off on my system for a long time, possibly since Catalina's days. Be that as it may, I'll try again and tweak config.plist accordingly.
Thank you for your advice. I'll look into that. Oddly enough, my current config.plist is the one that updated my system to Monterey 12.4 without any issues. The VMM flag has been off on my system for a long time, possibly since Catalina's days. Be that as it may, I'll try again and tweak config.plist accordingly.