MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Bmju]

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.

AllowToggleSip (twice) does do the trick. It may still report a weird setting, but SIP will be disabled (you can do what you need to do).

 

[sfalatko]

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.

Sorry @PeterHolbrook - you are correct - 21.6.0

I boot using a rescueCD so I babysit the install process and every reboot press the "C" key to boot from the rescueCD. The first reboot was "Macintosh CD", subsequent reboots (There were two or three) was "Monterey" (which I have named my Monterey volume).

Also - revisit the "macOS" section of Post #1 - right at the beginning of that section are the two options to seamlessly update Monterey (and BigSur). One is with VMM and one is without.

 

[MacToby]

I have edited the guide to support macOS 12.5

 

[PeterHolbrook]

I have edited the guide to support macOS 12.5

Do you mean post #1 in this thread? I haven't noticed any changes. What are they?

 

[MacToby]

Do you mean post #1 in this thread? I haven't noticed any changes. What are they?

Yes, I am talking about post #1. In order for macOS Monterey 12.5 to work/boot, as mentioned here a few times, the MaxKernel version of the AVXpel patch by @Syncretic must be increased from 21.5.0 to 21.6.0. This is now the case. Otherwise the patch is ineffective.

 

[Stex]

Yes, I am talking about post #1. In order for macOS Monterey 12.5 to work/boot, as mentioned here a few times, the MaxKernel version of the AVXpel patch by @Syncretic must be increased from 21.5.0 to 21.6.0. This is now the case. Otherwise the patch is ineffective.

did you reach out to OP @cdf about your edits to post #1? OP might be waiting for more data/info on 12.5 before making such edits. but perhaps you were in touch with OP.

 

[Dewdman42]

exactly. We actually need confirmation from Syncretic that the patch in question is still valid. It seems to be working ok for me so far, but that could be ancedotal.

 

[PeterHolbrook]

Yes, I am talking about post #1. In order for macOS Monterey 12.5 to work/boot, as mentioned here a few times, the MaxKernel version of the AVXpel patch by @Syncretic must be increased from 21.5.0 to 21.6.0. This is now the case. Otherwise the patch is ineffective.

Yes, I was aware of that. Unfortunately, that doesn't suffice in my case.

 

[Dewdman42]

I don't think VMM is required any more. Post #1 describes the hybridization options that should be used which will avoid needing VMM. I personally have an easy way to turn VMM on and off so I just turn it on when I update to be safe...but I don't think that is strictly necessary since a long time ago.

But @PeterHolbrook, see Conzipiral's other comments, you have some confusing things related to AVX work arounds...I think you need to choose one approach or the other..not both. But also I think you have something setup in the auto select feature of your boot menu and perhaps didn't go through the upgrade sequence quite exactly that requires a couple of reboots to complete it. We don't know what other bootable volumes are in your system, or how things are blessed, etc..

Sorry you're having problems, but I would start over from 12.4, check all your config.plist settings to make sure you are absolutely following CDF's guide correctly..and try again making sure to select the correct volume for each reboot during the upgrade.

 

[PeterHolbrook]

I've attempted the 12.5 update six times, with and without VMM, with and without UpdateSMBIOS, et cetera. All have failed miserably. I don't know the reason.

 

[Dewdman42]

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.

see above about AVX...you have a conflict there.

And as I said before, we don't know what kind of bootable volumes you have or what is blessed. As I said, the upgrade requires several reboots...and perhaps you are not rebooting correctly based on things you have said so far. Otherwise, I can offer no other help.

Good luck.

 

[PeterHolbrook]

see above about AVX...you have a conflict there.

And as I said before, we don't know what kind of bootable volumes you have or what is blessed. As I said, the upgrade requires several reboots...and perhaps you are not rebooting correctly based on things you have said so far. Otherwise, I can offer no other help.

Good luck.

Yes, there was a conflict, but that wasn't it. The conflict didn't prevent the 12.4 update. After getting rid of the conflict, the 12.5 update process still fails. My bootable volumes are all spinning disks. Blessings are correctly applied and have been for a long time. Would the update process succeed if I disable all the AVX patches?

 

[Dewdman42]

I would not disable AVX. Make sure its correct. However when I did the update, using VMM in case that matters, I did not have any AVX hack in place at all..since MaxKernel was still set to 21.5.0. But I am more suspicious that you are not rebooting to the correct volume during the upgrade procedure. I have no further advice. Good luck.

 

[PeterHolbrook]

I would not disable AVX. Make sure its correct. However when I did the update, using VMM in case that matters, I did not have any AVX hack in place at all..since MaxKernel was still set to 21.5.0. But I am more suspicious that you are not rebooting to the correct volume during the upgrade procedure. I have no further advice. Good luck.

Perhaps I haven't expressed myself correctly. When I let Software Update download the 12.5 installer and macOS begins its close down process, a progress bar and the Apple logo are displayed for perhaps two or three minutes (without booting). The progress bar will advance about 2 centimeters, and then the computer boots. The OC EFI kicks in and then the OC Picker is displayed. The pre-selected volume is macOS Installer. This installer is launched and then it dies in less than four minutes. Then the computer boots again. The OC EFI kicks in and then the OC Picker is displayed. The pre-selected volume is Macintosh HD, which is my 12.4 system. And that's it. This hasn't happened in earlier iterations of Monterey.

I'm considering the idea of downloading a full-fledged 12.5 installer.

 

[Dewdman42]

as I said, it took one extra reboot for mine to do to another stage during boot where it displayed the apple logo with a countdown message about how many more minutes, etc. When you said the pre-selected volume is your 12.4 system, are you referring to the 12.4 system that you are attempting to update? Just keep rebooting into the one you're trying to update a few more times. that is the stage where I saw the count down message.

You can try VMM mode like I did. When I did it with VMM, I made sure it was VMM over and over again through the 3 or so reboots..until finally it was running 12.5, then I changed back to hybridization and rebooted one last time.

 

[PeterHolbrook]

Yes, the 12.4 system I’m trying to update. I’ve tried the VMM flag to no avail. I’ve also tried manually selecting the macOS Installer three times in a row. It all ends the same: 12.4 being pre-selected for boot. What you describe is my experience with previous Monterey iterations. There’s obviously something wrong, but I can’t figure out what that might be.

 

[cdf]

I'm attaching my config.plist.

There’s obviously something wrong, but I can’t figure out what that might be.

I had a quick look at your config, and two things stood out:

1. "Updated" FirmwareFeatures and FirmwareFeaturesMask are missing from PlatformNVRAM (this also requires UpdateNVRAM=true)
2. BoardProduct is missing from DataHub (this also requires UpdateDataHub=true)

These settings are especially important in Monterey (see Complete your setup in post #1).

I have booted into 12.5 and seems to be working without bumping up the MaxKernel value of AVXpel. So that is good news, but I do know that there are certain usage patterns that have to be encountered in order for the missing AVX functionality to cause a panic.. I'm not sure what those test scenarios would be, in order to find out if 12.5 has somehow been fixed by Apple to not need AVXpel any longer.

I can't test AVXpel right now, but a simple test is to try enabling Voice Control (System Preferences > Accessibility > Voice Control). If the patch no longer works, then you'll get a panic (note that if you've never tried enabling it before, macOS might download some components first).

 

[Dewdman42]

I can't test AVXpel right now, but a simple test is to try enabling Voice Control (System Preferences > Accessibility > Voice Control). If the patch no longer works, then you'll get a panic (note that if you've never tried enabling it before, macOS might download some components first).

I enabled Voice Control, it downloaded some things and nothing panic'd. Guess either the patch works or Apple removed the dependency on AVX. One way or the other...

 

[PeterHolbrook]

I had a quick look at your config, and two things stood out:

1. "Updated" FirmwareFeatures and FirmwareFeaturesMask are missing from PlatformNVRAM (this also requires UpdateNVRAM=true)
2. BoardProduct is missing from DataHub (this also requires UpdateDataHub=true)

These settings are especially important in Monterey (see Complete your setup in post #1).

Thank you so much! I haven't tried yet, but I'm almost certain this will work now. I don't recall when exactly I left FirmwareFeatures and FirmwareFeaturesMask blank in PlatformNVRAM, but it must have been weeks ago. I think I must have misinterpreted advice by @tsialex or someone else that the presence of those values might eventually degrade the NVRAM chip. As for BoardProduct in DataHub, I doubt that ever was in my particular setup, although I may be mistaken.

So, I've changed all these parameters and I'll try them out later today. Thanks again!

EDIT: Yes!, that was it. Success at last! There was something odd, however. There were no indications whatsoever as to time left. No messages saying things like "Estimated time remaining: 12 minutes". The computer rebooted four or five times and then went straight to my 12.5 desktop. Excellent. Many thanks!

 

[Gustav Holdoff]

On my side, I'm running the following software (with no patch or kext related to AVX1.0):

    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'
        }
    ]

So far, I have never experienced any zlib related kernel panics, but if I start seeing them, I'll use NoAVXFSCompressionTypeZlib-v12.3.1.zip.

In my books, defining a value for MaxKernel is irrelevant, as people will follow always one of two scenarios:

1. Wait for others to validate if there are no issues with a new macOS release, then upgrade
2. Test the upgrade themselves and change the MaxKernel value to 21.6.0, from 21.5.0

In both cases, is useless to have MaxKernel defined. MinKernel is the key value to define, if the patch does not apply into a new OS release, you simply remove it.

since I am a user and not a developer, I am afraid of violating my settings if I run the automatic setup program.
since I have specific cards connected to pci slots:
on the third slot I have a double ssd card with nvme and with sata ssd,
on the first slot, a RadeonPro W5700 card -
(which, as a video card, works fine, but something in my opencore is not configured for its original work - there is some kind of unconfigured navi usb controller that calls some kind of kernel task that occupies the processor - and is comparable in resource consumption with the program - for example windows on parallels or archicad)
on the second slot- nvme
on the fourth thunderbolt Alpine. and i need own ACPI SSDT-TBOLT
and automatic programs do not always correctly understand what hardware and on what addresses are.
Based on my competence, I read the description of the plistlib generator to understand if I needed it.
for example, looked at command lines from 36 to 50
I understood about the configuration of the video card, but what do commands 43-47 do? I have nvme on these addresses, and nvme on the first address is not recognized by gfxutil
and I copy/paste my nvme addresses manually every time
that's why I still use the сdf instructions, because I understand each action and and decide whether I need to make each change or not
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb+msata crucial 1tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.2, mac os 12.5

 

[PeterHolbrook]

I enabled Voice Control, it downloaded some things and nothing panic'd. Guess either the patch works or Apple removed the dependency on AVX. One way or the other...

If your MaxKernel lines are set for 21.5.0, that should mean the AVX patches aren't being loaded on your system after the 12.5 update. Can anyone verify that AVX patches are no longer relevant for our old machines under Monterey 12.5?

 

[JanezP]

Thank you so much! I haven't tried yet, but I'm almost certain this will work now. I don't recall when exactly I left FirmwareFeatures and FirmwareFeaturesMask blank in PlatformNVRAM, but it must have been weeks ago. I think I must have misinterpreted advice by @tsialex or someone else that the presence of those values might eventually degrade the NVRAM chip. As for BoardProduct in DataHub, I doubt that ever was in my particular setup, although I may be mistaken.

So, I've changed all these parameters and try them out later today. Thanks again!

EDIT: Yes!, that was it. Success at last! There was something odd, however. There were no indications whatsoever as to time left. No messages saying things like "Estimated time remaining: 12 minutes". The computer rebooted four or five times and then went straight to my 12.5 desktop. Excellent. Many thanks!

Congrats, reading the thread it seems to be a very tedious job and I'm not qualified to step into the process. Would you mind sharing your updated config.plist as I've been struggling with the same symptoms on my cMP. Thanks in advance. JanezP

 

[tsialex]

I don't recall when exactly I left FirmwareFeatures and FirmwareFeaturesMask blank in PlatformNVRAM, but it must have been weeks ago. I think I must have misinterpreted advice by @tsialex or someone else that the presence of those values might eventually degrade the NVRAM chip.

FirmwareFeatures / ExtendedFirmwareFeatures / FirmwareFeaturesMask / ExtendedFirmwareFeaturesMask are not even set inside the NVRAM, these are non-volatile EFI variables and usually only change between firmware releases, like with the APFS support (FW_FEATURE_SUPPORTS_APFS) that was introduced back with MP51.0083.B00, to indicate the Mac hardware/firmware capabilities.

More info below:

OpenCorePkg/Include/Apple/IndustryStandard/AppleFeatures.h at master · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

Btw, without FW_FEATURE_SUPPORTS_LARGE_BASESYSTEM correctly set, you can't install, or update, Monterey.

 

[Conzpiral]

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.

Good that you made it! Looked over your config again and I see e.g you misplaced <key>MmioWhitelist</key>. You should put it below 'Patch':

<key>Patch</key>
<array/>
<key>MmioWhitelist</key>
<array/>

 

[PeterHolbrook]

Congrats, reading the thread it seems to be a very tedious job and I'm not qualified to step into the process. Would you mind sharing your updated config.plist as I've been struggling with the same symptoms on my cMP. Thanks in advance. JanezP

Sure thing. See the attachment. Perhaps I should point out a few oddities that work or have worked for me:

1. I'm spoofing an iMacPro1,1. I think most users prefer a MacPro7.
2. My config.plist contains references to kexts I no longer use. You can safely disregard those.
3. There seems to be a slight possibility that the AVX patches might no longer be necessary for Monterey 12.5, but I've haven't tested that possibility, so retaining them is probably safer.