My mac here is in the Beta program and reckons it is up to date with Beta 2 (which is great). Is this only just released or do we need some trickery to get this one?
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 MonteRand (probably the start of an ongoing saga)
- Thread starter Syncretic
- Start date
- Sort by reaction score
The update should be offered, maybe they stage availability but I definitely have it ready to install. Just not quite sure I want to be the first one doing it with an older CPU ?
I changed my OCLP version days ago from 0.3.2 with Monterand to 0.3.1 without Monterand and I have been using Beta 2 without issues.
Must be something different with your config, both of my two 5,1s are in the developer program and they report they are up to date still. I just checked again now. Must be checking the config I have and that prevents it from appearing.
I am not a computer professional so I am enchanted now using OCLP because it is automatic. I have not changed anything in my config.plst. I attach you it. I don't know if I have access to OTA updates because my account is enrolled as a developer in a supported Mac.
My MacBook Pro 4,1 (early 2008) is also updated to Monterey 12.1 Beta 3 via OTA under OCLP 0.3.1 (so, with SurPlus and without MonteRand)
Last edited:
Anyone here on 12.1b2 using the 0.7.5 package having freezes on start up?
Both of my 5,1 macs are randomly getting very slow/stalled boot up.
I will get the OC boot picker screen appear, choose macOS option and then the Apple logo appears with the progress bar going very slowly to about half way then stalling completely.
I have to turn off the machine and turn on again to get it to go. It was once off, rarely but is becoming more frequent now.
I'm not sure where to look for logging on this, so I'd appreciate some tips or advice.
Both of my 5,1 macs are randomly getting very slow/stalled boot up.
I will get the OC boot picker screen appear, choose macOS option and then the Apple logo appears with the progress bar going very slowly to about half way then stalling completely.
I have to turn off the machine and turn on again to get it to go. It was once off, rarely but is becoming more frequent now.
I'm not sure where to look for logging on this, so I'd appreciate some tips or advice.
12.1 beta 4 dropped yesterday. I have not installed it on my machine yet, anyone have anything to report on that?
Attach your config file for someone to take a look at. Patches or something else could be applied incorrectly within OpenCore
Attach your config file for someone to take a look at. Patches or something else could be applied incorrectly within OpenCore
Yeah it sounds like SurPlus is not applied. Double check MaxKernel values are 21.2.0 for both SurPlus patches.
Last edited:
I'm using the default 0.7.5 package from Martin Lo with no other changes aside from enabling the thunderbolt.
The MaxKernel is empty.
I ended up doing CMD-OPT-P-R and this appears to have stopped the issue and it boots normally again without problems. Before these freeze-ups occurred 12.1b2 worked fine without any problems and it since the CMD-OPT-P-R it appears to be working properly.
Edit: Unfortunately that was only a temporary resolve. It's back to doing its slow starts randomly.
Later today I'll fire up the single-processor 5,1 and install 12.1 beta 4 on that and see how it goes. The release notes in the Feedback Assistant look like it has various fixes.
Last edited:
Everything seems to work very well.
My MacBook Pro 13´´2018 have taken 3 minutes more than my old cMacPro using full InstallAssistant in both cases
Last edited:
I can confirm using 0.7.5 package (and modifying it as per Martin Lo instructions) allows the 12.1 update to work fine:
This is the machine I use primarily for Zwift, connected to 55" TV. HDD is 2TB Samsung 870 Evo. Sorry for image quality, quick photo of the TV screen.
This is the machine I use primarily for Zwift, connected to 55" TV. HDD is 2TB Samsung 870 Evo. Sorry for image quality, quick photo of the TV screen.
In my knowledge, Monterand seems to be an obsolete concept at the moment. It was created by @Syncretic to experimentally solve a specific booting problem in Monterey 12.1 Beta 1 (Experimental RDRAND patch) and it didn't apply for beta 2 to beta 4 and for the official 12.1.
SurPlus Patch continues to be essential for avoiding the Race Condition.
EDIT>18.DEC.21> Today some doubts are being published about if SurPlus 'continues to be essential' in Monterey 12.1: #9,846
EDIT>20.DEC.21> It is confirmed, SurPlus is not necessary for booting Monterey 12.1: #378
Last edited:
I have question about installation Monterey 12.1 on my Mac Pro 5.1 with Big Sur 11.1 via https://github.com/barrykn/big-sur-micropatcher) - Can I install and avoiding Race Condition? I ask because "Sur Plus" no longer required in Macos Monterey 12.1.
It appears the saga has resumed as the v12.4 release appears to use another unsupported CPU instruction, AVX in this case apparently, that causes random kernel panics.
Wonder whether this can be similarly patched. I suppose more and more instances will keep cropping up until the patches, if even possible/desirable, become as long as one's arm.
I expect the next MacOS version will be filled with similar instructions but let's live in hope!
Wonder whether this can be similarly patched. I suppose more and more instances will keep cropping up until the patches, if even possible/desirable, become as long as one's arm.
I expect the next MacOS version will be filled with similar instructions but let's live in hope!
Wonder whether the kext can be blocked and replaced by the one from the earlier working MacOS version in OpenCore.
If you're feeling adventurous, try to turn on Voice Control (System Preferences>Accessibility>Voice Control).
I'm very pressed for time right now, even more stuff on my plate than usual.
The problem reported by @Surf2bikes was correctly diagnosed by @joevt -
At first blush, the problem reported by @Charmandrigo appears to be the same
At first blush, the problem reported by @David403 (and confirmed by @cdf) also appears to be the same
The problem reported by @Macschrauber seems to be unrelated to AVX. I don't have time right now to investigate that one any further.
I will look into this some more when I can. In the meantime, I strongly encourage the adventurous to find a way to revert
(P.S. @lancemcv1 - sin-ˈkre-tik)
EDIT via iPhone: I should have also pointed out that until this is resolved, folks with MP5,1 and earlier should avoid upgrading to 12.4; there may be a risk of disk corruption.
The problem reported by @Surf2bikes was correctly diagnosed by @joevt -
AppleFSCompressionTypeZlib is using AVX, if only crudely. (They're using the YMM registers as temporary storage for a 512-byte chunk of something; there are 7 sections of code moving data in and out of all of the YMM registers. They're not doing any manipulations, just shoveling data in and out.) For the short term (and possibly the long term), someone should investigate the feasibility of using an older version - I had the 12.2 version at hand, and it does not use AVX. When I can find some time, a patch for this may be possible, but it will be a bit tricky because the patch will not only need to modify the code, it will need to create (at minimum) a new 512-byte data space as well. The problem is, this may well just be the tip of the iceberg, since Apple no longer has any reason to avoid using AVX.At first blush, the problem reported by @Charmandrigo appears to be the same
AppleFSCompressionTypeZlib AVX problem, despite the misleading stack dump.At first blush, the problem reported by @David403 (and confirmed by @cdf) also appears to be the same
AppleFSCompressionTypeZlib AVX problem, despite the misleading stack dump.The problem reported by @Macschrauber seems to be unrelated to AVX. I don't have time right now to investigate that one any further.
I will look into this some more when I can. In the meantime, I strongly encourage the adventurous to find a way to revert
AppleFSCompressionTypeZlib.kext to an earlier version.(P.S. @lancemcv1 - sin-ˈkre-tik)
EDIT via iPhone: I should have also pointed out that until this is resolved, folks with MP5,1 and earlier should avoid upgrading to 12.4; there may be a risk of disk corruption.
Last edited:
If there is disk corruption my problem maybe is related to this. Yesterday I had a 12.4 System what gave me suddenly the forbidden sign after rebooting.