Hey thanks for the feedback @yukari , @air.man and @******* ! Very helpful. Bookmarked your tips.
Did you guys all disable the discrete AMD GPU with the tricks posted elsewhere in the forums before attempting installation? Or has anyone suppressed it via a utility like gfxcardstatus running in the background post-install? My GPU still works (repaired twice though and disabled except during system reboots).
When I first installed Catalina, I had to disable dGPU as it was broken. I used this:
1) prepare the install setup of catalina (using the dosdude1 patch): http://dosdude1.com/catalina/in an usb pendrive.
2) SMC reset and than nvram reset Command + alt + p + r
3) click on "command" "S" at the boot, and than type:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
reboot
I think you only need steps 2 and 3 then install Monterey using OCLP patch.
This thread will be dedicated to the discussion of running macOS 12.0 on unsupported Macs
At the time of writing, WWDC has wrapped up and Developer Seeds have been sent out. We're eagerly awaiting for all our community developers and enthusiasts to test out the new version of macOS
We will be expanding this thread with much more information as the day goes by including known issues as well as patcher support
macOS Monterey Compatibility
2016 and later MacBook
MacBook9,1
MacBook10,1
2015 and later MacBook Air
MacBookAir7,x
MacBookAir8,x
MacBookAir9,1
2015 and later MacBook Pro
MacBookPro11,4-5
MacBookPro12,1
MacBookPro13,x
MacBookPro14,x
MacBookPro15,x
MacBookPro16,x
2015 and later iMac
iMac16,x
iMac17,1
iMac18,x
iMac19,x
iMac20,x
2017 and later iMac Pro
iMacPro1,1
2014 and later Mac mini
Macmini7,1
Macmini8,1
2013 and later Mac Pro
MacPro6,1
MacPro7,1
Not officially supported in macOS Monterey, but most likely fully capable of running Monterey (details will be found in the patcher documentation)
2013 and 2014 MacBook Pro
MacBookPro11,1-3
2013 and 2014 MacBook Air
MacBookAir6,x
2015 MacBook
MacBook8,1
2014 and early 2015 iMac
iMac14,4
iMac15,1
* Not officially supported in macOS Big Sur, but are fully capable of running both Big Sur and Monterey with a Metal-compatible GPU and upgraded WiFi/BT card. Nvidia dGPU based systems need Kepler patches (Beta 7+)
+ Does not support any form of graphics acceleration currently
++ Catalina supported system capable of running Monterey with Kepler (Beta 7+) and/or HD4000 patches
Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
MacPro3,1 *
MacPro4,1 *
MacPro5,1 *
iMac7,1 +
iMac8,1 +
iMac9,1 +
iMac10,x +
iMac11,x *
iMac12,x *
iMac13,x ++
iMac14,1-3 ++
MacBookPro4,1 +
MacBookPro5,x +
MacBookPro6,x +
MacBookPro7,x +
MacBookPro8,x +
MacBookPro9,x ++
MacBookPro10,x ++
Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
MacBookAir2,1 +
MacBookAir3,x +
MacBookAir4,x +
MacBookAir5,x ++
MacBook5,1 +
Early-2009 or newer Mac Mini or white MacBook:
Macmini3,1 +
Macmini4,1 +
Macmini5,x +
Macmini6,x ++
MacBook5,2 +
MacBook6,1 +
MacBook7,1 +
MacBook8,1 ++
Early-2008 or newer Xserve:
Xserve2,1 *
Xserve3,1 *
2006-2007 Mac Pros, iMacs, MacBook Pros, and Mac Minis:
MacPro1,1
MacPro2,1
iMac4,1
iMac5,x
iMac6,1
MacBookPro1,1
MacBookPro2,1
MacBookPro3,1
Macmini1,1
Macmini2,1
— The 2007 iMac 7,1 is compatible with Catalina and potentially Big Sur if the CPU is upgraded to a Penryn-based Core 2 Duo, such as a T9300.
2006-2008 MacBooks:
MacBook1,1
MacBook2,1
MacBook3,1
MacBook4,1 (as with Mojave and Catalina, we'll be on our own here, but Big Sur will be running on this machine!)
2008 MacBook Air (MacBookAir 1,1)
All PowerPC-based Macs
All 68k-based Macs
Nvidia Kepler GPU drivers
Beta7 dropped Nvidia Kepler support. This is affecting all stock 2012/2013 Mac models with Nvidia GPU including iMacs and MacBookPro systems, MacPro3.1/4.1/5.1 with Nvidia PCI GPU cards, and all iMac Late 2009 - Mid 2011 which have been modded with a MXM Nvidia Kepler GPU.
OpenCore Legacy Patcher has re-added support for these systems in v0.2.5
Intel HD 4000 drivers
Compared to macOS Big Sur, macOS Monterey has dropped support for Intel's Ivy Bridge Graphics. This means laptops with Intel HD 4000 GPUs will no longer have graphics acceleration such as the Macmini6,x, MacBookAir5,x, MacBookPro9,x and MacBookPro10,x
OpenCore Legacy Patcher has re-added support for these GPUs in v0.1.7
BCM94322, BCM94328 and Atheros drivers currently can't be re-added currently
Models included:
iMac12,x and older
Macmini3,1 and older
MacBook5,x and older
MacBookAir2,1 and older
MacBookPro7,1 and older (6,x excluded)
MacPro5,1 and older
BCM943224, BCM94331, BCM94360 and BCM943602 still function correctly with OpenCore Legacy Patcher
Installing macOS Monterey on an unsupported Mac Q: How do I determine what Mac model I have?
A: To determine your Mac's SMBIOS model identifier, simply run the below command in Terminal:
Q: How do I prepare my Mac?
A: Install the latest firmware release you can get for your Mac. All system pre 2012 do not receive any new updates. Install the lastest High Sierra or El Capitan (pre 2009) version to force your old Mac to get the firmware update.
All Macs 2012+ may still receive updates with Catalina until Summer 2022 and Big Sur until 2023. The most easy way to get this still upcoming updates is having a small Catalina/Big Sur installation on a separate APFS container on the internal disk and update this installation on a regular basis.
Q: How do I download macOS Monterey?
A: The easiest way is to use tools such as gibMacOS which can download macOS Monterey InstallAssistant packages directly from Apple.
Q: How to create a USB installer after downloading the InstallAssistant package?
A: Install the package, it creates an app named Install macOS Monterey in your applications folder. Create the USB installer following this official Apple guide.
Q: How can I use this installer on my unsupported Mac?
A:Before hitting the download button of the patcher tool (see below) please check OpenCore legacy Patcher's documentation. It contains a support statement about unsupported Macs running Monterey, too.
Q: Where/how can I download a patcher tool?
A: Currently there is only one patcher that will soon be supporting macOS 12, Monterey being OpenCore Legacy Patcher. As time goes on, we expect many more developers to join in with their own implementations of the patching process:
OpenCore Legacy Patcher by @khronokernel and @dhinakg is a completely different approach compared to older patcher methods based on OpenCore. This is currently the only option offering system updates via Apple software update like all supported Macs as well as Intel HD4000 iGPU and NVIDIA Kepler acceleration. While the preparation uses a simple GUI the Monterey installation and updating happens in the same way as on supported systems via System Preferences.
Supports macOS 10.9, Mavericks and later to run.
Supports macOS 10.7, Lion and later if Python3 is installed manually.
Q: How can I enable acceleration on my newly unsupported metal GPU?
A: Currently one can regain acceleration for both the Intel's HD4000 iGPUs and the NVIDIA Kepler dGPU via OpenCore Legacy Patcher. For users who wish to install the HD4000/Kepler acceleration patches on non-OpenCore Legacy Patcher machines see here: How to Root Patch with non-OpenCore Legacy Patcher Macs/Hackintoshes
Q: When can we expect OpenGL/non-Metal GPU Acceleration?
A: Starting with OCLP version 0.2.5 legacy OpenGL/non-Metal acceleration for Monterey has been implemented.
Please understand no one can predict when there will be patch sets ready or if current glitches can or will ever be resolved. Remember that it took over 300 days from Big Sur's unveiling to achieve public acceleration for non-Metal GPUs. And with TeraScale 2 acceleration, this took almost 3 years to achieve public acceleration. So be patient as developers are hard at work, however expect no error free support in Monterey. Additionally most applications rely more and more on Metal GPU features. Such apps may cause just a feature loss or will completely fail on non-Metal system. This will never change and the only way out is changing the GPU (iMac Late 2009-Mid 2011 and MacPro systems) with a Metal compatible one or buying a new Mac.
Please remember it is highly suggested that you have a backup in place before installing new system software on your main devices, overwriting any stable releases.
Apple and all patch developers are not responsible for any potential damage or data loss caused by using pre-release software or unofficial support patches. Please use at your own risk.
Are you installing to the internal drive, or an external USB drive? Also need to know what machine you are using, and from what version of macOS did you upgrade to Monterey? I assume you are using OCLP, correct?
Does it send you a message when you try to log in? This hasn't happened to me, but any information you can provide will be useful.
In my case, I have to login again when I switch from running macOS 12 on my main drive to macOS 10 on the external drive. Usually have to provide two passwords, one for my iCloud account, and one for my local machine user ID. Are you sure you're providing the right password(s)?
As of this post, I am currently running my MBP 15" 2014 on Big Sur installed on an external SSD/enclosure with the intent of installing Monterey with OCLP. I've done the same last week (Big Sur on External, Migrated my drive, patched, then installed Monterey, but, it got stuck on a startup loop. I fresh installed Moneterey on that same drive (thereby deleting the migrated system/data), but at that point, it got stuck on Startup/Apple logo.
This morning, I tried starting up from the external (with Monterey), the startup got stuck at 30% progress, but I heard an audio over my earphones (wasn't wearing mine last week while doing installation), the voice prompt talking about Voice Over and setting up the Mac with the keyboard.
I suppose the system has fully booted to the setup window (as the case when I installed Big Sur earlier), but the display wasn't changing for some reason. I've been reading up on OCLP boot process, but my brain is a little bit fried, and with the little coding I know, it's a bit too technical for me to follow.
As of this post, I am currently running my MBP 15" 2014 on Big Sur installed on an external SSD/enclosure with the intent of installing Monterey with OCLP. I've done the same last week (Big Sur on External, Migrated my drive, patched, then installed Monterey, but, it got stuck on a startup loop. I fresh installed Moneterey on that same drive (thereby deleting the migrated system/data), but at that point, it got stuck on Startup/Apple logo.
This morning, I tried starting up from the external (with Monterey), the startup got stuck at 30% progress, but I heard an audio over my earphones (wasn't wearing mine last week while doing installation), the voice prompt talking about Voice Over and setting up the Mac with the keyboard.
I suppose the system has fully booted to the setup window (as the case when I installed Big Sur earlier), but the display wasn't changing for some reason. I've been reading up on OCLP boot process, but my brain is a little bit fried, and with the little coding I know, it's a bit too technical for me to follow.
As of this post, I am currently running my MBP 15" 2014 on Big Sur installed on an external SSD/enclosure with the intent of installing Monterey with OCLP. I've done the same last week (Big Sur on External, Migrated my drive, patched, then installed Monterey, but, it got stuck on a startup loop. I fresh installed Moneterey on that same drive (thereby deleting the migrated system/data), but at that point, it got stuck on Startup/Apple logo.
This morning, I tried starting up from the external (with Monterey), the startup got stuck at 30% progress, but I heard an audio over my earphones (wasn't wearing mine last week while doing installation), the voice prompt talking about Voice Over and setting up the Mac with the keyboard.
I suppose the system has fully booted to the setup window (as the case when I installed Big Sur earlier), but the display wasn't changing for some reason. I've been reading up on OCLP boot process, but my brain is a little bit fried, and with the little coding I know, it's a bit too technical for me to follow.
Some problems I realized after installing Monterey 12.2 release with OCLP 0.4.1 final on my White MacBook 6,1:
After appliying post-install patches for nVidia graphics card non-Metal acceleration there are graphical glitches in the Control Center sliders for brightness and volume. Activating the "Beta Blur" options in OCLP have no effect and before patching the sliders are displayed correctly.
Login screen after booting up will show the wrong keyboard layout language although the correct layout is used. Curiously the correct layout is shown on login screen at wakeup from standby.
Wake up from hibernation (suspend-to-disk) returns to login screen a second time after entering password successfully. After second login sometimes the system freezes/reboots or will take a much longer time and system is slower.
I haven't found any other problems so far - everything else is working! I will test new Monterey 12.3 beta with OCLP 0.4.2 nightly and report back...👍 More feedback after updating to Monterey 12.3 beta with "sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/" (thanks to @K two for this one) and actual OCLP 0.4.2 beta:
Graphical glitches in Control Center still there with post-install non-Metal acceleration patch and no improvements even with "defaults write -g ASB_BlurBeta -bool true / defaults write -g ASB_BlurOverride -float 30".
The whole system is much slower and lagging now - no such behavior before with Monterey 12.2 final release. Perhaps the delta update from 12.2 final to 12.3 beta has some bugs with the OCLP setup?!
@OllieW, did you solve the graphic glitch of the Control Center? My sliders are a mess like in your pictures. I got Monterey 12.2.1 and oclp 0.4.2 on a 17" MBP late 2011 using the integrated Intel HD3000. The other gpu is fried. Post-install patches are in place (AMD TeraScale 2 and Intel Sandy Bridge). "Beta Blur" is activated. Cheers
If my Mac Pro 4,1 (flashed to 5,1) reports its Wi-Fi assembly as Broadcom BCM43xx 1.0 (5.106.98.102.30), that means the best I can do without a hardware update is Catalina, right? I can’t get Big Sur or Monterey? And would my Bluetooth cut out, too?
Oh, and any word on tricking OS X to let us install the nVidia web driver in Mojave or above yet?
I was interested in upgrading my 2012 MBA from Big Sur to Monterey, and unfortunately, the new OCLP 0.4.3 release seems to be the last regular release for a while.
The Ivy Bridge GPUs are not supported anymore on Monterey, so I would need to use their post-install volume patches. Are these patches specific for the currently available Monterey releases? For example, would this specific 0.4.3 patcher be able to patch the GPU driver for a future Monterey 12.4 release, or is there a risk that I would be stuck with 12.3 for an undetermined time?
I was interested in upgrading my 2012 MBA from Big Sur to Monterey, and unfortunately, the new OCLP 0.4.3 release seems to be the last regular release for a while.
The Ivy Bridge GPUs are not supported anymore on Monterey, so I would need to use their post-install volume patches. Are these patches specific for the currently available Monterey releases? For example, would this specific 0.4.3 patcher be able to patch the GPU driver for a future Monterey 12.4 release, or is there a risk that I would be stuck with 12.3 for an undetermined time?
Check the release notes of all OCLP releases starting last Summer when the patches have been published and search if there have been changes. Happy reading!
Anyway, I installed OCLP back then with 0.3.1, and I gather from the release notes that Universal Control support has been improved in 0.4.2:
Add Universal Control support for Monterey native Macs
Applicable for Haswell/Broadwell
Requires macOS 12.3 or newer
My Mac is Haswell, but not "Monterey native"; it's a MacBookPro11,2. So I'm not quite sure it applies?
Anyway, I downloaded the GUI patcher and hit "Post Install Root Patch". However, that one says "No patches found". Do I need to first un-apply the patches (I don't think I ever applied any in the first place, but I'm not entirely sure)? Do I need to re-build OpenCore?
I've re-built OpenCore, now at 0.4.3, and Universal Control… I'm not sure. The Universal Control… button shows up, as it did before, so I'm assuming part of macOS thinks it should work? But it doesn't seem to.
(Maybe the release notes are saying "if your Mac natively supports Monterey, but not Universal Control, we're patching it to add UC". Mine doesn't natively support Monterey. But it does have Haswell…)
Is anyone having some graphic problems with the Music app? If I go to the Explore tab, the first row containing big images are low resolution (?). Same problem with playlists containing custom artwork.
Also in the listen tab the range of color background in the titles and description seems to be off.
If my Mac Pro 4,1 (flashed to 5,1) reports its Wi-Fi assembly as Broadcom BCM43xx 1.0 (5.106.98.102.30), that means the best I can do without a hardware update is Catalina, right? I can’t get Big Sur or Monterey? And would my Bluetooth cut out, too?
My retina MBP 10,1 reports the same card and has worked perfectly for many months. I was gonna upgrade it to a faster card but I don't use wifi on that m/c so no point really. Bluetooth is solid, initially had to reset it sometimes but that problem has gone away. Here's what the system report picks up:
I was interested in upgrading my 2012 MBA from Big Sur to Monterey, and unfortunately, the new OCLP 0.4.3 release seems to be the last regular release for a while.
The Ivy Bridge GPUs are not supported anymore on Monterey, so I would need to use their post-install volume patches. Are these patches specific for the currently available Monterey releases? For example, would this specific 0.4.3 patcher be able to patch the GPU driver for a future Monterey 12.4 release, or is there a risk that I would be stuck with 12.3 for an undetermined time?
The basic idea of using the HD 4000 drivers from Big Sur should keep working. Then there have been various other fixes to things that didn't quite work even with this, as @Ausdauersportler mentions.
IMHO it is unlikely (though not completely impossible) that the basic patching method will stop working with Monterey, more possible that one or other of the small feature fixes could stop working, or even that another one might be needed.
Bookmarked your tips.
