Do you have a GitHub account? It’s free. Without it, the file is not available. I can download the app from the posted link even in my iPad.
Thanks, I wasn't logged in, regards
Does this link require compiling or is it Ventura Alpha .5 in a format like 4.11 which works well with my 13.2 Kepler/Ivybridge Imac. Thanks ron
This is the app compiled by OCLP site. To be run directly.Does this link require compiling or is it Ventura Alpha .5 in a format like 4.11 which works well with my 13.2 Kepler/Ivybridge Imac. Thanks ron
Again, @Ausdauersportler already told you. Don't use the "Force Web Drivers" option. It forces your GPU into non-Metal rendering mode. The option is solely there for development purposes, no practical application for end users. I feel like I should put a paywall/password up on OCLP's settings.Quadro K2000M video card works in Monterey and Venture systems, metal works!
The Quadro P5000M graphics card runs on the Monterey system, metal works! And in the Venture system, it requires KDK. I don't understand. Why KDK??????????????????????? OCLP does not require KDK for K2000M. And for P5000M requires KDK. After all, the P5000M supports metal. I won't install KDK because it kills the graphics card accelerator!
I like your work! I'm acting like I am. I have no power over this. I like to understand something new. I like to look for reasons and find the answer in problems.Again, @Ausdauersportler already told you. Don't use the "Force Web Drivers" option. It forces your GPU into non-Metal rendering mode. The option is solely there for development purposes, no practical application for end users. I feel like I should put a paywall/password up on OCLP's settings.
And the reason there's a KDK check is the non-Metal would require a KDK due to the nature of IOSurface swapping. And there's no non-Metal support in Ventura at this time:
Also please be more respectful and stop acting like you're in authority. We have enough misinformation floating around due to this thread, would really like to clean it up. Remember, people a year from now will be reading this thread for research...
Ironic the once in a blue moon I comment here is for this.
While I'm here, might as well make some general comments on Ventura support for the community. Namely what to expect when we do release OCLP 0.5.0 to the general public.
Currently we're quite happy with progress internally on legacy Metal. Still need a fair amount of love for the patches, however for the most part they're usable.
Regarding current issues, we believe these ones will remain broken by release time:
And other issues are listed on the Ventura issue, above are the main noteworthy concerns:
- USB 1.1 support
- Applicable for Penryn and Cheese Grater Mac Pros
- ie. Bluetooth, Internal Keyboard/Mouse
- Legacy Wireless support
- Applicable Wifi cards needing root patches in Monterey
- ie. Atheros, BCM94328, BCM94322
- Non-Metal Graphics Acceleration
- AMD TeraScale 1/2, Nvidia Tesla/Web Drivers, Intel Ironlake and Sandy Bridge
- MacPro6,1 Boot Support
- Completely unbootable for most (if not all)
- Cause unknown, will be looking into getting a unit (donations appreciated)
- Reference:
- Broken Power Management on Ivy Bridge and older
- CPU stuck at base clock, won't idle lower or boost
Otherwise that's all from me for now, I'll be returning to my cave again and hammering through some more development. Hope everyone's enjoying the work we've been putting out so far.
- Mykola
The "no space left on device" might be a clue...Question: when I try to install open core onto a 128gb apple ssd I get this anybody have a solution maybe a script or what?
Quite the contrary.I'm acting like I am. I have no power over this.
No, certainly not on your EFI volume. Check that one...The "no space left on device" might be a clue...
Didn't investigate further (I think I was on the wrong track) - khronokernel made many improvements to AMFI and KDK handling meanwhile.I'm continuing some post-install patch exercises on MBP5,2 (13.0b9, OCLP 050 from yesterday). I saw a difficulty to disable AMFI earlier (others as well?) and looked closer this time. AMFI should be disabled automatically but isn't.
I think it is likely a Python problem in resources/sys_patch_detect.py: the dictionary root_patch_dict has a conditional expression regarding "Validation: AMFI is enabled". This seems to be evaluated incorrectly. When pulling to expression out of the dictionary, works as expected.
(in the attached outputs never mind the KDK missing message - it is really not yet there).
python3.9 and 3.10 show the same problem. I could be on the wrong track of course.
Do not judge, so that you will not be judged, for with what judgment you judge, so you will be judged; and with what measure you measure, so they will measure you.Quite the contrary.
I really love people giving advices and do not (of course) act according to these on their own.Do not judge, so that you will not be judged, for with what judgment you judge, so you will be judged; and with what measure you measure, so they will measure you.
I like to understand everything and develop and help, prompt. And you - my advice - ask me first, and then condemn me. Ok?
I am not a OCLP developer!!!I really love people giving advices and do not (of course) act according to these on their own.
If you really want to understand everything why you cannot start your posts with a simple question?
Or just post the status you have achieved by using a software not meant to hit the public of inexperienced users.
No, the posts usually start with some (false) alternative facts and end with a lot of exclamation marks in a row and with demands like: This has to be fixed!
Jesus, you should hear yourself talking and see yourself writing here!