macOS 12 Monterey on Unsupported Macs Thread

[TimmuJapan]

Hi, I’m having a few minor issues, mainly just cosmetic with OCLP after updating to the latest OCLP and Monterey.
I’m on a MacBook book pro 9,1 (2012):

Issue#1:
I have Catalina and Monterey installed on separate volumes. Somehow the boot entry names have gotten mixed up. Both the Mac boot picker when holding down the option key, and the Open core menu are showing Catalina as Monterey and Monterey as Catalina. Does anyone know how via terminal or modifying the config.plist, we can rename boot entry icons??
Once booted into the OS, the disk names are listed correctly. The names are also listed correctly in disk utility and in the recovery— it’s just the boot picker names have gotten mixed up. I have already reset the NVRAM several times, and reinstalled the opencore to the EFI several times, but the names of the disks are still mixed up During start-up.

Issue#2:
whenever I restart the machine, I get the “your machine restarted because of an error “ message.

both of these things occurred after the last update. Neither are major issues, just small cosmetic things. I am wondering if anybody has any advice about how to resolve them.

 

[sinbad21]

Hi, I’m having a few minor issues, mainly just cosmetic with OCLP after updating to the latest OCLP and Monterey.
I’m on a MacBook book pro 9,1 (2012):

Issue#1:
I have Catalina and Monterey installed on separate volumes. Somehow the boot entry names have gotten mixed up. Both the Mac boot picker when holding down the option key, and the Open core menu are showing Catalina as Monterey and Monterey as Catalina. Does anyone know how via terminal or modifying the config.plist, we can rename boot entry icons??
Once booted into the OS, the disk names are listed correctly. The names are also listed correctly in disk utility and in the recovery— it’s just the boot picker names have gotten mixed up. I have already reset the NVRAM several times, and reinstalled the opencore to the EFI several times, but the names of the disks are still mixed up During start-up.

Issue#2:
whenever I restart the machine, I get the “your machine restarted because of an error “ message.

both of these things occurred after the last update. Neither are major issues, just small cosmetic things. I am wondering if anybody has any advice about how to resolve them.

Hi, for issue#1, on each system you could try the command

sudo bless -folder /System/Library/CoreServices

edit : The bless command sets volume bootability and startup disk options.

 

[TimmuJapan]

Hi, for issue#1, on each system you could try the command

sudo bless -folder /System/Library/CoreServices

edit : The bless command sets volume bootability and startup disk options.

no luck with this solution, but thanks for the input.

 

[sinbad21]

no luck with this solution, but thanks for the input.

Another idea : the program EFI Boot Renamer.

 

[DinkThifferent]

Hello, since upgrading my macbook to 12.6.1 (again) after running it apparently on 12.6.1 beta 1 (upgrading from catalina with open core 0.4.11) and using safari 16.1 suddenly my macbook cannot properly hibernate anymore. After closing the lid i have to start-up again after a couple of hours. i am greeted by 'your mac shut down due to a problem'. this was not the case with 12.6.1 beta 1 and safari 15.6.
Furthermore, the google search field remains blank when i type (but is visible after i press enter) and typing this message here on macrumors is very slow.

System-wide power settings:


Currently in use:

standbydelaylow 0
standby 0
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
sms 1
networkoversleep 0
disksleep 0
standbydelayhigh 4200
sleep 0 (sleep prevented by sharingd)
autopoweroffdelay 14400
hibernatemode 3
autopoweroff 1
ttyskeepawake 1
displaysleep 60
highstandbythreshold 50
acwake 0
lidwake 1



Any idea what to do?

I fixed my own problem by re-installing the open core patch. (Without updating it from 0.4.11 to 0.5). Just click ' post install root patch' and follow the on screen instructions!

Everything works like a charm again!

 

[HDMC]

I have a Mac pro 3,1 and no Bluetooth on Monterey 12.6.1 and BCM_4350C2 !
What is strange is that I have a Dual boot system with Catalina and Monterey and now Bluetooth isn´t working on Catalina also. Could it be that Opencore (0.4.11) is the problem here ?
I thought Catalina would be independent from Opencore ?!

Thanks !

 

[TimmuJapan]

Hi, I’m having a few minor issues, mainly just cosmetic with OCLP after updating to the latest OCLP and Monterey.
I’m on a MacBook book pro 9,1 (2012):

Issue#1:
I have Catalina and Monterey installed on separate volumes. Somehow the boot entry names have gotten mixed up. Both the Mac boot picker when holding down the option key, and the Open core menu are showing Catalina as Monterey and Monterey as Catalina. Does anyone know how via terminal or modifying the config.plist, we can rename boot entry icons??
Once booted into the OS, the disk names are listed correctly. The names are also listed correctly in disk utility and in the recovery— it’s just the boot picker names have gotten mixed up. I have already reset the NVRAM several times, and reinstalled the opencore to the EFI several times, but the names of the disks are still mixed up During start-up.

Haha, I'm a dork and answering my own question, but the below solution solved the problem easily to rename open core boot entry items in my case..... Holding down the option key also displays wrong boot entry names, so I wish that I knew where these files were also stored in Catalina or just how to rename incorrect bootable volume/partition names when holding down the option key--does anyone know?

The below solution will allow a user to edit the bootable volume names for the open core menu:

 

[MacHosehead]

I have a Mac pro 3,1 and no Bluetooth on Monterey 12.6.1 and BCM_4350C2 !
What is strange is that I have a Dual boot system with Catalina and Monterey and now Bluetooth isn´t working on Catalina also. Could it be that Opencore (0.4.11) is the problem here ?
I thought Catalina would be independent from Opencore ?!

Thanks !

If this is the original bluetooth module then there is no guarantee it would work past High Sierra. OCLP does not support this module. If it was previously working in Catalina then maybe you were booting from a different EFI?

 

[mwidjaya]

the below solution solved the problem easily to rename open core boot entry items in my case.....

The solution is sound but replacing the edited file using Finder will hit permission problems.

Using terminal commands will work. I use the rough guide below.

Rename macOS Monterey disk in Startup Manager - Ask Different (stackexchange.com)

 

[pauclaude]

I've installed Monterey on a MacBook Pro 4,1 without problems, except for the impossibility to install also "little snitch" for some file permission error.
Has anyone faced a similar problem?

 

[MacRumors3590]

I've installed Monterey on a MacBook Pro 4,1 without problems, except for the impossibility to install also "little snitch" for some file permission error.
Has anyone faced a similar problem?

I needed to install the latest version of little snitch.

 

[pauclaude]

I needed to install the latest version of little snitch.

Installed the last version, same error. Little Snitch's support says it is the fault of wrong permissions in the system files.

 

[ChrisOSX]

Little Snitch and Micro Snitch work fine for me.

The app I have issues with is TotalFinder. I get injection error. Remove root patch, all is well and it runs, but I lose my external monitor and a couple other things without the root patch 🤷‍♂️

 

[hwojtek]

Installed the last version, same error. Little Snitch's support says it is the fault of wrong permissions in the system files.

Something is screwed up with your systems. I run Little Snitch 5.5, last updated on Oct 12th (so two weeks before 12.6.1) and have absolutely zero issues.

 

[chrickers]

I needed to install the latest version of little snitch.

What about LuLu instead?

 

[HDMC]

If this is the original bluetooth module then there is no guarantee it would work past High Sierra. OCLP does not support this module. If it was previously working in Catalina then maybe you were booting from a different EFI?

Thanks for the reply !
I figured out a very strange behaviour of OC !
If I choose "show Boot Picker" building the EFI, than rebooting and choosing the EFI on which 10.15 is on,
Catalina will boot, but with the OC-Settings of Monterey.
Means no Bluetooth !
I now did build the EFI without the boot picker and Voilà:
By holding ALT while booting and choosing the Catalina-EFI it works !
So perhaps that can be fixed with an future update ?!

 

[MacRumors3590]

What about LuLu instead?

I now use LuLu and Love it! and it's free!

 

[B0URNE]

Greetings my excellent ihackers. I've familiarised myself with the guide and OCLP releases but would like a little clarification on the applicable OCLP version with my 2011 GTX880M setup. Can I use OCLP ver 0.4.11 - patch to macOS 12.6, or am I presently limited to 0.4.10 and patch ONLY to macOS 12.5.1?

Thanks in advance.

 

[Jazzzny]

You'll get the best experience if you use OCLP 0.5.1/latest release + the latest build of macOS Monterey.

 

[B0URNE]

You'll get the best experience if you use OCLP 0.5.1/latest release + the latest build of macOS Monterey.

So OCLP 0.5.1 and latest build of macOS 12.6 will still support Kepler GPU (GTX880M)?

 

[Jazzzny]

So OCLP 0.5.1 and macOS 12.6 will still support Kepler GPU (GTX880M)?

Correct. OCLP currently maintains support for Big Sur - Ventura, and you'll actually get a better experience with 0.5.X as OpenCL functionality has been restored for Kepler users on macOS 12+

 

[B0URNE]

Correct. OCLP currently maintains support for Big Sur - Ventura, and you'll actually get a better experience with 0.5.X as OpenCL functionality has been restored for Kepler users on macOS 12+

Thank you. I will use OCLP 0.5.1 and let the community know of the progress and end result.

 

[iLazarus]

Running Monterey 12.6 on a late 2013 iMac (14,2) with OCLP 0.4.11 successfully as far as I can work out, mainly using Logic Pro.

I installed DiskDrill, however although it would open it would not open the Main Window. Opening the preferences came up with "Disk Drill encountered an unexpected error" and gave me the chance to send some logs direct to their support. Their answer was "Thanks for reaching out.Per the logs you sent, the Mac computer you are currently using is not supported.". They confirmed it was becasue I was using OCLP. I've not had a issue with any other utility (or any other) program I've used.

I was wondering whether anyone had experienced this, and whether there might be a work around?

I have the exact same issue, upgraded to Monterey now DiskDrill does not work anymore... on Big Sur it worked just fine.

Have you found a solution to this??

 

[B0URNE]

Success! After experiencing the loop-back re-install glitch (which I initially missed seeing) booting OpenCore, I finally followed the extended EFI boot-process and now my iMac 27" 12,2 is running with macOS Monterey (12.6.1)

Thank you @nikey22 for hacking the GTX880M vbios, and the OCLP gurus @khronokernel and @dhinakg for breathing new OS life into this machine!

Now that this is finished I have a quick question with installing Win10 on a separate SSD for a dual boot system. Do you still need to bootcamp for windows, or is it better to natively perform the install? Some mixed responses on the methodology.

 

[Mw0103]

Monterey is running great on my old 21.5” mid-2011 iMac 12.1 thanks to OCLP. Running 12GB RAM and a new 1TB SSD in place of the failed 500 GB HDD.

When new in December 2011 (ignore the speakers for my old work laptop):


Now: