The earlier OCLP v030n (containing the bluetooth fix for Monterey) caused kernel panic during the boot up for my iMac12,2. It has been fixed 4 hours ago. It may be related to your issue as well. Download the latest release v0.3.0 and try again....
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.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thanks for letting me know about the update, however, the problem in my installation is due to Window Server and associated dependencies, rather then bluetooth. See attached back-trace:
?AHOY! OCLP_030 has been released. Seems to support Monterey nearly as well as it supports Big Sur. 
https://github.com/dortania/OpenCore-Legacy-Patcher/releases
https://github.com/dortania/OpenCore-Legacy-Patcher/releases
Last edited:
With the B10 update, I found that I have to kill displaypolicyd in order to enable switching to Integrated vs. Discrete (defaulted without killing displaypolicyd). This is with applying post-install patching of OCLP.
yeah but there was something funky about Big Sur on 4,1 for awhile. wondering if that got fixed
Macbook pro 2014 13 inch in Monterey beta 10 and open core 0.2.5 works fine until the notification "inconsistent hash in the volume: There has been detected hash in the volume disk1s5 that does not coincide. Reinstall macOS in this volume", then the brightness of the screen and keyboard becomes almost irresponsible
(Sorry for the screenshot in Spanish)
(Sorry for the screenshot in Spanish)
Im not quite sure, but I prefer not to take the risk until I have read enough success with the latest version on my model
I know that, but I ain't no wealthy man. With no way of solving the worst, I can't afford to bet for the best
It might be this issue.
Try replacing the extensions in your EFI/Kexts and report back. Had this several times with Big Sur and Monterey since April. Reinstallation does not help.
Ciao a tutti una piccola domanda quindi mac pro 3.1 monterey beta 8 funziona tutto ma non riesco a vedere i nuovi aggiornamenti beta tramite OTA. Fino alla beta 8 li vedevo ora non vedo più niente. Qualcuno ha info a riguardo? Grazie in anticipo. Try to delete content of update folder without result
Maybe your translator didn't work properly... Comunque...
Try to unenroll and enroll again to beta program. Use:
Code:
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll
Code:
sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeedI strongly disbelieve it being a ram issue since windows runs perfectly and without issue for several days, intense games don't crash or slow down more than the expected for the limitation of the hardware and the ram tests I have run didn't show a problem
As for the EFI/Kexts, I don't know where to find that, and because of my ignorance I don't want to brick my Mac
?AHOY! Beta 10 OCLP_030 BT fix incomplete. Apple BT keyboard cannot make selections under Open Canopy at start-up. 12.6 and 11.6 worked just fine. Must use wired KB and mouse. However, BT items work as expected once entry screen appears +10 seconds. bluetoothd no longer crashes at boot with new release but slow at start-up. ? BRCM2046 ?
Last edited:
MacBook Pro 4,1 (high rez) successfully on Monterey B10.
Ok, so a little update to my hash mismatch issue - I don't really know what actually fixed the issue, but the error no longer appears and everything seems fine. The one thing I've changed was the system language - IDK if that could be the case.
But I have another issue - every time I open up my Mac, I have to select the drive and enter the password (sometimes it unlocks as it should from Apple Watch). I've strictly followed the instructions and the boot menu still appears. Any tips with that?
But I have another issue - every time I open up my Mac, I have to select the drive and enter the password (sometimes it unlocks as it should from Apple Watch). I've strictly followed the instructions and the boot menu still appears. Any tips with that?