Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Plus also maps crashes as well, Mac mini 5,1 on Monterey 12.5 beta 4 but all of these programs crashed on 12.4 as well. Is a reall shame as with 16gb and ssd this is really really fast, just these bugs which are stopping this from being perfect, all seems gpu related to me as it's non mental and there is no official support for it, although I might be wrong!
I don't really know what I'm doing but with my mac mini 5,1 ( Monterey 12.5 beta 4) I just changed in oclp (4.7) smbios default from off to minimal and rebuilt OpenCore. It's glitchy but Apple TV now plays. However the other 2 affected apps that previously crashed (maps and iMovie) still do crash. But interesting that appletv which refused to ever play on Monterey beta or public release now does work with smbios set to minimal. I don't really understand smbios so whether changing these settings further will assist other apps working?
 
For those that had the log in bug I know this sounds daft but did you try unpatching graphics reboot to log in then try and log in again? I had a bug in earlier versions where I would patch to early rebooting after loggin in normally it would go around 50 % then return to Apple logo to continue installing.
So safe boot remove patch , reboot no safe mode log in and where it stall it reboots to installer.
However install successfully on my MacBook Pro mid 2014 12.5 beta 4 OTA and I’ve even changed the thermal paste to some MX-4 was getting abit hot on the bottom 100% needed it.
 
Last edited:
Trouble with Metal-1 capable card on latest 12.5 beta (build 21G5056b), as also reported in post #6651.
I installed the beta update and my GT630 Nvidia Kepler card was ok as long it was not root-volume patched for the missing Kepler drivers. (Slow and one screen only).
After the patch (with OCLP 0.4.7), the login window still comes up (seems accelerated also), but login goes to eternal re-login screen loop. (Window server thread seems to crash while loading Finder components).

I reverted back to a Terascale2 card and patched for non-metal, which works as a temporary makeshift solution.
Any hints what could be tried (aside from going back to 12.5 beta-3)? Does 0.4.8 nightly help out?
 
  • Like
Reactions: hvds
Hello,
Can anyone advise me which wifi card and adapter I should buy to update my original card from my CMP 3.1 from 2008. Is it the same as for 5.1… you have to have an extension cable? Thanks
 
Hello,
Can anyone advise me which wifi card and adapter I should buy to update my original card from my CMP 3.1 from 2008. Is it the same as for 5.1… you have to have an extension cable? Thanks
You don´t need the extension cable por por the bluetooth part on the 3,1.
 
  • Like
Reactions: JedNZ and 0134168
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).
My 2011 iMac with a Nvidia k4100 card updated to 12.5 beta3 and I am stuck in the boot loop. I tried your tip but it didn't work for me. Any suggestions, to get out of the boot loop?
 
I state that this message is not intended to be a judgment or a controversy, but a friendly advice.

I see a lot of posts refer to problems with the Beta versions of macOS. And it is understood that the users who do these tests are not Developers or advanced Nerds. The result is the crowding of the Forum with useless posts that do not help the development since the Beta of Monterey do not follow linear criteria, as they once did, but can vary a lot and even add or remove services to then get to the final version, finally stable and totally new.

These Betas, moreover, also cause problems for the Macs supported and I remind you that their purpose is only aimed at bringing out incompatibility with the series of numerous Macs but - ESPECIALLY - the Betas are used by Application Developers to adapt and test their Software ! The rest are done by the excellent Apple Engineers and the Betas for Developer have never had a function of reporting bad things in the GUI or noticeable bugs by the Developers, as an Apple external department :)

For a long time I have seen, unfortunately, that many consider the Beta as a "work in progress" that gradually improves and brings them to the final version. I reiterate that this is not the case and if, for example, someone now has graphic loops, it is absolutely not certain that they will have them when the final 12.5 version is ready, which is the one valid for everyone.

In current Betas, Apple often removes some features to test others without interference or for other reasons and in the final version, then, puts everything back in place.
Trying the Betas, therefore, does not provide any real help to the Community and can confuse many inexperienced users who try them expecting who knows what advantages...

I conclude by talking about myself. With macOS 12.4 and OCLP 0.4.7 my Mac lacks nothing and exactly it is as if I had naturally switched from Catalina to Monterey, improving all performance by 110%. So what more do I want? If macOS 12.5 will introduces greater stability and security, I will install it after waiting to make sure no one has had any problems. And by "nobody" I mean not only those with unsupported Macs, but also those with officially supported Macs. As a matter of fact, Apple often had to release a .1 version just a few days after the release of a major release...

So, I repeat without wanting to criticize anyone, I think that keeping calm and waiting patiently benefits physical and mental health of all of us :)
 
Will not work that way unless one starts to provide logs, not complaints. A simple it does not work for me will never be considered as a bug report,
I would LOVE to submit the logs but I remind you that I cannot get past the login screen. No need to respond to this message as I will roll it back to 12.4.
 
  • Like
Reactions: chris1111
I would LOVE to submit the logs but I remind you that I cannot get past the login screen. No need to respond to this message as I will roll it back to 12.4.
Logs should be stored on ur EFI partition so u could mount it in installer and get the logs from there
 
Guys, quick question... Upgrading OTA my MBP 9,2 with OCLP 0.4.7 (as usual) to the latest (21G5056b) Monterey beta, goes flawlessly until applying post root patches, which fail with an "unable to build kernel cache"error:

- Unable to build new kernel cache





Reason for Patch Failure (71):


Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.apple.driver.AppleATAPIStorage' names a dependency on 'com.apple.kpi.libkern', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'com.apple.driver.AppleATAPIStorage' names a dependency on 'com.apple.kpi.libkern', which was not found.}


checking collections...


Warning: com.apple.driver.KextExcludeList was not found!


unable to load existing release kernel collections, forcing rebuild


rebuilding release collections: boot, system


rebuilding release collections:


boot kernel collection


system kext collection


failed to build release collection:


Unable to resolve dependencies: 'com.apple.driver.AppleATAPIStorage' names a dependency on 'com.apple.kpi.libkern', which was not found.

I'm thinking about trying reinstalling with a full Monterey image... any other ideas?

Thanks!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.