Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacPro 3.1 boots with nonMetal GPU, without acceleration. RX 570 4GB shows black screen.
Thanks to Jazzzny for hint )

1658680386591.png
 
Is it realistically possible that the AVX2 compatibility issue will be solved via OpenCore AVX/AVX2 patches?
Don't think so, it's analogous of the requirement of SSE4.1 with Sierra and MacPro1,1/2,1 all over again.

With Monterey, the usage of AVX is minimal and very much contained while with Ventura Apple enabled AVX2 in a lot of places, like GPU drivers and libraries - patching is not going to work and even if someone is determined/crazy enough to start patching all the drivers and libraries, this is not maintainable over the long run.

Unless someone develop a fully working AVX emulator that correctly integrates with macOS, like @Syncretic is trying to do for the past two years, I don't see Ventura fully running with any Mac with a processor earlier than Haswell generation. If you follow OCLP Ventura commits and docs, that's the baseline that they are supporting right now.

Anyway, at least we still have two full years, and some months, of Monterey support/security updates until we are forced to migrate to something newer.
 
Don't think so, it's analogous of the requirement of SSE4.1 with Sierra and MacPro1,1/2,1 all over again.

With Monterey, the usage of AVX is minimal and very much contained while with Ventura Apple enabled AVX2 in a lot of places, like GPU drivers and libraries - patching is not going to work and even if someone is determined/crazy enough to start patching all the drivers and libraries, this is not maintainable over the long run.

Unless someone develop a fully working AVX emulator that correctly integrates with macOS, like @Syncretic is trying to do for the past two years, I don't see Ventura fully running with any Mac with a processor earlier than Haswell generation. If you follow OCLP Ventura commits and docs, that's the baseline that they are supporting right now.

Anyway, at least we still have two full years, and some months, of Monterey support/security updates until we are forced to migrate to something newer.
This is sad news but good to know. I will likely change my "main machine" to the MP5,1 with Monterey and OLCP. I look to take my hackintosh iMac 2017, running Big Sur, to Ventura.
 
Hello

what should be changed in config.plist to start ventura.

i have already replaced the dydl cache with the m1 cache
 
I'm confused, there are claims that Ventura boots fine on a cMP 5,1, while the world fails on [EB|#LOG:EXITBS:START]. Did anyone tried to install Ventura on a 5,1? As mentioned into an issue comment, several OC features will need to be reworked for Ventura.

Edit: Reference link to Ventura on Unsupported Macs, in macOS forums
I had ventura installed on MP4,1 upgraded to to 5,1. The system booted and work normal after installation first boot, after rebooted, mouse and keyboard no longer working. Tried to use usb hub but it pretty laggy, keyboard work randomly. I would say even if you succeed install and boot, you will face with input devices issues. I have x5680 with 32GB 1333MHz ram, rx580 8g
 
  • Like
Reactions: foliovision
Been tinkering with two MP5.1 2009 towers one has dual tray other single cpu.
First one doesn’t want to go further than Monterey 12.7.1
Other got to Ventura 13.6.1 without “hiccups” with one of configs from this forum on Ventura someone shared. Tho this config lacks different things.
My goal is at least tri-boot Monterey/Ventura/Sonoma
 
Last edited:
Seems that sucessful installations of Ventura & Sonoma heavily rely on config.plist and spoofing you can play around with different settings and set what you need, like max ram patch (32g-sticks). If most variables are in places like AVX patching then they have no problem even without dydl cache swap.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.