Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hey all, lurker since page one here. Managed to get Ventura b6 installed on my MacBookPro13,2 Intel 550. Used the ventura-alpha branch. Pretty dang pumped, so I'm going to stress test a bit with some XCode builds tonight.
 

Attachments

  • ventura-oclp.png
    ventura-oclp.png
    1.5 MB · Views: 411
Last edited:
1.png


Ventura doesn't get to the end. Why? The video card didn't boot up or something?
And through the safe mode, Ventura is loaded. And I see an AMD WX7100 graphics card.
Kernel_Debug_Kit_13.0_build_22A5331f - must I?
 
View attachment 2050210

Ventura doesn't get to the end. Why? The video card didn't boot up or something?
And through the safe mode, Ventura is loaded. And I see an AMD WX7100 graphics card.
Kernel_Debug_Kit_13.0_build_22A5331f - must I?
In dortania GPU Buyers Guide your DGPU should work with Monterey, need's Lilu and WEG (Latest) in your EFI (OpenCore).


Download the kext's from this source, is the latest.

 
Last edited:
Has anyone tried it on a late iMac 2012?

the instslations process runs at such well and also boots through a few times, but gets stuck at the end and freeze
 
Success with yesterdays nightly on MacBook8,1 with Intel HD5300.
Of course, AMFI ("get lost") and _authenticate_root_hash for Rosetta's OS.dmg contents have to be applied as well as SIP 0xa03. Then after patching, metal works. Trackpad (full featured) and Wifi also oob.
Not sure, if Kernel Debug Kit still needed (have it still on the root volume) because Kexts seem to register nicely with Ventura asking permission to enable them via control center privacy settings.
 

Attachments

  • Bildschirm­foto 2022-09-03 um 12.14.21.png
    Bildschirm­foto 2022-09-03 um 12.14.21.png
    343.8 KB · Views: 99
Any ideas how to get going with Open Core on MP6,1 ?

Is the dual-GPU and rather special bus interconnection a problem?
Can't get the ton booting with OCLP at all or it resets while logging in or a few seconds later* (even under Monterey, which while being natively supported for it, would be a good first test ground for OC / OCLP).
OCLP detects the machine correctly, but disables the "build & install" button if set to MP6,1.

* has been reported in mid-January to @khronokernel but there has not been any follow-up since (I suspect there were no sufficient logs/dumps/error reports to pursue it).
 
Stop this and read the twitter post, again. There is simply no GCN4 support (Polaris or Ellesmere cards) and no support for all this right now. Even the AVX2 problem has not been tackled.
last year, the same problem occurred in the Monterey system. I added the configuration to Openkore config.plist, and the Monterey system booted up to the end.
There are drivers in the Ventura system. I am a developer and programmer. I know for sure that Ventura has a driver for the W X 7100!!! Obviously, Ventura downloaded the video card. But the problem lies in the configuration of Openkore.
The fact that they write that Polaris and others have disabled it is not true!!!
Ventura requires AVX1 !!! And AVX2 does NOT require!!! We have to wait for Ventura's release. Then I'll figure it out completely.
 
last year, the same problem occurred in the Monterey system. I added the configuration to Openkore config.plist, and the Monterey system booted up to the end.
There are drivers in the Ventura system. I am a developer and programmer. I know for sure that Ventura has a driver for the W X 7100!!! Obviously, Ventura downloaded the video card. But the problem lies in the configuration of Openkore.
The fact that they write that Polaris and others have disabled it is not true!!!
Ventura requires AVX1 !!! And AVX2 does NOT require!!! We have to wait for Ventura's release. Then I'll figure it out completely.
The OCLP patcher worked with Monterey Beta 1 on the day it has been released with Polaris and Ellesmere dGPU. There was never a need to change the OpenCore to make it work (it is a C). So it cannot be the same problem as on Monterey, this is simply wrong.

I found AVX2 code in the graphics accelerator, that is why safe mode boot is working on systems with Polaris and Ellesmere dGPU (half way, just because it turns off acceleration). Check the first post about this AVX2 problem. AVX2 code has been found in many places. So your AVX statement is wrong, too.

There is a least one post from a user of an now unsupported MacBookPro 2016 with a Polaris dGPU, it does not run in normal mode using the dGPU (only the iGPU). At least this modern CPU does not suffer the general AVX2 problem.
(Edit: The system could use the dGPU and it is possible to fix brightness control. But it stuck on dGPU, so no switching to iGPU possible using these hacks.).

New versions of OpenCore can and will be a part of the solution, but I am afraid we will end up with patching even Polaris and Ellesemere although still supported BECAUSE OF THE AVX2 problem. Therefore I wrote no support for GCN4 in the current beta OCLP patcher.

But I am happy to see you fixing stuff and will wait until you release your fork of the patcher with OpenCore changes, only. Have fun and success!

EDIT: And I would be more than happy if we do not need any additional AVX2 related patches.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.