MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[trondl]

Doesn’t post #1 clarify your doubts? I followed it to the letter and everything worked as advertised.

I’ve now tried a Win10 install from USB on an empty temporary hdd, but with some modifications.
I used a GPT fat32 USB format and used Dism to split the install.wim file.
«Automatic» partitioning worked like a charm during install.
During the first reboot I did a pitstop to add OC to the EFI partition, but copied the wrong bootx64.efi file ?.
Yes, I got herpes on my nvram, but a quick reflash sorted it out.

Now, what I’m trying to achieve is to not have OC reside in the nvram, as in OC will only run when I boot from the Win10 disk and a reboot clears it out.
OC should not be active when I boot/reboot to High Sierra.

Is that the function of the «WriteFlash» option?
Also, what other functions can I disable since only win10 will use OC?
I’ve already disabled «DirectGOPRendering» as I have bootscreen.

 

[prefuse07]

so what's the consensus with Monterey and OpenCore?

 

[PeterHolbrook]

so what's the consensus with Monterey and OpenCore?

I don't know about a consensus. I can say it works for me.

 

[NC12]

so what's the consensus with Monterey and OpenCore?

Works almost flawlessly for me

The only problem is the USB 1.1 drivers were deprecated so certain devices that auto negotiate their speeds to 1.1 spec won’t work unless plugged in on boot. It’s easily remedied with a hub though

 

[hwojtek]

so what's the consensus with Monterey and OpenCore?

Were there ever any disagreements?

The only problem is the USB 1.1 drivers were deprecated so certain devices that auto negotiate their speeds to 1.1 spec won’t work unless plugged in on boot. It’s easily remedied with a hub though

Yes, this hub thing brought back my ancient yet perfectly capable M-Audio audio interface back to life.

 

[prefuse07]

I thought there was something similar to the RACE condition with AVX calls that Syncretic had to make a patch for?

I am talking about 12.4 (I believe that's where it begins)

 

[Dewdman42]

Monterey 12.3.1 working great for me, zero problems. I do use a USB hub also. I also have a very well supported GPU (RX-580). I have been using CDF's guide exclusively, I prefer that over OCLP because I understand more or less what is configured, with OCLP its a black box that seems to install quite a bit more hackologiy then I think I really need. But that's just me.

I will upgrade to 12.4 in a month or two after I see the AVX hacks settle in. Quite happy with my Monterey Open Core setup honestly.

Overall we had that boot up crisis a few months ago that the genius Syncretic figured out a work-around, then Apple seemed to fix their own problem in a subsequent update. Now we have the AVX situation, which there are already a few ways around it...but I suspect that AVX requirements could become more prominent in future MacOS releases, but who knows.

 

[hwojtek]

I thought there was something similar to the RACE condition with AVX calls that Syncretic had to make a patch for?

Not all users experience this. I, for one, do not. Despite running 12.4 and using Siri (which appeared to trigger the kernel panic). This may have to do with my particular setup:
- single MacOS disk, always half-empty (or half-full, for you optimists) on a PCIe SSD
- disallowed mounting of my Windows and Ubuntu disks in fstab
- no other disks writable to MacOS in the computer
So perhaps this 1TB of free space on the boot disk is the reason compression doesn't kick in.

For those who have encountered this condition, though, the patch seems to mitigate the issue. It's just another OC kext, so nothing out of ordinary to allow our hardware to stay relevant, same thing that you'd do to support an outdated wifi/bt combo or allow a decent GPU to work properly.

 

[Macschrauber]

I’ve now tried a Win10 install from USB on an empty temporary hdd, but with some modifications.
I used a GPT fat32 USB format and used Dism to split the install.wim file.
«Automatic» partitioning worked like a charm during install.
During the first reboot I did a pitstop to add OC to the EFI partition, but copied the wrong bootx64.efi file ?.
Yes, I got herpes on my nvram, but a quick reflash sorted it out.

Now, what I’m trying to achieve is to not have OC reside in the nvram, as in OC will only run when I boot from the Win10 disk and a reboot clears it out.
OC should not be active when I boot/reboot to High Sierra.

Is that the function of the «WriteFlash» option?
Also, what other functions can I disable since only win10 will use OC?
I’ve already disabled «DirectGOPRendering» as I have bootscreen.

check out @Dayo's RefindPlus variant of rEFInd what chainloads OC. I also dislike to run supported systems (like Mojave in my case) thru OC. So I use RP to boot it natively with the desired options like switching some csr bits. Or legacy Windows in bios mode, Linux, etc. Or to load different flavours of OC / OCLP thru RP.

 

[cdf]

The guide has been updated to OpenCore version 0.8.1. Also included are instructions for AVXpel. Happy updating!

 

[PeterHolbrook]

The guide has been updated to OpenCore version 0.8.1. Also included are instructions for AVXpel. Happy updating!

Is it safe to assume that AVXpel now fully replaces NoAVXFSCompressionTypeZlib.kext?

I thought the AllowToggleSip Security key was very convenient. Now that it's been deprecated, is there a replacement for it? It's unclear to me how to use ToggleSipEntry.

 

[cdf]

Is it safe to assume that AVXpel now fully replaces NoAVXFSCompressionTypeZlib.kext?

Yes. In theory, it's a more elegant solution.

I thought the AllowToggleSip Security key was very convenient. Now that it's been deprecated, is there a replacement for it? It's unclear to me how to use ToggleSipEntry.

Something like this should do it:

<key>UEFI</key>
<dict>
⋮
<key>Drivers</key>
<array>
⋮
<dict>
<key>Arguments</key>
<string></string>
<key>Comment</key>
<string>Plugin for toggling SIP</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>ToggleSipEntry.efi</string>
</dict>
⋮
</array>
⋮
</dict>

 

[trondl]

check out @Dayo's RefindPlus variant of rEFInd what chainloads OC. I also dislike to run supported systems (like Mojave in my case) thru OC. So I use RP to boot it natively with the desired options like switching some csr bits. Or legacy Windows in bios mode, Linux, etc. Or to load different flavours of OC / OCLP thru RP.

Thanks for putting me on the right track!

 

[TECK]

@cdf when is AVXpel required? Plistlib Generator 2.0.2 was released with support for OC 0.8.1 (see notable changes).

 

[cdf]

@cdf when is AVXpel required?

The problematic use of AVX occurs in at least two kexts, and panics can occur when using Voice Control and Siri. You can read more about AVXpel here:

https://forums.macrumors.com/threads/monterand-probably-the-start-of-an-ongoing-saga.2320479/post-31125212

 

[PeterHolbrook]

I take it for granted that the inclusion of AVXpel will still not cause sysctl machdep.cpu.features to imagine our CPUs support AVX/AVX2. Will that ever be achievable?

 

[cdf]

I take it for granted that the inclusion of AVXpel will still not cause sysctl machdep.cpu.features to imagine our CPUs support AVX/AVX2. Will that ever be achievable?

Right. There's no spoofing involved here. Basically, AVXpel replaces the problematic AVX stuff with a non-AVX version.

The problem is that because all supported Macs now have AVX, Apple will likely just use it regardless of what CPUID may report...

 

[David403]

Updated to OC 0.8.1 with no problems following Post 1 to the letter. I'm booting smoothly into Monterey 12.4.

I downloaded the Ventura beta1 and did a clean install on a spare 1TB SSD. It appeared to install. it looks as if it is finished but it then gets into a never-ending boot loop. I tried shutting down with the power button and restarting. I get the boot screen with Monterey, Monterey Backup, and Ventura in the boot selector. Selecting the Ventura starts up the boot loop again. Choosing Monterey works fine.

I assume some tweaks are going to be required?

Has anyone been successful? ...and how did you get it to run?

 

[startergo]

I assume some tweaks are going to be required?

disable quirk AvoidRuntimeDefrag in Booter Quirks . Update to latest Lilu and WEG from source.
With latest Lilu disabling the quirk AvoidRuntimeDefrag may not be needed. Needs testing.
Hopefully AVXpel still works for cMP.

 

[Atreyu25]

Updated to OC 0.8.1 with no problems following Post 1 to the letter. I'm booting smoothly into Monterey 12.4.

I downloaded the Ventura beta1 and did a clean install on a spare 1TB SSD. It appeared to install. it looks as if it is finished but it then gets into a never-ending boot loop. I tried shutting down with the power button and restarting. I get the boot screen with Monterey, Monterey Backup, and Ventura in the boot selector. Selecting the Ventura starts up the boot loop again. Choosing Monterey works fine.

I assume some tweaks are going to be required?

Has anyone been successful? ...and how did you get it to run?

No chip AVX2 support and Ventura requires it in order to boot. Hopefully the OCLP team is able to successfully emulate the instruction set without too much processor overhead. Unfortunately they aren't optimistic.

 

[PeterHolbrook]

No chip AVX2 support and Ventura requires it in order to boot. Hopefully the OCLP team is able to successfully emulate the instruction set without too much processor overhead. Unfortunately they aren't optimistic.

Are you disputing @startergo's assessment in post #11,069?

EDIT: User ITzTravelInTime, at https://github.com/acidanthera/bugtracker/issues/2038, claims macOS Ventura "booted fine on my mac pro 5,1 so it should work for people without avx instructions."

 

[Guitarmas]

Hi everyone.

I'm new here.
There is just so much information here. I don't know where to start.
I did see this video. It seems really easy.
I have the following setup.

Is it Really this easy?

Thoughts? Suggestions?

Thanks!

 

[hwojtek]

Thoughts? Suggestions?

Leave it until it matures enough to be comprehensible.

 

[Guitarmas]

Thanks.

I'm curious. Can you point me in the right direction for discussions about metal compatible video cards?

 

[Charles Liske]

Thanks.

I'm curious. Can you point me in the right direction for discussions about metal compatible video cards?

Generally most modern Radeon cards with TDPs below 275W work with the latest OS/metal version, here's apple's (rather tiny) list of officially metal supported cards from a while ago, and a much more helpful unofficial list of compatible GPUs (note that many of these are Nvidia GPUs or old cards which do not have drivers past High Sierra). The Radeon 5x00 cards have drivers in Catalina and later and the 6x00 cards in Big Sur and later (although you have to patch the 6x00 cards in a windows PC due to a ROM bug). RX 5x0 cards are another popular, fairly inexpensive option (I'm currently running an RX580) and have drivers in Mojave and later.