macOS 12 Monterey on Unsupported Macs Thread

[laertemeira]

Hi friends! New chapter on my cMP4,1->5,1 with Monterey 12.4 + OCLP 0.4.7: upgraded processor to a x5690 and 32GB Samsung ECC RAM 1066MHz. I also swapped the SATA SSD by an XPG Gammix S11 Pro 1Tb.
The Mac was fully disassembled and cleaned, and the boards were cleaned and got a chemical bath too.
I refreshed oclp enabling NVMe Boot option (and also, disabling Feature unlock, since my machine stay yet with legacy BT and USBs) and cloned my Monterey disk from SATA to NVMe using disk utility and, after a boot and the Monterey checked out almost all installed apps, the system appears to be way more stable, without any freezing episodes.
System remain freezing on certain apps, like Notion and EpocCam (I think its more about legacy USB).

Next step maybe a USB3 board or even a thunderbolt 3... and BT too...

 

[hwojtek]

I refreshed oclp enabling NVMe Boot option

It's not for your computer if you followed the guides before. If you have 144.0 bootrom (part of Mojave installation, IIRC), your computer is capable of booting NVMe natively.

 

[laertemeira]

It's not for your computer if you followed the guides before. If you have 144.0 bootrom (part of Mojave installation, IIRC), your computer is capable of booting NVMe natively.

Thank you @hwojtek! Before check this option, the NVMe was shown as a external disk... My boot ROM is 540.120.3-6.

Maybe I need to do a Mojave install to update bootrom?

The nvme speed is far below the theoretical speed but I think I'm not using the best pcie adapter...

EDIT: ok, removed the nvme boot option and the boot works. I changed the nvme to slot #2 and it appears as external once more. Refresh oclp (without nvme boot option) and applying turns disk as internal. No performance increment on this slot, despite being 16x width.

 

[tsialex]

Thank you @hwojtek! Before check this option, the NVMe was shown as a external disk... My boot ROM is 540.120.3-6.

OS loader is not the BootROM version.

You have to boot native, without any spoofing to see your BootROM version. Most OpenCore implementations mask the BootROM version via spoofing, that's why you see 9999.999.999.999.999 for the SystemFirmware version.

Boot Mojave or High Sierra without any loader/OC/OCLP/etc and you will see the real BootROM version that is installed. Current one is 144.0.0.0.0.

Maybe I need to do a Mojave install to update bootrom?

The nvme speed is far below the theoretical speed but I think I'm not using the best pcie adapter...

EDIT: ok, removed the nvme boot option and the boot works. I changed the nvme to slot #2 and it appears as external once more. Refresh oclp (without nvme boot option) and applying turns disk as internal. No performance increment on this slot, despite being 16x width.

The M.2 connector of a NVMe blade is a miniaturized version of a PCIe x4 slot. Installing on a x8 or x16 won't make the blade any faster, since it will always use 4 PCIe lines or less.

The real life bandwidth that a MacPro5,1 PCIe v2.0 x4 slot have is ~1450MB/s. Even the best high end blades like 970PRO, won't go any faster without a PCIe switched adapter that convert the wide and slow PCIe v2.0 x16 of the Mac Pro slot 1 or 2 to fast and narrow PCIe v3.0 x4. With the right adapter, you can get ~3250MB/s from one high end blade and ~5900MB/s from two in RAID-0.

 

[hwojtek]

Thank you @hwojtek! Before check this option, the NVMe was shown as a external disk...

That's two different things, making PCIe NVMe disks look internal and booting from NVMe And just like @tsialex said, you're on the high side of speed anyway. My XPG 8200 Pro, arguably one of the faster NVMe drives available, doesn't get any faster using a simple PCIe adapter. If you want to push your drive to the limits, you need to employ something with a PCIe switch (Syba SI-PEX40129 using AS Media's ASM2824 chipset is a good example).

 

[TOM1211]

Updating to latest 12.5 rc (21G72) and patching working with oclp 4.8 no isssues .
MacBook Pro 15 mid 2014

 

[makra]

Updating to latest 12.5 rc (21G72) and patching working with oclp 4.8 no isssues .

Could you pls insert your hardware in your signature? Seems essential at the moment...

 

[Larsvonhier]

21G72 running on Mac Pro 5,1 (but with patch for TeraScale 2). So far so good, dual monitors work, legacy accel works.
edit: Also tried the GT630 (Kepler) card with OCLP 0.4.8, got the same login loop again after patching for accel (metal).
So, it still means OCLP devs to the rescue ;-//

 

[OKonnel]

Caution. Currently, 12.5 and OCLP (current 0.4.8 and older versions!) do not work properly with Kepler GPUs like the GT630 and 640M/650M. Once you patch for acceleration, you'll be stuck in a login-loop.
This has been reported here now for a couple of times, and the last known version of Monterey without that flaw was 12.5 beta 2 (or 3). Beta 4, 5 and RC are affected.

Try OCLP 0.4.5 to patch-root

regardless of architecture, the patch-root was not working on Monterey 12.5 RC with the latest versions, I asked to test on OCLP 0.4.5 because this is the only one that managed to recreate the preboot on my Air, I believe others that depend on the rebuild preboot cache should solve using this OCLP 0.4.5, if you see the documentation, you can see that they changed a lot in the patch-root in this version, making it more robust, but in OCLP 0.4.7 some changes were made, and it is not effective with the Monterey 12.5 RC. Thank you so much for trying and reporting the bug.

VERY IMPORTANT!
Dear friends, unfortunately the situation is very unfavorable with macOS 12.5 and for the Macs with nVidia graphics cards of "Kepler" serie.

The "Changelog.md" file of the latest OCLP 0.4.9 Night version explain that the Login screen loop problem has been solved and that version 12.5 now allows to access at user Home, however... without graphic acceleration!

The issue is serious and you have to know that @khronokernel knows him perfectly.
Khronokernel explained what happens and says that he is working to solve this great issue, hoping that it can be solved.
So, anyone with a "Kepler" type nVidia Graphics Card can read - indeed... must read - what the good Khronokernel explains very clearly at this link -> https://github.com/dortania/OpenCore-Legacy-Patcher/issues/1004

We all hope that a solution is found as soon as possible and that there are other good developers able to help Khronokernel.

 

[gw463]

MOLTO IMPORTANTE!
Cari amici, purtroppo la situazione è molto sfavorevole con macOS 12.5 e per i Mac con schede grafiche nVidia della serie "Kepler" .

Il file "Changelog.md" dell'ultima versione OCLP 0.4.9 Night spiega che il problema del loop della schermata di accesso è stato risolto e che la versione 12.5 ora consente di accedere alla Home dell'utente, tuttavia... senza accelerazione grafica !

Il problema è serio e devi sapere che @khronokernel lo conosce perfettamente.
Khronokernel ha spiegato cosa succede e dice che sta lavorando per risolvere questo grande problema, sperando che possa essere risolto.
Quindi, chiunque abbia una Scheda Grafica nVidia di tipo "Kepler" può leggere - anzi... deve leggere - ciò che il buon Khronokernel spiega molto chiaramente a questo link -> https://github.com/dortania/OpenCore-Legacy-Patcher/ problemi/1004

Ci auguriamo tutti che una soluzione venga trovata il prima possibile e che ci siano altri bravi sviluppatori in grado di aiutare Khronokernel.

I wanted to wish good luck to all the developers who are working to get the old Macs with Kepler board working again ..... I am stuck at 12.4 with my old 3.1 video Nvidia gtx680 and ........ I hope

 

[0134168]

12.5 is out.

 

[TOM1211]

If you have the MGXC2LL/A obviously you have two graphic options if you log in it defaults to the Iris pro but if you obviously disable power switching graphics you will get stuck in the log in loop with one click if you reboot with the power options unticked . Yet to try with oclp 4.9 . Obviously if you disable switching graphics after log in it seems fine ?.

Boots to black screen if power options switched off after log in.

Update: going back to OCLP 4.5 will get me back past the log in loop only because I set it just to the NVIDIA 750m card and rebooted which got it stuck using OCLP 4.5 seems to default the system back to lris pro using battery saver overriding my stupid change.

 

[Taipan]

私はカワセミ3を使って、全く問題がないようです。(I am using Kawasemi 3, and there doesn't seem to be any problem,)
https://www.monokakido.jp/ja/mac/
macOS Montereyに対応したバージョン 3.0.1 をリリース。(Version 3.0.1 has been released to ensure compatibility with macOS Monterey.) What hardware are you using? computer info, model number, etc, and what version of OCLP?

Sorry, but I shouldn‘t need any third party software to write Hiragana or Katakana, should I? I assume the software you mentioned does more than just converting my input?
I‘m using a Mac Pro 4,1 patched to 5,1 with some upgraded hardware like a WiFi/BT4.2 module, PCIe SATA-3 Adapter, USB3-card, Radeon RX580, Monterey 12.4 and OCLP 0.4.6.

 

[Sevenfeet]

I wanted to wish good luck to all the developers who are working to get the old Macs with Kepler board working again ..... I am stuck at 12.4 with my old 3.1 video Nvidia gtx680 and ........ I hope

Same boat here with my 3,1 + GTX 680. Hopefully a solution will be found. In the meantime, I'm upgrading all the rest of the elderly Macs in the house.

 

[steverae]

12.5 is out.

Perfect timing as I've just successfully flashed my HD7950 card to make it a Mac Edition card so I can now install 12.5 on the 5,1 without issue.

Installed now on my MacBook Pro 11,2, just waiting on the OCLP dev's to give us a solution for my iMac 13,2.
For the record - the release version is the same build number as RC2 macOS 12.5 (21G72)

 

[davidlv]

Sorry, but I shouldn‘t need any third party software to write Hiragana or Katakana, should I? I assume the software you mentioned does more than just converting my input?
I‘m using a Mac Pro 4,1 patched to 5,1 with some upgraded hardware like a WiFi/BT4.2 module, PCIe SATA-3 Adapter, USB3-card, Radeon RX580, Monterey 12.4 and OCLP 0.4.6.

Of course, everyone's experience is different, but it is well known here in Japan that the default Japanese input method is rather lame. The Kanji dictionary is limited and so are the options for the input method in Apple's implementation. I didn't know if you were not aware of that or not. I suggested that software in the hope that it would solve your issues, using the trial system they offer, which is very reasonable, just like the price. Of course, you shouldn't need any other software to write basic hiragana, katakana, or convert Romaji to Kanji. But it is Apple's Kotoeri we are talking about, the infamously lame Japanese input method. I used ATOK for a long time, but they switched to a subscription payment method and I bailed out. I find Kawasemi fine for my limited use in writing Japanese, and the dictionary is good too. The Kotoeri dictionary will often balk at even the easiest Kanji, the Chinese characters it should find easily but doesn't! Sorry if that reference confused you. Here in Japan, everyone in the publication industry has long ago given up completely on Apple's Kotoeri, which of course has produced alternatives like ATOK, Kawasemi and even Google's free Japanese Input Method. I believe all of those alternatives are better than Apple's solution. If you are having issues with Apple's software, you can find alternatives! Kawasemi works even under Monterey 12.5 on an old Mac running OpenCore Legacy Patcher.

 

[MarvenSmith28]

So I am on a 2012 Macbook Pro Retina 15" (10,1) that uses a Kepler graphics card and I had no issues whatsoever updating to macOS 12.5 today. I am not stuck in a login loop or anything else. I wonder whether I got lucky because I am not using the latest version of OpenCore Patcher? I am on 0.4.7 instead of 0.4.9. Anyone else experienced this?

 

[MacRumors3590]

So I am on a 2012 Macbook Pro Retina 15" (10,1) that uses a Kepler graphics card and I had no issues whatsoever updating to macOS 12.5 today. I am not stuck in a login loop or anything else. I wonder whether I got lucky because I am not using the latest version of OpenCore Patcher? I am on 0.4.7 instead of 0.4.9. Anyone else experienced this?

did you do the post patch?

 

[MarvenSmith28]

did you do the post patch?

Indeed, using OCP 0.4.7.

 

[adamrc]

I had OCP 0.4.9 on my Late 2012 iMac (13,1). The update to MacOS 12.5 initially went fine. It wasn’t until I installed the post patch that completely messed it all up. It will not boot at all now. It gets to the Apple loading screen on boot up and gets about 40% progress and just stops.

Any ideas on what I can do to get it up and running again? This will be the last time I update so quickly after an update is released.

 

[MarvenSmith28]

I had OCP 0.4.9 on my Late 2012 iMac (13,1). The update to MacOS 12.5 initially went fine. It wasn’t until I installed the post patch that completely messed it all up. It will not boot at all now. It gets to the Apple loading screen on boot up and gets about 40% progress and just stops.

Any ideas on what I can do to get it up and running again? This will be the last time I update so quickly after an update is released.

Sorry to hear that. I’m not sure but if you can revert back with a backup, you could try an older version of OCP like I did with 0.4.7. No guarantees but it worked in my case.

 

[RogueB]

So I am on a 2012 Macbook Pro Retina 15" (10,1) that uses a Kepler graphics card and I had no issues whatsoever updating to macOS 12.5 today. I am not stuck in a login loop or anything else. I wonder whether I got lucky because I am not using the latest version of OpenCore Patcher? I am on 0.4.7 instead of 0.4.9. Anyone else experienced this?

Would you mind posting detailed (from system report) descriptive of your graphic card and actual computer model number. It would allow for comparison between your successful 12.5 (final(?)) release installation, and other Kepler based machines(?)

 

[0134168]

So I am on a 2012 Macbook Pro Retina 15" (10,1) that uses a Kepler graphics card and I had no issues whatsoever updating to macOS 12.5 today. I am not stuck in a login loop or anything else. I wonder whether I got lucky because I am not using the latest version of OpenCore Patcher? I am on 0.4.7 instead of 0.4.9. Anyone else experienced this?

Dual GPU?

 

[Larsvonhier]

Sorry to hear that. I’m not sure but if you can revert back with a backup, you could try an older version of OCP like I did with 0.4.7. No guarantees but it worked in my case.

Can you send a screenshot with GPU info please? (About this Mac -> Graphics).
Thanks!

 

[steverae]

Dual GPU?

Tihs has been reported before regarding the dual GPUs in the retina MacBook 15" - Ive got a 11,2 13" 2015 Map with the intel iris graphics running 12.5 21G72 fine without issue but have had no luck at all on my 13,2 iMac with anything higher than 12.5 b2.
There is a big warning on the OCLP GitHub page - https://github.com/dortania/Opencore-Legacy-Patcher/releases warning not to upgrade to 12.5 release build using 0.4.9 and I know from experience 0.4.7 and 0.4.6 did not resolve this login loop (WindowServer crashing issue with the Kepler drivers) We have to wait patiently - it is being looking into via macOS 12.5: Nvidia Kepler and WindowServer crashing #1004