macOS 12 Monterey on Unsupported Macs Thread

[SEJU]

I'm installing Monterey on an NVMe ssd on my 2012 5,1 Mac Pro. It's currently looping through the installer. I think I saw a fix for this a while ago, but can't find it in the thread. I think I'll just move the installer to an m.2 external SSD enclosure and finish with my 2015 MacBook Pro?

I might be off-road, but when I did the fresh install of Monterey on my upgraded iMac 2011, I had the installer rebooting about 7 times: installer install progress screen > reboot? > install continuation load screen > reboot > load screen > reboot > load screen > ... and so on, before getting to the login screen. I saw a new load screen between 5 to 7 times. Do you refer to this? At the end everything appears to have worked out. Maybe you have the same situation and just have to sit it out?

 

[Ausdauersportler]

After solving the benchmark issue I would like to troubleshoot hopefully the last thing I encountered upon my path of upgrading this 2011 iMac. Yesterday, when writing my post about the strange benchmarking values, the UI froze and displayed a strange yellow pattern. I could still move the mouse, music continued playing, but the UI had become non responsive. I had to press the power button to force a restart.

View attachment 2122718

After that the computer worked. After some time, when rerunning the benchmarks, the same thing happened, but with a blue pattern.

View attachment 2122717

After a force restart everything worked without issues for several hours until I shut the computer down.

This morning, when turning the computer on, for 5-6 times I had the same experience: the blue pattern appeared and the UI froze almost immediately after login into the system.

What does this depend on (GPU, Monterey, OCLP, an app misbehaving?) and how could I solve this?

It is currently only Monterey 12.6.2 + the Safari 16.1 update. I had Safari, Geekbench 5 as well and Plexamp open when the crashes happened.

Does not look really promising, those artifact are usually caused by GPU over-heating and can show already permanent damage. I am pretty sure the few benchmarks you made will not be the (root) cause. Most likely you got it in exactly this state.

I'm installing Monterey on an NVMe ssd on my 2012 5,1 Mac Pro. It's currently looping through the installer. I think I saw a fix for this a while ago, but can't find it in the thread. I think I'll just move the installer to an m.2 external SSD enclosure and finish with my 2015 MacBook Pro?

Guess the MacPro cannot find on reboot the correct volume and starts installation from scratch on every reboot? Try to catch it on the first reboot and select manually the volume named macOS Installer - should break he loop.

 

[SEJU]

Does not look really promising, those artifact are usually caused by GPU over-heating and can show already permanent damage. I am pretty sure the few benchmarks you made will not be the (root) cause. Most likely you got it in exactly this state.

Guess the MacPro cannot find on reboot the correct volume and starts installation from scratch on every reboot? Try to catch it on the first reboot and select manually the volume named macOS Installer - should break he loop.
.

Thanks for your feedback and I am sorry for all the trouble this card has caused you and all the others in assisting me!

Even the vertical stripes I had during installation, had a different appearance from those encountered by others in the thread. So I guess it was not just the ICs.

The machine is now running, but I came to the conclusion, that something with the card is indeed not right. I insisted with the installation, because I thought I had done something wrong, but with all the help I received, I have to accept that a replacement is needed. Your confirmation is just the last nudge I needed.

The strange thing was, that this morning with all the snow outside and the studio more than fresh the machine was cold ... The GPU maybe at 40ºC. Anyway ... I haven't found similar issues here related to Monterey, did not find something on OCLP, got the vBIOS from the source, no one else has this problem ... it has to be the card.

Strange stripes on first installation, on High Sierra GB Metal did crash, now this problems with ... windowmanager?

I will try to return the card and try to find a replacement.

In my opinion the update of the iMac 2011 is absolutely worth it. The performance is on par or regarding the GPU even far greater than my maxed out MBP 15" 2016, which still is of great service to me today. Thanks for all your work.

Thanks also to everyone else, who gave me a hand.

Now I am again on the hunt for a WX7100 or newer card... ;0(

 

[h9826790]

I'm installing Monterey on an NVMe ssd on my 2012 5,1 Mac Pro. It's currently looping through the installer. I think I saw a fix for this a while ago, but can't find it in the thread. I think I'll just move the installer to an m.2 external SSD enclosure and finish with my 2015 MacBook Pro?

Search AVXpel

 

[Ausdauersportler]

Search AVXpel

A technical similar and functional identical solution is already included into OCLP. Without this solution the installer would simply crash and enabling verbose by pressing CMD+V on the boot picker should show this.

Mostly the boot loops are can be circumvented/broken by picking the staged installer on disk after the first reboot named macOS installer manually.

 

[HDMC]

This is observation correct. AppleALC.kext is part of the complete OpenCore (OC) package and will be replaced on (re)installation using the OCLP app (with a same or different version). AppleALC 1.7.6 included in OCLP 0.5.2 seems to break sound on some, but not all legacy Macs. OpenCore aka OC lives in the EFI partition, which is a small hidden partition on your Mac. Either replace the complete OC version or just the AppleALC.kext.

This has been posted/described numerous times during the last days.

First of all thank you for the reply to my post in that structured way. Would have been nice beforehand, instead of telling me how dumb I am having a problem.
All you wrote I knew already, due to my research before.
I did replace the complete OC and it didn´t work, hence my seek for help.
I managed to mount the EFI and replace the ALC, but that didn´t help either. So I think there is some deeper problem with my system ...

If I reboot my system while holding ALT, there are two options to boot into my system
1) EFI boot
2) System boot, in that case "Monterey"

Both options seem to do the same and replacing the ALC either way having no effect.

EDIT: Strange thing I just discovered is that by booting the EFI with "sudo diskutil mount EFI" now the EFI is empty.

No, since 1) is correct installing Monterey will not provide sound support, if you changed OC properly and rebooted something different must be wrong.

Try PRAM reset after installing a non 0.5.2 OCLP version.

(As long as you have only Monterey OLCP 0.4.11 should work.)

I did reset the PRAM/NVRAM.

It is not necessary to change root patches (it some have been applied).
It is not necessary to re-install Monterey, since it does not touch the AppleALC.kext.



All this would be clear if you would have spent some time on reading approximately 20 pages of OCLP docs. Unfortunately trouble shooting is that complex most times and there are no real short cuts.

I did read the OLCP docs a while ago and now again and did spent hours on websites to figure it out. I surely dont look for shortcuts, but couldnt figure out the terminal commands to replace the ALC via terminal ... therefore I am here.

The docs have been published on purpose! It does not scale to have only a few developers and helping hands and literally thousands of users downloading, installing and sometimes struggling with OCLP running Big Sur, Monterey, and Ventura every week again and again. This cannot be a Genius Bar replacement.

I understand how docs are working ! I did wrote over 100 educational books.
It is not a question of a few developers not willing or having the time to help. At a forum like this there are surely more guys having a similar problem and have the potential to help.
That´s the definition of a forum. If I can help I will happily do it and don´t call the questioner an oportunist or whatever. That´s a crazy thought in general !
Surely it would not be a problem to establish a forum full of experts, which will flatter each other at least 3 times a week.

So I absolutely appreciate that you took the time and replied ! Thank you !

 

[highvoltage12v]

I Checked the install process entirely in Verbose mode. I saw a ton of NVRAM errors. I checked to see what bootrom my Mac Pro is running and it's on 140.0.0.0 which was actually rebuilt before by @tsialex . I created a new Mojave installer and performed a Bootrom upgrade to 144.0.0.0. After this the installer was able to complete, 12.6.1 is running with OCLP.

 

[MacHosehead]

I did read the OLCP docs a while ago and now again and did spent hours on websites to figure it out. I surely dont look for shortcuts, but couldnt figure out the terminal commands to replace the ALC via terminal ... therefore I am here.

I have a MacPro3,1 currently running Big Sur with OCLP 0.5.2 and no problems with audio.

For replacing AppleALC.kext, once I have mounted the booting EFI partition then I will use Finder to replace it by just dragging and dropping into the kext directory. Since installing older versions of OCLP have not fixed the problem then I would expect something else going on maybe with hardware. As a last resort you can use a mac-compatible USB sound dongle.

 

[lewnworxx]

Been struggling for a couple of days now trying to get the Bluetooth side of things working on my BCM943602CDP (genuine Apple). It worked fine in Mojave, but refuses to switch on in Monterey? What I'm trying to figure out if it is because of the internal USB 1.1 issue I've been reading about or something else perhaps? I thought the USB 1.1 issue only affected OpenCore and not OCLP? Anyway, tried everything deep NVRAM reset (5 chimes), re-seating the card and SMC reset etc. I've also read that some people have no issues with the BCM94360CDP (BT 4.0 version), whereas mine the the BT 4.2 version (BCM943602CDP)? *EDIT* FIXED!... Disabled SIP & uninstalled root patches (even though there weren't any installed), rebooted and BT now works. Weird.

SO I've got the exact same card, it's working fine under Mojave & Big Sur but like you in Monterey, it won't switch on.

It shows up in system profile, as:

NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0 c0
Product ID: 0x0001
Supported services: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
Transport: UART
Vendor ID: 0x004C (Apple)

Ok, found the "root patches". Still had no-compat check it here for Mojave purposes.

Took that out and it popped right up.

Can't get universal control or handoff to work though.

 

[FlorisVN]

Here also audio problems with 0.5.2 on 2011 iMac’s
I stayed on 0.5.1 for now… (12.6.1)

 

[serafin79]

Here also audio problems with 0.5.2 on 2011 iMac’s
I stayed on 0.5.1 for now… (12.6.1)

have you tried the solution outlined in post #8,064
it worked for me on my MBP 8,1

 

[FlorisVN]

have you tried the solution outlined in post #8,064
it worked for me on my MBP 8,1

I will wait for an new oclp version, i see no reason for now to do the work arround.

Thanks anyway.

 

[Sven G]

Yesterday, I examined the Nvidia Kepler root patch extensions in /S/L/E, in OCLP’d Monterey 12.6.1 on MBP11,3: here, there is a mix of new (16.0.14) and old (16.0.12) versions; while, on native Big Sur 11.7.1, they are all at the same version (16.0.13). So, I wondered if maybe this mix of new (beta?) and old extensions in Monterey could be the cause of some strange things, such as the missing setup and preferences windows in Acronis (my only remaining and still unsolved problem in Monterey)…? Or doesn’t this matter? What would happen if the latest official Big Sur 11.7.1 extensions were used for the root patch in Monterey…? Wouldn’t they work, maybe? Just some perhaps naive questions, also because I cannot understand why that Acronis missing windows problem is still there…

 

[Ausdauersportler]

Yesterday, I examined the Nvidia Kepler root patch extensions in /S/L/E, in OCLP’d Monterey 12.6.1 on MBP11,3: here, there is a mix of new (16.0.14) and old (16.0.12) versions; while, on native Big Sur 11.7.1, they are all at the same version (16.0.13). So, I wondered if maybe this mix of new (beta?) and old extensions in Monterey could be the cause of some strange things, such as the missing setup and preferences windows in Acronis (my only remaining and still unsolved problem in Monterey)…? Or doesn’t this matter? What would happen if the latest official Big Sur 11.7.1 extensions were used for the root patch in Monterey…? Wouldn’t they work, maybe? Just some perhaps naive questions, also because I cannot understand why that Acronis missing windows problem is still there…

Grab the latest Big Sur extensions form 11.7.1 and compare them (size and contents) with the ones found on the Monterey patched macOS (these are folders with a few or more files included). You may get an answer yourself.

 

[Sven G]

Yes, I see: the Monterey-modified extensions are bigger in size; and anyway the Big Sur ones are all from 2020, so they aren’t that new, after all. But I continue to have the missing windows problem with that one app (Acronis); and it must be something at the system level, as it persists in a freshly created new admin user; it is “fixed” only if you force the Nvidia Web Drivers in the OCLP developer settings, but that’s obviously not a viable solution. BTW, has someone perhaps been able to reproduce this strange graphics glitch (i.e., some windows - the setup (with transparency) and preferences (normal) ones - don’t appear in Acronis; except if booting in safe mode, which thus is the only way to access the Acronis setup and prefs)…? What could the reason(s) be? Very frustrated, also because everything else works perfectly!

 

[Ausdauersportler]

Yes, I see: the Monterey extensions often are bigger in size; and anyway the Big Sur ones are all from 2020, so they aren’t that new, after all. But I continue to have the missing windows problem with that one app (Acronis); and it must be something at the system level, as it persists in a freshly created new admin user; it is “fixed” only if you force the Nvidia Web Drivers in the OCLP developer settings, but that’s obviously not a viable solution. BTW, has someone perhaps been able to reproduce this strange graphics glitch (i.e., some windows - the setup (with transparency) and preferences (normal) ones - don’t appear in Acronis; except if booting in safe mode, which this is the only way to access the Acronis setup and prefs)…? What could the reason(s) be? Very frustrated, also because everything else works perfectly!

There is no Kepler based iMac available within the developer crew and all others here are obviously users. There are only a few such developers and thousands of users complaining about missing features here and there.

Honest answer: Start to work on it yourself. Fork OLCP, figure out how to change patch sets or patch the system yourself. It is not that complex, nobody else will solve your problem.

The Monterey versions you mentioned are not the Monterey versions: These versions are gathered and completed from various older macOS (Big Sur) releases. Especially read this page about problems with patching in general.

 

[Sven G]

Yes, of course I intended the Big Sur versions modified to work with Monterey… And for some reason (perhaps some video seen on YouTube), I was convinced that Mr. Macintosh had an MBP11,3: but maybe not anymore, who knows… Thanks for the do-it-yourself advice: but that’s probably beyond my skills; will try, anyway. (Those strange windows must have something non-standard, in order to behave that way, with root-patched Monterey and Ventura; while they work fine on a non-root patched MBP11,1, without Kepler graphics.)

 

[Staygrade]

I need help please!!! My specs= MBP 5,1 (15",Late 2008) 8GB RAM, 240GB SSD, running OPCL 0.5.1 Monterey 12.6.1 (+2nd internal HDD drive bootable to EL Capitan 750GB)
Anyone know how to resolve this boot arg? I have reset NVRAM. Etrecheck report showing Boot args: keepsyms=1 debug=0x100 -disable_sidecar_mac -btlfxallowanyaddr -lilubetaall ipc_control_port_options=0

 

[Ausdauersportler]

I need help please!!! My specs= MBP 5,1 (15",Late 2008) 8GB RAM, 240GB SSD, running OPCL 0.5.1 Monterey 12.6.1 (+2nd internal HDD drive bootable to EL Capitan 750GB)
Anyone know how to resolve this boot arg? I have reset NVRAM. Etrecheck report showing Boot args: keepsyms=1 debug=0x100 -disable_sidecar_mac -btlfxallowanyaddr -lilubetaall ipc_control_port_options=0

Please check the OLCP and the OpenCore docs about how to change/edit the (OpenCore) boot-args or how to delete OpenCore from your systems in case you do not want to have a working Monterey installation any longer.

 

[h9826790]

I need help please!!! My specs= MBP 5,1 (15",Late 2008) 8GB RAM, 240GB SSD, running OPCL 0.5.1 Monterey 12.6.1 (+2nd internal HDD drive bootable to EL Capitan 750GB)
Anyone know how to resolve this boot arg? I have reset NVRAM. Etrecheck report showing Boot args: keepsyms=1 debug=0x100 -disable_sidecar_mac -btlfxallowanyaddr -lilubetaall ipc_control_port_options=0

There is no need to "fix" this. If your Mac is working as expected, don't fix it. Especially if you are running a patched OS. The OCLP team has their own reason to put those boot arguments into the config plist.

 

[MacRumors3590]

All working perfect.

 

[Staygrade]

There is no need to "fix" this. If your Mac is working as expected, don't fix it. Especially if you are running a patched OS. The OCLP team has their own reason to put those boot arguments into the config plist.

Thank you h9826790. The reason I ask is because my MBP has a hanging habit. It beachballs regularly for 30 seconds at a time without any CPU spiking or with just Opera browser open. Disk Activity reveals no clues as to why. CPU activity does not change when beachballing occurs. I read of other installs of Monterey using OCLP on mbp 5,1 who have a completely smooth experience. I cannot seem to track down why this is happening. Is there are a more intense disk activity scrutinising software that would flag up what's happening at the point of beachballing occuring? Could it be something involving the graphics switching being deactivated?

 

[h9826790]

Thank you h9826790. The reason I ask is because my MBP has a hanging habit. It beachballs regularly for 30 seconds at a time without any CPU spiking or with just Opera browser open. Disk Activity reveals no clues as to why. CPU activity does not change when beachballing occurs. I read of other installs of Monterey using OCLP on mbp 5,1 who have a completely smooth experience. I cannot seem to track down why this is happening. Is there are a more intense disk activity scrutinising software that would flag up what's happening at the point of beachballing occuring? Could it be something involving the graphics switching being deactivated?

Did you check console?

 

[amaze1499]

After solving the benchmark issue I would like to troubleshoot hopefully the last thing I encountered upon my path of upgrading this 2011 iMac. Yesterday, when writing my post about the strange benchmarking values, the UI froze and displayed a strange yellow pattern. I could still move the mouse, music continued playing, but the UI had become non responsive. I had to press the power button to force a restart.

View attachment 2122718

After that the computer worked. After some time, when rerunning the benchmarks, the same thing happened, but with a blue pattern.

View attachment 2122717

After a force restart everything worked without issues for several hours until I shut the computer down.

This morning, when turning the computer on, for 5-6 times I had the same experience: the blue pattern appeared and the UI froze almost immediately after login into the system.

What does this depend on (GPU, Monterey, OCLP, an app misbehaving?) and how could I solve this?

It is currently only Monterey 12.6.2 + the Safari 16.1 update. I had Safari, Geekbench 5 as well and Plexamp open when the crashes happened.

Do you see the same issue when running diagnostics?

"Press the power button on your Mac and then immediately press and hold down the D key on the keyboard. (To start Apple Diagnostics over the internet, hold down Option-D.)"

 

[internetzel]

Thank you h9826790. The reason I ask is because my MBP has a hanging habit. It beachballs regularly for 30 seconds at a time without any CPU spiking or with just Opera browser open. Disk Activity reveals no clues as to why. CPU activity does not change when beachballing occurs. I read of other installs of Monterey using OCLP on mbp 5,1 who have a completely smooth experience. I cannot seem to track down why this is happening. Is there are a more intense disk activity scrutinising software that would flag up what's happening at the point of beachballing occuring? Could it be something involving the graphics switching being deactivated?

Dying hard disks or SSDs can cause such a behaviour.
I once had a nearly new SanDisk SSD which behaved like that after a short period of using it for macOS; it had to be reset in order to work well again, so it was some firmware error of the SSD controller. Never used that SSD for macOS again.