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.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Now running 13.0b8 on MBP5,2. No graphics acceleration of course but rather smooth:
Using OCLP 0.5.0n from today, i.e. last commit is regarding AVXpel-based NoAVX kext.
Still necessary to use the os.dmg from IPSV (and the external keybd/mouse) to get it booting.
BUT login was really smooth now, no window server crashes. So progress!
EDIT: was using 13.0b8 on MBP5,2 now for 6hrs without problems.
Attachments
Last edited:
On the OCLP Github, ventura alpha branch: https://github.com/dortania/OpenCore-Legacy-Patcher/tree/ventura-alpha
There under Code, download zip, unzip and run OpenCore-Patcher-GUI.command.
The attached terminal output shows where the os.dmg has to go on the target (the hex string will vary from installation to installation).
Be aware of the "double-beta" situation (Ventura and OCLP). Don't proceed unless you can take the risk.
The MBP5,2 I'm using is no longer my production system, still for Ventura test installations I use an external SSD. On the internal SSD is Monterey (which is running while copying the os.dmg to the external Ventura SSD).
Attachments
Last edited:
thank you
OS. DMG didn't understand, two 13, a general version with another M1 version, replace OS. DMG?
Yes - the os.dmg which comes with the installation of 13.0 beta for Intel is replaced with the one which comes with the restore file of same beta for M1.
Reason is that the former (size some 1.5 GB) no longer contains the code necessary for running on earlier Intel processors which don't understand AVX2 instructions. While the M1 one (about 4.2 GB) happens to contain this code.
Post #691 has some detail of how to get hold of the os.dmg from the M1 restore file.
Last edited:
OpenCL and Metal scores on iMac 27 late 2015 with AMD Radeon M9: macOS 13 beta 8 + OCLP 0.5.0 alpha.
I think the scores are good. OCLP root patch works fairly good despite of its alpha stage.
The scores are almost identical in macOS 12 (natively supported).
I think the scores are good. OCLP root patch works fairly good despite of its alpha stage.
The scores are almost identical in macOS 12 (natively supported).
Last edited:
@fernando.c.neves
Good night. I see that you have Acidanthera in motherboard. Instead of Apple Inc. So are you using OpenCore? Not OpenCore Legacy patcher? How do you do to have graphic acceleration without the OCLP root patch?
Good night. I see that you have Acidanthera in motherboard. Instead of Apple Inc. So are you using OpenCore? Not OpenCore Legacy patcher? How do you do to have graphic acceleration without the OCLP root patch?
@caiolbarros
Maybe. What I can say is that performance on Ventura beta is not worse than on Monterey.
Maybe. What I can say is that performance on Ventura beta is not worse than on Monterey.
No I use OCLP ventura-alpha branch in my (Real Mac), but I update the 0.8.0 OCLP OpenCore by new 0.8.5, and changed the SMBIOS for MacBookPro14,1 with OpenCore Configurator. Working everything like a charm.
@fernando.c.neves
Understood. I have OCLP 0.5.0 with OpenCore 0.8.3 so there is not so much difference but I hadn't thought about the possibility of updating OpenCore files within OCLP. I'm going to try it. Thanks.
Understood. I have OCLP 0.5.0 with OpenCore 0.8.3 so there is not so much difference but I hadn't thought about the possibility of updating OpenCore files within OCLP. I'm going to try it. Thanks.
Even better results here with iMac 17,1 Radeon M395, Beta 8. But Photos App is still crashing here, whenever you create a new library and add one picture... Do you have the same behavior?
This sounds good, for the things to come:
Yes, the same behavior. It has been fixed for Intel 5-6-7th gen. (I think) but not for AMD and Nvidia.
Great! Looks like it can be done until RC/final release is out!
Indeed very promising.
On MBP5,2 just re-installing 13.0b8 using the latest OCLP 050n which features the automatic Cryptex and KDK installation…
Last edited:
Would just like to note that Apple can break this very easily if they decide to stop shipping both cryptexes in the full bundle (which there is some incentive for, as they could save a few GB). Or they could also just stop shipping a non-AVX2 dyld cache on arm64e.
Combined with the KDK situation, Ventura is a tricky beast.
Installation on MBP5,2 proceeded automatically right to login, without replacing os.dmg manually. Also KDK seems in place. Writing from this installation now.
Installed from USB installer using latest OCLP 050n, to external SSD, over the existing 13.0b8.
(yet to verify that it is not positive effects of leftovers from previous installation)
Thanks dhinakg and khronokernel!
Edit: os.dmg is really from tonight's installation.
Attachments
Last edited:
Would you (or anybody else) please post a link to the most recent compiled OCLP 050n.app ... am finding it impossible to do myself from source, as all kinds of weird Python error are thrown in series. Cheers!
PS: finally got it compiled after downgrading from Python 3.10.7 to 3.9.13 & installing Command_Line_Tools_for_Xcode_14.dmg, with this report in Terminal:
~/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/Build-Binary.command ; exit;
- Starting build script
- Current Working Directory:
~/Downloads/OpenCore-Legacy-Patcher-ventura-alpha
- Starting preflight processes
- Deleting extra binaries...
- Downloading required resources...
- Universal-Binaries.zip already exists, skipping download
- payloads.dmg already exists, skipping creation
- Building GUI binary...
- Starting postflight processes
- Patching LC_VERSION_MIN_MACOSX
- No commit data provided, adding source info
- Adding commit data to Info.plist
- Build script completed in 15.73 seconds
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]... but when I double-click to run the resulting OpenCore-Patcher.app [a rather hefty 553.4MB] located in the Dist folder, literally nothing happens in Monterey 12.6 ... SIGH ... what am I doing wrong?
PPS: discovered via running OCLP.command (without building), that it still needed this:
pip3.9 install -U wxPython... after which it is working 99% (fails on permissions to write results into /EFI partition, but can be done manually) ... Phew!!
Last edited: