no need TM, use Disk Utility and create a new instance, install Ventura and copy your files and applications, after seeing that everything works, remove the Monterey instance.
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
no need TM, use Disk Utility and create a new instance, install Ventura and copy your files and applications, after seeing that everything works, remove the Monterey instance.
Hi folks,
My install of Monterey 12.6.5 on 5,1 with OCLP 0.6.2 has been quite solid since I installed it several months ago, but occasionally I get kernel panics (see condensed backtrace below). I think the Wi-Fi driver is the last thing executing on the panicked thread, if I understand the backtrace correctly. All panic reports have identical backtraces. My machine has an upgraded wi-fi ac card (BCM94360CD).
The root cause of the panic, which seems related to a failed memory block copy operation, might point at a RAM/hardware problem (I think), so not 100% sure this is a driver issue. However, after scanning this forum, I am realizing that recent OCLP versions like 0.6.2 might have de-stabilized Monterey. Any attempt on my part to downgrade by re-building OpenCore with a previous version of OCLP (tried 0.4.11 and 0.5.x) and installing to disk has resulted in wi-fi getting disabled after reboot, and an error pops up in the network preferences for wi-fi. It seems only 0.6.2 gets it to work... for a while anyway, until the next panic.
Any insight on what is going on? Any help would be appreciated!
*** panic report ***
My install of Monterey 12.6.5 on 5,1 with OCLP 0.6.2 has been quite solid since I installed it several months ago, but occasionally I get kernel panics (see condensed backtrace below). I think the Wi-Fi driver is the last thing executing on the panicked thread, if I understand the backtrace correctly. All panic reports have identical backtraces. My machine has an upgraded wi-fi ac card (BCM94360CD).
The root cause of the panic, which seems related to a failed memory block copy operation, might point at a RAM/hardware problem (I think), so not 100% sure this is a driver issue. However, after scanning this forum, I am realizing that recent OCLP versions like 0.6.2 might have de-stabilized Monterey. Any attempt on my part to downgrade by re-building OpenCore with a previous version of OCLP (tried 0.4.11 and 0.5.x) and installing to disk has resulted in wi-fi getting disabled after reboot, and an error pops up in the network preferences for wi-fi. It seems only 0.6.2 gets it to work... for a while anyway, until the next panic.
Any insight on what is going on? Any help would be appreciated!
*** panic report ***
Code:
panic(cpu 2 caller 0xffffff800b5044f0): __memcpy_chk object size check failed: dst 0xffffff9040ffe4a0, src 0xffffff9040a11494, (1024 < 1884) u/subrs.c:606
Panicked task 0xffffff8b757bf670: 275 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff9503731540, Frame : Return Address
0xffffffb916ab37e0 : 0xffffff800b67befd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffb916ab3830 : 0xffffff800b7de636 mach_kernel : _kdp_i386_trap + 0x116
0xffffffb916ab3870 : 0xffffff800b7cd9a3 mach_kernel : _kernel_trap + 0x4d3
0xffffffb916ab38c0 : 0xffffff800b61ba70 mach_kernel : _return_from_trap + 0xe0
0xffffffb916ab38e0 : 0xffffff800b67c2cd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffb916ab3a00 : 0xffffff800b67ba86 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffb916ab3a60 : 0xffffff800bf14983 mach_kernel : _panic + 0x84
0xffffffb916ab3b50 : 0xffffff800b5044f0
0xffffffb916ab3b70 : 0xffffff800d4ecae4 com.apple.iokit.IO80211FamilyLegacy : __ZN18IO80211ScanManager8scanDoneEb + 0x104
0xffffffb916ab3be0 : 0xffffff800d4d4dc7 com.apple.iokit.IO80211FamilyLegacy : __ZN16IO80211Interface11postMessageEjPvm + 0x9a3
0xffffffb916ab3c50 : 0xffffff800d83f2a3 com.apple.driver.AirPort.BrcmNIC : _wlc_scan_callback + 0x5c
0xffffffb916ab3c90 : 0xffffff800d83cae6 com.apple.driver.AirPort.BrcmNIC : _wlc_scantimer + 0xb7d
0xffffffb916ab3db0 : 0xffffff800d5fc3ba com.apple.driver.AirPort.BrcmNIC : __ZL17wl_timer_callbackP8OSObjectP18IOTimerEventSource + 0x80
0xffffffb916ab3dd0 : 0xffffff800be49ca5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffb916ab3e40 : 0xffffff800be49ba8 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc8
0xffffffb916ab3e70 : 0xffffff800b6cef75 mach_kernel : _thread_call_delayed_timer + 0x505
0xffffffb916ab3ee0 : 0xffffff800b6d0042 mach_kernel : _thread_call_delayed_timer + 0x15d2
0xffffffb916ab3fa0 : 0xffffff800b61b19e mach_kernel : _call_continuation + 0x2e
Instead of
Last edited:
Hey everyone, I just installed 12.6.8 on my Late 2013 Macbook Pro with Kepler graphics (MacBookPro11,3) using OCLP 0.6.8 and for the most part everything works as expected, except backups, specifically Synology Active Backup which relies on ASR. This is because of the broken APFS seal that happens after the root patching.
Is there any way to solve this? Should I use OCLP 0.5.0? Or is there a way to restore the seal integrity with the current version?
Is there any way to solve this? Should I use OCLP 0.5.0? Or is there a way to restore the seal integrity with the current version?
I'm on macOS 12.6.8 - build with OCLP 0.5.0 - but also experiencing issues (failed backups) with Synology Active Backup Agent version 2.6.1-3052. So in my case the OCLP version did not matter.
I added the Disk Utility info.
Last edited:
Hi,
just asking:
did you experience any problem after the installation's process, like, a little slow grafic movemet as you open and close folders or change desktops, or microphone and camera no accessable from any app? I own a MBP 8,2 with Snow Leopard, El Capitan and Monterey. The newest one has these issues but OCLP shows that all possible patches are already installed. I've tryed everything possible found on the net but nothing. On my iMac 2011 it run just fine and both Macs have ssd + RAM updrade.
Peace
Starting having a 4,1 MP freezing real bad. Thought it was from updating a system from way back so did fresh install. When it kept happening, I thought it could be since putting in a second pcie NVMe card and then when removing that it seemed ok for a while. Some time goes by and wanted to reinstall the second NVMe on the 1st card since it had two slots and realized the second slot was sata and think it required power, so tried shuffling the cards around the PCIe slots with the separate cards. (Theres also a USB3 card in there.) Still had the issue so took out the second card again. Seemed ok the first time so maybe after switching slots is why its still doing it?
Could be that one of the slots are a little off? I dont know but the freezing is making me want to get rid of it and just run the hack I made thats way better but I just dont want to give up that sweet case design if I can get it sorted.
Well, I updated the rom to enable native boot picker on pc gpus supporting GOP. In the process discovered a failing drive which I thought could be the problem but removing the drive did not fix the freezing after a couple hours of running from a restart.
Now trying RTC battery change.... so far no freeze. We'll see.
Problem persisted. Takes some usage of maybe an hour before happening.
Could be that one of the slots are a little off? I dont know but the freezing is making me want to get rid of it and just run the hack I made thats way better but I just dont want to give up that sweet case design if I can get it sorted.
Well, I updated the rom to enable native boot picker on pc gpus supporting GOP. In the process discovered a failing drive which I thought could be the problem but removing the drive did not fix the freezing after a couple hours of running from a restart.
Now trying RTC battery change.... so far no freeze. We'll see.
Problem persisted. Takes some usage of maybe an hour before happening.
Last edited:
Has anybody tried 12.6.7 -> 12.6.8 on OCLP 0.6.6+?
Turns out, I didn't login for a while and it went to sleep. I can confirm, 12.6.7 -> 12.6.8 on OCLP 0.6.6 works. Haven't tested other OCLP versions...
Last edited:
I'm using Monterey less and less on my MBP6,2 as Ventura 13.5.1 patched with OCLP 0.6.8 is working just as well. I'm still keeping Monterey and Big Sur Volumes for OCLP testing, but Ventura 13.5.1 is now my go-to macOS. OCLP Devs continue to work their miracles. I'm not suggesting that this good Ventura experience implies the same for other SMBIOS models and it definitely depends on graphics support in Ventura, but for the MBP6,2 with non-metal Nvidia Tesla, Ventura 13.5.1 is now just as good as Monterey.
Hey guys,
I am on 12.6.8 with OLCP 0.4.1 and have the following problem:
When I add an app who requires microphone or cam access e.g. the app doesn´t appear in System preferences/Privacy/Microphone or /Camera etc., so I cannot click to grant the access.
What can be the solution here ?
Reinstall some OS-related resources or some adjustments in the OLCP ?
Thanks
I am on 12.6.8 with OLCP 0.4.1 and have the following problem:
When I add an app who requires microphone or cam access e.g. the app doesn´t appear in System preferences/Privacy/Microphone or /Camera etc., so I cannot click to grant the access.
What can be the solution here ?
Reinstall some OS-related resources or some adjustments in the OLCP ?
Thanks
SOLVED:
Stopped making Synology Active Backup snapshots at all, deleted the service app. It automatically cleared all snapshots and cleaned up the failed snapshots. Gave me back some big chunk of my SSD disk space.
Stopped making Synology Active Backup snapshots at all, deleted the service app. It automatically cleared all snapshots and cleaned up the failed snapshots. Gave me back some big chunk of my SSD disk space.
I believe the permission issue is resolved on the newer version of OCLP, your really outta date
Hi guys and thanks for any help from your side. I've installed Os Monterey on my old 2011 Mac. Everything was super easy and fine till I tried to use Photo app and Maps. The photo shows all the shots in the library but is unable to edit them. I mean as I select one it appears big in the center screen and immediately disappear. Also seems a part of the program is missed, on the right you can't see the library above "memories" so no possibility to see years, days etc. No way. Map is no able to fix a position nor to download any maps. I've installed over my previous installation, could this be the main problem? If you switch post installation patch it become instable but photo are editable Thanks for any help
Not his fault. There's been advice in this forum to stay on old versions of OCLP.
Yes, that is right.
So, I have to apply the root patches with 0.6.8 or build Opencore with 0.6.8 or both ?
Thanks !
Whenever you upgrade to a new OCLP, you always "Build and Install OpenCore" and Apply Post-Install root patches with the new version (must always do both). As you have seen, one's success with a version of OCLP depends largely on their SMBIOS model and their graphics. For me on my MBP6,2 (non-metal Nvidia Tesla), continuing to upgrade to the latest OCLP (I currently use OCLP 0.6.8 for Big Sur, Monterey and Ventura and 0.6.9n for Sonoma) has been the best strategy. You'll need to test to determine what works best for you.
Hi everyone,
After cloning my previous 500GB Crucial SSD (2 partition: Catalina and Monterey-OpenCore Patcher, installed in Feb 2022) to a new 2TB Crucial SSD with CCC, my MBP 9,2 (13-inch, mid-2012) is booting from Catalina; but there is no first boot screen showing choice between Catalina and Monterey(OpenCore Patcher).
Is there a way to reinstall just the correct drivers to boot the new SSD Monterey Partition and the first boot screen showing the booting choice Monterey or Catalina?
Or shall I reinstall the full OCLP release (I can see that the Monterey folders have been cloned in the Monterey partition)?
Which OCLP version would you recommend for installing MAC OS 12 Monterey on my MacBook Pro 9,2 (13-inch, Mid 2012)?
After cloning my previous 500GB Crucial SSD (2 partition: Catalina and Monterey-OpenCore Patcher, installed in Feb 2022) to a new 2TB Crucial SSD with CCC, my MBP 9,2 (13-inch, mid-2012) is booting from Catalina; but there is no first boot screen showing choice between Catalina and Monterey(OpenCore Patcher).
Is there a way to reinstall just the correct drivers to boot the new SSD Monterey Partition and the first boot screen showing the booting choice Monterey or Catalina?
Or shall I reinstall the full OCLP release (I can see that the Monterey folders have been cloned in the Monterey partition)?
Which OCLP version would you recommend for installing MAC OS 12 Monterey on my MacBook Pro 9,2 (13-inch, Mid 2012)?
Your best bet is using the latest version of OCLP, but if you have any issues you can try 0.4.11.
@HDMC If by "same result," you mean that with OCLP 0.6.8, you are unable to grant camera and microphone permissions, you need to build your open core EFI without disabling AMFI (with AMFIPass.kext 1.3.1). If you continue to disable AMFI (boot-arg amfi=0x80), then you need to use tccplus to grant camera and microphone permissions.
The standard settings for 0.6.8 are without disabling AMFI. And I didnt change these settings.
So what you mean with "With AMFIPass kext 1.3.1" ? I have to install this kext manually ?
I did build OLCP 0.6.9 with no changes ...
For AMFIPass installation, users who are either using OpenCore Legacy Patcher 0.6.6 and newer or freshly installing can upgrade without issue!
Users who are upgrading from an older version of OpenCore Legacy Patcher will not have AMFI enabled by default until you re-root patch your system. This is due to root patches in 0.6.6+ having a Dortania signature allowing for binary validation. Once updated, OpenCore Legacy Patcher will notify you to rebuild OpenCore with AMFI enabled.
Users who are upgrading from an older version of OpenCore Legacy Patcher will not have AMFI enabled by default until you re-root patch your system. This is due to root patches in 0.6.6+ having a Dortania signature allowing for binary validation. Once updated, OpenCore Legacy Patcher will notify you to rebuild OpenCore with AMFI enabled.
@HDMC Check whether you have AMFI disabled by doing the following:
It is the Open Core EFI that determines whether you have AMFI enabled or disabled (the EFI you generate when you "Build and Install Open Core").
EDIT: One other thing... If you have manually set app permissions using tccplus or other utility when AMFI was disabled, you may want to reset app permissions after you enable AMFI so that running the apps prompts you for permissions like camera and microphone. See this document for more info about using tccutil.
- In terminal, issue command (without quotes) "nvram -p | grep amfi". This should return nothing. If you see amfi=0x80, then you have disabled AMFI
- In terminal, issue command (without quotes) "kextstat | grep -i amfi". You should see com.dhinakg.AMFIPass (1.3.1) in the returned text. If you don't see com.dhinakg.AMFIPass (1.3.1), then you are not properly enabling AMFI
It is the Open Core EFI that determines whether you have AMFI enabled or disabled (the EFI you generate when you "Build and Install Open Core").
EDIT: One other thing... If you have manually set app permissions using tccplus or other utility when AMFI was disabled, you may want to reset app permissions after you enable AMFI so that running the apps prompts you for permissions like camera and microphone. See this document for more info about using tccutil.
Last edited:
Last edited: