I tried re-enrolling in the beta program but without success. On another partition I have another monterey that I had previously installed and on that the beta update works I do not understand why this does not
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
I've had a little different issue - disk1s1 (s5 occurred before system reinstall). I've changed from Polish to English; it runs around a week now and 0 errors so far.
On my MBP5,2, same observation regarding beta10 installed with OCLP 0.3.0 release: installs and works fine, but after applying the volume patches, won't boot.
Progress bar hangs, and disk activity stops (using an external SSD, the USB to SATA interface has an activity LED).
I'm using the full installer for b10.
When booting with a 0.3.0 in verbose mode, the last activity when booting stalls is shown in the 1st photo.
Same crash log as RogueB's shown on the next boot into my Big Sur system.
(I had observed the same thing with beta9 and a 0.3.0 nightly from 12Oct but didn't follow up.)
Attachments
problem fixed after updating OCLP to version 0.3 i got beta updates and now i have 21A5552a which works great on mac pro 3.1 ...
try the latest v031n TUI, which may contain the fix for your particular MBP5,2.
I can confirm, that for MacBookPro 5,2, the latest nightly OCLP 0.3.1 TUI eliminates boot-stall issues with Beta10, restores resolution and brightness control, as well as menu bar and dock translucency. Monterey is on-par with BigSur functionality.
The functionality was restored a short time after the bag was reported to https://github.com/dortania/OpenCore-Legacy-Patcher/issues , per your [TigerA] suggestion.
Thank you to everyone involved in the process.
The functionality was restored a short time after the bag was reported to https://github.com/dortania/OpenCore-Legacy-Patcher/issues , per your [TigerA] suggestion.
Thank you to everyone involved in the process.
These issues have been resolved in latest OCLP 0.3.1 TUI update. I just updated my installation and usability is similar to BigSur. Bluetooth seems to function but, after connecting the two devices, iPhone disconnects with message that "[this] MacBooK Pro is not supported" (?)
Last edited:
Thanks. Successfully booted my MBP5,2 with beta10 now.
For a test, instead of using OCLP 0.3.1n directly, reverted in the existing (non-booting) b10 installation manually
/System/Library/Extensions/AppleGraphicsControl.kext/Content/PlugIns/AppleMuxControl.kext
from the 0.3.0 patch to the beta10 stock version.
Used jackluke BigSurmountsrw for this.
b10 now really behaves very well on MBP5,2. Photos working.
I'm using two b10 installations: this one made with OCLP, and one made with BaseSystemfix, on two USB SSDs.
Running with reduced transparency (as I already did in Catalina for performance) for less graphics artefacts.
Both are clean installations in this sense: on erased SSD, used CCC to copy over all data/apps/settings from my standard Big Sur. Then installed b10 over this using the full installer. The reason for using CCC is that the migration assistant, which runs after the OS installation, made the system non-bootable in several attempts.
Careful with CCC though: tried to update my running b10 (made with BaseSystemfix) to the data state of my Big Sur with CCC. The system was non-bootable after that, rerunning the patches didn't help, and installing again over it did not work, so had to erase everything. Using a set of rsyncs instead until I will switch my daily system to Monterey.
Confidently looking forward to the Monterey release.
Thanks to the OCLP team, to jackluke, to ASentientBot and the whole community here.
Attachments
Last edited:
The purpose of that file from Sierra if I not misread the post on unsupported 10.14 thread, is to provide fast GPU switching directly on desktop for MacBookPro5,x dual Nvidias, but since it's not tested on Catalina and later I guess to work reliably it might require the alignment with AGC set from Mojave or even HighSierra, from a superficial test even the HighSierra AGC kmutil correctly with Monterey, the fact is without having the target machine is not simple, also after any OTA updates where I am recently proceeding avoiding the InstallAssistants download, the System turns sealed again (reinstalling through HaxLib and full macOS install app unseals it), not a big deal since BigSur can detect and decode the later macOS Sealed Systems, but a bit annoying to make replacements especially when wrong non metal graphics patches can easily prevent booting, but it's doable anyway with some efforts (not from CMD+S rather from BaseSystem with kernel ≥ 20.0.0 ) .
I'll try a non clever patch on kernel to allow "mount -uw /" on a Sealed System, but this 99% going to fail.
Code:
These are in the "apfs kext" binary embedded in Boot Kernel Extensions kc
%s:%d: %s failed to retrieve default root snapshot xid: %s (%d)
apfs_find_named_root_snapshot_xid%s:%d: %s failed to find root-snapshot-name <%s>: %s (%d)
%s:%d: %s failed to allocate memory for root-snapshot-name%s:%d: %s failed to find named root snapshot: %s (%d)
%s:%d: %s Tagged and root-snapshot-name are the same.
apfs_root_snapshot_select%s:%d: %s RELEASE build rooting from tagged sealed snapshot!enableddisabled%s:%d: %s Rooting from tagged snapshot, xid %llu. Integrity checks will be %s.
%s:%d: %s Rooting from tagged snapshot, xid %llu.
%s:%d: %s Rooting from snapshot with xid %llu.
"Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"
apfs_vfsops.capfs_device_locked busy (1)%s:%d: %s apfs is being LOCKED!
handle_keybag_lock%s:%d: %s apfs is now LOCKED (flags 0x%llx)!
apfs_device_locked busy (2)%s:%d: %s apfs is now UN-locked! (flags 0x%llx)
handle_keybag_unlock%s:%d: %s apfsreceived an unexpected lock-state: %d
apfs_device_lockedmountsnap_wait_(un)mountcom.apple.private.vfs.snapshotcom.apple.private.apfs.arv.limited.snapshot%s:%d: %s attempting to tag sealed snap without entitlement
handle_root_to_snapshot%s:%d: %s attempting to tag sealed snap without disabling ARV
%s:%d: %s attempting to tag UNSEALED snap without entitlement
%s:%d: %s Volume is already set to root to snapshot "%s" w/snap xid %lld on next boot
%s:%d: %s Volume is already set to root to live file system on next boot
%s:%d: %s using unsealed snapshot (%llu) as root filesystem is not supported
Last edited:
Yes, have it on various machines here. What helps is to quit Safari and re-open it.
Seems to happen when Safari is not used (in background) for a while.
yes, that is my impression as well (MBP5,2 with 12.0b10).
Hi! Successfully updated my CMP 3.1 (Early 2008) from MacOS Monterey 12.0 Beta9 to Beta 10 by system OTA updates.
OCLP - 0.3.0
System Volume patched for keppler GPU support
Issues - sleep mode stiil don't work
Greate work guys! Thanks to all contributors.
OCLP - 0.3.0
System Volume patched for keppler GPU support
Issues - sleep mode stiil don't work
Greate work guys! Thanks to all contributors.
Macbook Pro 13" 2010 - OCLP: 0.3.1 (nightly)
The nightly version solved the above problem and, with that, I was able to install Beta 10.
Network and bluetooth are not working. Does anybody know how to solve this?
Thanks.
The nightly version solved the above problem and, with that, I was able to install Beta 10.
Network and bluetooth are not working. Does anybody know how to solve this?
Thanks.
Beta 10 Post-OCLP_030TUI Bluetooth observed changes for BRCM2046 on multiple Mini3,1 -
• In B/T CP
1 - Apple B/T keyboard battery condx vanishes where Apple trackpad indicator is unchanged.
2 - Cannot add a new device and will only connect to the entries listed.
• Open Canopy w/Apple B/T KB
a - option/alt and control keys work as expected (didn't try other keys).
b - arrow keys have no response until after entry screen, once fully booted arrow keys return.
Note: System Information attached - "THIRD_PARTY_DONGLE" ??
Apple's macOS Monterey will be released on October 25
Apple has confirmed its macOS Monterey software will be released in full on October 25.
www.imore.com
@Bravo2zero -- So you got Monterey running on a Mac mini 2012? Any problems/issues? I've got the same system, have Big Sur running on it via OCLP, have held off on installing the betas, but seems like we're almost there...itching to install it, especially in light of the newly updated today Safari with normal tabs again. Any input would be appreciated.
Last edited:
Did you run OCLP TUI app after booting up B10 and select #3 to apply Post-Install Volume Patch?
to those of you that have installed beta on 2015 MBP (model 11,5) with AMD Graphics (if anybody) can you recommend Monterey? Or not? I am on the fence...
?AHOY! MacOS 12.01 installed perfectly OTA atop Beta 10 on this Mini3,1. Re-installed OCLP EFI and NVIDIA and WI-FI root patches from the curret OCLP_031n Offline Variant which completed as normal. Option>control booted into OCLP then selected Monterey ENTER>progress far ran until 2/5th complete then came the black screen of death.
☠️ Still looking for a method to recover.?
☠️ Still looking for a method to recover.?
Last edited:
Prior to today's release, was on latest beta and today noticed 12.0.1 (no longer beta). Download size showed 1.9GB OTA so I went for it (previously updating to OCLP 0.3.0 release). After installation and reboot (and another post-install patch for my HD4000), looking all good so far. Afterwards, I was prompted to update/install ProRes via System Update which it took and no issues since.
You mean the developer RC, isn't it? Haven't seen the RC for public yet on my computer.