Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Big Sur has extended SIP bits split into 2 sections. Specifically
csrutil disable and csrutil authenticated-root disable. OpenCore Patcher correctly shows you which bits you need to set including authenticated-root
i would like to install and try out the new mac os but im not very good at that could you help me?
show me please a correct config setting because I have this and that's the result in my previous post
EF0F0000(or 0xFEF) would be correct, ensure the variable is correctly applied by resetting NVRAM so OpenCore will repopulate csr-active-config with the updated value
Good thanks probably forget to reset NVRAM I will try then report
Last edited:
Hello everyone, we're proud to release OpenCore Legacy Patcher v0.1.7! And with it, work in progress macOS Monterey support!
Currently, Monterey support is very much in active development with many previously working hardware in Big Sur now broken. However, we've put great effort into restoring these patches with the aid of @jackluke, EduCovas, @khronokernel, and I by re-introducing Intel HD 4000 iGPU support.
Please do note that with macOS Monterey, Intel HD 4000 iGPU users will need to have their root volumes patched to achieve full acceleration meaning no more FileVault or SIP support. 2012 iMacs with supported Nvidia GPUs are however excluded as they can have their internal iGPUs disabled with little consequence.
Additionally, other legacy hardware has been dropped from Monterey. This includes the following hardware:
Additionally, we've also added FireWire boot support, courtesy of @internetzel's testing, as well as TeraScale 2 Acceleration in Big Sur, courtesy of @ASentientBot!
We've got quite a jam-packed build, hope everyone enjoys the new release!
Currently, Monterey support is very much in active development with many previously working hardware in Big Sur now broken. However, we've put great effort into restoring these patches with the aid of @jackluke, EduCovas, @khronokernel, and I by re-introducing Intel HD 4000 iGPU support.
Please do note that with macOS Monterey, Intel HD 4000 iGPU users will need to have their root volumes patched to achieve full acceleration meaning no more FileVault or SIP support. 2012 iMacs with supported Nvidia GPUs are however excluded as they can have their internal iGPUs disabled with little consequence.
Additionally, other legacy hardware has been dropped from Monterey. This includes the following hardware:
- All BRCM2046-based Bluetooth cards no longer function
- All Mojave and older era wireless Cards no long function
- BCM94322, BCM94328, and Atheros series included
- BCM943224, BCM94331, BCM94360 and BCM943602 still work great with OpenCore Legacy Patcher
Additionally, we've also added FireWire boot support, courtesy of @internetzel's testing, as well as TeraScale 2 Acceleration in Big Sur, courtesy of @ASentientBot!
We've got quite a jam-packed build, hope everyone enjoys the new release!
great news you guys are awsome sadly i dont know how to do root volumes patch or anything
Hi @mogaleksej!
I didn't do anything strange:
- I downloaded the latest build of OpencCore Legacy Patcher (note that the final build 0.1.7 has just been released);
- I started OpencCore Legacy Patcher
- I clicked 1 to automatically create EFI Build
- I clicked 2 to automatically install the OC EFI Build into the EFI partition of the internal disk on which I have the System.
- after selecting the Disk with the System (note that you can use any other disk, but if you don't know what to do don't do it ...), you are asked to select the EFI Partition of the chosen disk and generally have to press 1
- at this point I was asked for the password.
- I entered my Mac password, I pressed enter and nothing else needs to be done.
AFTER these steps, ATTENTION.
- you have to restart the Mac and at the sound of the Gong you have to press and hold the ALT-Option key.
- the disks or the disk appear and the EFI-Boot icon is also displayed.
- select the EFI-Boot icon, press Enter and from that moment on your system will automatically recognize it and the prohibition sign will no longer appear.
Tips:
If then, from System Preferences, you select the Startup Disk, you will also get a faster boot.
Confirm Sucseed OC Legacy Patcher release 0.1.7 HP ProBook 6570b Ivy Bridge HD 4000 Fully working
Thanks @khronokernel @jackluke @PG7 @ASentientBot @dosdude1 @dhinakg
You guys doing a great JOB!
Thanks @khronokernel @jackluke @PG7 @ASentientBot @dosdude1 @dhinakg
You guys doing a great JOB!
I just made another test non metal Monterey, it's an iMac9,1 , of course no graphics acceleration, no wifi and no bluetooth, so nothing new, but for many already know, this is a legacy USB non APFS Mac, booting an external USB legacy root device, I know and tested OC and OCLP for booting legacy USB machines, but in this case I used an OC setup with apfs driver and without patches, instead I applied my previous BigSurFixes legacy USB patches to this Monterey and they worked.
From picture can notice that brightness control doesn't work even if are installed the ASentientBot Nvidia Tesla framebuffer fixes (also nvenet.kext works for ethernet), probably because this is a legacy monitorpanel, also webcam doesn't turn on the green led (I guess linked to graphics patches or IOHID).
For legacy USB patches (that I made on BigSurFixes) thanks to:
@parrotgeek1 (LegacyUSBInjector.kext) , @Syncretic (for pointing where merge the legacy USB properties) and @ASentientBot (IOHIDFamily to avoid booting through CMD+S and exit).
From picture can notice that brightness control doesn't work even if are installed the ASentientBot Nvidia Tesla framebuffer fixes (also nvenet.kext works for ethernet), probably because this is a legacy monitorpanel, also webcam doesn't turn on the green led (I guess linked to graphics patches or IOHID).
For legacy USB patches (that I made on BigSurFixes) thanks to:
@parrotgeek1 (LegacyUSBInjector.kext) , @Syncretic (for pointing where merge the legacy USB properties) and @ASentientBot (IOHIDFamily to avoid booting through CMD+S and exit).
Attachments
Running macOS Monterey thanks to OpenCore Patcher Legacy.
Thanks guys, You are awesome.
I noticed that maybe we will have to bring more parts of Big Sur Kexts to Monterey
Mainly things that use graphics, like PhotoBooth.
MacBook Air 2012 11" 4GB RAM
SSD 120GB External - Kingston
Thanks guys, You are awesome.
I noticed that maybe we will have to bring more parts of Big Sur Kexts to Monterey
Mainly things that use graphics, like PhotoBooth.
MacBook Air 2012 11" 4GB RAM
SSD 120GB External - Kingston
Attachments
don’t worry, my machine is same with you. i will try first and let you know later. i think should be ok.
So during some tests EduCovas on our Discord noticed that enabling FileVault on a 2012 MacBook Pro in Monterey would crash the system. Originally we believed perhaps it was due to the modified root volume however after further inspection it seems Apple now has an AVX2.0 requirement on FileVault.
This seems to be entirely a bug on Apple's end as the Trash Can Mac Pro (MacPro6,1) doesn't support AVX2.0 and would trash as well. Anyone with Trash Can, I highly recommend verifying as well as reporting to Apple this bug. We would greatly appreciate Apple knowing and fixing as soon as possible
This seems to be entirely a bug on Apple's end as the Trash Can Mac Pro (MacPro6,1) doesn't support AVX2.0 and would trash as well. Anyone with Trash Can, I highly recommend verifying as well as reporting to Apple this bug. We would greatly appreciate Apple knowing and fixing as soon as possible
Additionally regarding Bluetooth support on older machines, it seems I glossed over a few missing firmwares. Apparently Monterey dropped all 2011 and older Bluetooth modules, not just BRCM2046. 2012+ machines should be fine (MacPro5,1 not included, needs upgraded bluetooth as well)
Following Firmware Files are missing, should be easy for users to match device IDs off file name:
Apple really trying to clean up legacy hardware support with macOS Monterey, understandable as they haven't supported these machines since High Sierra (or Mojave for the MacPro5,1) however quite unfortunate as this adds more work onto our plate as community developers. Will continue researching this issue
Also note that all Apple branded BRCM20702 are still supported. Firmware dropped seemed to be modules Apple didn't use at first glance (do correct me if I'm wrong)
Edit: 2012 MacBook Pros in fact do use the 20702_821D.dfu firmware, Apple already killing the 2012 series it seems
Following Firmware Files are missing, should be easy for users to match device IDs off file name:
Code:
* 2046_820F.dfu
* 2046_8210.dfu
* 2046_8213.dfu
* 2046_8215.dfu
* 2046_8216.dfu
* 2046_8217.dfu
* 2070_821A.dfu
* 2070_821B.dfu
* 2070_8218.dfu
* 20702_821D.dfu
* 20702_821F.dfu
* 20702_828A.dfu
* 20702_828B.dfu
* 20702_828C.dfu
* 20702_8281.dfu
* 20702_8286.dfuAlso note that all Apple branded BRCM20702 are still supported. Firmware dropped seemed to be modules Apple didn't use at first glance (do correct me if I'm wrong)
Edit: 2012 MacBook Pros in fact do use the 20702_821D.dfu firmware, Apple already killing the 2012 series it seems
Last edited:
I guess this means if the GPU fails in one of my 2011 iMacs and I decide to get it repaired I'll need to get the wifi/bluetooth card replaced with a newer one at the same time. Though using ethernet and USB bluetooth adapter for 3rd party keyboard and mouse, internal bluetooth and wifi aren't critical so if the Terascale 2 patches end up coming to OCLP for Monterey it may not be a deal breaker to stop me from trying Monterey.
I would also like to mention this is still beta 1 and only a week has passed since we've had the betas in our hand. I seem to be the main developer (at least publicly) looking into Bluetooth and Wireless support for legacy as well as juggling the many other concerns in Monterey and our Patcher (OpenCore Legacy Patcher) so the speed at which I can resolve all these different issues is limiting.
If you plan to invest in new hardware, I encourage everyone to hold off until macOS Monterey's official release this fall. Gives a much better idea as to where we stand with patch sets as well as gives other developers time to research and publish findings and hopefully fixes similar to our 5 day long HD 4000 iGPU acceleration adventure on our discord last week. Jackluke, DhinakG, ASentientBot are all working behind the scenes and on our discord tirelessly, though don't expect a quick breakthrough like we did with HD 4000 ;p
Big Sur is still running great on these machines, and many of the user-facing changes in Monterey are pretty minor overall. So try to hold off
Happy to report my 2012 13" MacBook Pro non-retina HD4000 graphics accelaration works, newly released OCLP 0.17 used. Thanks to everyone involved.
Last edited:
Much appreciated. Thank you v. much from a current user of OCLP on 2012 macmini, with HD 4000.
Understand. I am happily running Big Sur and will look forward to when Monterey is officially released to the public. By that time, I would think we can OCLP it without any dramas.
I am not keen to run Beta OS on my workhorse home server.