Sidebar Sidebar
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

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.
MacHosehead said:
The only thing I can confirm is that the Apple BCM94360CD card included with this product works in my MacPro3,1 with Monterey and OCLP. I cannot confirm that the adapter that goes with it works well for both wifi and bluetooth but it looks like it should. It's only suspicious that the 3,1 wasn't in the list as compatible.
Click to expand...
Thanks :)
 
Reading comments in other posts on this website even m1 macs having issues on beta 5 then again it is a beta who knew there would be issues
 
Mystere65 said:
After twice the finder no longer launches from the dock, so for the recycle bin and the shutdown command in the top bar ...
Click to expand...
I have Monterey 12.5 beta5 installed on MacBook Pro 5,2 (2009).
I can confirm finder problems that were not present in beta4 release.

Problems emptying trash; re-launching finder via Force Quit command (in drop down menu under the Apple icon) fixed the issue.

Key combination to launch new window in FireFox does not work, however, using track-pad (or mouse(?)) and manually slecting new window command from Firefox menu does work.

No issues noted when launching programs from the dock.

Hope above information may be of help.
 
  • Like
Reactions: Larsvonhier and macinfo
TOM1211 said:
Reading comments in other posts on this website even m1 macs having issues on beta 5 then again it is a beta who knew there would be issues
Click to expand...
Hello TOM1211,

No doubt that there are bound to be issues with most betas, but sharing information allows users to determine whether problem is related to their specific setup, or to all machines in general. Some "gremlins" have "fixes" any user can apply, once someone posts a solution.

Problems which persist through multiple betas, and are hardware specific, e.g. Kepler graphic cards, require developer level (OCLP) intervention, if a solution is even available.
 
Hi guys! Hope you all are having a good day! I observed one interesting thing about my cMP4,1->5,1: 90% of my freezing episodes happen when I'm not using the machine. I thought about some energy feature or screen saving... so I did all I could to disable sleep and choose the lightest screen saver... nothing worked... That episode when my mac booted without any USB or BT (and appeared to be more stable) made me think some kext used to enable these hardware was the cause. But today my machine hadn't any freeze! My ethernet cable was disconnected all the day...
Someone can relate similar scenario?

I'm using OCLP 0.4.7 and Monterey 12.4.
 
Last edited:
RogueB said:
Hello to all,

Attempted to Install Monterey 12.5 beta5 on 27” iMac 13,2 - late 2012, 1 TB fusion drive , 24 GB Ram,
NVIDIA GeForce GTX 680MX 2 GB.

An OTA Update installed without any problems, as have betas 3 and 4 before, but just as the latter, it stalled in a loop at final Login Window.

I booted into Safe Mode to try and retrieve logs from the OCLP EFI partition, *by any means”, realizing, that under normal circumstances it is not possible to mount EFI partition in Safe Mode(?)

Just a side note: macOS install log is always(?) located on the target drive in /var/log/install.log per some reliable resources. I will try to install next 12.5 beta(6?), boot into safe mode, and see if logs are retrievable from location noted above, rather than EFI partition (assuming that OCLP keeps its own logs?) and compare data from both.

In case of iMac 13,2 , Apple seems to have “banned” certain Kepler Nvidia cards(?)


In contrast, installation of Monterey 12.5 beta5 on MacBook Pro 5,2 (2009) with Nvidia Ge Force 9600 GT 512 MB, went without a problem; machine is fully functional.

Hope this information may be of help.
Click to expand...
the issue with the keplar based Nvidia cards and any beta after 12.5 beta 2 is well known especially on the 13,1 13,2 iMacs. We will have to wait until the dev team fix this issue in a later version of OCLP. Until then it is recommended to stay on 12.5 beta 2.
 
  • Like
Reactions: Vacusuck, RogueB, MacRumors3590 and 1 other person
Hey guys I have a MacBook 5,1 with what I believe is the BRCM2046 wifi card. I’m running Monterey and the latest OCLP. For some reason whenever I wake up my laptop my wifi stops working, no networks show up or anything. However if I reboot or turn the laptop all the way off and on again it starts working again? Anyone know a fix for this?(if there is one) thanks
 
steverae said:
the issue with the keplar based Nvidia cards and any beta after 12.5 beta 2 is well known especially on the 13,1 13,2 iMacs. We will have to wait until the dev team fix this issue in a later version of OCLP. Until then it is recommended to stay on 12.5 beta 2.
Click to expand...
Hello steverae,

I concur with your assessment that 12.5 beta2 is currently the latest stable release of Monterey 12.5 for iMacs 13,1 and 13,2; it is near self evident, after series of posts from multiple individuals.

While there is an element of hope for serendipitous resolution (extremely low odds) I am also prompted by requests put forth by @Ausdauersportler in posts 6691, and 6695, the latter in particular (https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-31228770).
Getting logs from affected machines seems to be an imperative rather than casual exercise. My iMac 13,2 is dual boot enabled (the Macbook Pro is triple boot), where Monterey is an experimental partition. In order to secure logs it is necessary to try and install the failing beta and then access logs OCLP developers may need to solve the problem(s).
The question remains which logs in particular are of interest to the OCLP group.

Hope above information may be of help.
 
Last edited:
Ausdauersportler said:
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,
Click to expand...
Please elaborate, which logs in particular may be of help to developers(?)
Thanks for your insight.
 
herrdude said:
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?
Click to expand...
This is indeed late reply, but as you have already discovered there is currently no viable way to bypass the login loop. The command I used to bypass login window was an attempt to check whether fault was centered just around login window function, or had a much greater reach; machine bypasses login widow but still fails to boot.
It would seem whoever at Apple made changes, which rendered Kepler cards "in-viable", build in an error trap that bring user back to login window, rather than just freeze the computer (?)
 
Last edited:
il-rollino said:
Hey everyone,
I just want to report the successful installation of Monterey 12.3 b2 on my MBPr 10,1. Since I use it especially in clamshell mode, I did not expect the desktop to show up in external monitor right after the update, because I thought the graphic drivers would be missing prior to patching the system with OCLP. Instead, it did, without graphic acceleration i guess (no transparencies, very laggy performances) but that was just good enough to let me apply the post install patches, reboot, and have back the fully functioning OS. Also, the boot picker did show up a very few times while in clamshell mode before the last updates (monterey and OCLP), but now it shows up every time. Yay!
Thanks for the splendid work the developers did, to let us still use our old but gold hardware.
Click to expand...
I'd be very grateful if you could confirm your settings for OCLP as i'm unable to get the installer to run - it says "This copy of the install macOS Monterey application is damaged"
 
laertemeira said:
90% of my freezing episodes happen when I'm not using the machine
Click to expand...
So you come back to frozen screen or black screen that doesn't wake up? If I was to guess I would suspect a memory issue? I don't know if mixing memory types could cause this? The GPU I would think less likely to matter but you could try a swap with the original card. I have the same upgraded machine running the same versions of software and I don't see these issues. It is at a location right now where I can connect with ethernet or wireless and it works about the same.

I have changed the GPU in my other MacPro, which is a 3,1, to a Sapphire RX 570 4GB. I can run Monterey now without root patches. I suppose I will have to swap back if I want to run High Sierra. It's ready for Ventura whenever that happens.
 
Weird issue just started to occur with 12.5 Beta (21G5063a) - any subfolder on the doc (whether it be Documents or Downloads with "fan" view is now resulting in a Finder message - "The application Finder can't be opened. -609". I've restarted but that did not fix it. I am able to open New Finder Window under File of Finder and navigate to the folders without issue. Any suggestions? This is the first time with these betas that I've run into this.
 
MacHosehead said:
So you come back to frozen screen or black screen that doesn't wake up? If I was to guess I would suspect a memory issue? I don't know if mixing memory types could cause this? The GPU I would think less likely to matter but you could try a swap with the original card. I have the same upgraded machine running the same versions of software and I don't see these issues. It is at a location right now where I can connect with ethernet or wireless and it works about the same.

I have changed the GPU in my other MacPro, which is a 3,1, to a Sapphire RX 570 4GB. I can run Monterey now without root patches. I suppose I will have to swap back if I want to run High Sierra. It's ready for Ventura whenever that happens.
Click to expand...
Hi @MacHosehead! When Monterey freezes I need to reboot holding power button. So, the system restarts and I have a message telling me about reboot by failure and a error log. Disconnecting Ethernet kept machine running without no one failure happened in a whole day. I was reading the earliest posts about Monterey and mac pro Ethernet problems. I wonder if the solution used to bring Ethernet working can be responsible for my system freezes. Or maybe some executable that runs only with network/internet connection may cause the freezes too...
 
Last edited:
cab_007 said:
Weird issue just started to occur with 12.5 Beta (21G5063a) - any subfolder on the doc (whether it be Documents or Downloads with "fan" view is now resulting in a Finder message - "The application Finder can't be opened. -609". I've restarted but that did not fix it. I am able to open New Finder Window under File of Finder and navigate to the folders without issue. Any suggestions? This is the first time with these betas that I've run into this.
Click to expand...
These are System issues and although your Mac is not officially supported it would be useful to report it to Apple through the Feedback Assistant utility. Generally they take into account as these errors are a signal of issues in the code that is better to solve. [I think 🤔 :) ]
 
  • Like
Reactions: Larsvonhier and cab_007
OKonnel said:
These are System issues and although your Mac is not officially supported it would be useful to report it to Apple through the Feedback Assistant utility. Generally they take into account as these errors are a signal of issues in the code that is better to solve. [I think 🤔 :) ]
Click to expand...
Thanks and I was able to remedy it by simply killing Finder process, it automatically restarted and dock functionality for opening Documents/Downloads (via Fan view) are now working again :)
 
  • Like
Reactions: RogueB
RogueB said:
Problems emptying trash; re-launching finder via Force Quit command (in drop down menu under the Apple icon) fixed the issue.

Key combination to launch new window in FireFox does not work, however, using track-pad (or mouse(?)) and manually slecting new window command from Firefox menu does work.

No issues noted when launching programs from the dock.
Click to expand...
I can also confirm these errors (despite the FireFox problems - the key combination still opens a new window) on my White MacBook (MacBook6,1) with latest OCLP 0.4.8n after upgrading to macOS 12.5 Beta 5. I will cross-check with my official Monterey supported MacBook Pro 15 (Late 2016), but I guess it's an OS-specific bug in the new beta (at least it's not a problem with the post-install patches for Nvidia Tesla Non-Metal acceleration - it's the same behaviour without installing them!).

Forcing Finder restart will fix the problem temporarily, but the bug returns (also the "The application Finder can't be opened. -609") after some minutes.

I also realised the the new macOS 12.5 beta 5 really speeded up video playback in Safari using Non-Metal acceleration - that's a huge step forward! A first test with the new technology preview release 148 of Safari 16.0 is also running very smooth on the late-2009 White MacBook.. ;)
 
Last edited:
  • Like
Reactions: Larsvonhier, RogueB, TOM1211 and 2 others
roscho said:
Not sure if this is the right place, but as my issue started with upgrading to monterey...

I have an imac mid 2011 with a WX7100 MXM card running Monterey 12.3 and OCLP/OC0.8.1.

Before I was using a Sonnet Solo10G PCIe Card flawlessly in a TB1 enclosure (Atto Thunderlink).

After upgrading to Monterey, the card is no longer recognized as an ethernet card upon start and after poering off and on again either it is detected but does not receive an IP or the system freezes.

Neither manual Aquantia patches nor the new OC Kernel Quirk changes something.
IORegistryExplorer does not list AppleVTD. As I don't have a hackintosh, I cant't activate VT-d in Bios either...

Ideas anyone?

Is it due to Thunderbolt? Internal Aquantia cards seem to work in MP with OC?

Best regards,

r.

EDIT: Upgrade to OCLP 0.4.5 and Monterey 12.4 went flawlessly, but Aquantia ethernet still "broken"...
Click to expand...
Right now I have a dualboot System because I got the Aquantia card working in 12.2 but in 12.3 or 12.4 it won't do its job. Can I somehow find out why it is working in 12.2?

I had to add the following patch to the config to get it working in 12.2

<dict>
<key>Arch</key>
<string>Any</string>
<key>Base</key>
<string></string>
<key>Comment</key>
<string>AQC 107 10 GbE v2</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>
D4TAAgAA
</data>
<key>Identifier</key>
<string>com.apple.driver.AppleEthernetAquantiaAqtion</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data>
</data>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>Replace</key>
<data>
Zg8fRAAA
</data>
<key>ReplaceMask</key>
<data>
</data>
<key>Skip</key>
<integer>0</integer>
</dict>
Click to expand...

PS: Cards with the AQC-107S chipset (like Sonnet Solo10G PCIe) seem to work.
https://discussions.apple.com/thread/253782051
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back