macOS 12 Monterey on Unsupported Macs Thread

[khronokernel]

No race condition with a cMP3,1 with the signature setup that I have seen despite what tsialex claims.

I don't believe @tsialex claimed your specific machine had issues, but that MacPro3,1's in general are likely to experience the issue.

With development of OpenCore Legacy Patcher, we've seen over dozens of 3,1's experience these boot issues. These range from fully stock configurations too many variations of upgrades with no adding PCIe drives as well as with PCIe/NVMe drives. I would be wary of using only the 11.3 Race Condition thread as your main source, as only a few 3,1 users have commented there, whereas most 3,1 users with the issue were on our discord from what we've seen.

While yes your hardware locally may be less prone to the issue, I would be wary of saying that exact combo on everyone's machine would work the same. This can create more confusion when in reality the prevention of the race condition cannot be reliably predicted on every single machine with the same hardware configuration.

And just to clarify, I am not discounting your specific experiences with your specific machine, I am merely saying that these experiences should not be assumed for everyone with your hardware setup.

 

[M3Tech]

Successfully got Monterey Beta 2 running on my MacBook (Retina, 12-inch, Early 2015).
It runs even smoother than on Big Sur.

 

[pshufd]

Successfully got Monterey Beta 2 running on my MacBook (Retina, 12-inch, Early 2015).
It runs even smoother than on Big Sur.

Nice job. I agree that Monterey is smoother than Big Sur.

I'm looking forward to the official release as I'll upgrade my M1 mini then.

 

[JoinMeinHeaven]

I installed monterrey with the open core patcher on my MacBook Pro 2014 successfully but I was unable to boot into Bootcamp, open core made it imposible, is there a way to fix this ?

 

[Ausdauersportler]

I installed monterrey with the open core patcher on my MacBook Pro 2014 successfully but I was unable to boot into Bootcamp, open core made it imposible, is there a way to fix this ?

It is one of the patcher warnings. Right at the start of the online documentation. How could you miss this

 

[JoinMeinHeaven]

It is one of the patcher warnings. Right at the start of the online documentation. How could you miss this

But I don't want to reinstall windows, is really no way of make it work without doing so ? Installing open core in a separate partition would work ?

 

[startergo]

But I don't want to reinstall windows, is really no way of make it work without doing so ? Installing open core in a separate partition would work ?

Can't you not select Bootcamp from the OpenCanopy boot picker? It should work.

 

[JoinMeinHeaven]

It boots into macOS

Can't you not select Bootcamp from the OpenCanopy boot picker? It should work.

In the boot menu appears the open core icon saying windows but inside its my main disk and if i select it, it boots into macos

 

[startergo]

I never had a problem with Bootcamp on my MBP11.3 with OC, but I did not spoof yet the board id. I will test it later.

 

[pshufd]

If I needed Bootcamp to work, I think that I'd create Monterey and OC on an external drive and leave the internal drive with the Bootcamp setup. I haven't tried this but I think that you're using the default Apple bootloader if you do the OC stuff on an external drive.

 

[LFO8]

Reverted colours are okay, but you can’t boot High Sierra with OCLP. You should boot installer on USB.
Download installer of BS/Monterey make bootable USB and boot it with OCLP.

Supported Models | OpenCore Legacy Patcher

Ok, I got it working now after a couple of verbose boots. I'm on a 8,1 MacBook Pro A few things I am noticing:

- The fans are going nuts a lot (seems to test the limits of the resources available on this small machine)
- The trackpad scrolling seems off
- I can not adjust my screen brightness. Neither in System Preferences nor using the dedicated keybard buttons.
- Eventhough I installed OCLP to my internal drive's EFI, I can only boot it holding option during boot and then pick the EFI (or is this intended behaviour?) otherwise it takes me to the screen that say's this version of macOS is not supported on this model.
- Also the graphics are a bit off in dark mode (thin white line around the dock, dark color too dark etc) I guess that is down to the Intel HD3000 not being Metal compatilble or something?

 

[startergo]

It boots into macOS

In the boot menu appears the open core icon saying windows but inside its my main disk and if i select it, it boots into macos

Ok so here is the workaround. @khronokernel I would suggest adding this path:

\EFI\Microsoft\Boot\bootmgfw.efi

To the BlessOverride section in the OCLP app. It is harmless for any system.
I have some questions about the OCLP on mbp11.3
Why are these needed:
1. CPUFriend.kext and CPUFriendDataProvider.kext
2. USB-Map.kext
Also some concerns:
1. After booting once through the OC generated by the OCLP I can no longer boot Big Sur from the Apple bootpicker after NVRAM reset.
I always get:

panic(cpu 0 caller 0xffffff8022c0acc6): "Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"com.apple./System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.120.9/kext/apfs_vfsops.c:2047

.
I tried quadruple NVRAM reset, but when bypassing the OC it always panics and reboots. It never used to try booting from a sealed volume before and I used OC booting before with very minimalistic approach without an issue.
2. Bootcamp or Recovery partition are no longer visible in the Apple bootpicker after NVRAM reset (non OC boot).

 

[khronokernel]

Why are these needed:
1. CPUFriend.kext and CPUFriendDataProvider.kext
2. USB-Map.kext

CPUFriend because we spoof a new board ID, thus macOS would attach an incorrect power management profile meant for another machine. USB map is there more as a precaution in the event that Apple drops maps in the OS like was done with non-Metal Macs in the past. We also use USB Maps for when the model does a full SMBIOS spoof, as then the maps would be conflicting with those defined already

Ok so here is the workaround. @khronokernel I would suggest adding this path:

Ah thank you for the suggestion!

1. After booting once through the OC generated by the OCLP I can no longer boot Big Sur from the Apple bootpicker after NVRAM reset.
I always get:

That's quite an odd issue, depending on what OCLP build you used, it may be caused by the usage of SecureBootModel. Problem is that we disable OpenCore's SecureBootModel with v0.1.7 to avoid a Monterey bug. However not entirely sure why it would kernel panic, what SecureBootModel identifier did you use previous in your minimal OC config?

2. Bootcamp or Recovery partition are no longer visible in the Apple bootpicker after NVRAM reset (non OC boot).

If you installed OpenCore onto the same place Windows' boot loader is located, your firmware will hide the non-OC entry. Recommend adding a dedicated partition for OC as a Mac's firmware won't scan a single ESP for multiple boot loaders. More info here

 

[JoinMeinHeaven]

So...in conclusion...if I install open core in a separate partition of the same disk where bootcamp and macOS are, then i will not have issues booting into windows ?

 

[khronokernel]

Hello everyone, we're proud to release OpenCore Legacy Patcher v0.2.3!

Release 0.2.3 · dortania/OpenCore-Legacy-Patcher

With this release, we're pleased to also announce our new GUI for OpenCore Legacy Patcher! With the great aid of dosdude1, we not have a full Objective-C front end to make the process a bit easier....

github.com

Some of the more note worth changes from this release:

- Add NightShift support in Monterey for unsupported Macs
- Fix Intel HD4000 DRM support in Monterey (thanks EduCovas!)
- Allow TeraScale 2 acceleration on all models

And many more changes under the hood!

---

Additionally after much anticipation, we're pleased to also announce our new GUI for OpenCore Legacy Patcher! With the great aid of dosdude1, we not have a full Objective-C front end to make the process a bit easier.

• Currently the GUI is missing some more developer-centric features such as custom SMBIOS overriding, however the front end will continue to develop in the coming releases

---

Final note for this release, our provided binaries will be a bit different. Now we'll have the following:

• OpenCore-Patcher-TUI
  • This is the familiar Text-based interface users are familiar with
• OpenCore-Patcher-GUI
  • This is the new Graphical-based interface added with v0.2.3
• OCLP-CLI
  • Backend used for the GUI, only applicable to developers. End users can ignore

 

[emax81]

great new OCLP 0.2.3 !

How I can upgrade to 0.2.3 from 0.2.2 ???

Thanks

 

[startergo]

That's quite an odd issue, depending on what OCLP build you used, it may be caused by the usage of SecureBootModel.

I was using latest artefact:
commit 9cf19319c552abd96710e748944dd1cfc446c38d

If you installed OpenCore onto the same place Windows' boot loader is located, your firmware will hide the non-OC entry.

Not sure about this. I repeated the same test on my MacMini3.1. Before and after OCLP I still have these boot options on a single drive:

 

[Bravo2zero]

Can you help me to install Big sur on 9,1 iMac, now i´m on Catalina patched, is there a guide for the installation?

I used the open core patcher app and watched a YouTube video.

, you can use the latest 2.2.3 to patch. I found however the 9,1 a little funny with some USB sticks. I used a scan disk 16gb USB3 that would not show when you boot to launcher but then my other scan disk one USB3 ( slightly older model ) did boot.

 

[Ausdauersportler]

So...in conclusion...if I install open core in a separate partition of the same disk where bootcamp and macOS are, then i will not have issues booting into windows ?

Just start reading the online docs! There you will find all options where and how to install OC and how to uninstall the current misplaced version.

 

[Ausdauersportler]

great new OCLP 0.2.3 !

How I can upgrade to 0.2.3 from 0.2.2 ???

Thanks

There is no update, there is only a new installation replacing the old one. I am 100% sure the online docs cover this, too.

 

[khronokernel]

Not sure about this. I repeated the same test on my MacMini3.1. Before and after OCLP I still have these boot options on a single drive:

Well there's a small issue comparing a Macmini3,1 to a MacBookPro11,3, where does Windows store the bootloader? On the MacBook Pro (or any mid 2013+ machine), it's a UEFI setup by default and thus relies on the ESP to store Windows' bootloader. Whereas with Macmini3,1, the machine relies on the legacy CSM format for booting of Windows

 

[startergo]

Well there's a small issue comparing a Macmini3,1 to a MacBookPro11,3, where does Windows store the bootloader? On the MacBook Pro (or any mid 2013+ machine), it's a UEFI setup by default and thus relies on the ESP to store Windows' bootloader. Whereas with Macmini3,1, the machine relies on the legacy CSM format for booting of Windows

I understand the issue with Windows but what about the recovery partition and the sealed volume booting?

 

[JoinMeinHeaven]

Just start reading the online docs! There you will find all options where and how to install OC and how to uninstall the current misplaced version

I already get rid of open core and i don't want to reinstall windows, i wasn't able to find a fix for the problem that's why i had to make and account here and ask

 

[startergo]

CPUFriend because we spoof a new board ID, thus macOS would attach an incorrect power management profile meant for another machine.

Upgrading to Monterey from Big Sur fixed the sealed system boot panic when not using OC. I wonder if the OCLP somehow broke the seal when installed first. Also worth mentioning that MBP11.3 only needs -no_compat_check boot argument for booting Monterey without OC. There is no need for board id spoofing and power management profile change. Of course the updates may be broken without OC. Beats me why Apple dropped support for MBP11.3.

 

[khronokernel]

There is no need for board id spoofing and power management profile change. Beats me why Apple dropped support for MBP11.3.

Board ID spoof is required for OTA updates, and thus why CPUFriend and WhateverGreen are required to handle the updated board ID