Pri-est
macrumors regular
Are you seriously?For real? Post an issue on Github and hopefully he’ll see it.
Are you seriously?For real? Post an issue on Github and hopefully he’ll see it.
currently it's not work, not available patches for BroadwellI'll try it as soon as I have access to my pro 13 2015
as expected...currently it's not work, not available patches for Broadwell
Downloading 15.7.9 (24G830) on my mid 2012 retina MacBookPro (ivy bridge).
The 5.1's CPU is already struggling on Sequoia, due to lack of AVX, let alone on TahoeHas anyone tried installing Tahoe, on the 5,1?
JUST WONDERING?
I have managed to boot my Mac mini 2018 into the macOS 26 Tahoe installer, but when it’s time to boot the OS from an external SSD, APFS related kexts (I think AppleImage4.kext + apfs.kext), both panic with Needs authenticator (81):Good to know. I suspect the challenge this year will be getting it to run on non-T2 Macs. Macs like the 2018 Mac mini and 2020 MacBook Air with T2 should be easier I'd think.
Although, if MacOS can still run in a VM environment with no T2, maybe not. Someone please confirm!
your work is amazing, I hope you and your team have great success with this project! and hopefully more than just T2 Macs! but again I still hope for success for the official dortaina OCLP!I have managed to boot my Mac mini 2018 into the macOS 26 Tahoe installer, but when it’s time to boot the OS from an external SSD, APFS related kexts (I think AppleImage4.kext + apfs.kext), both panic with Needs authenticator (81):
This issue is documented in my project: https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/issues/130
So if you can help me, you can come to my repo. But since I don’t have serial debugging cable, and bridgeOS panics shortly after displaying the panic, an Ethernet debugging would be as useless as a broken HDD hard drive.
Okay, just opened a new discussion here: https://forums.macrumors.com/thread...it-fails-with-appleimage4-apfs-panic.2486563/@Albert Müller You may want to start a new macRumors thread for discussion of unsupported T2 debugging. You can post a link to your thread in this thread. Just a thought.
Yes, you're absolutely right. Broadwell patches are not available at this time in any PatcherSupportPkg for macOS 26 Tahoe. Anyone using these series GPUs should avoid upgrading to Tahoe.currently it's not work, not available patches for Broadwell
It’s sad, but I want to say that you’re a cool I’m sure your future work will benefit both T2 and non-T2 Macs🙂Yes, you're absolutely right. Broadwell patches are not available at this time in any PatcherSupportPkg for macOS 26 Tahoe. Anyone using these series GPUs should avoid upgrading to Tahoe.
Except the Broadwell graphics, and maybe the old NVIDIA GPUs, everything else seems to work fine on Tahoe.It’s sad, but I want to say that you’re a cool I’m sure your future work will benefit both T2 and non-T2 Macs🙂
The problematic one is PatcherSupportPkg (any), the Metallibs is fine. PatcherSupportPkg has no patches for Broadwell GPUs for Tahoe, regardless of the repo I looked at. The Metallibs that you pointed is exactly the one I’m using and that one has zero issues with all GPUs that require it. To be exact, the missing patches in PatcherSupportPkg are these:So, for example, would your OCLP-T2 make Tahoe work, with all required patches, with Haswell, Intel Iris Pro and NVIDIA GeForce GT 750M (as in the MBP11,3)…? Or is it too early and still better to wait? And the needed Tahoe MetallibSupport package should presumably be taken from here:
![]()
GitHub - pyquick/MetallibSupportPkg
Contribute to pyquick/MetallibSupportPkg development by creating an account on GitHub.github.com
… right…? I would be tempted to try, but only if reasonably sure that it really works (and maybe experimenting on an external Thunderbolt drive, initially: possible?)…
same boat hereInteresting… And I guess that it might be better to wait a little more, for Tahoe on the late 2013 MBP (no hurry: Sequoia works perfectly). Good to know there is an actively developed OCLP fork…
yup Sequoia works perfectly currently even on my ivy bridge 10,2 so we can wait for Tahoe either on the official Dortaina OCLP or this T2 OCLP which both developers for are amazing! but I do wish the official team would show us some updates tho.. also can you send me the OCLP 2.5.0 nightly? I had the package but Windows ate my SSD yesterday and I had to re install Sequoia alongside lossing my stuff on the 10,2 sadly 🙁Interesting… And I guess that it might be better to wait a little more, for Tahoe on the late 2013 MBP (no hurry: Sequoia works perfectly). Good to know there is an actively developed OCLP fork…
I understand why this sentiment goes around but I doubt for a second that Apple is the slightest bit concerned about OCLP or any more than it has shown itself to be about hackintoshes because it helps to keep people within the Apple ecosystem where they may otherwise drift away. At the end of the day, the biggest money spinners for Apple are its iPhone and associated services. Traditional computers take a much smaller slice of the pie but help to keep interest in the iPhone and provide hardware for iOS development. As popular as OCLP seems to be, it is still a tiny minority of the entire Apple userbase which bothers with it, ditto hackintoshes.And I also think the work of developers in privacy is a very reasonable plus because I think the Apple team also monitors some times how things are in the old Mac and the popular patcher, and let's imagine how it could be the developers of the patcher spread the patch or what they did to start something, and Apple while still working on Tahoe could freely close the hole so that the patch or something stops working, still I think the new marketing teams in apple are clearly not happy because people can buy the old one instead of the new one and without any problems installing the new system and use