macOS 12 Monterey on Unsupported Macs Thread

[internetzel]

I’ve installed Monterey 12.5 on 12.4 on my MacBookPro10,1 in clamshell mode, connected to an external display via TB-DisplayPort. Despite not having a full graphic acceleration (no transparencies, everything was laggy) I, as well, didn’t need to boot into safe mode to avoid boot loop and install OCLP patches. The Nvidia dGPU did work before the patches, otherwise I wouldn’t have been able to have the external display working.

OCLP 0.4.9 allowed for Kepler GPUs to be used again, but only using the plain framebuffer driver without any 3D graphics acceleration - maybe you were using that?

 

[amd is the best]

So I think I screwed up. Let me know if anyone else has done this and if there's a fix without a clean wipe.

Kepler upgraded 2011 iMac 27 previously running perfect on 12.4/OCLP 0.4.7. Saw the warnings and didn't do any updates until I knew there was a fix.

This morning, I downloaded and applied the OCLP 0.4.10 patches prior to updating the OS from 12.4. to 12.5. Now, I get the same issue others were facing having gone from 12.4 to 12.5 without the patch. Boots fine, login screen appears, attempt to login and the screen locks up and eventually redirects back to the login.

Anyone have any ideas or tips?

 

[Ausdauersportler]

So I think I screwed up. Let me know if anyone else has done this and if there's a fix without a clean wipe.

Kepler upgraded 2011 iMac 27 previously running perfect on 12.4/OCLP 0.4.7. Saw the warnings and didn't do any updates until I knew there was a fix.

This morning, I downloaded and applied the OCLP 0.4.10 patches prior to updating the OS from 12.4. to 12.5. Now, I get the same issue others were facing having gone from 12.4 to 12.5 without the patch. Boots fine, login screen appears, attempt to login and the screen locks up and eventually redirects back to the login.

Anyone have any ideas or tips?

Safe mode boot (check the docs howto) and install patches from there.

 

[GrandLepton]

So I think I screwed up. Let me know if anyone else has done this and if there's a fix without a clean wipe.

Kepler upgraded 2011 iMac 27 previously running perfect on 12.4/OCLP 0.4.7. Saw the warnings and didn't do any updates until I knew there was a fix.

This morning, I downloaded and applied the OCLP 0.4.10 patches prior to updating the OS from 12.4. to 12.5. Now, I get the same issue others were facing having gone from 12.4 to 12.5 without the patch. Boots fine, login screen appears, attempt to login and the screen locks up and eventually redirects back to the login.

Anyone have any ideas or tips?

I did the same on iMac 13,2:

Running 12.4 with OCLP 0.4.9.
Install OCLP 0.4.10
Software update to 12.5
Automatic reboot in success but GPU not working
OCLP 0.4.10 Post-Install Volume Patch, then reboot
Everything looks OK!

 

[OKonnel]

So I think I screwed up. Let me know if anyone else has done this and if there's a fix without a clean wipe.

Kepler upgraded 2011 iMac 27 previously running perfect on 12.4/OCLP 0.4.7. Saw the warnings and didn't do any updates until I knew there was a fix.

This morning, I downloaded and applied the OCLP 0.4.10 patches prior to updating the OS from 12.4. to 12.5. Now, I get the same issue others were facing having gone from 12.4 to 12.5 without the patch. Boots fine, login screen appears, attempt to login and the screen locks up and eventually redirects back to the login.

Anyone have any ideas or tips?

It seems to me that you applied both EFI Boot and the OCLP 0.4.10 Post Install Patch before installing macOS 12.5; after that you got the loop at the Login. It's right?

In this case, even in light of what happened to me after installing (foolishly…) “AutoPkg-Assets.pkg” 0.4.10 on macOS 12.4, WHILE I didn't have any loops before... that's my idea.
1) If we have macOS 12.4 which works fine with OCLP 0.4.9 it is possible to install OCLP 0.4.10 EFI Boot, but we absolutely don't need to install the 0.4.10’s Post Install Patch.
2) The OCLP 0.4.10 Post Install Patch should ONLY be installed AFTER updating the system to macOS 12.5!!!

Simple and trivial... But sometimes you want to exceed and they are wrong...

In conclusion: it is always better to follow what indicated in the OCLP instructions and in CHANGELOG.md. So, if OCLP 0.4.10 PIP (Post Install Patch) was designed for macOS 12.5... why on earth would our brains allow us to apply it unnecessarily while we still have fully functional macOS 12.4?...

Note. If I was right, then it would have been perfect to prevent the 0.4.10 PIP from installing on macOS if the macOS version is below 12.5.
@khronokernel can be suggested to insert a block or a warning’s window, for this purpose, in the next OCLP Night Build and respective PIP.

 

[il-rollino]

OCLP 0.4.9 allowed for Kepler GPUs to be used again, but only using the plain framebuffer driver without any 3D graphics acceleration - maybe you were using that?

Yes, I had 12.4 running patched with OCLP 0.4.9. The “behavior” of my Mac updating to 12.5 was the same as the previous updates.

 

[HowowcanIgo]

Hi guys,
Just wanted to inform that the install of 12.5 with OCLP 0.4.10 succeeded without a hitch on my MacBook Pro 5.2. I've waited a while before updating this time as everything already worked like a charm.
I do think 12.5 made my system a little bit slower (previously 12.4 installed with OCLP 0.4.4n).

Another thanks to all the amazing work from the developers! You guys are unbelievable!

 

[Larsvonhier]

Hi guys,
Just wanted to inform that the install of 12.5 with OCLP 0.4.10 succeeded without a hitch on my MacBook Pro 5.2. I've waited a while before updating this time as everything already worked like a charm.
I do think 12.5 made my system a little bit slower (previously 12.4 installed with OCLP 0.4.4n).

Another thanks to all the amazing work from the developers! You guys are unbelievable!

As always after major OS updates and upgrades: See if spotlight indexing is still running if you believe that system performance has changed. If that is not the case, it´s always helpful to check activity monitor to find what might be hogging your CPU resources. Also: Your MacBook Pro 5,2 is not equipped with Nvidia Kepler (but Tesla) so OCLP patches for non-metal acceleration. As noted elsewhere, the options for setting correct UI window opacity might also eat up a bit of performance there, so you could try to go without it.

 

[rehkram]

rMBP 10,1 with OCLP 0.4.10 is working here, both wired to the external monitor TB2 adapter -> DisplayPort and also with screen sharing over the LAN. Most of the time it's completely up and running, but in the mornings it's black screen and force restart time. I opened up the kernel panic notification which I've copied below.

panic(cpu 4 caller 0xffffff800ed5799f): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
service: logd, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins since wake (130 seconds ago): 2, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago

Panicked task 0xffffffa54bc90700: 3 threads: pid 120: watchdogd
Backtrace (CPU 4), panicked thread: 0xffffffa54bda0000, Frame : Return Address
0xffffffffff6eb690 : 0xffffff800b87fd6d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffffff6eb6e0 : 0xffffff800b9e1016 mach_kernel : _kdp_i386_trap + 0x116
0xffffffffff6eb720 : 0xffffff800b9d0383 mach_kernel : _kernel_trap + 0x4d3
0xffffffffff6eb770 : 0xffffff800b81fa70 mach_kernel : _return_from_trap + 0xe0
0xffffffffff6eb790 : 0xffffff800b88013d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffffff6eb8b0 : 0xffffff800b87f8f6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffffff6eb910 : 0xffffff800c114e53 mach_kernel : _panic_with_options + 0x89
0xffffffffff6eba00 : 0xffffff800ed5799f com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffffff6eba10 : 0xffffff800ed575f2 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffffff6eba30 : 0xffffff800ed56971 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xffffffffff6ebb60 : 0xffffff800c0835ec mach_kernel : _is_io_connect_method + 0x42c
0xffffffffff6ebcc0 : 0xffffff800b986d16 mach_kernel : _iokit_server_routine + 0x4f56
0xffffffffff6ebdd0 : 0xffffff800b85a98b mach_kernel : _ipc_kmsg_send + 0x46b
0xffffffffff6ebe60 : 0xffffff800b8711d9 mach_kernel : _mach_msg_overwrite_trap + 0x2c9
0xffffffffff6ebef0 : 0xffffff800b9b2fea mach_kernel : _mach_call_munger64 + 0x1ea
0xffffffffff6ebfa0 : 0xffffff800b820256 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[8BE4EE7F-9150-3161-BE84-36874BF82DE2]@0xffffff800ed55000->0xffffff800ed57fff

Process name corresponding to current thread (0xffffffa54bda0000): watchdogd
Boot args: keepsyms=1 debug=0x100 -lilubetaall ipc_control_port_options=0

Mac OS version:
21G72

Kernel version:
Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022; root:xnu-8020.140.41~1/RELEASE_X86_64
Kernel UUID: E3E2BC4D-7B6F-39CC-8890-73A6FB513830
KernelCache slide: 0x000000000b600000
KernelCache base: 0xffffff800b800000
Kernel slide: 0x000000000b610000
Kernel text base: 0xffffff800b810000
__HIB text base: 0xffffff800b700000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 19331743944640
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000119505bb20d2
Sleep : 0x00001172d85ede7d 0x000000003a3ab6be 0x00000e2b5f2ba31b
Wake : 0x00001172e0fca33e 0x000000003a246ad2 0x00001172dfdcf95a
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 1 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff907e027000 - 0xffffffb07e027000
. PGZ : 0xffffff907e027000 - 0xffffff907f028000
. VM : 0xffffff907f028000 - 0xffffff954ba8e000
. RO : 0xffffff954ba8e000 - 0xffffff96e535a000
. GEN0 : 0xffffff96e535a000 - 0xffffff9bb1dc0000
. GEN1 : 0xffffff9bb1dc0000 - 0xffffffa07e826000
. GEN2 : 0xffffffa07e826000 - 0xffffffa54b28c000
. GEN3 : 0xffffffa54b28c000 - 0xffffffaa17cf3000
. DATA : 0xffffffaa17cf3000 - 0xffffffb07e027000
Metadata: 0xffffffe572d20000 - 0xffffffe592d20000
Bitmaps : 0xffffffe592d20000 - 0xffffffe595d20000

Any ideas?

 

[joevt]

Any ideas?

Do you see any logs for WindowServer? It seems to be hanging.
Is there a way to disable watchdogd so it doesn't cause a panic when WindowServer hangs?

 

[rehkram]

Do you see any logs for WindowServer? It seems to be hanging.
Is there a way to disable watchdogd so it doesn't cause a panic when WindowServer hangs?

Good points, thank you. Those logs are hard to read! I did do one restart in safe mode, I read somewhere that can fix some things like this but it's probably a long shot. It's running normally now.

I'll check it out in the morning. If the watchdogd panic reoccurs I've decided the best thing to do is a squeaky-clean install. I'll do an NVRAM reset, erase the partition, reinstall from USB drive, reapply post install patches. It'll take a while but it might turn out to be faster than chasing a discrete fix.

One thing I've noticed since installing Monterey 12.5 with OCLP 0.4.10 is the About This Mac panel is showing both GPUs, I don't recall ever having seen that before.

 

[0134168]

Good points, thank you. Those logs are hard to read! I did do one restart in safe mode, I read somewhere that can fix some things like this but it's probably a long shot. It's running normally now.

I'll check it out in the morning. If the watchdogd panic reoccurs I've decided the best thing to do is a squeaky-clean install. I'll do an NVRAM reset, erase the partition, reinstall from USB drive, reapply post install patches. It'll take a while but it might turn out to be faster than chasing a discrete fix.

One thing I've noticed since installing Monterey 12.5 with OCLP 0.4.10 is the About This Mac panel is showing both GPUs, I don't recall ever having seen that before.

View attachment 2041648

Never seen that before also.

 

[chrisx78]

Never seen that before also.

I have currently the Same behavior on iMac 12.1. i have done the Post install twice, with the 04.9, After that the iMac cant Boot. Is it possible to make an undo from the Legacy Patcher, so i will do it new with the Version 04.10? Is there a Backup from the Files created from the Legacy Patcher ?

 

[davidlv]

I have currently the Same behavior on iMac 12.1. i have done the Post install twice, with the 04.9, After that the iMac cant Boot. Is it possible to make an undo from the Legacy Patcher, so i will do it new with the Version 04.10? Is there a Backup from the Files created from the Legacy Patcher ?

Don't overthink so much. "Undo, backup etc." Read the last few pages, the solution to your issue is right there in front of you. Install 12.5 from a USB install disk. Then Boot up in Safe mode (shift key down on boot). Install OCLP 0.4.10 and run the post install root patches. Refer to post # 7,131.

 

[OKonnel]

Good points, thank you. Those logs are hard to read! I did do one restart in safe mode, I read somewhere that can fix some things like this but it's probably a long shot. It's running normally now.

I'll check it out in the morning. If the watchdogd panic reoccurs I've decided the best thing to do is a squeaky-clean install. I'll do an NVRAM reset, erase the partition, reinstall from USB drive, reapply post install patches. It'll take a while but it might turn out to be faster than chasing a discrete fix.

One thing I've noticed since installing Monterey 12.5 with OCLP 0.4.10 is the About This Mac panel is showing both GPUs, I don't recall ever having seen that before.

View attachment 2041648

In fact it is strange... You made me doubt that it was the same for me and that I had not noticed the indication of the dual GPU.
So (since I'm on iPhone right now and I'm not on Mac), I searched for the post with my screenshot and as you can see my iMac indications are normal.
Note: if instead I launch “Geekbench 5” it also shows me the internal GPU of the CPU i7 which in Catalina is completely ignored…. But that's okay in Monterey.

 

[HowowcanIgo]

As always after major OS updates and upgrades: See if spotlight indexing is still running if you believe that system performance has changed. If that is not the case, it´s always helpful to check activity monitor to find what might be hogging your CPU resources. Also: Your MacBook Pro 5,2 is not equipped with Nvidia Kepler (but Tesla) so OCLP patches for non-metal acceleration. As noted elsewhere, the options for setting correct UI window opacity might also eat up a bit of performance there, so you could try to go without it.

Thanks voor the advice. I'm not sure what's causing it (apart from age). I don't think it's indexing anymore. It's particularly when typing that I notice some delay. On here for example. In Mail there's less delay.

 

[0134168]

Thanks voor the advice. I'm not sure what's causing it (apart from age). I don't think it's indexing anymore. It's particularly when typing that I notice some delay. On here for example. In Mail there's less delay.

Force it to reindex.

 

[OKonnel]

Thanks voor the advice. I'm not sure what's causing it (apart from age). I don't think it's indexing anymore. It's particularly when typing that I notice some delay. On here for example. In Mail there's less delay.

I think it is completely normal.
Basically ... it's a real miracle to be able to run Monterey on a 2009 MacBookPro 5,1.
I have a very powered MacBook Pro 7,1 (mid 2010) and have the kind of lag you describe and other lags even using macOS Catalina 10.15.7 installed via the dosdude1 patch.
I've also tried installing Monterey, via OCLP, but Macs lose a lot more fluency and cause the kind of problems you described. It's unnerving because it almost feels like you're using a computer with an old Celeron CPU struggling with Winzozz.

You have to be satisfied and at most you can disable enhancements such as transparency and GUI system actions.
But then ... out of curiosity ... have you noticed that all recent versions of iMovie and Final Cut Pro and other software don't work with Monterey installed on older Macs?... I know they don't work because in my old Catalina-patched Macs (but also when I tried Monterey with OCLP) iMovie and Final Cut Pro crash and I have found, therefore, that in order to work it is necessary to use the High Sierra versions of these and other applications.

So, my advice would be to go back to Catalina or better to High Sierra to resume enjoying all the power and fluidity of a good MacBook Pro like yours.

 

[il-rollino]

One thing I've noticed since installing Monterey 12.5 with OCLP 0.4.10 is the About This Mac panel is showing both GPUs, I don't recall ever having seen that before.

I’m not sure when and how, but I did see both GPUs on this panel before. Maybe even on Big Sur, possibly at time when displaypolocyd process issue prevented from using the iGPU. Since I’m using mostly my MBP in clamshell mode, it didn’t bothered me but I did some tests to help other users to understand it. Maybe I’m a little OT, anyway I did notice that sometimes the external display got a signal and turned on right ad the start of the computer (showing OCLP boot picker) while in other occasions, despite not having changed the setup of the Mac or OCLP version, it didn’t get the image signal until the login screen. Lately seems to start at the very beginning everytime.

 

[Larsvonhier]

I think it is completely normal.
Basically ... it's a real miracle to be able to run Monterey on a 2009 MacBookPro 5,1.
I have a very powered MacBook Pro 7,1 (mid 2010) and have the kind of lag you describe and other lags even using macOS Catalina 10.15.7 installed via the dosdude1 patch.
I've also tried installing Monterey, via OCLP, but Macs lose a lot more fluency and cause the kind of problems you described. It's unnerving because it almost feels like you're using a computer with an old Celeron CPU struggling with Winzozz.

You have to be satisfied and at most you can disable enhancements such as transparency and GUI system actions.
But then ... out of curiosity ... have you noticed that all recent versions of iMovie and Final Cut Pro and other software don't work with Monterey installed on older Macs?... I know they don't work because in my old Catalina-patched Macs (but also when I tried Monterey with OCLP) iMovie and Final Cut Pro crash and I have found, therefore, that in order to work it is necessary to use the High Sierra versions of these and other applications.

So, my advice would be to go back to Catalina or better to High Sierra to resume enjoying all the power and fluidity of a good MacBook Pro like yours.

OP was "happy" with the speed of 12.4 on his MacBook, so if in comparison 12.5 feels slower there is something going wrong and the advice of going back to High Sierra or Catalina feels somewhat misplaced (although in terms of overall performance true for almost all older machines).

 

[rehkram]

M/c was up and running in sleep mode this morning, woke up normally. I'd left the the display's OSD switched to the wired port, screen sharing was not active. Maybe booting once in safe mode fixed it. I doubt it but will report back. Tonight I'll try again, this time with screen sharing active.

Later: Spoke too soon. It restarted itself with the same crash log after I switched the display to a Mac mini 2018 with Ventura, watchdogd reporting timeout due to WindowServer not checking in. Looks like I'll be doing an NVRAM reset and clean install from USB drive later.

Much as I dislike Discord (too many children reducing the signal-to-noise ratio) I'll see if there's any discussion and maybe report it there.

 

[MacRumors3590]

Updated all my Macs with oclp 0.4.10 and os 12.5 with no issues!
Thanks Guys!

 

[Borak]

Come on.

Config iMac: iMac 27" Mid 2011 - i7 - 3.4GHz - Nvidia GTX 770M by nikey22 - macOS Catalina - SSD 240GB + HD 1TB - 16GB RAM.

1 - I installed Monterrey, according to the script.
2 - Installed Montrey on the internal SSD.
3 - I restarted the iMac in safe mode.
4 - I applied the patcher with the default options without changing any settings in OCLP.
5 - I restarted the machine and it is in loop.

It turns out that even now trying to get into safe mode, I can't and the progress bar doesn't advance.

I would be pleased if you can install any version of macOS Monterey.

 

[ChrisOSX]

Anybody have conflicting SIP settings?

System Information says Disabled. SilentKnight says enabled. The only SIP setting I have added to the default config was ALLOW_TASK_FOR_PID to try and get TotalFinder working.

View attachment 2030943

Thoughts? Thank You.

Still stuck on this. I can't figure out why the SIP settings would show different. I haven't gone into recovery via OpenCore boot picker (shouldn't have to since the OCLP app does SIP settings).

I believe this is the reason (maybe?) why I'm getting the "couldn't receive apple events" when launching total finder. Even though it shows in my automation tab that it does have special events checked. 🤷‍♂️

 

[rehkram]

M/c was up and running in sleep mode this morning, woke up normally. I'd left the the display's OSD switched to the wired port, screen sharing was not active. Maybe booting once in safe mode fixed it. I doubt it but will report back. Tonight I'll try again, this time with screen sharing active.

Later: Spoke too soon. It restarted itself with the same crash log after I switched the display to a Mac mini 2018 with Ventura, watchdogd reporting timeout due to WindowServer not checking in. Looks like I'll be doing an NVRAM reset and clean install from USB drive later.

Status update: The m/c hasn't crashed in 2 days so I'll skip doing a clean install for now.