Upgraded from Monterey 12.4 to beta 3 with no issues. I was using 0.4.7 and upgraded by joining the official beta. I think people having the issues are the ones upgrading via usb. No problems with official app os upgrade (Mac mini mid 2001 5,1).
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
Thank you for the suggestions.
1. I have wired USB keyboard and bluetooth magic mouse. Mouse works in the installer which I wasn't expecting, but not wifi. Weirdly I even see a mouse cursor pop up on the progress bar loading screen for a minute just before it reboots. I will try with wired mouse or no mouse.
2. Installer drive was made with same OCLP version that internal drive has.
3. Internal SSD is an aftermarket OWC Mercury Electra 6G. Could that be the problem?
4. I have not, didn't notice a smaller EFI icon but I will try again.
I could stop with Big Sur but wanted to test Monterey in case Ventura ends up being the end of the line on this machine.
Are you saying you were able to successfully go to Beta 3 using SU on an iMac 13,2? I have a 13,1 with the same login loop problem.
Hi, as I mentioned on my post, I joined the apple beta and upgraded that way, but I've got a Mac mini 5,1 not iMac 13,2
A 5,1 is back from mid 2011. I have a Mac mini 2009 3,1 I installed Beta 3 on with no problems. I have no idea why the 13,1 iMac from 2012 would not run properly. I'm still on Beta 2 until it's worked out. Or, as I've seen others say, this might be the last update unless it's fixed in a subsequent seed.
Such possibility existed from day one of this venture for everyone participating in this thread.Or a final dead end for whole branch
Still, it would be "disappointing", if totally understandable, if your prediction became a fact.
So I tried the whole process once again this time following Mr Macintosh's new install Monterey video exactly. One part I had missed is installing OCLP to the USB installer EFI. That's why I didn't see the other EFI boot option. Turns out it didn't make any difference, still same problem even when I choose to boot off the USB's EFI.
I realized it's actually rebooting after the automatic 3rd reboot which you can see at this timestamp in the video
I wonder if I can try an older version of OCLP before it had the root patch auto installer.
It was a question a) addressed to RogueB and b) regarding specific Mac model known to have specific problem.
Monterey 12.5 beta4 (21G5056b) released!!!
I reverted back to OCLP 0.4.6
And did this, as suggested by @webg3
> hold the Option key when turning on the system and in the boot selector, choose EFI boot and then hold Ctrl and press Enter to mark as default <
This late 2013 iMac, (14,2), is NOW auto-booting off the EFI of the 2TB SSD.
Perhaps I could have left OCLP 0.4.7 installed, and did webg3's suggestion,
But it is working perfectly now, so I say, leave good alone !
Same problem beta 4 Kepler patch "login screen loop"
For those that may be having a log in loop issue, I encountered this on the beta 3 as well as the latest beta 4 (21G5056b) when I tried to run VMware Fusion and things went haywire. Even booting from OCLP EFI and then another instance of beta 4 was resulting in my boot loop. Only when I cleared the PRAM and proceeded to boot OCLP EFI and then my instance was I out of the login loop and things worked correctly.
Sadly, latest beta does not resolve the issue with VMware Fusion running guests.
Sadly, latest beta does not resolve the issue with VMware Fusion running guests.
Last edited:
iMac 27 "late 2013 and nVidia. Monterey 12.4 and OCLP 0.4.6. Everything works 110%.
Well, now I suspect Apple may be doing something remotely to annoy Macs not officially supported by Monterey!!!
Last night, in fact, I wanted to restore the system with Time Machine. I state that with Monterey 12.3 the restore had worked perfectly.
Yesterday, however, after selecting the Backup that I wanted to restore and starting the Monterey Installer (as required by the new restore method) the Installer said that it needed various important files that at that moment are not could download from Apple!!! (???)
I wll try again to see what happens with a “minimal” OCLP spoofing, but it's still weird.
That would be an alarm… DO YOU HAVE any solution?... For example, first download the Installer and leave it in /Applications?...
Obviously I know that I could use a USB Key with Installer to boot…, but I was very happy because by now my Mac was behaving 110% better than when I was using Catalina... (which I have on other smaller internal SSD to use with the new updates that update the Firmware)
A good weekend to all
Well, now I suspect Apple may be doing something remotely to annoy Macs not officially supported by Monterey!!!
Last night, in fact, I wanted to restore the system with Time Machine. I state that with Monterey 12.3 the restore had worked perfectly.
Yesterday, however, after selecting the Backup that I wanted to restore and starting the Monterey Installer (as required by the new restore method) the Installer said that it needed various important files that at that moment are not could download from Apple!!! (???)
I wll try again to see what happens with a “minimal” OCLP spoofing, but it's still weird.
That would be an alarm… DO YOU HAVE any solution?... For example, first download the Installer and leave it in /Applications?...
Obviously I know that I could use a USB Key with Installer to boot…, but I was very happy because by now my Mac was behaving 110% better than when I was using Catalina... (which I have on other smaller internal SSD to use with the new updates that update the Firmware)
A good weekend to all
Interesting I signed up to the beta on Mac mini 5,1 and got beta 3 via the updater but beta 4 isn't showing up, says I'm up to date!
try taking a slo-mo video with your phone?
ETA nevermind i see you caught it on video
That was Mr Macintosh's video.
Here's what I was able to capture in the last few seconds before it reboots. The 4th image is the last thing I can see. In the second image it says "Killing all processes" which I don't know if that means it was supposed to shut down or if it shut down because of an error.
I wonder if maybe a shutdown was initiated sometime before this and the actual error happened earlier.
This is happening during first attempted boot into Monterey after installer has completed, but before root patches auto install themselves.
Edit: Added more images in correct order
Attachments
Last edited:
Yep my upgrade to beta 4 actually went more smoothly than beta 3. No issues at all with 0 4.7
Sorry! I've got a Mac mini 5,1. Upgraded from beta 3 to beta 4 using open core legacy 0 .4.7. I've signed up to the official update program. I'm running 16gb memory and Samsung Evo 870 SSD.May be, it's time to place your configuration in signature?
You propose to remember all this by heart or get back to this comment every time someone needs to know your config?
Why not put it to signature, really?Just added my hardware now, just hadn't got round to it yetYou propose to remember all this by heart or get back to this comment every time someone needs to know your config?
Hello to all,
I installed the 12.5 beta 4 onto my iMac 13,2 which, as others have also reported, resulted in login-loop identical to the one seen with 12.5 beta3 installation.
The common thread among Macs, which fail to fully boot and get "caught" in login-loop, is presence of the Nvidia Kepler graphic card.
I scanned the web for similar occurrences (boot loop) with Nvidia cards and found that to be a problem with other operating systems, e.g. Ubuntu (Linux), notably when the latter is updated. The commonality there was loss of Nvidia cards "ability" to find their drivers and / or presence of a secondary Intel Graphic Card or drivers. The final result was a boot-loop very much like iMacs'. There was a proposed solution, to modify some boot parameters, but it applied to window system and terminal commands evoked do not seem to have Mac OS equivalents.
However, when I looked at the screen output from OCLP patch 0.4.8n installation, I noted that patch seems to install Kepler Drivers, as well as drivers for "graphics Intel Ivy bridge" cards. While above correlations are tenuous at best, would it be possible to remove (or Block) Intel driver installation from the Volume Patcher (when used in iMacs with Kepler); that would result in Kepler drivers installation only. It is possible that in the past two betas, Apple changed how graphic drivers are "called" during boot process.
One more data point: while enabling "auto login" in system preferences does not seem to prevent login-screen looping, the command listed below did work on my machine (to bypass login screen), when executed form Safe Boot via terminal.
Command: defaults write /Library/Preferences/com.apple.loginwindow "autoLoginUser" 'username'
Replace 'username' space holder in above command with an actual user name used to login into the computer (omit quotation marks, e.g, drakes and not 'drakes'). Do keep quotations around "autoLoginUser".
When booting after executing the "auto-login command", computer progress stalls at the near end of progress bar, screen turns gray, and fans go to maximum. It is reminiscent of kernel panic. Shutting down the computer is the only viable way to leave the "grey screen of computer panic(?)".
Hope this may be of help.
One more data point: Installed Monterey 12.5 beta3 on MacBook Pro 5,2 (2009) without a problem; machine is fully operational, including graphic acceleration (used OCLP version 0.4.8n).
I installed the 12.5 beta 4 onto my iMac 13,2 which, as others have also reported, resulted in login-loop identical to the one seen with 12.5 beta3 installation.
The common thread among Macs, which fail to fully boot and get "caught" in login-loop, is presence of the Nvidia Kepler graphic card.
I scanned the web for similar occurrences (boot loop) with Nvidia cards and found that to be a problem with other operating systems, e.g. Ubuntu (Linux), notably when the latter is updated. The commonality there was loss of Nvidia cards "ability" to find their drivers and / or presence of a secondary Intel Graphic Card or drivers. The final result was a boot-loop very much like iMacs'. There was a proposed solution, to modify some boot parameters, but it applied to window system and terminal commands evoked do not seem to have Mac OS equivalents.
However, when I looked at the screen output from OCLP patch 0.4.8n installation, I noted that patch seems to install Kepler Drivers, as well as drivers for "graphics Intel Ivy bridge" cards. While above correlations are tenuous at best, would it be possible to remove (or Block) Intel driver installation from the Volume Patcher (when used in iMacs with Kepler); that would result in Kepler drivers installation only. It is possible that in the past two betas, Apple changed how graphic drivers are "called" during boot process.
One more data point: while enabling "auto login" in system preferences does not seem to prevent login-screen looping, the command listed below did work on my machine (to bypass login screen), when executed form Safe Boot via terminal.
Command: defaults write /Library/Preferences/com.apple.loginwindow "autoLoginUser" 'username'
Replace 'username' space holder in above command with an actual user name used to login into the computer (omit quotation marks, e.g, drakes and not 'drakes'). Do keep quotations around "autoLoginUser".
When booting after executing the "auto-login command", computer progress stalls at the near end of progress bar, screen turns gray, and fans go to maximum. It is reminiscent of kernel panic. Shutting down the computer is the only viable way to leave the "grey screen of computer panic(?)".
Hope this may be of help.
One more data point: Installed Monterey 12.5 beta3 on MacBook Pro 5,2 (2009) without a problem; machine is fully operational, including graphic acceleration (used OCLP version 0.4.8n).
Last edited:
