Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

lee1302

macrumors newbie
Jul 25, 2017
25
5
did not find if the MBP mid 2012 non retina works... so I tried my self.
My steps: MBP mid 2012 with BigSur (patched) SSD with BigSur (cloned for installation)

Download InstallAssistant Package from post#1
install InstallAssistant

open terminal type:
sudo /Applications/Install\ macOS\ 12\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/USBNAME

Download and open Nightly OpenCore-Patcher
#1 build OpenCore
#2 Install OpenCore to internal Drive
reboot and choose opencore boot
start installation MacOS 12 beta over MacOS 11 - after a while it's done and works. BUT only with the Nvidia GPU even if I disconnect the external Display - GPU is still active.

View attachment 1791244 View attachment 1791246
i have same model but i have intel hd 4000 :(
 

startergo

macrumors 68040
Sep 20, 2018
3,564
1,591
From what I read on pictures others posted, when Monterey on unsupported Metal Mac shows and detect "Graphics" on "About this Mac" then any IGPU feature should work as display mirroring.

If "Graphics" is hidden could mean there is an issue in detecting correctly the laptop built-in display, I'd exclude that this depends from any kext, rather I guess in some Display* or MonitorPanel framework so also on /System/Library/MonitorPanels/ where there is the Arrange.monitorPanel , the "Arrangement tab" is automatically added to Displays.prefpane when plug to an external video output signal.
I have 2014 MBP with dual graphics which I am planning to test. I know for that one DG is switched in the DSDT upon detection of external monitor. I was not able to completely disable DG through software. I know it can be done by modifying the DSDT/SSDT. I am not sure though how IG only handles external displays.
 

derOyabun

macrumors newbie
Jun 11, 2021
9
4
Germany
Post patching with open core patcher does not work.
SIP deactivated but still receive "cannot patch!!! please disable SIP!!!
Any idea why?

Bildschirmfoto 2021-06-11 um 14.35.31.png
 

jackluke

macrumors 68040
Jun 15, 2018
3,302
7,981
I have 2014 MBP with dual graphics which I am planning to test. I know for that one DG is switched in the DSDT upon detection of external monitor. I was not able to completely disable DG through software. I know it can be done by modifying the DSDT/SSDT. I am not sure though how IG only handles external displays.

I have low knowledge of DSDT/SSDT this is more expertise opencore developers stuff, about graphics switching is also a task of AGC kext (with all its plugins) and AGPM , currently on a dual GPU Ivy Bridge Monterey the graphics switching through gfxcardstatus is working correctly keeping kext stock, but I've also attempted to replace AGC and AGPM from Big Sur and it still works.
 

jackluke

macrumors 68040
Jun 15, 2018
3,302
7,981
I was not able to completely disable DG through software. I know it can be done by modifying the DSDT/SSDT. I am not sure though how IG only handles external displays.

Why you are trying to disable dGPU on a dualGPU supported Big Sur Mac ? Maybe to use as main the IGPU on other operating systems as windows or linux ?
 

derOyabun

macrumors newbie
Jun 11, 2021
9
4
Germany
Is there a easy way to remove the open core patcher?

I can't boot my Big Sur partition. at the moment I have no issues with Monterey (ok, 1password is not working,) but I feel more better if I can use Big Sur at the same time.
 

pshufd

macrumors 601
Oct 24, 2013
4,904
11,530
New Hampshire
From what I notice on pictures others posted, when Monterey on unsupported Metal Mac shows and detect "Graphics" on "About this Mac" then any IGPU feature should work as display mirroring.

If "Graphics" is hidden could mean there is an issue in detecting correctly the laptop built-in display, I'd exclude that this depends from any kext because if I don't get wrong the wired HDMI display mirroring works also without acceleration , rather I guess apple removed some references in Display* or MonitorPanel framework so also on /System/Library/MonitorPanels/ where there is the Arrange.monitorPanel , the "Arrangement tab" is automatically added to Displays.prefpane when plug to an external video output signal.

Im going to install on an external SSD given this uncertainty. I’ll do backups too. It’s a spare system but I don’t want to have to rebuild it if I don’t have to.
 

webg3

macrumors 6502
Jul 19, 2018
347
584
my 2 cents

to MacBook Pro 2013-2014

EFI OpenCore 0.7.0 working
 

Attachments

  • EFI_OpenCore_0.7.0_MacBookPro_2013-2014_macOS_Monterey.zip
    6 MB · Views: 40
Last edited:

grilledcheesesandwich

macrumors newbie
Jun 10, 2021
7
7
I'm using my 2015 MacBook Pro in clamshell mode to a Dell QHD monitor via HDMI cable. I haven't had any problems with the setup. Are you using DP to DP and HDMI to HDMI or DP to HDMI? I did HDMI to HDMI because the cable was handy.

I do mean to setup my 2014 as well (same config you have I guess) and have DP, HDMI and DP to HDMI cables - they're just in a box under a table.
Both DP/DP & HDMI/HDMI. Just tried connecting three other different monitors, same result. Looks like Monterey bricked my video output ports—USB ports work fine. Any fix would help me out.
 

Ausdauersportler

macrumors 68040
Nov 25, 2019
3,152
3,184
Post patching with open core patcher does not work.
SIP deactivated but still receive "cannot patch!!! please disable SIP!!!
Any idea why?

View attachment 1791247
You may add a signature, we cannot guess which system you are attempting to patch and nobody wants to search back several pages just to gather all information a user has spreads over several posts.

Patching for the 2012 was not necessary with Big Sur. So there will be no gain in trying it because it was meant - so far - for legacy pre metal video patching.

The code base of the upcoming OCLP 0.1.7 is the same as the Big Sur patcher and to my knowledge there has nothing added regarding the HD4000 so far. Please join Discord and check the online docs about the support list for post install patching.
 
Last edited:
  • Like
Reactions: derOyabun

Supesu

macrumors newbie
Oct 8, 2020
4
2
Here are some problems with OCLP 1.7 while patching to Monterey

So, ever since Monetery got released to the public, I've been trying to upgrade all of my Machines to Monterey from Big Sur, and it was and still is a process. So far as of the third day trying to put Monterey on all of my macs, only one of my Macs have successfully installed Monterey onto it. All five of my other macs are having issues I'll get to a bit later. I have six Macs, so that's already not a good success rate, but hey, this is a brand new operating system and we need time to work on our MacOS patchers.


So, what are these problems?

Well on 4/5 of my Macs, they're post-install issues that I haven't been able to resolve in any way but a fresh install of Monterey only for basically the same thing to happen all over again.

I call it 'The Pinwheel of Death'.

Basically, the Monterey installer will boot up and install Monterey just fine, and your Mac might work great on first boot, but one reboot later and you could be done. What happens on the bootup is the progress bar will get a little over halfway full before going to a black screen with a pinwheel that will spin on/off for three seconds at a time and an unmovable cursor in the top left corner. It never leaves this screen, and you can't just install a new Monterey over the broken one, you have to wipe the disk clean, lose your data, and start over again. So far four of my macs have all gotten to this state even after installing the patches. I haven't found a way to get past this issue yet.


The next issue is only taking place on one of my macs (MacBookPro10,2) and sporadically on a couple of my other Macs

It's basically just the prohibited sign. Even with the OCLP EFI, for some reason I get the prohibitory symbol on my 10,2. I suspect this has to do with Intel Macs dropping support at a stupidly rapid rate and OpenCore not having updated for that. My reason behind that thought is when I manually select the 11,2 model, it spoofs to a supported model and the prhobitory symbol goes away. However, the reason why it's still not working after that is yet again because of The Pinwheel of Death. Also yes, I know the Intel graphics aren't supported by Monterey anymore. You don't have to tell me.

Those are the major issues that I've found so far and haven't been able to get past while installing Monterey. There are some other issues with Opencore like for some reason there's no gui and the EFI boot is all just text based, the Apple logo and Hard Drive icons will scale to giant proportions, One USB stick of OpenCore won't let the system boot while the other will, or the fact that the 1.7 release of OpenCore Legacy Patcher can't be found on Github for some reason. I'd really like to install Monterey onto my Macs, but I haven't found a solution to these major problems yet, especially The Pinwheel of Death. The pinwheel has been a major problem the entire way through.

So, if I had a say on weather or not you patch to Monterey yet, I'd say no. 110% no. Wait with Big Sur until the patchers develop more so you don't have to risk losing your data over a pinwheel. I also hear that DosDude1 will be working on a Monterey patcher as well, and his patchers always have worked extremely well. I'd say wait for that, don't do what I did yet.
 
  • Like
Reactions: webg3 and derOyabun

derOyabun

macrumors newbie
Jun 11, 2021
9
4
Germany
You may add a signature, we cannot guess which system you are attempting to patch and nobody wants to search back several pages just to gather all information a user has spreads over several posts.

Patching for the 2012 was not necessary with Big Sur. So there will be no gain in trying it because it was meant - so far - for legacy pre metal video patching.

The code base of the OCLP 0.1.7 is the same Big Sur patcher and to my knowledge there has nothing added regarding the HD4000 so far. Please join Discord and check the online docs about the support list for post install patching.
Yeah okay. I will add signature. But: Patching was not necessary with Big Sur? Graphics yes - no need but for wifi i used the Big Sur patcher for sure..

the problem is that I can't use the internal graphics. I can't regulate the brightness for the internal display.
I tried to patch with the open core patcher nightly disabled SIP and SSV bt still not working.

EDIT: checking discord now. thanks
 
  • Like
Reactions: Ausdauersportler

Ausdauersportler

macrumors 68040
Nov 25, 2019
3,152
3,184
Yeah okay. I will add signature. But: Patching was not necessary with Big Sur? Graphics yes - no need but for wifi i used the Big Sur patcher for sure..

the problem is that I can't use the internal graphics. I can't regulate the brightness for the internal display.
I tried to patch with the open core patcher nightly disabled SIP and SSV bt still not working.

EDIT: checking discord now. thanks
The WiFi functionality came back in through pre-boot injection of legacy kernel extensions. There was no patching, i.e. no adding or changing of kernel extensions on disk( unless you had to do the video legacy patching).

This is the great beauty of OpenCore: No changes on disk, no broken seals, Apple software updates works as Filevault, until you start patching.

Monterey dropped HD4000 support (and it is not only the HD4000.kext missing). To get this back one has to find out what Apple has pulled from the system and what and how to patch it back without getting linking errors and brewing other things. This is not a 60 minutes effort.
 

derOyabun

macrumors newbie
Jun 11, 2021
9
4
Germany
The WiFi functionality came back in through pre-boot injection of legacy kernel extensions. There was no patching, i.e. no adding or changing of kernel extensions on disk( unless you had to do the video legacy patching).

This is the great beauty of OpenCore: No changes on disk, no broken seals, Apple software updates works as Filevault, until you start patching.

Monterey dropped HD4000 support (and it is not only the HD4000.kext missing). To get this back one has to find out what Apple has pulled from the system and what and how to patch it back without getting linking errors and brewing other things. This is not a 60 minutes effort.
of course.. I see. it's not a big issue for me at the moment. right now I have a bigger issue :-D I tried to use my Big Sur partition but this is not starting anymore. I have one disk, 2 partitions. Monterey starts but when I choose Big Sur I receive a forbidden 🚫 sign. After a reboot with the alt key internet recovery starts.

now I have to figure out how to use my "old" Big Sur partition.
if someone has a hint that would be great 😂
 

Ausdauersportler

macrumors 68040
Nov 25, 2019
3,152
3,184
of course.. I see. it's not a big issue for me at the moment. right now I have a bigger issue :-D I tried to use my Big Sur partition but this is not starting anymore. I have one disk, 2 partitions. Monterey starts but when I choose Big Sur I receive a forbidden 🚫 sign. After a reboot with the alt key internet recovery starts.

now I have to figure out how to use my "old" Big Sur partition.
if someone has a hint that would be great 😂
Installing, starting and using OpenCore is covered in the online docs linked in on post #1. After reboot with the alt key you should pre select (using the CRTL key) the OpenCore EFI, boot into it, select the Big Sur partition and start it. You cannot boot directly into an unsupported macOS version unless you use at least some technology to allow starting it up.
 

derOyabun

macrumors newbie
Jun 11, 2021
9
4
Germany
Installing, starting and using OpenCore is covered in the online docs linked in on post #1. After reboot with the alt key you should pre select (using the CRTL key) the OpenCore EFI, boot into it, select the Big Sur partition and start it. You cannot boot directly into an unsupported macOS version unless you use at least some technology to allow starting it up.
I guess I’m to stupid 😂
Tried what you said - then I received the internet recover. After another reboot Big Sur recovery starts automatically.

4743F165-E03E-44FF-BE89-F366DFA9389F.jpeg D30C4D01-5D96-4621-AAD9-FB3B35868537.jpeg D6243C3B-F35A-444E-9E0D-F34CF6336E53.jpeg 836E6A4C-AD87-4B84-83B4-C0538C921AEE.jpeg
 

Ausdauersportler

macrumors 68040
Nov 25, 2019
3,152
3,184
I guess I’m to stupid 😂
Tried what you said - then I received the internet recover. After another reboot Big Sur recovery starts automatically.

View attachment 1791313 View attachment 1791315 View attachment 1791314 View attachment 1791316
You have installed a Big Sur Beta? You may just take your Big Sur installer and reinstall the very same version (or a more recent one) on top of the existing one. This way your are keeping your data.

Something broke possibly the preboot volume, I do not know. When installing new Beta versions of macOS like the current Monterey I would strongly recommend to use a different partition on your SSD or a second external disk, not just an APFS container.
 
  • Like
Reactions: iMac-iPad

derOyabun

macrumors newbie
Jun 11, 2021
9
4
Germany
You have installed a Big Sur Beta? You may just take your Big Sur installer and reinstall the very same version (or a more recent one) on top of the existing one. This way your are keeping your data.

Something broke possibly the preboot volume, I do not know. When installing new Beta versions of macOS like the current Monterey I would strongly recommend to use a different partition on your SSD or a second external disk, not just an APFS container.
yes. but im sure its the lastest Big Sur beta 11.4.
however I split my ssd 50/50 cloned the Big Sur and installed Monterey over.
monterey still starts.. so I need to reinstall Big Sur and then both will work (maybe?)?

Bildschirmfoto 2021-06-11 um 17.22.31.png
 

Dilli

macrumors 6502
Oct 21, 2019
433
411
I read the documents and spoilers on 1st page. So to get things correctly if I want to install Monterey on my iMac 12,2 I need to first upgrade the wifi/ Bluetooth card to the Broadcom mentioned on the 1st page right. Already have the metal kepler graphics installed.

ot no success with OCPL though I tried numerous times. Rather I had to use Jackluke’s BigSur fix patch which worked perfectly for me and finally got my BigSur version updated to 11.4 after a long try.

Will wait for Jackluke’s and Dosdude1’s patches for Monetery update. Meanwhile will try to locate the broadcom wifi/BT card for prep work for Monetery.

Thank you all wonderful developers and people for giving us these patchers for our unsupported machines.
 
Last edited:

dhinakg

macrumors member
Mar 22, 2021
34
124
United States
Well on 4/5 of my Macs, they're post-install issues that I haven't been able to resolve in any way but a fresh install of Monterey only for basically the same thing to happen all over again.
Which Macs?

You can't just complain about issues without telling us what hardware you're experiencing it on.
What happens on the bootup is the progress bar will get a little over halfway full before going to a black screen with a pinwheel that will spin on/off for three seconds at a time and an unmovable cursor in the top left corner.
Sounds like you're trying to boot Monterey on unsupported graphics... We don't support Monterey on HD 4000 or any models that required root volume patching in Big Sur because we don't have graphics patches for that yet. This has been explained here and on Discord.
It's basically just the prohibited sign. Even with the OCLP EFI, for some reason I get the prohibitory symbol on my 10,2. I suspect this has to do with Intel Macs dropping support at a stupidly rapid rate and OpenCore not having updated for that. My reason behind that thought is when I manually select the 11,2 model, it spoofs to a supported model and the prhobitory symbol goes away.
Should have been reported on GitHub, but then again, graphics aren't supported...
There are some other issues with Opencore like for some reason there's no gui and the EFI boot is all just text based,
The only way this can happen is if OpenCanopy was not present (or if the config was modified), and we add it on all configurations and set the config appropriately. So this is either a bug, or you've modified the OCLP EFI.
One USB stick of OpenCore won't let the system boot while the other will
OCLP EFIs are specific to your machine and hardware configuration
or the fact that the 1.7 release of OpenCore Legacy Patcher can't be found on Github for some reason
Yes, because there is no 0.1.7 release yet. There are only nightlies.

If you're not a developer, don't install Monterey. It's a developer beta for a reason. And if you're gonna do it anyway and claim there are issues with our patcher (which doesn't even have official Monterey support yet!), do your due diligence and ask in the Discord or on GitHub, please. There's lots of work to do with Monterey but the onus for properly reporting issues is on you, not us.
 

dhinakg

macrumors member
Mar 22, 2021
34
124
United States
It looks like people are trying to boot Monterey on Macs that OCLP doesn't actually support currently, so I'm going to repost what I posted in Discord here.

A word on OCLP's Monterey support

As some of you may have noticed, initial beta Monterey support has been merged into the main branch, and we hope to push a release with this support on Monday. This'll allow some (but not all) of the Macs that OCLP supports for running Big Sur to additionally boot Monterey, and machines that were supported in Big Sur but dropped in Monterey to boot too. However, there's still a bunch of bugs that we need to identify and fix. Currently, there is no ETA for full Monterey support - nor is there any ETA for support for HD4000 and non-Metal machines. Developers are working on this but it will take some time.

Since this is a beta OS, consider support unstable. Do not run this on a Mac you rely on. And although very unlikely to happen, do not run Monterey if you cannot risk a brick.

OCLP's current Monterey support
Machines are grouped by supported graphics.

Intel Haswell Graphics Machines
MacBookPro11,1 - MacBookPro11,2
MacBookPro11,3 (iGPU + dGPU supported)
MacBookAir6,1 - MacBookAir6,2
iMac14,1
iMac14,4

Intel Broadwell Graphics Machines
MacBook8,1

AMD GCN 1.0 Machines
iMac15,1

NVIDIA Kepler Machines
MacBookPro9,1 (dGPU supported, iGPU not supported)
MacBookPro10,1 (dGPU supported, iGPU not supported)
iMac13,1 (dGPU supported, iGPU not supported)
Note: iMac13,1s without an iGPU are not supported
iMac13,2
iMac14,2 - iMac14,3

Machines Supported with a Metal Supported GPU Upgrade
MacPro3,1 - MacPro5,1
iMac11,1 - iMac11,3 (may kernel panic if WiFi card is not upgraded)
iMac12,1 - iMac12,2 (may kernel panic if WiFi card is not upgraded)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.