macOS 12 Monterey on Unsupported Macs Thread

[georgeimac]

Went ahead and did the upgrade to 0.4.10 and Monterey 12.5.
1. Ran into trouble.
2. Got the loop error.
3. Couldn't get back into OS.
4. Went to Mr Macintosh videos and reviewed some issues with metal upgrades.
5. Got the idea to boot-up in safe mode (held down shift key at start-up)
6. Opened 0.4.10 in safe mode
7. Went to Developer settings/Set GPU model for MXM Mac/clicked drop down menu for Kepler
8. Ran post install patches
9. Rebooted system
10. Ran OCLP 0.4.10, built and installed open core with new settings.
11. It's Working!

Pretty stable all day. Thank you Mr. Macintosh for the idea to boot up in safe mode.

 

[rehkram]

I had to reinstall 12.5 from an installer usb drive with OCLP on it but it was worth it!! External monitor wired TB2>DisplayPort is now working perfectly.

For the sake of documentation the first attempt failed; since I already had Monterey 12.5 installed I just downloaded and updated OCLP to 0.4.10. It didn't work, login loop as before when external monitor attached.

Many thanks to the OCLP devs, great job!

 

[OKonnel]

…omissis… For the sake of documentation the first attempt failed; since I already had Monterey 12.5 installed I just downloaded and updated OCLP to 0.4.10. It didn't work, login loop as before when external monitor attached. Many thanks to the OCLP devs, great job!

I confirm that the first attempt caused the login screen to loop for me too.
In my case I solved it perfectly by installing macOS 12.5 via USB stick.

Reading what happened to you even though you proceeded normally, I add this two note.

[Note 1: If it helps Developers to understand a possible problem, so far I had always preceded - successfully - every installation of a new OCLP release with the installation of corresponding “AutoPkg-Assets.pkg”, without ever having problems. But in this case, I got the Login loop instead]

[Note 2: I know it is useless to install “AutoPkg-Assets.pkg manually!…, But saying about the issue can be used to focus the attention of the Developers on something to be solved]

 

[Ausdauersportler]

I confirm that the first attempt caused the login screen to loop for me too.
In my case I solved it perfectly by installing macOS 12.5 via USB stick.

Reading what happened to you even though you proceeded normally, I add this two note.

[Note 1: If it helps Developers to understand a possible problem, so far I had always preceded - successfully - every installation of a new OCLP release with the installation of corresponding “AutoPkg-Assets.pkg”, without ever having problems. But in this case, I got the Login loop instead]

[Note 2: I know it is useless to install “AutoPkg-Assets.pkg manually!…, But saying about the issue can be used to focus the attention of the Developers on something to be solved]

From what I have read in the docs and GitHub issues this behavior (login loop) is well known since September last year when Beta 7 dropped Kepler support.

You need either to boot into save mode with Kepler machines to install the patches needed or you can (for some months now) use the auto patching feature.

Guess there is nothing more to be noticed on the developers side - having no supported/accelerated dGPU on an iMac gives you either a black login screen or crashes when acceleration is demanded. The internal screen needs an accelerated dGPU to work in normal mode, it is as simple than that, and I guess it is a valid assumption for all iMac models having a dGPU installed (having spent some years on testing new dGPU in modular iMacs). The hardware is simply built in this way.

Even the Monterey section of the OCLP docs has already a paragraph explaining the situation and the work around (safe mode boot patching). One could of course claim that iMacs are not explicitly mentioned there.

 

[Sven G]

@khronokernel Mykola and anyone else who helped him deserve the MacRumOscar and the MacRumNobel! 😀
Thankful very much!

MacRumors Oscar immediately (really great job, with Kepler on 12.5): and MacRumors Nobel when the other “big” bug will be solved, i.e. the OpenCL one - not easy and maybe even impossible, who knows, but anyway…?!

 

[uygar]

Hi,

I installed yesterday Monterey with the latest Version of OCLP on my iMac 21’5 late 2013. Everything works but the internal speaker doesn’t. The boot sound works. The speakers ain’t shown up in the audio menu for “output”, ist just say “digital putput

Please help

 

[houser]

Hi,

I installed yesterday Monterey with the latest Version of OCLP on my iMac 21’5 late 2013. Everything works but the internal speaker doesn’t. The boot sound works. The speakers ain’t shown up in the audio menu for “output”, ist just say “digital putput

Please help

That might be the classic issue with dirt in the audio output. Seen it a few times. Possibly/probably not OCLP related.
Plug and unplug a connector a few times, blow it clean?

 

[ray308]

Working 12.5 on an iMac14,2 with version 0.4.10. (restoring from TM backup with migration assistant stops the show, so build it up from scratch.)

Only issue this moment, when the screen is black long enough, it doesn't come up again, need to hard reboot. (Sleep is not enabled when the screen goes black)

 

[coolio2004]

Working 12.5 on an iMac14,2 with version 0.4.10. (restoring from TM backup with migration assistant stops the show, so build it up from scratch.)

Only issue this moment, when the screen is black long enough, it doesn't come up again, need to hard reboot. (Sleep is not enabled when the screen goes black)

This happened to me with a supported MacMini as well.

 

[rehkram]

Mine's sleeping and waking up OK, even when the screen is black

 

[uygar]

That might be the classic issue with dirt in the audio output. Seen it a few times. Possibly/probably not OCLP related.
Plug and unplug a connector a few times, blow it clean?

Didnt help. I am getting mad. The internal speakers are not shown. I also don’t think that it is oclp related. Tried some resets, but didn’t help. Anyone an idea?

 

[XLN82]

I'm screaming for help guys....
unfortunately my Mac 11,3 updated to Ventura... I decided to do a backup with time machine, I restored it with migration assistant and now I'm facing the problem the Mac is not booting anymore, not normal, nor safe.
Here a screenshot of the verbose.
Thanks

 

[Larsvonhier]

From what I have read in the docs and GitHub issues this behavior (login loop) is well known since September last year when Beta 7 dropped Kepler support.

You need either to boot into save mode with Kepler machines to install the patches needed or you can (for some months now) use the auto patching feature.

Guess there is nothing more to be noticed on the developers side - having no supported/accelerated dGPU on an iMac gives you either a black login screen or crashes when acceleration is demanded. The internal screen needs an accelerated dGPU to work in normal mode, it is as simple than that, and I guess it is a valid assumption for all iMac models having a dGPU installed (having spent some years on testing new dGPU in modular iMacs). The hardware is simply built in this way.

Even the Monterey section of the OCLP docs has already a paragraph explaining the situation and the work around (safe mode boot patching). One could of course claim that iMacs are not explicitly mentioned there.

I stand to correct: When Apple dropped Keppler support last year, the effect was that you ended up without acceleration and no picture on a 2nd screen (attached via DP), but you could still log in (obviously). Initially, there was no solution for acceleration, but the devs were quick in finding that previous Nvidia / metal kexts could be re-applied and solved the issue until 12.5 beta 3, where we encountered this type of log-in loop for the first time.

 

[gw463]

I couldn't resist and upgraded my old MacPro 3.1 with Nvidia Gtx 680 to Monterey 12.5 with OCLP 0.4.10. Everything perfectly ok and thanks to the developers for this incredible step forward .... good job

 

[Ausdauersportler]

I stand to correct: When Apple dropped Keppler support last year, the effect was that you ended up without acceleration and no picture on a 2nd screen (attached via DP), but you could still log in (obviously). Initially, there was no solution for acceleration, but the devs were quick in finding that previous Nvidia / metal kexts could be re-applied and solved the issue until 12.5 beta 3, where we encountered this type of log-in loop for the first time.

No, this is wrong, again! Read my post and the documentation I quoted the before you post. The login loop happened already the back in September and was visible immediately on those MacBooks. What has changed recently: Now are iMacs affected, too (for different technical reason).

But if you would have spent some more attention on this topic and some time on helping users to overcome this particular login-loop you would have noticed it long ago.

 

[OKonnel]

I'm screaming for help guys....
unfortunately my Mac 11,3 updated to Ventura... I decided to do a backup with time machine, I restored it with migration assistant and now I'm facing the problem the Mac is not booting anymore, not normal, nor safe.
Here a screenshot of the verbose.
Thanks

Unfortunately, you have been imprudent, as Khronokernel & C have dedicated a page to explain the great difficulties that exist with Ventura in unsupported Macs and have also warned of the risk of blocking them.
The most serious way to proceed now is via USB Key with macOS 12.5 installer and the latest OCLP.
At the end of the installation, you have to restart OCLP and do the Post Install Patch.
If the Mac has started working fine again, at this point you have to restore the Internal Accounts and manually copy all your data from the last Time Machine backup.
Obviously you will have to reinstall those Applications that it is not enough to copy (e.g. Adobe Acrobat, Photoshop, etc.)
Before proceeding, it would be a good idea to clear the NVRAM.
At startup (Gong) hold down the CMD+ALT+P+R keys until you hear the sound of the Gong a couple of times.
You can also do it via OCLP by pressing the space bar as soon as you see the HD icon, so that the various choices appear, then you have to click on the Reset NVRAM icon.
I wish you everything goes well.

 

[Larsvonhier]

No, this is wrong, again! Read my post and the documentation I quoted the before you post. The login loop happened already the back in September and was visible immediately on those MacBooks. What has changed recently: Now are iMacs affected, too (for different technical reason).

But if you would have spent some more attention on this topic and some time on helping users to overcome this particular login-loop you would have noticed it long ago.

I can only report back what the situation is and was on Mac Pro equipped with Kepler cards (because I actually run several of them and supplied hands-on info). Pls. take it as a field report. No need for me to dig into old documents that I (or you) might interpret in a wrong/inaccurate fashion.
As for "would have spent some time ... helping other users". Have you not noticed that one of the first crash dumps and boot logs came from me, after others were not able to supply them? And that in a situation when new issue reporting was halted on GitHub and we have not been sure if the login loop was even on the radar of the main devs?

 

[Afro_]

Went ahead and did the upgrade to 0.4.10 and Monterey 12.5.
1. Ran into trouble.
2. Got the loop error.
3. Couldn't get back into OS.
4. Went to Mr Macintosh videos and reviewed some issues with metal upgrades.
5. Got the idea to boot-up in safe mode (held down shift key at start-up)
6. Opened 0.4.10 in safe mode
7. Went to Developer settings/Set GPU model for MXM Mac/clicked drop down menu for Kepler
8. Ran post install patches
9. Rebooted system
10. Ran OCLP 0.4.10, built and installed open core with new settings.
11. It's Working!

Pretty stable all day. Thank you Mr. Macintosh for the idea to boot up in safe mode.

Hi, did you do an OTA upgrade from 12.4 or a clean 12.5 install through a USB?

 

[pandacat]

This question is solved

 

[makra]

No, this is wrong, again! Read my post and the documentation I quoted the before you post. The login loop happened already the back in September and was visible immediately on those MacBooks. What has changed recently: Now are iMacs affected, too (for different technical reason).

But if you would have spent some more attention on this topic and some time on helping users to overcome this particular login-loop you would have noticed it long ago.

But my MBP 9,1 worked flawlessly until 12.5... 🤔

 

[Ausdauersportler]

But my MBP 9,1 worked flawlessly until 12.5... 🤔

Different model! And I have never denied this, so what is your point here?

The login loop is not the or a new problem, it is just a symptom caused by lacking Kepler support. The symptom is well known for more than a year (from this particular different model only noticed by a small fraction of users and developers, there is even a solution safe mode boot) and this is the only thing I wanted to point out.

One cannot make this symptom go away after initial installation (Apple provides the installer packages). You have to apply the (new) OCLP post install patches. Unfortunately (now with 12.5) all users of Kepler systems face this particular nasty symptom, and now all these users will have to rely on auto patching or safe mode boot & patching. Get used to it.

Have you read my response to @OKonnel? Have you checked the docs I quoted? It is only about the particular symptom and how to take care of it before having the post install patches applied.

 

[OKonnel]

Different model! And I have never denied this, so what is your point here?

The login loop is not the or a new problem, it is just a symptom caused by lacking Kepler support. The symptom is well known for more than a year (from this particular different model only noticed by a small fraction of users and developers, there is even a solution safe mode boot) and this is the only thing I wanted to point out.

One cannot make this symptom go away after initial installation (Apple provides the installer packages). You have to apply the (new) OCLP post install patches. Unfortunately (now with 12.5) all users of Kepler systems face this particular nasty symptom, and now all these users will have to rely on auto patching or safe mode boot & patching. Get used to it.

Have you read my response to @OKonnel? Have you checked the docs I quoted? It is only about the particular symptom and how to take care of it before having the post install patches applied.

Great explanation, @Ausdauersportler! It is a good help to understand better.
However, I installed macOS 12.5 with a USB stick (OCLP 0.4.10) and the installation was successful, allowing me to access my Home directly.
After that I installed the Post Install Patch.
So in my case it wasn't necessary to boot into Safe Mode to get through the Login loop; but perhaps, again in my case, it could have had a positive impact that (mistakenly, I know...) I first manually installed "AutoPkg-Assets.pkg" by OCLP 0.4.10 whose presence in the System (perhaps...) has avoided the Login loop (Loop had, instead, by the user above).
In short, as you say, those of us who have Macs with Kepler series cards now have to resign ourselves to having some more hassle.
A warm greeting

 

[makra]

Different model! And I have never denied this, so what is your point here?

Sorry, I thought, all Kepler MBPs were affected. I'll do some more reading then.

 

[Ausdauersportler]

Sorry, I thought, all Kepler MBPs were affected. I'll do some more reading then.

Honestly I do not know the complete current status. Back in the past it was only the MBP11,3. This caused so much traffic on the Discord that the solution made it finally to the OCLP docs.

Would be nice if all you guys post from time to time your new update experiences.

 

[il-rollino]

So in my case it wasn't necessary to boot into Safe Mode to get through the Login loop

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.