I get a kernel panic.If I’m cable connected… continuity works without issue.
If I try wirelessly i’m done. Totally frozen.I get a kernel panic.
Do we need to install everything that´s on the video? The Kernel Debug and Universal Binaries? I've never installed any of these, only OCLP and eveything runs smoothly.Just finished watching this. Thought people would find the progress encouraging :
I'm not currently running with OCLP. I'm only keeping up with progress right now for knowledge. Currently I'm running Monterey which is the last supported OS for this iMac. So, I would say do your research based on your mac. This video is only a tool in that process for those who want to try the beta.Do we need to install everything that´s on the video? The Kernel Debug and Universal Binaries? I've never installed any of these, only OCLP and eveything runs smoothly.
It is implicit in OCLP:Do we need to install everything that´s on the video? The Kernel Debug and Universal Binaries? I've never installed any of these, only OCLP and eveything runs smoothly.
What graphics card do you use on your Mac Pro?Works great on my MacBook Pro 14,3 and Mac Pro 5,1. Thanks to the developers for great work!
Is the screen brightness adjustable?Works great on my MacBook Pro 14,3
Stop spreading misinformation.The process kernel_task is visible - a bad sign. It will take up a lot of virtual memory and thousands of errors. On a normally working computer it should not be visible. I would not install this on my computer. Even under a court order.
He is actually right about the `kernel_task`. As you are aware, because you Googled it, `kernel_task` is responsible for multiple functions related to maintaining your system, among other things. Up until last year, for example, the Mac Pro 6,1 had broken support for CPU throttling and would constantly keep the CPU clocked high, causing the system to run hot. That’s just one of many examples involving different models. He is not wrong—`kernel_task` should not be visible at the top of the list in iStat for more than a few minutes after startup. If it remains there the entire time, that is not normal. If you open the Event Viewer in Utilities, I guarantee you will see errors. Now, while you used Google, I can overlook that because I used to work for Apple. So, before you call people out, please use more than just a Google search. Other than that, let’s try to be kind to each other. There's already enough hatred in the world, and this isn't the place nor the time for it.
Yes - maybe. The screenshot was taken just 9 minutes after the initial boot after patching, now it is quite silent.The process kernel_task is visible - a bad sign. It will take up a lot of virtual memory and thousands of errors. On a normally working computer it should not be visible. I would not install this on my computer. Even under a court order.
RX580 8gbWhat graphics card do you use on your Mac Pro?
Could I get the file you built?MBP11,1 (Haswell): OTA updated to 15.0b8, then root patched with latest 1.6.0n sequoia-development branch.
Wonderful work by the developers using novel techniques to overcome the sequoia graphics hurdles! Have a look at all of the recent change log.
The patcher installs MetallibSupportPkg in /Library/Application Support/Dortania which contains all the good things.
Graphics acceleration is there, transparency, proper display resolution, brightness adjust... wifi anyway. Photos (10.0) works.
Running the patcher from source. Bypassed a "3802 patchability check" for now by just one change:
in sys_patch/detections/detect.py line 724 commented out the return False.
This is just for testing... better wait for the release by developers.
What guests are you virtualizing? Windows, macOS, Linux, etc? Also what GPU. Maybe macOS 15 will make these graphics issues easier to work with going forward on patched macs.Maybe someone else can use a way to deactivate the Gatekeeper here
disable Gatekeeper with configuration profiles in macOS 15
disable Gatekeeper with configuration profiles in macOS 15 - README.mdgist.github.com
In addition, hardware acceleration in Parallels Desktop is running again on my Macbook Pro 13.2 with macOS 15
With macOS 14, the whole Macbook always freezes when starting up