Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
open your config.plist and enable the VMM flag and change SecureBootModel from disabled to default
once installed the VMM flag and SecureBootModel can the be safely disabled again
Given this a whirl on my MP5,1 and each time it appears to be trying a firmware update, then selecting my Monterey boot drive on reboot and landing me back at the beta. Manually choosing the "Macintosh HD" which appears just seems to repeat the process.
 
Last edited:
  • Like
Reactions: hutzi20
Changing the language didn't solved my issue with the hash mismatch, in the console the issue with corebrightnessd appear to be a EXC_BAD_ACCESS exception KERN_MEMORY_ERROR, I know is not a ram issue, after the mismatch notification appeared and the brightness control stoped working I still continued working for hours without any issue at all even tough I had a bunch of files and programs open.
 
Here on MacBook Pro 4,1 also stuck:
Installed the 12.0.1 RC, booted into it without Nvidia accel root volume patch. So far it went as usual with B9 and B10.
After doing the root volume patch, I cannot boot further than to a crashing login window.
Really nasty without a full installer package (did OTA with the RC): Cannot revert back to B10 with the USB installer as it throws the error msg "cannot recover this volume" at the disk selector in the installer...
Now will have to wait for the public beta full installer package.
The 031 Nightly that was supposed to have fixed this issue didn't work for NVIDIA root patching. :rolleyes::apple: Root patching lockouts have become far too common to be ignored. 🤨
 
Last edited:
Who has installed Monterey RC (12.0.1) on Mac mini 2012? Any issues? What’s the installation process? Currently have Big Sur running with OCLP.
OCLP 3.1 nightly updated from System Pref/Software Update.
All is good.
 

Attachments

  • Screen Shot 2021-10-19 at 23.25.54.png
    Screen Shot 2021-10-19 at 23.25.54.png
    117.7 KB · Views: 88
  • Screen Shot 2021-10-18 at 18.33.50.png
    Screen Shot 2021-10-18 at 18.33.50.png
    82.5 KB · Views: 104
  • Like
Reactions: k.alexander
and the VMM flag doesn't work anymore at least for MacPro 5,1
@KvR Sharing khronokernel's reply, as I opened a bug in oc.

Apple removed VMM from the Pallas Catalog temporarily, should be restored in the coming days. Either use a non-T2 SMBIOS or set SecureBootModel with a T2 ID and ensure VMM is not exposed

Nothing to be done on our end, wait for Apple to fix this

So...just wait...!
 
  • Like
Reactions: AlexSakha67 and KvR
Given this a whirl on my MP5,1 and each time it appears to be trying a firmware update, then selecting my Monterey boot drive on reboot and landing me back at the beta. Manually choosing the "Macintosh HD" which appears seems to repeat the process.
The same thing happened to me apparently it’s an issue with the installer apples end
 
  • Like
Reactions: roobarb!
The 031 Nightly that was supposed to have fixed this issue didn't work for NVIDIA root patching. :rolleyes::apple: Root patching lockouts have become far too common to be ignored. 🤨
It is a wide range of hardware to be supported by OCLP, and developers don‘t have all hardware at hand for testing. Plus patches are more complex than two macOS generations ago as the gap between Apple supported and unspported gets wider, even between betas.

I‘m happy to help testing, even if it leads to a non-bootable system from time to time. In some cases it is sufficient to manually revert part of a patch to revive the system, then one learns the most; sometimes re-installing is easier. A separate external disk improves testing turnaround and reduces risk.

Anyway it will be worth the inconvenience to have an old machine running Monterey in the end.
 
Can someone please clarify this to me :

I have rMBP mid 2014 with dGPU , I can do OTA updates but everytime it downloads a Full Installer (+10GB) , is this the normal and it is supposed to work like this ? we can no longer receive Delta updates ? or I have to change some settings in OCLP to be able to receive Delta updates and not Full Installer everytime ? I'm Currently have Monterey 12.0.1 RC , built my EFI with OCLP 0.2.5 and root system patched by 0.3.0 for NVIDIA support .

Thanks in Advance
 
Can someone please clarify this to me :

I have rMBP mid 2014 with dGPU , I can do OTA updates but everytime it downloads a Full Installer (+10GB) , is this the normal and it is supposed to work like this ? we can no longer receive Delta updates ? or I have to change some settings in OCLP to be able to receive Delta updates and not Full Installer everytime ? I'm Currently have Monterey 12.0.1 RC , built my EFI with OCLP 0.2.5 and root system patched by 0.3.0 for NVIDIA support .

Thanks in Advance
On patched root - yes, that's normal and the only possible.
 
On patched root - yes, that's normal and the only possible.
Thank you , another question , I have now my EFI built with 0.2.5 , should I do rebuild it with 0.3.0 and so on with every new release to have best support ?
 
Thank you , another question , I have now my EFI built with 0.2.5 , should I do rebuild it with 0.3.0 and so on with every new release to have best support ?
Formally it's non-mandatory, but some people here claim that they couldn't install RC with 0.2.5 and got success with 0.3.0. Moreover, new support features are added with almost every new build of OCLP. So... it's up to you ;)
 
  • Like
Reactions: samiqa
Formally it's non-mandatory, but some people here claimed that they couldn't install RC with 0.2.5 and got success with 0.3.0. Moreover, new support features are added with almost every new build of OCLP. So... it's up to you ;)
the only " problem " I face right now that after every update it get stuck when trying to get to login screen , I have to enter User Mode ( COMMAND + S ) and edit NVRAM settings to boot with iGPU not dGPU , after that I apply root system patch and everything is 100% , do you think this can be fixed by future builds that I may benefit from updating ?
 
the only " problem " I face right now that after every update it get stuck when trying to get to login screen , I have to enter User Mode ( COMMAND + S ) and edit NVRAM settings to boot with iGPU not dGPU , after that I apply root system patch and everything is 100% , do you think this can be fixed by future builds that I may benefit from updating ?
Anyway, before installing another build you can read here (or on OCLP Github page) about the changes and make your decision.
 
  • Like
Reactions: samiqa
can someone on 12.0.1 report if Safari still freezes after a while? (scrolling, for sure, doesnt work any more)?
 
Hello everyone, I just installed macOS Monterey on my MacBook Pro 11.2, with an upgraded 1TB NVME m.2 SSD, patched with OCLP 0.3.0 but it keeps crashing within a few minutes after booting.

It runs fine in safe mode and doesn't have a dedicated graphics card.

Do you have any experience with this problem? As of what I know it should run fine "out-of-the-box" on this model?
 
Hello everyone, I just installed macOS Monterey on my MacBook Pro 11.2, with an upgraded 1TB NVME m.2 SSD, patched with OCLP 0.3.0 but it keeps crashing within a few minutes after booting.

Do you have any experience with this problem? As of what I know it should run fine "out-of-the-box" on this model?

BTW. it runs fine in safe mode and doesn't have a dedicated graphics card.
So why had you to patch it if it's officially supported?
 
So why had you to patch it if it's officially supported?
Hi Tockman, it isn't officially supported however as of what I've read you don't have to patch the graphics compared to pre. 2013 MacBook Pro's with Intel 4000 graphics.

To clearify the model is a mid-2014 MacBook Pro and the official support starts from early 2015 and later.
 
  • Like
Reactions: Tockman
Stuck in a black screen boot on a MacBookPro8,1. OCLP 0.3.0 and tried external boot of 0.3.1.

AMFI: Denying for dump for pid xxx (MirrorDisplays)com.apple.Ambien

Also stuck in a black screen on a MacMini5,3. Not near that one currently.
 
Stuck in a black screen boot on a MacBookPro8,1. OCLP 0.3.0 and tried external boot of 0.3.1.

AMFI: Denying for dump for pid xxx (MirrorDisplays)com.apple.Ambien

Also stuck in a black screen on a MacMini5,3. Not near that one currently.
Hi! I created new partition on internal SSD on my MacMini 3,1. After this - i done the clean install of 12.0 Beta 10 from USB stick (OC bootlloader compilled by 0.3.1NB), and get 12.0.1 by system delta updates. After system volume was patched by latest OCLP 0.3.1NB - all works, without stucks and freezes.

Wating for full installer package, to recover yesterdays broken system.
 
  • Like
Reactions: K two
Hi! I created new partition on internal SSD on my MacMini 3,1. After this - i done the clean install of 12.0 Beta 10 from USB stick (OC bootlloader compilled by 0.3.1NB), and get 12.0.1 by system delta updates. After system volume was patched by latest OCLP 0.3.1NB - all works, without stucks and freezes.
Ideally I'd like to not have to wipe the machine since it is setup with some software that, while I have it, isn't fun to get back to good working order. Even tried to set it up in Target Disk as another volume the other night and re-run the patcher on it that way in case it wanted it. Nada. That was with 0.3.0.
 
  • Like
Reactions: K two
can someone on 12.0.1 report if Safari still freezes after a while? (scrolling, for sure, doesnt work any more)?
Not happening here. I did not run anything prior to 12.0.1 (well, I installed 12.0 for a second, just to upgrade to 12.0.1), but I was not having Safari freezing issues on Safari 15 on Big Sur on my unsupported Mac mini 2012 then either.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.