idk but take your query to https://discord.com/ >unsupported Macs better coverage may be avail. there?
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
After 2/3 days on Monterey with a cMP 3.1 and GTX 680, no perceptible slowdown compared to Catalina.
Just lost the programming functions of my Logitech MX Master due to the loss of bluetooth (planned). I have the original card, this will be corrected with an update of this card (links would be nice). The only problem is that I can't run SSE4.2 anymore, goodbye creative suite 2021/22, any solutions ?.
Thank you to all these wonderful developers who allow a 14 year old mac to work fine
Just lost the programming functions of my Logitech MX Master due to the loss of bluetooth (planned). I have the original card, this will be corrected with an update of this card (links would be nice). The only problem is that I can't run SSE4.2 anymore, goodbye creative suite 2021/22, any solutions ?.
Thank you to all these wonderful developers who allow a 14 year old mac to work fine
Hello
I have problem disabling NVRAM write protection , I make the correct settings and build and install on my efi , but csrutil status reports that protection is Enabled and commands to write is not permitted , anyone have this setting working for him ?
it's on my side or the problem from the OCLP itself ?
my setup : OCLP 0.4.1 , Macbook 11,3 Monterey 12.1
Thanks
I have problem disabling NVRAM write protection , I make the correct settings and build and install on my efi , but csrutil status reports that protection is Enabled and commands to write is not permitted , anyone have this setting working for him ?
it's on my side or the problem from the OCLP itself ?
my setup : OCLP 0.4.1 , Macbook 11,3 Monterey 12.1
Thanks
I made a mistake. I didn't test it carefully,I have two different MAC remote controls. The battery power is not enough. Without a good test, I take it for granted that I need to pair it again to use it
If the remote control has been paired before, it can be used normally on Monterey.
-----
I thought about it again. Originally, in order to prevent the two remote controls from interfering with each other, I used a single pairing with the Mac. Now I upgraded the Monterey. This restriction does not seem to exist. If the remote controls are not paired, they should also be used normally,Because they use infrared...
-----
There are still bugs
swinsian is ok, but the remote control can't control movist-pro2.8.1 now.
Last edited:
What do you mean by "anymore"? Do you mean SSE4.2 was working before with creative suite 2021/22 on your MacPro3,1? Describe that setup.
OCLP 0.4.1 has been released, GUI now includes in-app check for updates of the patcher.
Awesome. The developers/creators of OCLP do magnificent work and are highly inventive. Heartfelt thanks to them.
Awesome. The developers/creators of OCLP do magnificent work and are highly inventive. Heartfelt thanks to them.
Hi, hope someone will be able to help me out (I opened an Isue on OCLP Github but was told to use forums instead)
I don't know if this is a known issue but I'm currently testing macOS Monterey on my iMac 14,3. It is installed on an external ssd and works well. The problem is: I cannot update this version through my iMac:
I go to System Preferences, the download starts, prepares, then the Mac reboots and then things get complicated. If I hold the option key down, I see the "macOS Installer" volume. However, when I select the EFI Boot to use OCLP I cannot see this macOS Installer anymore (even if I press the space bar), so no possibility to install any update... I don't know it that's a known issue/limitation (wasn't able to find out) or if that could get fixed in the future?
I currently have Big Sur on my internal fusion drive (so that it works more "natively" without post-install patch) and wanted to test a little more Monterey before installing it on my main drive...
Thank you for your help :=)
I don't know if this is a known issue but I'm currently testing macOS Monterey on my iMac 14,3. It is installed on an external ssd and works well. The problem is: I cannot update this version through my iMac:
I go to System Preferences, the download starts, prepares, then the Mac reboots and then things get complicated. If I hold the option key down, I see the "macOS Installer" volume. However, when I select the EFI Boot to use OCLP I cannot see this macOS Installer anymore (even if I press the space bar), so no possibility to install any update... I don't know it that's a known issue/limitation (wasn't able to find out) or if that could get fixed in the future?
I currently have Big Sur on my internal fusion drive (so that it works more "natively" without post-install patch) and wanted to test a little more Monterey before installing it on my main drive...
Thank you for your help :=)
Did you copy EFI volume (made by OCLP) to the external disk where Monterey is installed?
No the OCLP EFI volume is on my internal drive. Do you think it is related ? I could try installing in on my external drive ?
I just think it's much more convenient, and no need to press option key at boot because you choose your boot volume once and forever. When update installs it's to be chosen automatically.
Have you checked the first post of this thread?
macOS 12 Monterey Full Installer Database. Download Directly from Apple!
Download macOS Monterey full installer with one click straight from Apple! Every version of Monterey Beta & Final available all in one place!!
mrmacintosh.com
Sorry, my mistake, think I scrolled too fast over the spoiler. Thank you
Just to say it works! Installing the UFI on the external drive now shows (and selects automatically) the macOS Installer to update! Thanks!
I mean that I cannot used CS Adobe after the 2020 because the next CS adobe 2021/2022 need SSE4.2. My very old cMP 3.1 use SSE4.1. I use OCLP 0.3.3 with Monterey 12.1. By the way, the standby mode works badly because I always hear the fans running.
About a USB3 expresscard (nanoTECH) again after a while.
The new OCLP 0.4.1 provides support for booting from USB3. And it works well in BigSur which is very useful, see post https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-30795183 .
An SSD with Monterey, connected via USB3, is correctly seen by OCLP, but then booting fails - has to fail, because it fails the same way when the SSD is on an on-board USB port and any USB storage medium (a memory stick e.g.) is connected to USB3. - A keyboard or mouse connected to USB3 work fine.
Attached is a verbose boot output which points to a missing NMI.
That is not a new problem for me. It happens with 12.0.1, 12.1, 12.2 betas, 12.2 RC. Tried with various OCLP versions. Feeding in some auxiliary power doesn't help. - It always works with 11.x.y.
Could be due to my specific nanoTECH card still. I know it works in Monterey for @macinfo, see post #3364.
If anyone else with a nanoTECH USB3 board (or similar with the FL1100 chipset) could confirm one way or the other, that would be great. If others see the problem as well I would follow up for a potential patch. A working USB3 will be even more useful now with 0.4.1’s booting capability.
The new OCLP 0.4.1 provides support for booting from USB3. And it works well in BigSur which is very useful, see post https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-30795183 .
An SSD with Monterey, connected via USB3, is correctly seen by OCLP, but then booting fails - has to fail, because it fails the same way when the SSD is on an on-board USB port and any USB storage medium (a memory stick e.g.) is connected to USB3. - A keyboard or mouse connected to USB3 work fine.
Attached is a verbose boot output which points to a missing NMI.
That is not a new problem for me. It happens with 12.0.1, 12.1, 12.2 betas, 12.2 RC. Tried with various OCLP versions. Feeding in some auxiliary power doesn't help. - It always works with 11.x.y.
Could be due to my specific nanoTECH card still. I know it works in Monterey for @macinfo, see post #3364.
If anyone else with a nanoTECH USB3 board (or similar with the FL1100 chipset) could confirm one way or the other, that would be great. If others see the problem as well I would follow up for a potential patch. A working USB3 will be even more useful now with 0.4.1’s booting capability.
Attachments
Last edited:
I just ran OCLP 0.4.1 build & install on both the internal and external drives. I noticed after rebooting that there was no need to run post install patches. In the past I would have to run option 3 in order to get my screen resolution back from tiny to normal. With OCLP 0.4.1 this doesn't seem to be necessary any more.
Am I right, did something change?
Am I right, did something change?
Update to 12.2RC atop 12.1 OTA via OCLP_041TUI offline variant - everything intact. Runs as expected.
The Dreaded $50 Mini strikes, again.
?
The Dreaded $50 Mini strikes, again.
?
Last edited:
It´s not posible to boot from USB pcie. In fact, you are booting from OC.
Using your logic, it's not booting from OC. Its booting from firmware which loads EFI drivers from firmware then loads OC which loads more EFI drivers from EFI partition. What difference does it make where the drivers are loaded from (firmware or EFI)? The point is that macOS can now be booted from USB pcie.
The loading of OC happens after the Startup Manager would load (when you hold the option key at boot) but this can be changed by having firmware load the drivers earlier from EFI partition using the Driver#### mechanism. Maybe this mechanism doesn't work on some newer Macs but I know it at least works on the MacPro3,1. I would like to see OpenCore split into parts where some of its drivers are loaded by the Driver#### mechanism so that the Startup Manager can benefit from those drivers (to enable boot screen for Startup Manager to allow bypassing OpenCore). I already have the apfs driver working this way (or at least the apfs.efi driver from Apple). Other useful drivers for Startup Manager would be the Screenshot driver, NVMe driver, these new USB drivers, UGA on GOP driver, Thunderbolt driver (to support Thunderbolt booting one day), ...
Thank you both for discussing terminology and mechanism of booting via OC(LP).
I looked at it end-to-end (hardwarewise), ie SSD connected to USB3 on pcie, to macOS user interface working with that disk. It works when BigSur is on the disk, fails with Monterey on the disk.
I forgot to mention: when running Monterey, booted from an on-board USB or SATA, and then plugging any memory device into USB3 on pcie, macOS freezes after ~20sec. Hard for me to diagnose at this point, but it could well be a missing interrupt. And as I said, USB3 works fine with a mouse or keyboard connected to it. Should be something around the Monterey disk driver for XHCI. Or my card (unlikely as it works with BigSur).