Apple just released Monterey 12.7.2, build is 21G1974.
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.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thanks, I did already add the kexts you mentioned, but wasn't able to make the changes to config.plist. No matter what I change in the plist, booting is broken afterwards.
OTA updates seem to be working just fine. I just updated (OTA) to todays release of Monterey, and got several App Store updates.
I'm pretty irritated at the moment. Any change I make to the config breaks booting. If I could just get apple services to work. I’d call it a day.
Last edited:
I just updated opencore 0.9.7 and updated MacOS 12.7.2 using method 2
I couldn't do it on the first try: after downloading the update on the very first reboot - after a black screen I got a black screen with random green rectangles instead of OC boot picker with MacOS installer option
The computer immediately booted into 12.7.1
I remembered that I have a Logitech wireless mouse connected to the front USB (
I disconnected the mouse receiver and ran the update again without changing anything
in this case, without connected USB devices, the update is done as usual.
I try to ensure that nothing else that Apple doesn’t like is connected
I just forgot to turn it off today
EDITED
While I was writing this post, for the first time since Monterand, my computer froze and rebooted itself
At the same time, after downloading opencore, I lost the recovery and Macos options - only Windows remained
The thing is that I have two SATA disks with opencore and Windows
and only these discs remain available (Apparently the nvme controller has crashed)
but I have Macos on NVME
Right now, while I’m writing, I’ve been watching all sorts of MDS and Mdworker processes for 20 minutes
Tomorrow I'll see who the culprit is - OC 0.9.7 or macOS 12.7.2
P.S.
looked at the crash report
System crash caused by online Google translator
Maybe google still doesn’t know how to work with the updated Safari?
I couldn't do it on the first try: after downloading the update on the very first reboot - after a black screen I got a black screen with random green rectangles instead of OC boot picker with MacOS installer option
The computer immediately booted into 12.7.1
I remembered that I have a Logitech wireless mouse connected to the front USB (
I disconnected the mouse receiver and ran the update again without changing anything
in this case, without connected USB devices, the update is done as usual.
I try to ensure that nothing else that Apple doesn’t like is connected
I just forgot to turn it off today
EDITED
While I was writing this post, for the first time since Monterand, my computer froze and rebooted itself
At the same time, after downloading opencore, I lost the recovery and Macos options - only Windows remained
The thing is that I have two SATA disks with opencore and Windows
and only these discs remain available (Apparently the nvme controller has crashed)
but I have Macos on NVME
Right now, while I’m writing, I’ve been watching all sorts of MDS and Mdworker processes for 20 minutes
Tomorrow I'll see who the culprit is - OC 0.9.7 or macOS 12.7.2
P.S.
looked at the crash report
System crash caused by online Google translator
Maybe google still doesn’t know how to work with the updated Safari?
Post your new config with the required changes and I'll take a look. Also, if your Mac Pro has two processors, you'll need to make sure to add AppleMCEReporterDisabler (as mentioned in the guide).
@crjackson2134 your config looks good. I'm really surprised your Monterey installation isn't booting. Can you confirm that if you add the VMM flag to this very config, your installation will boot. Also, just to make sure: It looks like your graphics card is installed in Slot 2. Is that right?
The only possibility I see config-wise is disabling GopBurstMode and setting SetApfsTrimTimeout to 0. These settings have caused booting issues in the past. Failing that, I would try creating a bootable Monterey installer and verify that booting it through OC with your config is possible.
The only possibility I see config-wise is disabling GopBurstMode and setting SetApfsTrimTimeout to 0. These settings have caused booting issues in the past. Failing that, I would try creating a bootable Monterey installer and verify that booting it through OC with your config is possible.
Last edited:
Yes, absolutely! If I could use Apple Services with the VMM flag enabled, I'd stop right here. As compared to Catalina, I like the fresher look of Monterey, but it's looking like that's not going to work for me.
When I get the energy to tinker some more, and see about making a USB installer and starting over. I'll have to read-up and see how to do that on an incompatible machine.
These settings make no difference at all.
Booted up and typing this now based on the config.plist I uploaded, just by enabling VMM.
Last edited:
Given that this is your first foray into OC, did you by any chance update a patched (dosdude1) installation of Catalina to Monterey? This can be problematic.
No, I started with a fresh Mojave install on an unused drive (NVMe).
I'm trying how to figure out how to do an OC install of Monterey on an empty drive. Is that even possible with a USB thumbdrive, order I need to make another clean install of Mojave and build there again? I don't see that as being productive really, since that's what I did to begin with.
Yes, this is certainly possible: First, create a USB installer from a full installer. Boot the installer through OC by selecting it in the OC boot picker. Use Disk Utility in the installer to format your Monterey volume (just the volume, not the entire device, as that will get rid of your OC installation if it is on that disk). Finally, install Monterey to the newly formatted volume. If you are going to do this, I would suggest adopting method 2 in the guide (see macOS) to avoid having to play with the VMM flag. Good luck!
Doing that now...
Okay, OC boot picker currently doesn't appear on my screen. Do I hold the esc-key as it's booting to get the OC boot-picker, or should I change some settings 1st?
I'll review that section again.
Currently, FirmwareFeatures has a data string entered. So leave that there and set UpdateNVRAM <true/>?
Last edited:
You can do that. You can also keep ShowPicker=true and Timeout=10.
Yes. You want those “updated” firmware features in NVRAM. And in addition to hybridization (changed board ID, which you already have), you also want SecureBootModel=Default.
Please forgive me if I didn't post in the right OCLP.
I having an issue not being able to quit my audio program Pro Tools. Just hangs on the spinning ball.
I am using a firewire device for the input and from what I noticed in Mojave in the network tab you can clearly see my firewire device, but in Monterey it's not listed?
My question being if the firewire device is not listed in the Network tab, could that be why it doesn't see it to shut down the program?
I having an issue not being able to quit my audio program Pro Tools. Just hangs on the spinning ball.
I am using a firewire device for the input and from what I noticed in Mojave in the network tab you can clearly see my firewire device, but in Monterey it's not listed?
My question being if the firewire device is not listed in the Network tab, could that be why it doesn't see it to shut down the program?
Well, this didn't workout so well. Totally unbootable drive after install. Even turning on VMM doesn't help. It's looking more & more like this isn't doable at all on my system.
I’ll give it another try. One thing I did see that I’m not sure about. It stopped at one point and threw a notification that it wasn’t able to download a needed firmware update. Is it supposed to do that? Perhaps I need to tweak another config setting.
Last edited:
@crjackson2134 were you able to boot the installer and proceed with the installation through reboots, though?
The firmware update notification is not normal. It indicates an OC setup problem or an unhealthy firmware chip.
The firmware update notification is not normal. It indicates an OC setup problem or an unhealthy firmware chip.
Yes & no. I tried again and again. No warnings about firmware being unable to update anymore.
It proceeded through several boots, and then it gets to a point (at what I presume is the last boot because it shows no countdown) where it loads about 1/3 on the progress bar. From there it goes into a perpetual boot-loop (for hours).
I started over several times, never having any errors reported, then being stuck at the boot-loop.
I'm going to make a couple of config checks/tweaks to what was working, and if that doesn't do it. Well I guess it's time to stop trying for a while. I can only assume that for some reason, something my actual, physical machine isn't compatible.
Last edited:
Hi. Does someone use a WD Black SN770 NVMe SSD on his cMP here? I got one to replace my Samsung 970 EVO plus that seems to be disliked in Monterey. With SSN some issues seems to be disappeared, but speed measured by Blackmagic Disk Speed Test are really worse. Even I measure it in Monterey booting from SN770, even I measure it from Mojave (booted from another device). About half of the speeds measured with Samsung 970 EVO plus.
Last edited:
Known issue with a MacPro5,1 when installed to slots 3 or 4:
NVMe card linking at 2.5GT in slot 3 on Mac Pro 5,1
Hi, I’ve a genuine Mac Pro 5,1 running mojave updated to the latest 144 firmware and booting from a sata ssd drive. I also have an nvme drive in slot 3 (in a x4 pcie slot adaptor), but it only links at 2.5GT/s, not the 5.0GT/s the 144 is supposed to enable. I know it’s not the card as it...
forums.macrumors.com
The issue seems to be with MacPro5,1 IDT PCIe v2.0 switch that share the southbridge PCIe lines to slots 3 and 4, since when installed to slots 1 or 2 the SN770 blade works correctly at 5GT/s.
The SN770 works perfectly fine when installed to a MacPro6,1.
Correct throughput when installed to a MacPro6,1:
Last edited:
