Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
That's my problem! I can't start the patcher. With 0.1.6 and also with 0.1.7 it says "only for macOS 11" und i can only quit.
Basically root volume patching for systems having no metal enabled GPU is still in the public beta phase with Big Sur. I am not quite sure if it will work straight ahead on Monterey in the same way it does with the recent version of Big Sur. For that reason it might have been blocked.

Please just wait a few days until internal testing has been finished.
 
  • Like
Reactions: iMac-iPad and mdgm

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
To be more specific, how can one know which model is faked to? For example, in my case?
If you are using OCLP it will be printed to the screen while creating the configuration. You can also open the EFI partition of your system and search for the config.plist and read the first few lines:

Code:
    <key>#Revision</key>
    <dict>
        <key>Build-Version</key>
        <string>0.0.22 - 2021-04-10</string>
        <key>OpenCore-Version</key>
        <string>0.6.8 - RELEASE - c528597 - 2021-04-05</string>
        <key>Original-Model</key>
        <string>iMac12,2</string>
        <key>Spoofed-Model</key>
        <string>iMacPro1,1</string>
    </dict>
 

VKondakoff

macrumors member
Apr 12, 2013
62
24
Tried to install using a test partition on my late 2014 5K iMac and got an error during the update that the startup disk could not be verified. The update didn’t succeed; I’m back on my regular Big Sur installation. Now the EFI seems to be somewhat goofed — my screen resolution options appear to correspond to those of a 4K iMac instead of 5K:

I have exactly the same issue: booted from
OpenCore Legacy Patcher v0.1.7 #
# Selected Model: iMac15,1 #
# Target OS: macOS 12.0.

There were no errors and now the screen resolution is 3840 x 2160 instead of 5120 x 2880.

Patched:

Снимок экрана 2021-06-09 в 13.23.10.png


Non-patched:

Снимок экрана 2021-06-08 в 23.00.04.png


System Information still recognizes my display correctly:

Снимок экрана 2021-06-09 в 13.23.44.png


Any chance to fix this?
 
  • Like
Reactions: jonblatho

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
@sinbad21 on MBP9,1 that is dualGPUs Nvidia Kepler based, you can install the Big Sur IntelHD4000* kext and they will work adding brightness control and GPU power management features, here is an attached: https://forums.macrumors.com/attachments/intelhd4000-11-4-kext-zip.1789983/

if you know the kmutil methods to install kext making a new snapshot from an USB Monterey installer (or even from an USB Big Sur Installer) then you can use them, otherwise from direct Monterey desktop booting you could try this: https://github.com/jacklukem/BigSurmountsrw/releases/tag/1.0

Just select your Monterey diskXs5 from list, add the kext directly from Finder, then click Rebuild KC and at reboot it should work.

Note for others: currently the IntelHD4000 kext won't work on single GPU machines, only on dualGPUs machines because they have a Monterey supported Nvidia Kepler dGPU.
 

hvds

macrumors 6502a
Sep 1, 2017
852
2,032
Switzerland
Hello everyone, I made some attempts to install and boot Monterey either on unsupported non metal and unsupported metal Mac, I'd share my insights.

All the known installing method are nearly identical to Big Sur, some main examples: @ASentientBot HaxLib.dylib , OpenCore, OCLP

in my case to install Monterey I used a modified BigSurBaseSystemfix making a new patched Monterey BaseSystem, through the ASentientBot HaxLib, IOHIDFamily and patched boot.efi

I used MacBook7,1 and installation completed correctly on external USB SSD with less efforts than I had on Big Sur, then using my previous BigSurBaseSystemfix (based on a patched hybrid BigSur beta3 beta9 BaseSystem), through "BigSurFixes delete snapshot" I still can even delete the "com.apple.os.update" of Monterey resulting in a working "mount -uw /" (hence I removed telemetry plugin for C2D kp and PlatformSupport.plist from Preboot)

Now the weird part, while installation completed smoothly, on MacBook7,1 the welcome screen worked even if is very slow, after create the admin user there is a kind of loginwindow or skylight crash so can't log to desktop, let's say only the "setup assistant" graphical environment showed correctly, I'd attempt some AGC kext and plugins replacements.

I also noticed that apple changed and renamed the Wifi kext in this way:

IO80211Family.kext in IO80211FamilyLegacy.kext
IO80211FamilyV2.kext in IO80211Family.kext

I tried to replace some patched Wifi kext but kmutil refuses to rebuild kc correctly, because they rely on many dependency symbols on AppleBCMWLAN* and IOSkywalkFamily.kext so eventually an OpenCore kc patch would fix the AirPort4360 and 4331 drivers while keeping the stock Monterey Wifi driver.

About the minimum unsupported Metal Mac that are Ivy bridge, as many already wrote what surely works without efforts (just with -no_compat_check) on unsupported Metal acceleration OOB is any Nvidia Kepler based GPU because those drivers are present on stock monterey kernel collection (and its Extensions folder).

Weirdly if manually installed the IntelHD4000 Big Sur drivers currently only works on a dualGPUs Nvidia Kepler GPU, while on a single GPU IntelHD4000 produces a similar loginwindow crash as non Metal (non framebuffer patched) GPUs .

On dualGPUs IntelHD4000 IGPU Nvidia Kepler dGPU the Big Sur AppleIntelGraphicsHD4000* kext and its AppleIntelFramebufferCapri provide the Brightness control, GPU power management and switching, Ethernet also works without kext patching.

The picture is the same external USB SSD installed Monterey plugged to a MacBookPro9,1 , booting currently without OpenCore.
Installation of 12.0 beta on a MBP5,2 in progress.
Using OCLP 0.1.7. installing over 11.4 on a USB SSD.

First, booting the Monterey installer KP‘d early, the log pointing to the wifi driver as culprit. Now following jackluke‘s confirming post, chose in the OCLP options to always assume upgraded wifi which then omits the legacy (Mojave) driver.
With this option 0.1.7 boots the installer OK. Stage2 in progress.
 

OKonnel

macrumors 6502
Apr 16, 2009
360
655
Italy
Hurrà!
In my 27 '' late 2013 iMac (i7 CPU - 24GB RAM - nVidia GTX 780M 4GB) Monterey works better than Big Sur!

Who says Apple has ruled out nVidia cards in macOS 12?... With Big Sur I have never been able to get Photo Booth to work and it took several changes to the OpenCore Legacy Patcher before my films were working in Apple TV... (@Ausdauersportler and @khronokernel know this well ...)
As soon as I installed Monterey, instead, my iMac started working completely fine, as if macOS Catalina had been installed and not a Beta of two successive Systems...
This means that Apple shouldn't have ruled out my iMac from Big Sur and laters.
Even in what I add below, apparently O.T., it suggests that many aspects have been overlooked in Big Sur to entice many of us to switch to the new iMacs. I was about to do it, until a few minutes ago ... Thanks Monterey and thanks MacRumors!

O.T. but not too much...
Regarding planned aging, my iMac was just dead, some days ago, since the hinge broke. Well, I repaired it by replacing the two PLASTIC washers with a metal rod that could never, ever give way under the pressure of the two springs... But if you saw the two plastic washers that have given way and how thin they are, you would understand that have been purposely designed to fail after a number of years...
The hinge, in fact, is wonderfully engineered, which means that it has been calculated based on weight and function. Nothing would have been simpler, therefore, to use either two metal washers or, better still, a single metal bar (with two holes for the two screws), as I maked.
Instead, two plastic washers were intentionally designed and made, at the cost of making the fabrication more complicated and a little more expensive.
From my point of view it is either pure nastiness or some bad Engineer may have acted in bad faith, despite being very good at knowing how to design this splendid hinge. If there had been Steve Jobs, in this case, this person would have stopped working all over the world. Therefore it is legitimate to suspect that someone from the Marketing has deliberately ordered to plan the failure after a few years from the expiry of the guarantee.

I.T. ;) To be able to enjoy all of us
Now, however, since the hinge has been repaired perfectly, I have stopped considering the purchase of the new iMac. Then, I will continue to use my iMac, noting that it has never worked so wonderfully well since I bought it.
Of course I'd buy a new Mac if I needed better performance for videos and more.
 

Attachments

  • Monterey 01.jpg
    Monterey 01.jpg
    36.9 KB · Views: 242
  • Monterey 02.jpg
    Monterey 02.jpg
    66.3 KB · Views: 213

iMac-Oldschool

macrumors regular
May 22, 2019
149
157
Brexit
Hi @iMac-Oldschool

Yes mainly replaced this line:

Code:
for x in "Install macOS Big Sur" "Install macOS Big Sur Beta" "Install macOS Beta"

by it:

Code:
for x in "Install macOS Monterey" "Install macOS Monterey Beta" "Install macOS Beta" "Install macOS 12 Beta"

But also of course replaced in all places "Big Sur" by "Monterey" including in error messages (even if this is not essential and does not interfere with the operation)

here is the full modified script:
Thanks Alphascorp. Installation ran without problems.

The WiFi patcher did not run however. Patch-kexts.sh generated various error messages:
-Unable to detect macOS version on volume. Make sure you chose
the correct volume. Or, perhaps a newer patcher is required.
-Unable to find the volume.
Cannot proceed. Make sure you specified the correct volume.
-When the system was booted from the USB patcher, patch-kexts.sh was not visible.

You probably have an updated wifi card and do not need the patch.
 

chechugarriga

macrumors newbie
Sep 22, 2020
10
5
Tarragona, Catalonia , Spain
Hurrà!
In my 27 '' late 2013 iMac (i7 CPU - 24GB RAM - nVidia GTX 780M 4GB) Monterey works better than Big Sur!

Who says Apple has ruled out nVidia cards in macOS 12?... With Big Sur I have never been able to get Photo Booth to work and it took several changes to the OpenCore Legacy Patcher before my films were working in Apple TV... (@Ausdauersportler and @khronokernel know this well ...)
As soon as I installed Monterey, instead, my iMac started working completely fine, as if macOS Catalina had been installed and not a Beta of two successive Systems...
This means that Apple shouldn't have ruled out my iMac from Big Sur and laters.
Even in what I add below, apparently O.T., it suggests that many aspects have been overlooked in Big Sur to entice many of us to switch to the new iMacs. I was about to do it, until a few minutes ago ... Thanks Monterey and thanks MacRumors!

O.T. but not too much...
Regarding planned aging, my iMac was just dead, some days ago, since the hinge broke. Well, I repaired it by replacing the two PLASTIC washers with a metal rod that could never, ever give way under the pressure of the two springs... But if you saw the two plastic washers that have given way and how thin they are, you would understand that have been purposely designed to fail after a number of years...
The hinge, in fact, is wonderfully engineered, which means that it has been calculated based on weight and function. Nothing would have been simpler, therefore, to use either two metal washers or, better still, a single metal bar (with two holes for the two screws), as I maked.
Instead, two plastic washers were intentionally designed and made, at the cost of making the fabrication more complicated and a little more expensive.
From my point of view it is either pure nastiness or some bad Engineer may have acted in bad faith, despite being very good at knowing how to design this splendid hinge. If there had been Steve Jobs, in this case, this person would have stopped working all over the world. Therefore it is legitimate to suspect that someone from the Marketing has deliberately ordered to plan the failure after a few years from the expiry of the guarantee.

I.T. ;) To be able to enjoy all of us
Now, however, since the hinge has been repaired perfectly, I have stopped considering the purchase of the new iMac. Then, I will continue to use my iMac, noting that it has never worked so wonderfully well since I bought it.
Of course I'd buy a new Mac if I needed better performance for videos and more.

Good afternoon, glad you succeeded OKonnel.

Allow me a question.
We are on the very same computer like yours, but with i5 CPU late 2013 27".
On our actual computer Big Sur was installed with the micropatcher approach, without any additional changes.

Where you in need of using OCLP 0.1.6 to run the installer of Monterey Beta?

Thanks in advance. Regards.
 

webg3

macrumors 6502a
Jul 19, 2018
507
774
@sinbad21 on MBP9,1 that is dualGPUs Nvidia Kepler based, you can install the Big Sur IntelHD4000* kext and they will work adding brightness control and GPU power management features, here is an attached: https://forums.macrumors.com/attachments/intelhd4000-11-4-kext-zip.1789983/

if you know the kmutil methods to install kext making a new snapshot from an USB Monterey installer (or even from an USB Big Sur Installer) then you can use them, otherwise from direct Monterey desktop booting you could try this: https://github.com/jacklukem/BigSurmountsrw/releases/tag/1.0

Just select your Monterey diskXs5 from list, add the kext directly from Finder, then click Rebuild KC and at reboot it should work.

Note for others: currently the IntelHD4000 kext won't work on single GPU machines, only on dualGPUs machines because they have a Monterey supported Nvidia Kepler dGPU.

I believe IntelHD4000 kext work on single GPU machines can be fixed with an update of these two:

Lilu and WhateverGreen

waiting hopefully
 

Chumnick

macrumors newbie
Dec 1, 2011
23
2
I installed Monterey on an thunderbolt drive using a usb flash drive and patched this usb and thunderbolt drive with opencore 0.1.7. MacBook Pro (Retina, 15-inch, Late 2013) doesn't need any post install drivers.
 
  • Like
Reactions: webg3 and bbfc

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I believe IntelHD4000 kext work on single GPU machines can be fixed with an update of these two:

Lilu and WhateverGreen

waiting hopefully

Of course opencore is powerful tool, maybe some kind of kernel patch or even dualGPUs SMBIOS spoofing with agpdmod could allow booting IntelHD4000 single GPU.

If you check my previous attempt on IntelHD4000 dualGPUs, apart that Graphics is not showed on "About this Mac" (I guess this is due to incorrectly detected built-in display), here is another difference from BigSur, as if IntelHD4000 Metal API are detected incomplete.

Monterey system report for IntelHD4000 Metal: Supported

Big Sur system report for IntelHD4000 Metal: Supported, Metal GPUFamily macOS 1

here is a quick table of Metal feature set: https://developer.apple.com/documentation/metal/mtlfeatureset
 
Last edited:

Desjek-T

macrumors newbie
Jul 26, 2012
20
19
Hi,

Installed beta 1 developper without problem on my MBP 9,1. There is an annoying bug : when the Mac goes to sleep, it is impossible to wake it again. I have to force power button to restart the machine.

Also, I wonder, no kext for HD 4000 integrated card, does it mean it is never used ?

I have the same problem with my iMac 13.2 Late 2012 with 802.11ac Wi-Fi card.
 

bbfc

macrumors 68040
Oct 22, 2011
3,910
1,676
Newcastle, England.
I installed Monterey on an thunderbolt drive using a usb flash drive and patched this usb and thunderbolt drive with opencore 0.1.7. MacBook Pro (Retina, 15-inch, Late 2013) doesn't need any post install drivers.
I’m installing it on the same model. Seems to be going ok so far.
 

alphascorp

macrumors 6502
Jul 16, 2018
343
635
Brest, France
Thanks Alphascorp. Installation ran without problems.

The WiFi patcher did not run however. Patch-kexts.sh generated various error messages:
-Unable to detect macOS version on volume. Make sure you chose
the correct volume. Or, perhaps a newer patcher is required.
-Unable to find the volume.
Cannot proceed. Make sure you specified the correct volume.
-When the system was booted from the USB patcher, patch-kexts.sh was not visible.

You probably have an updated wifi card and do not need the patch.
Yes I upgraded the cMP5.1 WiFi card with BCM94360CD, so I don't need to add kexts.

About the script "patch-kexts.sh" it is necessary to modify the lines concerning Big Sur in the code part below:

Code:
# Make sure this script is running as root, otherwise use sudo to try again
# as root.
[ $UID = 0 ] || exec sudo "$0" "$@"

IMGVOL="/Volumes/Image Volume"
if [ -d "$IMGVOL" ]
then
RECOVERY="YES"
else
RECOVERY="NO"
# Not in the recovery environment, so we need a different path to the
# patched USB.
if [ -d "/Volumes/Install macOS Big Sur" ]
then
IMGVOL="/Volumes/Install macOS Big Sur"
elif [ -d "/Volumes/Install macOS Big Sur Beta" ]
then
IMGVOL="/Volumes/Install macOS Big Sur Beta"
else
# if this is inaccurate, there's an error check in the next top-level
# if-then block which will catch it and do the right thing
IMGVOL="/Volumes/Install macOS Beta"
fi
fi

With this (but I'm not really sure)

Code:
# Make sure this script is running as root, otherwise use sudo to try again
# as root.
[ $UID = 0 ] || exec sudo "$0" "$@"

IMGVOL="/Volumes/Image Volume"
if [ -d "$IMGVOL" ]
then
RECOVERY="YES"
else
RECOVERY="NO"
# Not in the recovery environment, so we need a different path to the
# patched USB.
if [ -d "/Volumes/Install macOS Monterey" ]
then
IMGVOL="/Volumes/Install macOS Monterey"
elif [ -d "/Volumes/Install macOS 12 Beta" ]
then
IMGVOL="/Volumes/Install macOS 12 Beta"
else
# if this is inaccurate, there's an error check in the next top-level
# if-then block which will catch it and do the right thing
IMGVOL="/Volumes/Install macOS Beta"
fi
fi

The "remount-sysvol.sh" script should also be modified because it checks the version year of macOS, (replace "20" by "21") in the line of code below:

Code:
if echo $SVPL_BUILD | grep -q '^20'
 
Last edited:
  • Like
Reactions: Larsvonhier

sinbad21

macrumors regular
Nov 5, 2017
182
186
France
if you know the kmutil methods to install kext making a new snapshot from an USB Monterey installer (or even from an USB Big Sur Installer) then you can use them, otherwise from direct Monterey desktop booting you could try this: https://github.com/jacklukem/BigSurmountsrw/releases/tag/1.0

Just select your Monterey diskXs5 from list, add the kext directly from Finder, then click Rebuild KC and at reboot it should work.
Well, I copied the kexts directly with BigSurmountsrw, then clicked Rebuild KC, rebooted and it works. Thanks.
 
  • Like
Reactions: jackluke

Larsvonhier

macrumors 68000
Aug 21, 2016
1,611
2,983
Germany, Black Forest
Interesting crash behaviour of macOS 12 on Mac Pro 3,1 (0.1.7 patcher does not help here):
Whenever a (previously working, usable) WiFi card is connected to the internal miniPCIe slot, boot process crashes at a very very early time (never seen this before). Last verbose output reporting number of CPUs and cores. Then the hard crash with reset.

Have tried with three different Atheros cards (one of them proven to work up to Big Sur).
Update: I just got a "new" cMP3,1 with a Broadcom BRCM94321 Wifi module in it. With this module, the system boots fine, but of course due to unpatched 80211 kexts Wifi does not work yet. But this might be helpful in finding the drastic reset/reboot behaviour of the three other types of cards (see original post).
 

PG7

macrumors newbie
Jun 8, 2021
26
12
world
if you know the kmutil methods to install kext making a new snapshot from an USB Monterey installer (or even from an USB Big Sur Installer) then you can use them, otherwise from direct Monterey desktop booting you could try this: https://github.com/jacklukem/BigSurmountsrw/releases/tag/1.0

hello good afternoon Jackluke,

would it be possible to make it compatible with MonteRey?

thanks

it would be for me to do tests with HD4000 and Nvidia GT320M

Google Translate !
 

vince22

macrumors 6502a
Oct 12, 2013
649
629
as expected 2012 13" MacBook Pro non-retina HD 4000 no kext loaded, wifi working ...barry's micropatcher used.

Monterery.png
 

Bmju

macrumors 6502a
Dec 16, 2013
702
768
  • Like
Reactions: Tockman

chetzar

macrumors regular
Oct 12, 2013
194
309
Kinda bummed that the late 2013 rMBP got dropped from the list, I absolutely love that machine and it might be my favorite MacBook Pro ever. Also understand that it's 8 years old, but there is actually nothing wrong with it. On one hand, kinda upset, but on the other, I did get 8 years of OS support from it, so I guess I cannot be tooooo upset. I'll probably try to get Monterey setup eventually, but not in a rush to upgrade from Big Sur.

The 2016 rMBP however, I actually won't be upset at all when support drops for that, it's been the worst MacBook I have ever had.

Glad to see there are options for Monterey on older machines - agree with the comments that it's not "that old" and the hardware is not too different from those still supported (other than the nVidia GPU's)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.