macOS 12 Monterey on Unsupported Macs Thread

[macinfo]

I encountered a color profile rendering problem with the root patches of OCLP 0.6.8 and 0.6.9n compared to 0.6.7 on a MacBookPro4,1 (Default Display Profile) with Monterey. As can be seen in the image below, the 0.6.8 version renders colors desaturated and with a slightly different brightness or gamma compared to OCLP 0.6.7. The comparison was done on a freshly installed macOS 12.6.8 as well on macOS 12.3.1.

 

[deeveedee]

@macinfo Could it be that your non-metal settings changed in OCLP GUI, so that they are not the same in 0.6.7, 0.6.8 and 0.6.9? I'm not sure how these settings would result in the differences you observed - just a guess.

Spoiler

 

[macinfo]

@deeveedee, I already played with these settings too, as I regularly check 'Disable Beta Rim', but that didn’t change the color rendering behaviour.

 

[trifero]

I encountered a color profile rendering problem with the root patches of OCLP 0.6.8 and 0.6.9n compared to 0.6.7 on a MacBookPro4,1 (Default Display Profile) with Monterey. As can be seen in the image below, the 0.6.8 version renders colors desaturated and with a slightly different brightness or gamma compared to OCLP 0.6.7. The comparison was done on a freshly installed macOS 12.6.8 as well on macOS 12.3.1.

View attachment 2242232

Have you tried anearlier version of OCLP?

 

[macinfo]

@trifero, as the colors look about right with OCLP 0.6.7 compared to the slightly washed out ones with 0.6.8, I did not try any older versions of OCLP lately. I can’t remember recognizing any different color renderings in earlier versions, at the time using them (only slight color and shadow differences seen in the menu bar background, but not elsewhere).

 

[m4v3r1ck]

@trifero, as the colors look about right with OCLP 0.6.7 compared to the slightly washed out ones with 0.6.8, I did not try any older versions of OCLP lately. I can’t remember recognizing any different color renderings in earlier versions, at the time using them (only slight color and shadow differences seen in the menu bar background, but not elsewhere).

I'm still at macOS 12.6.8 but reverted to OCLP 0.5.0 as being my system's sweet spot.

 

[macinfo]

Thanks to all for giving tips on that little color 'anomaly', after all it’s not a big issue. Maybe the devs will have a look into it going forward, when it’s suitable, but not a priority of any kind that I see. Also it may just be this particular MacBookPro that is a bit picky when it comes to colors. ;-)

 

[Dolphins1972]

I can't be the only one who has had this problem? So far OCLP Discord forum has not been helpful.

Currently booted into Mojave trying to reinstall latest version of Monterey that was corrupted by Apple security update 12.6.8. For some reason OCLP is not creating EFI Boot partition so I'm unable to complete install of OpenCore or Monterey. Tried starting over with 0.6.7 but I get the same results. I went through 3 USB flash drives to find one that passes validation every time so it's not the USB drive.

Summary of what happened:

Installed Monterey 12.6.7 using OCLP 0.6.7 which worked flawlessly. Installed 12.6.8 security update through System Update which caused Monterey to boot into recovery where I was unable to complete install or recover TM backups that I have saved to a 3rd HDD. I have TM backups of both Mojave and Monterey but restoring would get stuck at "Preparing" and never finish after 6 hrs. So I purchased a thumb drive on Amazon with a full Mojave installer loaded. Tried installing fresh copy of Mojave but again was booted into Recovery but this time I was able to restore a TM backup of Mojave using Mojave Recovery. My previous attempts were done using Monterey Recovery. Now every time I boot Mojave I get notification, "Incompatible Disk: This disk uses features that are not supported on this version of macOS" but it doesn't seem to effect the OS as I'm using it now. Now when I try installing 12.6.8 using OCLP 0.6.8 it fails to create EFI Boot option so I can't install Monterey.

 

[macinfo]

Now every time I boot Mojave I get notification, "Incompatible Disk: This disk uses features that are not supported on this version of macOS"

This notification comes up if a APFS Volume is detected that has some newer filesystem specs, that were not created or just different enough at the time Mojave was released. I also get this when I boot into a older Mojave system, it just doesn’t fully understand how the Volume Groups work in Big Sur and later systems. In my case it mounts the Monterey Data Volume but not the System Volume.

 

[Dolphins1972]

This notification comes up if a APFS Volume is detected that has some newer filesystem specs, that were not created or just different enough at the time Mojave was released. I also get this when I boot into a older Mojave system, it just doesn’t fully understand how the Volume Groups work in Big Sur and later systems. In my case it mounts the Monterey Data Volume but not the System Volume.

When I did the Mojave restore from TM backup I erased the boot drive (SSD). By erasing it, it should not have any traces of OpenCore or any other data. The backup I used was the last time I used Mojave before installing Monterey with OCLP. I was not having any issues at that time, I know this because it's only been a month since installing Monterey the first time so everything is still kinda fresh in my mind. I'm not really worried about Mojave as I'm more interested in getting Monterey back up and running. But thanks for the info, anything is helpful at this point. Getting frustrated with OCLP at the moment.

 

[Dolphins1972]

Infinite Recovery OS Booting

With OpenCore Legacy Patcher, we rely on Apple Secure Boot to ensure OS updates work correctly and reliably with Big Sur. However this installs NVRAM variables that will confuse your Mac if not running with OpenCore. To resolve this, simply uninstall OpenCore and reset NVRAM


Note: Machines with modified root volumes will also result in an infinite recovery loop until integrity is restored.

OK, I have a Kepler GPU which was modified in the Post Install Patcher. How do I remove the Kepler patches?

 

[Dolphins1972]

Update:

Still trying to figure this one out? In the process of trying different solutions I checked SIP and found that NVRAM is protected by SIP. I have ran the command csrutil disable multiple times over the last week or so and every time it has been successful. Would this custom setting cause the OCLP EFI boot partition to fail?

Is this custom setting implemented by OCLP to keep you from re-enabling SIP after root patching?

 

[jgleigh]

SIP is controlled by OCLP, so using csrutil will get overridden when OC boots. If you want to change SIP settings you'll have to use OCLP settings.

What do you mean the OCLP EFI boot partition is failing? The EFI boot partition is hidden, so you won't see it in a normal volume display.

Are you booting off the OCLP created USB drive to install Monterey?

Normal process: Boot off the USB drive. Install Monterey. Then install OCLP on your boot drive.

 

[Dolphins1972]

SIP is controlled by OCLP, so using csrutil will get overridden when OC boots. If you want to change SIP settings you'll have to use OCLP settings.

What do you mean the OCLP EFI boot partition is failing? The EFI boot partition is hidden, so you won't see it in a normal volume display.

Are you booting off the OCLP created USB drive to install Monterey?

Normal process: Boot off the USB drive. Install Monterey. Then install OCLP on your boot drive.

I can see the contents of the USB, no EFI boot option is created. (see image)

So when I'm at the last stage of installing to USB drive, there's no EFI boot option. (see image)

This is as far as I get:

OK this just happened, I selected install to USB but look what showed up in my applications folder. The OCLP icon is just an icon, clicking it just brings up a collage of icon images but the EFI folder appears to be intact but no way to implement it.

 

[jgleigh]

Looks like OC might be running just fine off the USB. The EFI partition is HIDDEN. You won't see it normally. Have you tried running the Monterey Installer from where you got to?

Please try and follow the instructions exactly.

What is OpenCore? | OpenCore Legacy Patcher

 

[Dolphins1972]

Looks like OC might be running just fine off the USB. The EFI partition is HIDDEN. You won't see it normally. Have you tried running the Monterey Installer from where you got to?

Please try and follow the instructions exactly.

What is OpenCore? | OpenCore Legacy Patcher

Monterey installer boots into recovery where it's endless cycle. You have to boot into OCLP in order to install Monterey. I had Monterey installed and running without issue using OCLP for about a month. I have completed the steps correctly multiple times, it's not difficult. The last Apple security update 12.6.8 corrupted the OC boot loader when I installed it via system update. So I had to purchase a thumb drive with a full Mojave installer to get my OS back up so I could do a TM restore. Before installing Mojave via TM backup restoring would freeze at preparing and never show progress bar. My only option was to wipe Monterey drive and start over with Mojave using a fresh install from thumb drive with full Mojave installer.

 

[stephan182730]

I am trying to install Monetery on a 2008 iMac 8,1. Everything seems to work ok, but I get really bad artifacts intermittently.


Has anybody seen something like that before.

 

[ZebraDude]

I am trying to install Monetery on a 2008 iMac 8,1. Everything seems to work ok, but I get really bad artifacts intermittently.


Has anybody seen something like that before.

Yep I had that with my iMac 11,2. Terascale 1 issue. I believe a fix is in the patcher for Ventura (not sure such an underpowered iMac would handle it thought.

 

[deeveedee]

I am trying to install Monetery on a 2008 iMac 8,1. Everything seems to work ok, but I get really bad artifacts intermittently.

Has anybody seen something like that before.

What version of OCLP are you using to generate your Open Core EFI and apply post-install patches?

 

[stephan182730]

I used the latest 0.6.8. I went back to version 0.6.7. and that one worked.

 

[Steven*]

I just updated to Mac OS 12.6.8 and I noticed the USB, Firewire & Ethernet ports on my Thunderbolt Display no longer function. Any suggestions?

 

[joevt]

I just updated to Mac OS 12.6.8 and I noticed the USB, Firewire & Ethernet ports on my Thunderbolt Display no longer function. Any suggestions?

Connected using your MacBookPro9,1?

Do the USB, FireWire, and Ethernet controllers appear in the PCI tab of System Information.app?

What drivers are matched to each controller in an earlier version of macOS? Check ioreg.

Do those drivers still exist in Monterey 12.6.8? Check the System extensions folder.

Do those drivers have the thunderbolt compatibility flag set? Check the Info.plist of each kext of the drivers.

https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/post-28693185
https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/post-30117941

 

[Steven*]

Connected using your MacBookPro9,1?

Do the USB, FireWire, and Ethernet controllers appear in the PCI tab of System Information.app?

What drivers are matched to each controller in an earlier version of macOS? Check ioreg.

Do those drivers still exist in Monterey 12.6.8? Check the System extensions folder.

Do those drivers have the thunderbolt compatibility flag set? Check the Info.plist of each kext of the drivers.

https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/post-28693185
https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/post-30117941

Thanks! I'll check… I noticed USB and Ethernet work when I 1° disconnect the TB display, 2° put the MacBook to sleep, 3° wake up the MacBook and 4° connect the TB Display. When I connect a FW device: total freeze, reboot necessary. When I connect a FW device before start up, the Boot picker shows the options of startup volumes that are on the FW drive.

 

[dono42]

Updated cMP 5.1 12.6.7 -> 12.6.8 with OCLP 0.4.11 took about :40 everything appears to be good.

 

[m4v3r1ck]

I'm preparing my current Mac Pro 5,1 - macOS Monterey 12.6.8 - for the upgrade to macOS Venture 13.5.1. My plan is to perform a clean install - advised by Mr. Macintosh - and then use Migration Assistant to copy the rest to my new instance of macOS Ventura. I have a Carbon Copy Cloner backup, but for double safety reasons I'm currently creating a Time Machine backup to my SynologY NAS using single SMB3.

1. Why is TM rendering - mdsync 99/100% - my Mac Pro to an unusable state? Beach balls flying everywhere.
2. Is there a way to troubleshoot this TM issue?
3. Any other advice that my help me to fix this?

Thanks.