Thank you again. Any thoughts on how to go back to big sur, should i wipe the whole drive, clean install ? Or theres a way to rollback without backup?
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
There is no official roll back and has never been. You should have a Big Sur TM backup and try to restore it after a clean new Big Sur installation, best results can be experienced without having any patches applied.
I updated my machine (exactly same) from Dosdude Catalina Patcher to Monterey 12.5 using OCLP 0.4.9.
After a boot loop and a PRAM reset (that brought red stripes on my screen) the installation finished successfully (I deactivated RADEON graphics again after PRAM reset).
It's running Monterey beautifully. Every app that crashes my Mac Pro ran without errors or crashes. Now I need to decide what to do with my Mac Pro. After I had upgraded RAM, SSD and processor, I can try a fresh install, or replace GPU... or at the end, replace whole machine, saving the upgrades.
Thank you all that work in OCPL and the community. It's a beautiful work!
In the case the Kepler dGPU problems with Monterey 12.5 were too difficult to solve, would it be possible to provide some form of “basic” patching in OCLP, where the dGPU is disabled but at the same time the brightness controls still work…? For example, probably an old MacBook Pro with dual graphics is perfectly usable also with only the iGPU enabled: or would some applications just not work without the dGPU…? In other words, if the machine is still usable without the Kepler dGPU, maybe the easiest way would be to disable it, provided everything else works (brightness controls included); sadly, this is not possible for machines with only Kepler as primary graphics, but for the dual ones maybe it could work, if made easy through the OCLP app. Of course, the best option would still be to solve the Kepler problem: so, let’s hope that it will possible for the developers to do something, even if of course it might take some time…
What could help is to power down the complete dGPU at boot time via NVRAM command. This was done successfully on dual GPU machines with defective dGPU.
The command would be:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
Works for i.e. MacBook Pro 8,2 and others.
edit: checked on MBP8,2 - everything works as it should (screen backlight and keyboard illum. control, also via function keys)
Last edited:
Anybody having sleep/hibernation issues?
If I let my machine sit too long it goes from sleep to just powering off. Upon restarting, I'm presented with the following report.
If I let my machine sit too long it goes from sleep to just powering off. Upon restarting, I'm presented with the following report.
Code:
panic(cpu 0 caller 0xffffff801f8299c1): AppleAHCIDiskQueueManager::setPowerState(0xffffff90af389480 : 0xffffff8021796cf0, 0 -> 3) timed out after 101407 ms @IOServicePM.cpp:5524
Panicked task 0xffffff90af83c670: 184 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff9a474a5540, Frame : Return Address
0xffffffbde7cfba30 : 0xffffff801f07fd6d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffbde7cfba80 : 0xffffff801f1e1016 mach_kernel : _kdp_i386_trap + 0x116
0xffffffbde7cfbac0 : 0xffffff801f1d0383 mach_kernel : _kernel_trap + 0x4d3
0xffffffbde7cfbb10 : 0xffffff801f01fa70 mach_kernel : _return_from_trap + 0xe0
0xffffffbde7cfbb30 : 0xffffff801f08013d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffbde7cfbc50 : 0xffffff801f07f8f6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffbde7cfbcb0 : 0xffffff801f914d93 mach_kernel : _panic + 0x84
0xffffffbde7cfbda0 : 0xffffff801f8299c1 mach_kernel : __ZN9IOService12ackTimerTickEv + 0x801
0xffffffbde7cfbe00 : 0xffffff801f829189 mach_kernel : __ZN9IOService21actionAckTimerExpiredEP8OSObjectPvS2_S2_S2_ + 0x9
0xffffffbde7cfbe10 : 0xffffff801f84353e mach_kernel : __ZN10IOWorkLoop9runActionEPFiP8OSObjectPvS2_S2_S2_ES1_S2_S2_S2_S2_ + 0x3e
0xffffffbde7cfbe50 : 0xffffff801f827fc8 mach_kernel : __ZN9IOService17ack_timer_expiredEPvS0_ + 0x38
0xffffffbde7cfbe70 : 0xffffff801f0d2655 mach_kernel : _thread_call_delayed_timer + 0x505
0xffffffbde7cfbee0 : 0xffffff801f0d3722 mach_kernel : _thread_call_delayed_timer + 0x15d2
0xffffffbde7cfbfa0 : 0xffffff801f01f19e mach_kernel : _call_continuation + 0x2e
Process name corresponding to current thread (0xffffff9a474a5540): kernel_task
Boot args: keepsyms=1 debug=0x100 -disable_sidecar_mac -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:
KernelCache slide: 0x000000001ee00000
KernelCache base: 0xffffff801f000000
Kernel slide: 0x000000001ee10000
Kernel text base: 0xffffff801f010000
__HIB text base: 0xffffff801ef00000
System model name: MacBookPro6,2 (Mac-F22586C8)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 11
System uptime in nanoseconds: 15852998425759
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000e6b105709d3
Sleep : 0x00000e5304a8d643 0x000000005297976d 0x00000e4fe3579066
Wake : 0x00000e5329fd2c1f 0x000000005318e6d6 0x00000e53298b480c
Compressor Info: 1% of compressed pages limit (OK) and 1% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff80af14d000 - 0xffffffa0af14d000
. PGZ : 0xffffff80af14d000 - 0xffffff80b014e000
. VM : 0xffffff80b014e000 - 0xffffff857cbb4000
. RO : 0xffffff857cbb4000 - 0xffffff8716480000
. GEN0 : 0xffffff8716480000 - 0xffffff8be2ee6000
. GEN1 : 0xffffff8be2ee6000 - 0xffffff90af94c000
. GEN2 : 0xffffff90af94c000 - 0xffffff957c3b2000
. GEN3 : 0xffffff957c3b2000 - 0xffffff9a48e19000
. DATA : 0xffffff9a48e19000 - 0xffffffa0af14d000
Metadata: 0xffffff808c13d000 - 0xffffff80ac13d000
Bitmaps : 0xffffff80ac13d000 - 0xffffff80af13d000Yes, I also tried this, some time ago: and everything seemed to work, on my MBP11,3, except for the screen brightness controls on the keyboard; so, I wondered if all this could be automated through the OCLP app, also with some form of minimal patching which would allow for working brightness controls. The ideal goal would be to solve all Kepler problems, thus restoring complete functionality (with a fully working root patching): but in the meantime…
Edit: With disabled Kepler dGPU, the MBP11,3 - and possibly also other models - would require brightness and also sleep patches similar to those already working on the MBP8,2 and others: This is a clear and versatile solution. But now the brightness is not regulated and there is no way out of sleep mode. This requires patches similar to those for 5.x and 8.2. Similar patches are needed for 10.2, if NVidia is faulty in it. Please add the ability to apply these patches to such machines. (Source: https://github.com/dortania/OpenCore-Legacy-Patcher/issues/522.)
Last edited:
Just checked again: On MBP8,2 with the disabled dGPU brightness control is still functional, also keyboard backlight. Function keys work correctly in that regard also.
So, as long as there is no patch for 12.5 > beta 2 and OCLP has not been figured out, this NVRAM command is as good as it gets right now... ;-)
It indeed looks like the MBP8,2 already has brightness and sleep mode patches in OCLP (see the link in my previous post), when the dGPU is disabled: ideally, similar patches would have to be added also to the MBP11,3 and others, if the Kepler problem cannot be solved in a reasonable time…
… Another link here (similar patches, if possible, would be required also for the MBP11,3 and other models with disabled dGPU, without relying on workarounds):
https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#no-brightness-control
https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#no-brightness-control
This is interesting.. but what happens then with code that wants to use the Kepler graphics when that dGPU is disabled if I may ask? Like the Photos app. I assume those apps would not work at all?
Last edited:
If you intentionally cut off one foot you are probably forced to limp around. I cannot understand this complete discussion. Go back to 12.4 or better Big Sur, Kepler patching was never 100% working, OpenCL is still broken and on Monterey apps like Photoshop already complain about missing hardware.
You might read the GitHub issue about the complete story (metal patching problem). More complex problem than just adding some older kexts.
I have the same m/c as you, rMBP 10,1 2012. I'm at 12.5 now with OCLP 048 including post install patches of course.
Initially the external monitor was not working via Thunderbolt to DisplayPort and was hanging the system with a black screen followed by a return to the login prompt. So I disconnected it. It boots up and logs in fine now. I'm using screen sharing from my Mac mini 2018 to type this on the rMBP. The dGPU is active, my usual test for this is to startup Sketchup 2017 and check it in Activity Monitor, Energy.
Soooo.... I ordered a Thunderbolt 2 cable and TB2- to TB3 adapter from my local Apple store today so I can boot the rMBP in target disk mode for fast access from the Mac mini (which has only a 256 GB SSD). That way I can use the rMBP's bigger SSD more effectively while things develop around all things Kepler.
On a late 2012 iMac, 13,2 with Kepler/Nvidia GPU, after the update from 12.4 to 12.5 fiasco, I did the following:
What am I doing wrong? and what needs to be done to boot up correctly?
- using OCLP v0.4.9., I created a Monterey version 12.4 installer
- Booted from OCLP and managed to fully erase the SSD, then install Monterey Version 12.4 to the SSD. Including successfully rebooting from the SSD EFI and even applying post install patches. So iMac working perfectly under v12.4
- Then, Using migration assistant., and the time machine backup, migration assistant confirmed a 100% successful restore of the user account and to reboot.
- BUT I can’t get the machine to Boot to the login screen of the user account. It continually never gets past 1/3 of the boot up progress bar, ending with displaying a crash error and the iMac attempts to reboot, only to display the sam error message , rinse and repeat, perpetually
What am I doing wrong? and what needs to be done to boot up correctly?
Sorry to contradict: Kepler patching worked pretty fine until 12.5 beta 3 broke drivers.
We have several machines here running as work horses in our office with 12.4 and Kepler (patched). GT630 do an execellent job, metal apps running fine.
So the current situation is a loss and in no way neglectable as "Kepler was never 100% working".
Still hoping for a fix but I fully understand if focus of devs is somewhere else right now.
No external monitor through miniDP or other interfaces, but external TB GPUs can still be used - with increased effort of hooking up and configuring things correctly, probably again and again after each macOS update...
(Been there, done that).
Read my post again and try to find where I am exactly contradicting the facts, not just your personal evaluation of this situation (which I am not interested to comment on).
Ach komm, Ausdauersportler, verstehe nicht, weshalb hier so auf Krawall gebürstet?
Kepler patches used to work fine*. Period & session closed.
Do not need your reading and comprehension advice, really.
* your turn to bring conclusive evidence to prove otherwise, just slapping in some of your personal musings is not enough.
@BuffyzDead I did exactly the same, no login as a result.
I think it is because of the backup TM restore through migration assistant. I'll try it again, but than only with the user account and apps. and not the last one (forgot how it is called) I think there is something in the TM backup that triggers the same event. Even when you're on 12.4. (and upgraded to 12.5 to find out it's not working ;-) )
Because a clean install with 12.4 is working fine.
You can try to start in safe mode, tried that?
I think it is because of the backup TM restore through migration assistant. I'll try it again, but than only with the user account and apps. and not the last one (forgot how it is called) I think there is something in the TM backup that triggers the same event. Even when you're on 12.4. (and upgraded to 12.5 to find out it's not working ;-) )
Because a clean install with 12.4 is working fine.
You can try to start in safe mode, tried that?
Last edited:
That's exactly what I was thinking. I've also had mixed results with Migration assistant. I solved them by doing another clean install and manual user setup and data restore. Also, maybe try an NVRAM reset at some point. But I'm just guessing here.
Re. restoring the data files, I moved all my data files to iCloud this week. It is making my life a lot easier. I set up 'Projects' folders on both desktops, moved all the data subfolders into them, then specified to store the Desktops in the cloud. Did it on both my production machines. After a clean install and user setup, after logging back in to iCloud I can access everything from either m/c without restoring manually. This greatly simplifies the whole process.
TM gave me so many headaches in the past that I switched to CCC many years ago. Not a single problem till then. You just boot from the cloned, clone again and everything is like before.
Hello rehkram,
I noted your response to my post. I usually recluse myself from "conversations" which enter realm of emotion driven statements. This time, however, "I'll bite", to paraphrase another user.
I have utmost respect for developers, their work is amazing, but it is not dogma. Statements, which developers publish, are often advisories, many directed at people who might be tempted to install untested solutions on mission critical devices. There are participants in this forum with various levels of computer skills and experience, so caution is advisable. Conversely, there are just as many posters on this forum who are well aware of the risks, and take steps needed to protect their data, while providing test beds for developers' programs. Often, that "cooperation" results in discoveries that lead to solutions applicable to everyone. I belong to the latter group.
"Supposition" by its very definition, and as employed in the sentence, equates its meaning to "conspiracy theories", e.g., it's a well intentioned quip. Finally, let me know, which of my posts seemingly contradict statements (within known parameters of non- metal machines), that Monterey 12.5 RC runs perfectly well on the MacBook Pro 5,2 and Monterey 12.5 beta2 runs just as well on (metal compatible) iMac 13,2?
Above all, we are colleagues on this forum.
Last edited: