macOS 12 Monterey on Unsupported Macs Thread

[steverae]

Just got round to installing this latest beta on my 2013 27" iMac along with on my officially supported MacBook. I also installed the latest beta of 15.4 on my iPad M1 pro and tested the universal control feature across all three....

WOW !!! using the OpenCore Legacy Patcher 0.4.1 on my unsupported iMac and this feature works flawlessly .... Have to say I was not expecting this to be so seamless .....

I can now control all three devices from my magic keyboard and trackpad of my iMac as if they were one device with multiple screens ......

This is probably a little off topic here but - since you guys have all helped me on my journey through the Monterey Beta's on my 2013 iMac - I just wanted to share

One thing I've noticed, my 2015 MacBook Pro - doesn't seem to work with UC - might try and install OpenCore on this to try and trick Monterey to think its a more modern MacBook... hadn't realised UC was capped on the 2015 and below models - I'lll let y'all know. how I get on

 

[webg3]

I have "MacBook Pro 13 early 2011" with Intel HD Graphics 3000
I installed clean Monterey 12.2 and I noticed some graphics issues, one example when click right click on Recycle basket it flickers and glitching and this is anoying. Is there any graphics patch/fix to solve this? Also can I increase graphics memory from 512 MB to 1024 or more?

Fix Glitches non-metal GPUs >

 

[maurer]

The artifacts with HD3000 and Monterey have nothing to do with the ammount of RAM of the HD3000. It´s a matter of OpenGL.

I know that doesn't have nothing with that glitch, but also would be great to have more VRAM. I have 16 GB of RAM installed

 

[maurer]

Fix Glitches non-metal GPUs >

Ok tnx, I wil try this

 

[Pri-est]

Has anyone managed to successfully install macOS 12.3 Beta 1 on a cMP?

I think, that nobody lucky. System that gone hang on my CMP 3.1 - is not corrupted, i done a copy to sata SSD (from PCI-SSD) - and complite 2nd stage of install via USB on MacMini 3.1. After system successfully booted to start screen. But no one of CMP (3.1 and 5.1) can't boot in this 12.3B1.

 

[MacToby]

I think, that nobody lucky. System that gone hang on my CMP 3.1 - is not corrupted, i done a copy to sata SSD (from PCI-SSD) - and complite 2nd stage of install via USB on MacMini 3.1. After system successfully booted to start screen. But no one of CMP (3.1 and 5.1) can't boot in this 12.3B1.

Thank you for replying! That's what I thought! I installed the beta on an officially supported Mac on a SATA SSD, then put it back into my cMP. Unsuccessfully though. Boot still with kernel panic…

 

[Shadow Demon]

Thank you for replying! That's what I thought! I installed the beta on an officially supported Mac on a SATA SSD, then put it back into my cMP. Unsuccessfully though. Boot still with kernel panic…

This is what is so great about this thread. With this info, I know to stay well clear of 12.3B until either Apple makes a positive change or OCLP is updated.

 

[fant0mas]

Interesting: Some combination of OCLP (0.3.2n) / Monterey 12.1b1 / root volume patch (Kepler) again rendered DisplayPort unusable... Metal accel works (on DVI), but 2nd screen stays dark. This is on MP3,1 with GK107 GPU (GT630).
The boot args for agdpmod=vit9696 are still active in the EFI config, but to no effect any more.
Any clues, @vit9696 et al?

Hi!

May I ask if you could manage to solve the issue afterwards (didn't find a solution in this thread)?

Got a similar problem with both my DP and HDMI port. While my MBP 10.1 switches to discrete graphics (GT 650M), and my monitor detects something is connected, no signal arrives there.

Adding the boot-arg adgpmod=vit9696 didn't help for me as well - it rather caused my mac to reset during boot, so I removed it again.

Thanks!

Edit: Sorry, forgot to mention that I use Monterey 12.2 and OCLP 0.4.1 with minimal spoofing and applied the post install patch.

 

[macsba]

A little warning here.

If you have Catalina with FileVault turned on you may have booting problems trying to install the latest Monterey beta.

Ref: https://developer.apple.com/documentation/macos-release-notes/macos-12_3-release-notes

 

[Larsvonhier]

Hi!

May I ask if you could manage to solve the issue afterwards (didn't find a solution in this thread)?

Got a similar problem with both my DP and HDMI port. While my MBP 10.1 switches to discrete graphics (GT 650M), and my monitor detects something is connected, no signal arrives there.

Adding the boot-arg adgpmod=vit9696 didn't help for me as well - it rather caused my mac to reset during boot, so I removed it again.

Thanks!

Edit: Sorry, forgot to mention that I use Monterey 12.2 and OCLP 0.4.1 with minimal spoofing and applied the post install patch.

Well, yes. The solution was to post-install patch the Nvidia/Kepler kext via OCLP tool (menu item "patch root volume").
This is necessary from Monterey beta 6 on (if I recall correctly), because Apple left out the drivers from then on.
Recent versions of OCLP do the trick (again), no problem here any more.

 

[K two]

This Apple refurb lives on. ? OTA w/OCLP_042N

 

[eikic1]

This Apple refurb lives on. ? OTA w/OCLP_042N

View attachment 1951347

where download OCLP_042N???
in github latest versio 0.41


can you tell me step by step for upgrade 12.3 beta??
i have a problemm 2x install but stuck Apple LOGO

 

[K two]

where download OCLP_042N???
in github latest versio 0.41


can you tell me step by step for upgrade 12.3 beta??
i have a problemm 2x install but stuck Apple LOGO

Software Update CP offers the OTA if enrolled in Apple Developer Beta Program, here: sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/ Resources/seedutil enroll DeveloperSeed Read thus carefully for OCLP_N: https://github.com/dortania/OpenCore-Legacy-Patcher#readme

 

[Pri-est]

where download OCLP_042N???
in github latest versio 0.41


can you tell me step by step for upgrade 12.3 beta??
i have a problemm 2x install but stuck Apple LOGO

On CMP 12.3B1 unworkable now.

 

[vince22]

A little warning here.

If you have Catalina with FileVault turned on you may have booting problems trying to install the latest Monterey beta.

Ref: https://developer.apple.com/documentation/macos-release-notes/macos-12_3-release-notes

just adding some notes regarding Monterey 12.3 beta, downgrade using the same volume not possible if you plan to go back to 12.2

 

[roysterdoyster]

Same here on MBP4,1:
Found the culprit with 12.3 beta: Somehow, the Skylight Framework is only fixed incompletely for this OS build.
I get constant, CPU hogging crashes of the replay daemon /usr/libexec/replayd due to missing symbol in SkyLight.
Also, interestingly, the CPU seems throttled in addition, only reaching low temperatures while being 100% active with no idle time.

edit: checked back with running Onyx maintenance job, does (of course) not solve the root issue with SkyLight in 12.3

Indeed, Onyx takes almost 20+mins. to complete, which is noticeable. Also, startup times are within the regular range, but until the whole system is ready, it takes several minutes after the login screen. Applications are unresponsive until then, while until 12.2 they loaded fast. But after that, 12.3b is running fast as before.

Is there a way to fix the Skylight Framework according to your findings?

 

[roysterdoyster]

just adding some notes regarding Monterey 12.3 beta, downgrade using the same volume not possible if you plan to go back to 12.2

Confirmed, a clean install is necessary

 

[OllieW]

Some problems I realized after installing Monterey 12.2 release with OCLP 0.4.1 final on my White MacBook 6,1:

• After appliying post-install patches for nVidia graphics card non-Metal acceleration there are graphical glitches in the Control Center sliders for brightness and volume. Activating the "Beta Blur" options in OCLP have no effect and before patching the sliders are displayed correctly.
• Login screen after booting up will show the wrong keyboard layout language although the correct layout is used. Curiously the correct layout is shown on login screen at wakeup from standby.
• Wake up from hibernation (suspend-to-disk) returns to login screen a second time after entering password successfully. After second login sometimes the system freezes/reboots or will take a much longer time and system is slower.

I haven't found any other problems so far - everything else is working! I will test new Monterey 12.3 beta with OCLP 0.4.2 nightly and report back...?

---

More feedback after updating to Monterey 12.3 beta with "sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/" (thanks to @K two for this one) and actual OCLP 0.4.2 beta:

• Graphical glitches in Control Center still there with post-install non-Metal acceleration patch and no improvements even with "defaults write -g ASB_BlurBeta -bool true / defaults write -g ASB_BlurOverride -float 30".
• The whole system is much slower and lagging now - no such behavior before with Monterey 12.2 final release. Perhaps the delta update from 12.2 final to 12.3 beta has some bugs with the OCLP setup?!
• Added some screenshots!

 

[fant0mas]

Well, yes. The solution was to post-install patch the Nvidia/Kepler kext via OCLP tool (menu item "patch root volume").
This is necessary from Monterey beta 6 on (if I recall correctly), because Apple left out the drivers from then on.
Recent versions of OCLP do the trick (again), no problem here any more.

Thank you!
I had done that though, and graphics acceleration, correct scaling etc. is working well - just the external display does not get any signal.

Might it be, that since I use minimal spoofing with OCLP 0.4.1 (rest is default setting), the /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/Info.plist does not include the correct (spoofed?) board ID and thus the DP/HDMI connectors won't work (Edit: the file includes the board ID for my MBP10,1 but seemingly not of 'newer' MBPs)? I read about these entries here: https://github.com/mayankk2308/purge-wrangler/issues/48#issuecomment-619603685
I guess this later led to the approach to disable the board-id checks altogether (-> "vit9696 boot-arg") which didn't have any effect for me though.

I wonder if it is safe to just switch from "minimal spoofing" to the spoofless approach. When I did so the first time (0.3.0->0.3.3), my Mac wouldn't boot anymore, so I reverted to 0.3.0 and just recently gave 0.4.1 a try, but with "minimal spoofing" enabled.

EDIT: Solved the issue finally! It had indeed to do with the board ID check; when checking the config.plist again, I realized that earlier I accidentally didn't set the agdpmod=vit9696 boot-arg properly syntax-wise, thus it didn't work at that time.
Setting it like in the screenshot below solved all issues and external screens are working perfectly again:

 

[xLorak]

I had firmware update bug on unsupported Air 2012 yesterday, but just did image from already running Mac with this version, but today? MacBook Pro 2014 on big sur i had invite to upgrade via system notification, of course update did not shows in center, so i took pendrive with clean 12.2 beta, put to Mac few minutes ago and its in middle of upgrade ?

 

[Larsvonhier]

Indeed, Onyx takes almost 20+mins. to complete, which is noticeable. Also, startup times are within the regular range, but until the whole system is ready, it takes several minutes after the login screen. Applications are unresponsive until then, while until 12.2 they loaded fast. But after that, 12.3b is running fast as before.

Is there a way to fix the Skylight Framework according to your findings?

I´ve just checked to see if 0.4.2N does any good for 12.3b on the MBP4,1.
Unfortunately, not. The replayd keeps crashing, less frequently also mds! - you can check this with console.app
Also, for some reason, the machine stays underclocked (and cool, but slow). Can be seen with iStat Menus i.e.
That is the main reason for sluggishness, and constant crashes and reporting in background do no good here ;-//

edit: Neither "disable CPU friend" nor disabling battery throttling does help to regain full CPU clocking (correct speedstepping)

 

[gw463]

Macpro 3.1 bad news with Monterey 12.3 .... I tried to update via OTA with OCLP 4.1 all right until the first reboot when it crashes and I could not help but reinstall 12.2 ..... at the moment I rest here.

 

[Peter Labaš]

After last nights OCLP Quartz patch as a fix for the rounded corner rendering on NVidia, Montery is now very much as usable on unsupported machines as Big Sur is. (Dropped Wifi support on many machines set aside).

Just the old issue of garbled context menu bottom shadow area and corners there remains...
See screenshot taken on Geforce 320M

yes this problem whether it is solved, thank you for all in OpenCore team. It's a pity that I still haven't found how sensible to get the right support for the NVIDIA GeForce 320M (Mac mini 4.1 (2010)). Even after OpenCore post-install, it still didn't recognize the corresponding * .kext file (GeForce.kext), and it graphics only works on resolution 1080p. Maybe I'm making a mistake, if you can advise, please email me, but based on what I'm reading, the problem is rather with unsupported graphics within OpenCore.

 

[K two]

Upon wake - replayd was crashing repeatedly. Killed the process in the Activity Monitor, successfully. Have yet to reboot. macOS 12.3b1 and OCLP_042NVIDIA. Seems OK other than that. ? Also, not seen in 12.2?️

 

[HowowcanIgo]

12.2 (21D49) ran perfectly on my MBP4,1 Early 2008, while 12.3b seemed significantly slower. However, the post-install patches were successfully applied to the system. I did, like you, NVRAM and SMC reset, to no avail.
I then let Onyx app do a maintenance routine, one task "System integrity check" took 20mins. (2mins. was normal so far), but then the problem was gone.
A fresh install and reverting to the previous macOS that ran perfectly is always something to consider, as long as you have a Time machine backup.

Thanks for the reply Roysterdoyster. I’ve tried a fresh install and got the same result. As I used migration assistant during the install I thought that was the mistake and maybe I should’ve done a complete clean install. Then I tried a few times reinstalling the root patches to no avail.
Turns out I just needed to first uninstall the root patches and then install them again. Man am I glad I tried that function ?.

Thanks again for responding and to the geniuses who created this beautiful tool!

HowowcanIgo