Bluetooth is pooched as well. This cMP has the updated BT4LE and Wifi card from a later iMac that was working fine in 11.5 beta 3 and 12.0 beta 1 but is now MIA.
Cannot be switched on. WiFi and Ethernet are working OK.
Sytem Infomation Hardware Bluetooth shows this:
To eat my own dogfood, fixed the missing BT and Audio In/Out problems by reinstalling the EFI files from the 0.2.2 Patcher to the internal SSD. It was booting normally from the EFI on the internal SSD without an USB EFI booter, but that EFI was quite old from 0.1.2 or so. A new EFI install to the internal SSD was the answer. Airplay to Apple TVs also works now.
Here is an interesting Monterey problem.
I just installed a flashed (GC-Titan-Ridge-V2.0-Mod-NVM50-CaseySJ.bin) Titan-Ridge Thunderbolt 3 card (with pins 1 to 3 jumpered) in a classic Mac Pro 3,1 running Monterey 12 beta-2 and booting using OCLP 0.2.2.
It seems to be working and shows up in the System Information hardware profiles for Thunderbolt/USB4 and PCI.
Additionally, if I use a Thunderbolt cable to connect to a MacBook Air 2015 (supported) running the same 12.0 beta-2 but booted in Thunderbolt target mode, the MBA IS listed under the Thunderbolt Device Tree.
If I disconnect the MacBook Air from the Thunderbolt cable, it disappears instantly from the cMP Device Tree, so it seems to be working.
HOWEVER, the drive (SSD) in the MacBook Air never mounts on the desktop of the cMP and neither Disk Utilities nor diskutil list show its presence. Finder Preferences is set to show external hard disks!
Any ideas?
I have the update for beta 2 in settings and it downloads but then my Mac restarts without updating the software. am I doing something wrong? I updated to beta 1 with legacy patcher.
You may need to break into the OC boot picker, e.g. hold ALT while booting to get into Mac picker and then select OC EFI boot option, or hold ESC while booting to get into OC picker directly. Once you've got into OC picker, you may have to manually select an Install/Update macOS boot option which is there, to coax the update to happen.
So just tested the beta 2 and noticed that apple already labelled it as "Install macOS Monterey" assigning the official product icon with the purple gradient vector image, rather than a true landscape as they did on Big Sur.
They also unlocked the "hello screensaver" to Intel cpus Mac (but it requires Metal) and of course also the M1 iMac initially exclusive wallpaper.
Then fixed the non metal login screen, that on non metal allows to use a custom Memoji but only static, its Animoji dynamic effect only works with Metal GPU.
Also for fun tried to fetch where all the offline resources for custom Memoji (you can make it also offline) and they are exactly here on PrivateFrameworks: AvatarKit and AvatarKitContent
Then some other a bit technical, they added a new dictionary key for the stage2 installer (macOS Installer):
<key>CleanUpSharedSupport</key>
<false/>
attached as UpdateOptions file example
and they schedule after stage1 installer in nvram these arguments:
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
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.
+ Does not support any form of graphics acceleration currently
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
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 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.
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 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 unsupported GPU
A: Currently the only unsupported GPU that could regain acceleration is with Intel's HD4000 iGPUs via OpenCore Legacy Patcher. Legacy OpenGL cards (ie. non-Metal) currently have no acceleration at all in Monterey. Please stay on macOS Big Sur or older until acceleration has been achieved. For users who wish to install the HD4000 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: With macOS Monterey, there is no working legacy acceleration patch sets. As of right now, only basic framebuffer and brightness control may be achieved, however proper animations and hardware acceleration is not available.
Understand no one can predict when there will be patch sets ready. 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 acceleration support in Monterey until next year at the minimum.
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.
Maybe a dumb question, but what would be the difference between me using this patcher to install Monterey on my cMp5,1 and just installing OpenCore 0.7.0 and spoofing my model to a 2019 MP in the config and THEN installing Monterey?
Hi everyone! How to fix this? I have installed Monterey B2, restored from Time Machine and then… Micropatcher booting results in failure(this is verbose from that) and booting with OCLP causes bootsplash to hang on 1/3. Before restoring of backup everything worked fine. I suspect that there is some sort of conflict between BS and MT services.
I am able to boot to single user mode.
You may need to break into the OC boot picker, e.g. hold ALT while booting to get into Mac picker and then select OC EFI boot option, or hold ESC while booting to get into OC picker directly. Once you've got into OC picker, you may have to manually select an Install/Update macOS boot option which is there, to coax the update to happen.
It is indeed necessary to restart with the option key, and in my case there were two restarts with macOS Installer, then two restarts without.
The first reboot happens when there are 12 minutes left in my case, in fact the remaining time goes up briefly to 13 minutes and then the reboot is done.
The second reboot is easier to anticipate because the remaining time decreases to zero before the reboot.
It is indeed necessary to restart with the option key, and in my case there were two restarts with macOS Installer, then two restarts without.
The first reboot happens when there are 12 minutes left in my case, in fact the remaining time goes up briefly to 13 minutes and then the reboot is done.
The second reboot is easier to anticipate because the remaining time decreases to zero before the reboot.
But it's also worth knowing that if OC is set up correctly, it should not be required:
OC must be your default boot option at the Mac boot picker
macOS should be the default boot option within the OC boot picker
You definitely need RequestBootVarRouting set to true in config.plist
Then, with a fair wind - I've done this, it definitely can (and should) work - the entire update can go through without needing any manual intervention.
But it's also worth knowing that if OC is set up correctly, it should not be required:
OC must be your default boot option at the Mac boot picker
macOS should be the default boot option within the OC boot picker
You definitely need RequestBootVarRouting set to true in config.plist
Then, with a fair wind - I've done this, it definitely can (and should) work - the entire update can go through without needing any manual intervention.
Good to know, thanks. But Monterey is not my main system, my main system is Catalina, and I don't want to change the EFI of the internal dd, because OpenCore is useless for Catalina and even if it's not incompatible, I'm afraid it will have unwanted effects under Catalina.
So I put OC on the EFI of the external dd, where I have Monterey. The disadvantage is that I have to press the option key every time I reboot and choose the OpenCore boot.
From within BigSur I did ran OpenCore patcher. Downloaded the installer using SoftwareUpdate within Settings.
No other issues, than Monterey installer did not progress because apparently not enough space for installation left. BigSur reported 80GB free though. Ran first aid from Disk Utility on Monterey USB, rebooted. Issue solved.
macOS 12 Beta 2 makes no difference in terms of performance/speed compared to macOS 11.4. It feels like a renamed BigSur after all. Bluetooth audio stutter issues are back, while playing YouTube videos (Safari) via Bosesoundlink. (Could be hardware related)
Would love to see an option being implemented to have the second screen available while an app runs in fullscreen mode on the first monitor.
Hi guys! Just finished updating my MBP 9,2 non-retina, HD4000 to macOS Monterey Beta 2 using the OCLP 0.2.2 GUI patcher. Just wanted to state that even though I have installed on June 7th the Monterey developer profile on my MBP, I am not seeing the updates on System Prefferences like it was suppose to... Since June 17th, I no longer have access to the developer downloads since I haven't renewed my subscription, so I can re-install the profile Anyone else seen this issue? Thank you guys for all your help and support!
Maybe a dumb question, but what would be the difference between me using this patcher to install Monterey on my cMp5,1 and just installing OpenCore 0.7.0 and spoofing my model to a 2019 MP in the config and THEN installing Monterey?
The difference is whatever kexts, patches and drivers OCLP sets up for you.
To compare them, you could do a clean install of OC from here https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/ , and just get that working - at least for Big Sur 11.2 or Catalina; then you could run OCLP and put the setup it produces somewhere else. Then you can compare the two configs, specifically the two config.plist files which you get from the two setups.
Thank you for that clarification, so this legacy patcher fetches the drivers and kexts for your model automatically.
I currently run Martin Lo’s OC 0.7.0 package to run Big Sur 11.2.3 on my cMp 5,1 (won’t be updating that beyond 11.2.3 as you pointed out; many issues). I might just wait for Martin to update his package to support Monterey for the 5,1
Having played around with beta 2 the most apparent issues over here are:
Safari is literally unusable. Constantly freezing up. Stops loading pages. Alternative: Firefox. No issues.
Bluetooth is unusable. Heavy audio stutter. Plus mouse and keyboard loosing connection repeatedly. Reset via command option click into the bluetooth icon in the menubar not available in this version. Keyboard strokes are being repeated numerous times. On the other hand once bluetooth audio is not being used, keyboard and mouse are not loosing the connection anymore.
- edited -
Reapplied OCP 0.2.2, removed bluetooth plists, rebooted. Both issues are solved for the time being.
Having played around with beta 2 the most apparent issues over here are:
Safari is literally unusable. Constantly freezing up. Stops loading pages. Alternative: Firefox. No issues.
Bluetooth is unusable. Heavy audio stutter. Plus mouse and keyboard loosing connection repeatedly. Reset via command option click into the bluetooth icon in the menubar not available in this version. Keyboard strokes are being repeated numerous times.
@bluetooth: Its really surprising and so unlike Apple, this is an ongoing issue ever since ElCapitan. Are they even interested in fixing this permanently? However, there is a possibility of bad hardware on my side. I'll try a bluetooth dongle. But hey, i am not the only one.
Bluetooth is pooched as well. This cMP has the updated BT4LE and Wifi card from a later iMac that was working fine in 11.5 beta 3 and 12.0 beta 1 but is now MIA.
Cannot be switched on. WiFi and Ethernet are working OK.
Sytem Infomation Hardware Bluetooth shows this:
Same here, initially: BT missing after beta2 update on cMP3,1.
Did NVRAM reset and re-installed 0.2.2 OCLP (which was already on that machine before 12b2 Monterey update).
BT shows up again and is usable.
Is there anyone who performed clean install of Monterey and restored Time Machine backup? Or installing from USB over BS installation? Does that work for someone?
Is there anyone who performed clean install of Monterey and restored Time Machine backup? Or installing from USB over BS installation? Does that work for someone?
Yeah, I meant Migration Assistant. It restores from TM backup.(results in Kernel Panic after reboot)
And reinstall with USB on top doesn’t work at all.
Yeah, I meant Migration Assistant. It restores from TM backup.(results in Kernel Panic after reboot)
And reinstall with USB on top doesn’t work at all.
Use OCLP 0.2.2 . Make bootable USB drive . Install OC on it. Boot with option then to EFI. Then install over existing BS. Should work. Read "readme" of OCLP.
Use OCLP 0.2.2 . Make bootable USB drive . Install OC on it. Boot with option then to EFI. Then install over existing BS. Should work. Read "readme" of OCLP.
Thanks! Will try. I was just getting error in half of the first stage.(Failed to prepare update or something, will post screenshot if it does not start) Clean installation worked.(Migration Assistand ruined system afterwards)
Anyone else seen this issue? Thank you guys for all your help and support!
