On page that I have linked. There it is.

Join the OpenCore Patcher Paradise Discord Server!
Check out the OpenCore Patcher Paradise community on Discord - hang out with 54034 other members and enjoy free voice and text chat.
On page that I have linked. There it is.
It's honestly incredible to follow the Discord server and see how quickly progress is being made! At this rate I wouldn't be surprised if Ventura will be working as well as Monterey by the time it releases!Oh yes, White Penryn Macbook, dammit that’s fast!(Don’t throw your cMPs3.1 away yet.) Arrandale and Sandy Bridge left.
Wow, this gives me a lot of hope for the cMP! Do we know how this was made possible on a Penryn CPU?Oh yes, White Penryn Macbook, dammit that’s fast!(Don’t throw your cMPs3.1 away yet.) Arrandale and Sandy Bridge left.
Couldn't refrain from trying a Ventura installation also on my retired (partly repaired) MBP5,2 (Penryn 9600).Thank you! AVX2 is shown:
hvds@macbookpro-hvds ~ % sysctl -a | grep machdep.cpu.leaf7_features
machdep.cpu.leaf7_features: RDWRFSGS TSC_THREAD_OFFSET SGX BMI1 AVX2 SMEP BMI2 ERMS INVPCID FPU_CSDS MPX RDSEED ADX SMAP CLFSOPT IPT SGXLC MDCLEAR TSXFA IBRS STIBP L1DF ACAPMSR SSBD
hvds@macbookpro-hvds ~ %
Running Ventura on this MBP16,1 now.
Clean install on an external SSD in my usual way: CCC clone of the data volume to an erased SSD; install Ventura over it from USB installer (InstallAssistant.pkg obtained via gibMacOS). All straightforward as it should on a supported machine, still good to know that this 1st beta of Ventura behaves well.
Edit: booting back into Monterey (internal SSD) worked and running fine, but it did an extra reboot in the background - don't know what it did. Maybe should be more prudent with such an early beta, even if on an external disk.
First try to understand how it all works by watching some of the videos from Mr. Macintosh:Is there any way a noob such as me could help in this project?
Wow, this gives me a lot of hope for the cMP! Do we know how this was made possible on a Penryn CPU?
End of the road for my mid-2012 unibody. It was a great run.Devices with Ivy Bridge CPUs and older, basically all Macs older than Late 2013 do not support AVX2 natively.
Maybe not yet. I would not give up on it yet. We got amazing people and developers in this thread and on discord that I am sure could pull it off. This was just posted on the OCLP discord server which you can join at this link: https://discord.gg/rqdPgH8xSNEnd of the road for my mid-2012 unibody. It was a great run.
End of the road for my mid-2012 unibody. It was a great run.
I just have shown MBP 9.2 running it.(AVX2 can be somehow bypassed)End of the road for my mid-2012 unibody. It was a great run.
what macbook air model identifier is it spoofing to?There is a link for it on OCLP page. https://github.com/dortania/OpenCore-Legacy-Patcher Screenshot to prove it included
9.2 spoofed as Air, but hey, it works!
Development goes pretty fast, I am sure it will be fine for final Ventura release.
Pretty sure 2018+(there are only 3 Intel models), you can join server and ask him. Anyway, acceleration is not done yet, so it will not be usable.what macbook air model identifier is it spoofing to?
You don't say if you started the "Post Install Patch" from OCLP after macoS Ventura installation. If you haven't, please try to do it now and let us know... ThanksManaged to get it installed on my unsupported MacBookAir7,1, spoofed as MacBookAir8,2.
It works really well, with everything other than graphics acceleration working.
It's been a while since I've done any hackintoshing, but is it possible to get graphics acceleration on this machine?
Apologies for my ignorance; again, it's been a while since I've done stuff like this haha!
The chance for the older interdependencies to still work with replaced frameworks (skylight et al) on Ventura is very low, probably the patcher either refuses to do it or the result will crash or not log in (windowserver crashing). But pls. try and report back. Curiosity killed the cat. ;-)You don't say if you started the "Post Install Patch" from OCLP after macoS Ventura installation. If you haven't, please try to do it now and let us know... Thanks
wont work since the device just got dropped. so there is no post install patches yetYou don't say if you started the "Post Install Patch" from OCLP after macoS Ventura installation. If you haven't, please try to do it now and let us know... Thanks
There is a reason for the huge drop at least on the GPU side. Metal 3 is a huge API upgrade.I couldn't agree with you more in terms of Planned Obsolescence - I've literally had no issues with either Big Sur or Monterey via OCLP since my machine EOL'd at Catalina in 2019. It kinda sticks in my throat to be honest. I'm hoping for a system upgrade towards the end of the year, and it will involve a lot of thinking on my part. I could get a ball-tearer of a Linux machine for the same cost as a Mac Studio M1 Max and that is VERY tempting. This gives me options macOS just doesn't.. I get to stick to Unix/Linux under the bonnet while using the Proton layer to run PC games. Factor in much more hardware flexibility and.. 🤷♂️
Interesting times.
In the case of iOS and iPadOS 16 they are clearly keeping support for devices that do not support Metal 3. So there is perhaps a chance to get devices that support older versions of Metal running with acceleration even in Ventura if the fallback code is in place there, too, without having to patch the entire OS.There is a reason for the huge drop at least on the GPU side. Metal 3 is a huge API upgrade.
See for yourself:
![]()
View attachment 2016524
Wait MBP2015 has Intel Iris Pro 5200? Is there a driver for it in Ventura?See for yourself:
Wait MBP2015 has Intel Iris Pro 5200? Is there a driver for it in Ventura?
View attachment 2016627
My iMac14,1 without dedicated graphics also has the Intel Iris Pro 5200Wait MBP2015 has Intel Iris Pro 5200? Is there a driver for it in Ventura?