macOS 12 Monterey on Unsupported Macs Thread

[peirato]

Yes, my Macbook Pro does the same. However, it's been like this for a long time, ever since I switched to OCLP.

Is your battery ok? Mine have status 'Service recommended'. I guess this is the reason.

I found the same problem here, but it didn't help me.

I think I've found a fix by making two changes. I haven't done much testing yet, but the computer does not seem to be shutting down completely when going into hibernation mode anymore.

1. Download the TUI version of OpenCore, and set the following to True
Patcher Settings -> Miscellaneous Settings -> Set Hibernation Workaround
2. Build and install OpenCore to your computer.

The following steps might not be necessary, but should probably be done regardless if you have an NVMe SSD installed in your Mac:

3. Once OpenCore has been installed to the EFI partition, download SsdPmEnabler (https://github.com/kvic-z/SsdPmEnabler), mount the EFI partition (using https://github.com/corpnewt/MountEFI for example) and copy the SsdPmEnabler.kext into EFI/OC/Kexts
4. Edit the EFI/OC/config.plist file so that it loads the SsdPmEnabler kext at boot (using https://mackie100projects.altervista.org/opencore-configurator/ for example)

So, I returned to Big Sur because it works better for me (without any issues like hash volume or hibernation mode).

 

[amaze1499]

Update done using patched standalone usb installer. No issues. Thanks!

On another topic:

Does someone know a way to thin the dyld folder within the system folder just leaving the necessary cache files behind?

 

[chrickers]

Is your battery ok? Mine have status 'Service recommended'. I guess this is the reason.

I replaced it a couple of months ago and it's fine. So it must be something else. I'll try the workaround though.

Regarding Hash-Mismatches: I had opencore configured with features partially disabled. However, i got two warnings today, the second one just in this very moment I'm writing.

 

[OKonnel]

Update done using patched standalone usb installer. No issues. Thanks!

On another topic:

Does someone know a way to thin the dyld folder within the system folder just leaving the necessary cache files behind?

The dyld cache is a new form of System optimization introduced by Apple.
From what I understand, to improve the System's performance, in this cache many binary and other files are inserted and linked together that are no longer inserted directly in many Framework and Kext modules. So I don't think it can be emptied.
That said, in the last MacPilot, I found this option and I'm sending you a screenshot. Cocktail also allows this. However I don't think it really works...
After that, I test it in my Mac and let you know if it worked through an EDIT of this post.

EDIT
So! I started cleaning with MacPilot and as I imagined it made no changes...
The files in the dyld folder were 25 and 25 remain and the total size is the same [Select all files with CMD + A and then execute (CMD + Alt Option + I)] : 12.736.938.798 (5,13 GB on Disk).
The dates also remained the same: August 24, 2022, 10:59 am (GMT + 2.00)

I hope I have answered you

 

[OKonnel]

Warning for those who love always the risk...
I strongly advise against avoiding Safari version 16.1 Beta 2 as it has very serious problems with JavaScript.
Many sites appear black and only when JavaScript is disabled (from Develop menu) do sites appear; however they work terribly. Google Maps and some Extension (1Password) also don't work...
I insert this notice because if I had known I would have avoided installing it by adhering to the invitation I received directly from Apple... So, to restore version 16 of Safari, I had to reinstall macOS 12.6 completly.

 

[Sven G]

I replaced it a couple of months ago and it's fine. So it must be something else. I'll try the workaround though.

Regarding Hash-Mismatches: I had opencore configured with features partially disabled. However, i got two warnings today, the second one just in this very moment I'm writing.

Just right-click on the hash mismatch notification and choose to not let it show anymore: problem solved (of course, if it’s only a cosmetic issue and there are not other problems)…

 

[Tockman]

Warning for those who love always the risk...
I strongly advise against avoiding Safari version 16.1 Beta 2 as it has very serious problems with JavaScript.
Many sites appear black and only when JavaScript is disabled (from Develop menu) do sites appear; however they work terribly. Google Maps and some Extension (1Password) also don't work...
I insert this notice because if I had known I would have avoided installing it by adhering to the invitation I received directly from Apple... So, to restore version 16 of Safari, I had to reinstall macOS 12.6 completly.

"Against avoiding"?

 

[chrickers]

Just right-click on the hash mismatch notification and choose to not let it show anymore: problem solved (of course, if it’s only a cosmetic issue and there are not other problems)…

Haha, thanks. I actually did not know this

 

[JDJones92]

Just right-click on the hash mismatch notification and choose to not let it show anymore: problem solved (of course, if it’s only a cosmetic issue and there are not other problems)…

I always get actual issues whenever I get the mismatch warning; I won't be able to do things like open anything in the system settings or change the audio output device. I've had different levels of success with each OCLP version, I can currently run with 'partial unlock' but previously had to go without completely.

 

[Ausdauersportler]

I always get actual issues whenever I get the mismatch warning; I won't be able to do things like open anything in the system settings or change the audio output device. I've had different levels of success with each OCLP version, I can currently run with 'partial unlock' but previously had to go without completely.

This problem happens also on supported systems without using OC. A year ago I decided to delete/disconnect all devices having APFS file systems not created with Big Sur/Monterey from my Macs and to reinstall the macOS in case the particular error message comes up. Since then there is silence…

 

[JDJones92]

This problem happens also on supported systems without using OC. A year ago I decided to delete/disconnect all devices having APFS file systems not created with Big Sur/Monterey from my Macs and to reinstall the macOS in case the particular error message comes up. Since then there is silence…

Yeah, I know it wasn't something happening exclusively to OC systems, just sharing how it has affected me over the months.
I did a fresh install of Montery on my 11,1 Macbook Pro and got the error within 24 hours 🤷🏻‍♂️ There seems to be no rhyme nor reason to it.

 

[Ausdauersportler]

Yeah, I know it wasn't something happening exclusively to OC systems, just sharing how it has affected me over the months.
I did a fresh install of Montery on my 11,1 Macbook Pro and got the error within 24 hours 🤷🏻‍♂️ There seems to be no rhyme nor reason to it.

Have you deleted the internal disk using the disk utility from the Monterey installer? Tried here to avoid having any residues from former macOS versions on disks. Too bad that there is no clear path to get/come around this problem.

 

[JDJones92]

Have you deleted the internal disk using the disk utility from the Monterey installer? Tried here to avoid having any residues from former macOS versions on disks. Too bad that there is no clear path to get/come around this problem.

Yup, that's exactly what I did. It's not really a problem as I am not fussed about the missing features but it is mildly annoying me that it doesn't work 🤣

 

[rehkram]

Hi guys. After OC running pretty much flawlessly for some time I am now finding that my Mac will no longer shutdown properly, nor will it ever wake again from sleep once it does.

On shutdown everything quits etc and the sounds wind down but it stays on the desktop pic for a long time (10 min+). If nothing is done it will eventually restart itself, without a chime, presenting the 'computer didn't shut down properly' message before starting up. The crash reports seem to be the same every time.

If allowed to sleep nothing will happen when keyboard or mouse is activated. Sometimes it sounds like mechanically its waking but sometimes not.

Any ideas where to start looking to try and fix this? Its completely the same every time now and not random at all.
Thanks.

What version of OCLP are you running? Watchdogd timeouts were fixed a while back. Install OCLP 0.4.11, rebuild and reboot.

edit later: I see from your sig you're running something other than OCLP, not sure what.

 

[shafez]

Yup, that's exactly what I did. It's not really a problem as I am not fussed about the missing features but it is mildly annoying me that it doesn't work 🤣

I have MacBook pro 11,1 an not had any hashmismatch errors since I partially disabled the features in OCLP MISC SETTINGS.

 

[JDJones92]

I have MacBook pro 11,1 an not had any hashmismatch errors since I partially disabled the features in OCLP MISC SETTINGS.

As I said originally, that is what I have been using now without issues 👍

 

[ronton3]

Is there any advantage or disadvantage to using compiled .5 Alpha with 12.6.1 Monterey?

 

[davidlv]

oclp v0.4.11r and Monterey 12.6.1
All still working well.. Big thanks again and again to the OCLP Crew!
View attachment 2082743

Anyone know how to set up the General system preference display, accent and highlight colors so that Word will display a copied section so it is readable rather than all black?
Using a MacBookPro8,2 with Monterey 12.6 and PCLP 0.4.11 which requires a ton of root patches after installation.
Using only the HD video card (discrete Radeon disabled via nvram).

 

[makra]

Anyone know how to set up the General system preference display, accent and highlight colors so that Word will display a copied section so it is readable rather than all black?
Using a MacBookPro8,2 with Monterey 12.6 and PCLP 0.4.11 which requires a ton of root patches after installation.
Using only the HD video card (discrete Radeon disabled via nvram).

AFAIK the only way is to use the most recent version, that doesn't have this problem on non metal machines. 16.49 is your friend. Se #5,507

 

[ronton3]

Imac/27/late2012/13.2/Kepler/Ivybridge now Catalina was Monterey 12.6.1/4.11 and running well.

Divided into 2 APFS 500gb partitions. I have been experimenting the past couple of days and screwed things up enough I decided to go back to Catalina via USB, erased both partitions, and now have Catalina running normally, the problem is that when I download 4.11 to go back to Monterey, the line "Post install Root Patch" is grayed out, even after I Build and Install OpenCore, then reboot, it is the same and I get Build and install again.

Any way to fix this please.

 

[Shadow Demon]

Imac/27/late2012/13.2/Kepler/Ivybridge now Catalina was Monterey 12.6.1/4.11 and running well.

Divided into 2 APFS 500gb partitions. I have been experimenting the past couple of days and screwed things up enough I decided to go back to Catalina via USB, erased both partitions, and now have Catalina running normally, the problem is that when I download 4.11 to go back to Monterey, the line "Post install Root Patch" is grayed out, even after I Build and Install OpenCore, then reboot, it is the same and I get Build and install again.

Any way to fix this please.

Just to be sure I understand. "... the problem is that when I download 4.11 to go back to Monterey, the line "Post install Root Patch" is grayed out". Is this in Catalina or Monterey? In Catalina, it will always be greyed out. Further, you erased the two partition setup and went back to one in which you installed Catalina by USB, is the current plan to upgrade your 1 partition Catalina to Monterey?

 

[ronton3]

Just to be sure I understand. "... the problem is that when I download 4.11 to go back to Monterey, the line "Post install Root Patch" is grayed out". Is this in Catalina or Monterey? In Catalina, it will always be greyed out. Further, you erased the two partition setup and went back to one in which you installed Catalina by USB, is the current plan to upgrade your 1 partition Catalina to Monterey?

To clarify, I now have 2 partitions one with Catalina and the other is in reserve. I was thinking of installing Monterey on the 2nd disk.

 

[Shadow Demon]

To clarify, I now have 2 partitions one with Catalina and the other is in reserve. I was thinking of installing Monterey on the 2nd disk.

You should create a USB Monterey installer. I have had problems using OCLP to create the USB installer since it will automatically do the patching on installation which was unworkable on MacBook Pro 5,1. For me, the best option was using Terminal to create Monterey USB installer and then use OCLP to install EFI on USB drive. Also, I don't know if having OLCP installed on your boot drive with a supported Catalina and unsupported Monterey is a good option or not. I am fairly certain that using USB is better than trying to upgrade to Monterey to the other partition within Catalina.

 

[ronton3]

Okay I will try that, I have probably been complicating to much. Thanks for the response.

 

[vince22]

RC2 Version 12.6.1 (21G211) released today, updated firmware as well.