macOS 13 Ventura on Unsupported Macs Thread

[Painkiller]

Just out of curiosity I swapped the os.dmg out of a m1 bspw file with the one on my preboot drawer and got Ventura booted on my old 2011 iMac. Because it is running from an external ssd it feels a bit sluggish. Have to play a bit with it to see for myself how useful ist is.

😁
PS: after root patching the second screen is still offline.....

 

[justperry]

Everything works including updates. There might be some bugs, but I expect them to be fixed on final release. NOTE: Installed it on my productive system, no issues so far. Grab OCLP binary from Github(you need to be registered, there is a link https://github.com/dortania/OpenCore-Legacy-Patcher/actions/runs/3250950723 and go for it. Patching process is not different from Monterey, pretty easy to install over Monterey installation. In case Public Beta 9 does not work use 8 and then update it.

Installed yesterday on separate Hdd in a 2012 Mac Mini which has the same internals as the Mbp, seems to run well, I didn’t have a lot of time on the OS yet, if it’s ok after a week I will try to install over Monterey.

Edit: These people figuring out how to install these os’s and make everything work are heroes.👍🥳🍰🍸

 

[amaze1499]

Update to 22A5373b done using 0.5.0. No issues. Stage manager works, but from what I can see it's literally another dock only for open app windows.

In this build Finder shows for whatever reasons extraordinarily long loading times for content on external media on numerous occasions. First time ever: AppleTV plays content without crashing. Many apps still need quite a bit of polishing from what I can gather.

Thanks to all developers making this possible!

 

[megaholti]

Hi my mac is 14.2 with gforce graphic. i installed Ventura since beta 1 without Keppler graphic. after Ventura-alpha support i try to install root patches.

but i get on all Ventura betas since 0.5.0 alpha error 71. there is no information on screen from kdk, so i installed manually from my apple developer account myself, but it doesn't work.
after reboot the mac starts normal, but the display is still black. there's nothing showing only a black screen.
after reboot in safe mode it works normal but without accerlation. so i need help.

maybe i forgot one step before?!

 

[TOM1211]

VM fusion working again on beta 11 with newest oclp patches which is great two unsupported operating Systems running at once lol

 

[perez987]

@megaholti
This has happened to me anytime. Are you re-applying the patch with the same OpenCore-Patcher app not updated in the meantime? Last time I wasn’t able to fix it. Had to erase and reinstall.

 

[megaholti]

@megaholti
This has happened to me anytime. Are you re-applying the patch with the same OpenCore-Patcher app not updated in the meantime? Last time I wasn’t able to fix it. Had to erase and reinstall.

reinstall, really? that's bad news. maybe i wait for public release from Ventura and OCP. if there's no reason after release, i reinstall. maybe anyone has a great idea?

 

[shafez]

Could someone post a link to the latest compiled OCLP 0.5.0 Alfa nightly build as I find it difficult to copile the sorce, regards

 

[sinbad21]

Could someone post a link to the latest compiled OCLP 0.5.0 Alfa nightly build as I find it difficult to copile the sorce, regards

Look at Actions page, and search the most recent "Build wxPython" item.

 

[EAMTIsMyThing]

Requirements. They are aggressive - Not only 2015 MBP dropped, but the 2016 MBP dropped too!


View attachment 2014423

Yeah pretty upset about the dropped 2015 MBP-Just got mine second hand a little while ago and its already being dropped

 

[OKonnel]

Hi my mac is 14.2 with gforce graphic. i installed Ventura since beta 1 without Keppler graphic… …(…omissis…)… *Maybe i forgot one step before?*

I say this with sympathy, @megaholti : you forgot the great invitation addressed to everyone by @khronokernel (the OCLP’s Developers leader) to wait for the development team announce that all these problems have been solved.
I also have your Mac 14,2 CPU i7 with nVidia GTX780M Kepler series and if you really want to try the progress of OCLP 0.5.0 you can do as I did, but using Monterey and not Ventura.
So, in Monterey 12.6 I got OpenCL recognition from Geekbench 5 and last Photoshop 2022 and that's already something.
I tried OCLP 0.5.0 and its Post Install Patch with Monterey; however I have reinstalled the official OCLP 0.4.11 and OpenCL continues to work as GPUCompiler.framework remains in System as modified by the OCLP 0.5.0’s PIP.
If you are a Discord user you can read —> here

 

[shafez]

Yes it gets installed, but it's useless because ntfs devices are readonly.

It works for me 😀, Download the latest Trial Version , Install , Allow ind Privacy&Security and restart. Register, Unmount then mount again. macOS 13 B11.

 

[Painkiller]

Is someone experiencing issues with a second external screen via thunderbolt? Is there a new limitation again?

 

[sinbad21]

It works for me 😀, Download the latest Trial Version , Install , Allow ind Privacy&Security and restart. Register, Unmount then mount again. macOS 13 B11.

Good news, it's probably because I had the option "mount readonly" checked in preferences. I had this problem also with Monterey, I've just verified, the option readonly was on.

 

[justperry]

Hi my mac is 14.2 with gforce graphic. i installed Ventura since beta 1 without Keppler graphic. after Ventura-alpha support i try to install root patches.

but i get on all Ventura betas since 0.5.0 alpha error 71. there is no information on screen from kdk, so i installed manually from my apple developer account myself, but it doesn't work.
after reboot the mac starts normal, but the display is still black. there's nothing showing only a black screen.
after reboot in safe mode it works normal but without accerlation. so i need help.

maybe i forgot one step before?!

Did you use migration assistant, I did use migration assistant last week after having problems with Monterey, did not boot, black screen but safe boot worked, obviously without acceleration.

 

[drew24]

tanks to u guys and OCLP iam running Ventura 11 on my MBP 6.1 cant wait for the release

 

[perez987]

Tonight @khronokernel has made major fixes: resolve numerous AMD GCN 1-3 issues (ex. Photos.app, Screen Saver, etc.). The skill of this team continues to amaze me.

 

[nico81]

MacBookPro13,3 (the only computer with a Polaris GPU and no Ventura support) does in fact have dGPU acceleration, but sleep and brightness aren't working and the GPU shows as "AMD Radeon Polaris". This appears to be because ATY,Berbice support was removed from AMD9500Controller. I am going to see if spoofing as ATY,Longavi (the 2017 MBP; same connector config) works.

Using openCore? I didn't even manage to boot. Can you link me the guide you follow?

 

[Sanmiguel71]

Tonight @khronokernel has made major fixes: resolve numerous AMD GCN 1-3 issues (ex. Photos.app, Screen Saver, etc.). The skill of this team continues to amaze me.

With this nightly, my iMac 17,1 legacy AMD GCN 2(?), AMD Radeon R9 M395, is not able to boot anymore? Anyone else?

 

[perez987]

@Sanmiguel71
Not tried yet but there are reports of issues by other users. Eg: stuck at login screen.

 

[Sanmiguel71]

Ok thanks, I do not even reach the Login screen… try to do more research later.

 

[khronokernel]

With this nightly, my iMac 17,1 legacy AMD GCN 2(?), AMD Radeon R9 M395, is not able to boot anymore? Anyone else?

Did you build from source without cleaning the binaries? OCLP has new resources that are updated all the time (ie. PatcherSupportPkg). You need to reset them each time you compile.

OpenCore-Legacy-Patcher/SOURCE.md at main · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

# Optional Arguments
#    '--build_tui':          Create TUI vairant
#    '--reset_binaries':     Redownload and generate support files
python3 Build-Binary.command --reset_binaries

 

[khronokernel]

I will add to this, everyone please stop compiling OCLP from source. We've gotten a ton of noise about builds we cannot validate due to potential environment issues when you compiled the program. Please everyone, use Github Actions:

Workflow runs · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

Each commit will have a compiled binary that is both signed and notarized, using the same build server we use for release binaries.

If you want to find an exact commit, look at the check mark next to each commit on Github and select wxPython Details. The binaries are under Summary:

 

[Sanmiguel71]

Did you build from source without cleaning the binaries? OCLP has new resources that are updated all the time (ie. PatcherSupportPkg). You need to reset them each time you compile.

OpenCore-Legacy-Patcher/SOURCE.md at main · dortania/OpenCore-Legacy-Patcher

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.

github.com

# Optional Arguments
#    '--build_tui':          Create TUI vairant
#    '--reset_binaries':     Redownload and generate support files
python3 Build-Binary.command --reset_binaries

Hi,

first of all, thank you for your massiv support and work for this awesome project.

To my issue: not sure anymore, tried several versions (self compiled), including the binary you recommend by direct downloading from GitHub. Just tried again from my Monterey SSD (booted natively without OCLP), then with the latest downloaded binary, first deleted the EFI portion of the (internal) Ventura SSD and reapplied OCLP from scratch. But the result is the same, cannot reach the Login screen...

 

[khronokernel]

But the result is the same, cannot reach the Login screen...

You reinstalled Ventura with the latest commit outright? Reason you couldn't log in previously is that your root patches were outdated/incompatible