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

[Guitarmas]

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.

Thanks!

I've noticed a few cards on ebay are metal compatible and support macOS EFI boot screens. They're priced around $200. This seems a bit much. Is this what I expect to pay for one?

 

[David403]

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.

Thanks for those suggestions

With OC 0.8.1 when AvoidRuntimeDefrag set as false Ventura selected from the boot picker starts with Boot Loop (Apple Logo appears; progress bar starts for about 0.5 seconds then re-boots)

With OC 0.8.1 when AvoidRuntimeDefrag set as true Ventura selected from the boot picker starts to boot but gets only as far as Apple Logo and the progress bar never starts

With OC 0.8.1 when AvoidRuntimeDefrag is removed Ventura selected from the boot picker starts to boot but gets only as far as Apple Logo and the progress bar never starts.

AVXpel does work for cMP for Monterey 12.4 which I can select from the boot selector - just not able to boot into Ventura to test it there yet.

 

[startergo]

Thanks for those suggestions

With OC 0.8.1 when AvoidRuntimeDefrag set as false Ventura selected from the boot picker starts with Boot Loop (Apple Logo appears; progress bar starts for about 0.5 seconds then re-boots)

With OC 0.8.1 when AvoidRuntimeDefrag set as true Ventura selected from the boot picker starts to boot but gets only as far as Apple Logo and the progress bar never starts

With OC 0.8.1 when AvoidRuntimeDefrag is removed Ventura selected from the boot picker starts to boot but gets only as far as Apple Logo and the progress bar never starts.

AVXpel does work for cMP for Monterey 12.4 which I can select from the boot selector - just not able to boot into Ventura to test it there yet.

You need either latest Lulu or
-lilubetaall

 

[David403]

You need either latest Lulu or
-lilubetaall

Thanks.

I followed the links in your post 11,068 but don't know how to compile the latest Lilu and WhateverGreen after doing that.

....the alternative approach using -lilubetaall - Is it a boot argument? where do I place that in the config.plist?

Thanks

 

[startergo]

Thanks.

I followed the links in your post 11,068 but don't know how to compile the latest Lilu and WhateverGreen after doing that.

....the alternative approach using -lilubetaall - Is it a boot argument? where do I place that in the config.plist?

Thanks

It is a boot argument. You don't need to compile them they are compiled and you should just download the artifact. You need to be logged in to GitHub.

 

[TECK]

Is it Really this easy?

How is this related to current OC guide?

 

[TECK]

I'm confused, there are claims Ventura boots fine on a cMP 5,1, while the world fails on [EB|#LOG:EXITBS:START]. Did anyone tried the install Ventura on x5690 Westmeres?

[macOS Ventura 13.0] Booting issues · Issue #2038 · acidanthera/bugtracker

Hi there, I'm opening this issue to keep track of the bugs and future development of OpenCore as well as the kexts, in terms of macOS Ventura 13.0 support. I'm not there to hurry the devs up keep t...

github.com

Edit: link to discussion thread

 

[PeterHolbrook]

You need either latest Lulu or
-lilubetaall

Have you actually been able to boot to the Ventura desktop on a cMP? Do you know anyone who has?

 

[prefuse07]

Have you actually been able to boot to the Ventura desktop on a cMP? Do you know anyone who has?

It looks like @David403 is attempting it right now, if you scroll up

 

[David403]

Have you actually been able to boot to the Ventura desktop on a cMP? Do you know anyone who has?

I have NOT been able to boot into Ventura beta1.

I have followed @startergo’s advice (post 11069) I disabled quirk AvoidRuntimeDefrag in Booter Quirks. I updated to the latest Lilu and WEG from source. I have tried with and without -lilubetall both with the same results as below.

Initially, I updated to OC 0.8.1 with no problems following Post 1 to the letter and I am able to boot into Monterey 12.4. (i.e. including AvoidRuntimeDefrag set to false)

I downloaded the Ventura beta1 and did a clean install on a spare 1TB SSD. It appeared to install. It looked as if it had finished but went into a never-ending boot loop. I shut down with the power button and restarted.

I get the boot screen with Monterey, Monterey Backup, and Ventura in the boot selector. Selecting the Ventura starts up with the boot loop again. Choosing Monterey works fine.

Following @startergo’s advice, Ventura selected from the boot picker starts to boot but gets only as far as the Apple Logo and hangs with that. The progress bar does not appear.

I reformatted the Ventura beta SSD; went back to Monterey (with disabled quirk AvoidRuntimeDefrag set to true) and tried to reinstall it only gets as far as the first reboot and hangs with the Apple Logo. The progress bar does not appear. Powering off and rebooting gives in to the OC boot selector: Monterey, Ventura, and the Installer. Selecting the installer: It hangs with the Apple Logo. The progress bar does not appear.

FOR CLARITY: Monterey Boots
Ventura does not

 

[startergo]

I have NOT been able to boot into Ventura beta1.

I have followed @startergo’s advice (post 11069) I disabled quirk AvoidRuntimeDefrag in Booter Quirks. I updated to the latest Lilu and WEG from source.

Initially, I updated to OC 0.8.1 with no problems following Post 1 to the letter and I am able to boot into Monterey 12.4. (i.e. including AvoidRuntimeDefrag set to false)

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

Following @startergo’s advice, Ventura selected from the boot picker starts to boot but gets only as far as and hangs with the Apple Logo. The progress bar does not appear.

I reformatted the Ventura beta SSD; went back to Monterey (with disabled quirk AvoidRuntimeDefrag set to true) and tried to reinstall it only gets as far as the first reboot and hangs with the Apple Logo. The progress bar does not appear. Powering off and rebooting gives in to the OC boot selector: Monterey, Ventura, and the Installer. Selecting the installer: It hangs with the Apple Logo. The progress bar does not appear.

There is something wrong with the configuration if you can't boot Monterey with it. Try the rescue CD @cdf recommended.

 

[PeterHolbrook]

@David403 & @startergo: No, I don't suppose there's much that can be done right now until @Syncretic finishes his in-depth analysis on the feasibility of emulating AVX+ instructions on the cMP. Right now, the likelihood of a happy outcome for these old machines is rather grim, I would think.

 

[David403]

There is something wrong with the configuration if you can't boot Monterey with it. Try the rescue CD @cdf recommended.

I CAN boot Monterey - I said so in the last phrase of paragraph 4 of my post 11,085.

Writing this in Monterey now

 

[borgo1971]

I'm still with OC 0.77, even becouse I had no few troubles to update to it. But now I'm thinking to update to OC 0.81 before try again to install BigSur and Monterey (I'd like to try my main applications with both). So I'd like to know if there is a place where I can find previous (then the last) update I should do to config.plist.

 

[cdf]

I'm still with OC 0.77, even becouse I had no few troubles to update to it. But now I'm thinking to update to OC 0.81 before try again to install BigSur and Monterey (I'd like to try my main applications with both). So I'd like to know if there is a place where I can find previous (then the last) update I should do to config.plist.

You can follow the guide to create your custom config for 0.8.1 from scratch, or you can use the "WikiPost History" button to view the update notes for 0.7.7 to 0.7.8, ..., 0.8.0 to 0.8.1. Have an emergency plan in place (back up of ESP, rescue CD, etc.) and make sure to use ocvalidate.

 

[David403]

@David403 & @startergo: No, I don't suppose there's much that can be done right now until @Syncretic finishes his in-depth analysis on the feasibility of emulating AVX+ instructions on the cMP. Right now, the likelihood of a happy outcome for these old machines is rather grim, I would think.

Unfortunately, you're probably correct. It is encouraging that AVXpel (thanks @Syncretic) works well in Monterey.

I was pleased that when I did a clean install of Ventura beta with OC 0.8.1 (with AvoidRuntimeDefrag still set to false initially) it appeared in the boot selector. The progress bar after the Apple logo appeared moved forward only for a split second before rebooting; on all the other permutations reported it hung on the Apple logo for up to 30 minutes before I switched off the power.

What I haven't tried is installing from scratch with the updated Lilu and EverGreen. I'll try that with AvoidRuntimeDefrag still set to false then AvoidRuntimeDefrag still set to true.

I'm assuming for the moment it will still not boot and will only post again if I've had any result that's different from those already posted.

 

[Jazzzny]

After a lot of work in the OCLP community (and a few headaches), here it is:

Not very stable (multiple loginwindows and WS crashes), but Ventura does boot on a cheesegrater!

 

[tsialex]

I'm ultra busy this week with WWDC stuff and didn't had much time to look at Ventura, but I noticed that Apple removed the AMD GPU drivers for anything earlier than Polaris, so, after ~10 years of service, HD 7950/R9 280 and friends are finally deprecated. This will be a real problem for MacPro6,1 where it will need root patching to work.

Btw, not all hope is lost for MacPro5,1. People on OCLP discord already got Westmere Xeons to boot Ventura, but let's see if the final result will be usable.

So a summary of Ventura Developer Preview 1 and MacPro5,1:

• Ventura.DP1 boots and kinda works with a MacPro5,1, but you can't do the full install on a MacPro5,1, you have to use a Mac with Haswell or newer CPU to complete the InstallAssistant, it freezes at the last reboot, just before the InstallAssistant opens.
• You'll need to spoof a MacPro7,1.
• You'll need to install the dyld shared cache from a M1 install to overcome the need of AVX2 CPU support - M1 Rosetta don't support AVX and that's why you can bypass the need of AVX2 for the kernel. This don't mean in any way that apps that require AVX/AVX2 will ever work.
• Apple removed drivers for all AMD GPUs older than Polaris family / only AMD Polaris and newer AMD cards have acceleration.
• Only BCM94360/BCM94362 AirPort Extremes are still supported/work.
• The install process is highly convoluted right now.

I'll continue to update this post as things evolve.

 

[Alex-IN]

After a lot of work in the OCLP community (and a few headaches), here it is:

Not very stable (multiple loginwindows and WS crashes), but Ventura does boot on a cheesegrater!

It is possible to look at EFI?

 

[Jazzzny]

It is possible to look at EFI?

Sure, here it is:
OCLP Build with Moderate Spoofing with quite a bit of modification
Edit: huh, seems to be too large for macrumors
give me a moment
Edit 2: I've split the EFI into two parts, one zip contains the kexts and the other contains everything else

Note: it is currently not possible to boot a "fresh" ventura installation. As we know, Apple did not ship Non-AVX caches for Ventura. However, khronelkernel discovered that the M1 build of Ventura does have Non-AVX caches (probably for Rosetta). So with the caches copied to the preboot partition, Ventura does boot!

 

[David403]

Unfortunately, you're probably correct. It is encouraging that AVXpel (thanks @Syncretic) works well in Monterey.

I was pleased that when I did a clean install of Ventura beta with OC 0.8.1 (with AvoidRuntimeDefrag still set to false initially) it appeared in the boot selector. The progress bar after the Apple logo appeared moved forward only for a split second before rebooting; on all the other permutations reported it hung on the Apple logo for up to 30 minutes before I switched off the power.

What I haven't tried is installing from scratch with the updated Lilu and EverGreen. I'll try that with AvoidRuntimeDefrag still set to false then AvoidRuntimeDefrag still set to true.

I'm assuming for the moment it will still not boot and will only post again if I've had any result that's different from those already posted.

Follow up - fortunately, I hadn't started when post 11,092 appeared - I'll look through the downloaded EFI on post 11,095 before trying anything more. - Thanks @Jazzzny

 

[prefuse07]

Follow up - fortunately, I hadn't started when post 11,092 appeared - I'll look through the downloaded EFI on post 11,095 before trying anything more. - Thanks @Jazzzny

Godspeed, and keep us updated!

 

[zzzippp]

However, khronelkernel discovered that the M1 build of Ventura does have Non-AVX caches (probably for Rosetta). So with the caches copied to the preboot partition, Ventura does boot!

Thank you, @Jazzzny! Does that mean replacing the entire Intel x86 kernel cache file on preboot with the one from the M1 build, post install? Is there a thread / channel where we could read the details?

 

[Jazzzny]

Thank you, @Jazzzny! Does that mean replacing the entire Intel x86 kernel cache file on preboot with the one from the M1 build, post install? Is there a thread / channel where we could read the details?

I'll give a brief description of the file replacement process:
Firstly, you'll want to grab the os.dmg image from an M1 preboot volume. If you look into this image, you'll see the x86_64 caches (non-h variant).
Copy this disk image to a USB drive in preparation for the replacement.
Then you'll want to get Ventura "installed" onto your CMP. macOS will eventually stall at a point during the verbose portion of the first "installed" boot.
Once macOS stalls, reboot and ensure that macOS is still stalled.
Then you can reboot again into the recovery environment
From the recovery, you can open up a terminal window and mount the fresh install's preboot volume (diskutil list, diskutil mount disk#s#)
Once you get the preboot mounted, you'll want to navigate to /Volumes/Preboot/Long-UUID(check this using ls)/cryptex1/current/
Run an ls command here, and you should see the os.dmg file
Now run a cp command and replace the Preboot's os.dmg with the M1 os.dmg
Once that's done, reboot your machine and Ventura should boot to either a loading bar at ~60% with a cursor or a grey screen with a beachball.
Now you'll need to remove the Ventura drive from your cMP and install it/boot from it in another mac that is Ivy Bridge+.
This is done because the Ventura setup assistant does not play well with Non-AVX1 machines
Once you get through the Ventura Setup assistant, remove the drive and reinstall it in your cMP
If all things go to plan, you should boot into the Ventura desktop!
Oh, that wasn't very brief
Well, good luck!
Edit: oh, and this should be done with the EFI I sent, or at least with the "APFS Disable Patch thingy" from the config.plist
Edit 2: for convenience, here's the M1 os.dmg image: https://drive.google.com/uc?export=download&id=12vCE0MAzcRqN7zJu5EbbzsZeroeI_Gsm

 

[startergo]

I'll give a brief description of the file replacement process:
Firstly, you'll want to grab the os.dmg image from an M1 preboot volume. If you look into this image, you'll see the x86_64 caches (non-h variant).
Copy this disk image to a USB drive in preparation for the replacement.
Then you'll want to get Ventura "installed" onto your CMP. macOS will eventually stall at a point during the verbose portion of the first "installed" boot.
Once macOS stalls, reboot and ensure that macOS is still stalled.
Then you can reboot again into the recovery environment
From the recovery, you can open up a terminal window and mount the fresh install's preboot volume (diskutil list, diskutil mount disk#s#)
Once you get the preboot mounted, you'll want to navigate to /Volumes/Preboot/Long-UUID(check this using ls)/cryptex1/current/
Run an ls command here, and you should see the os.dmg file
Now run a cp command and replace the Preboot's os.dmg with the M1 os.dmg
Once that's done, reboot your machine and Ventura should boot to either a loading bar at ~60% with a cursor or a grey screen with a beachball.
Now you'll need to remove the Ventura drive from your cMP and install it/boot from it in another mac that is Ivy Bridge+.
This is done because the Ventura setup assistant does not play well with Non-AVX1 machines
Once you get through the Ventura Setup assistant, remove the drive and reinstall it in your cMP
If all things go to plan, you should boot into the Ventura desktop!
Oh, that wasn't very brief
Well, good luck!
Edit: oh, and this should be done with the EFI I sent, or at least with the "APFS Disable Patch thingy" from the config.plist
Edit 2: for convenience, here's the M1 os.dmg image: https://drive.google.com/uc?export=download&id=12vCE0MAzcRqN7zJu5EbbzsZeroeI_Gsm

Isn't it going to be faster to install it on a drive attached to an IB+ Mac, replace the Preboot's os.dmg with the M1 os.dmg and return to the cMP?