It would actually be great to hear at least something, at least some current progress of development, where exactly they are, that would be really cool🙂🙂🙂
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Tahoe 26 on Unsupported Macs Discussion
- Thread starter jshayya0184
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
This is like the sequel to Spaceballs for me right now; they always said a sequel was coming, and then it finally arrived 40 years later. 🙂
While sure showing where you are in development would help us ( the community) a LOT but that will also open doors for you, Some positive and some negative and some doors will lead to people asking "after this update, can we see Tahoe THIS September?? and Will my 2008 MacBookPro Work on Tahoe Perfectly?" that message alone makes it questionable IMO.
Good reference lol 😆 But hopefully with OCLP we see it sooner than later.. But we have to remember to keep our expectations in check.. sadly.
answer: yes your 18 years old MacBook Pro will work perfectly! Even better than apple silicon devices, because apple gave it a gift for its 18th birthday, full optimization for Tahoe, so enjoy🎂😁
that must sound nice lmao 😂 But jokes aside those comments that people send the devs are probably a reason why they don't give us updates about progress. Which while sad but I understand the view point.
It seems an odd hill to die on, passively defending the idea of people that swipe code without remorse or due credit from creative people under an arbitrary non-charitable self-serving non-reading of Open Source licensing and I am pretty sure that was never the plan, as I attended meetings many moons ago pre-internet about this. But along with AI and the age of solipsism it has certainly become the flow.
For whatever time is left on this thread it would certainly be nice if we just support our own specific code creators and ignore the code swipers. I would surmise that ignoring this kind of behaviour is also self-serving and surely not conducive to an inspirational open source coding environment for the humans that still take time to create the code we need and use.
No more from me about this though and who knows, as unlikely as it seems at this time, this thread may still live to see another patch or two released. But about this we know precisely 0% as @hackintosh_user wrote. I am regardless happy with what happened during an extra ordinary open source coding run.
For whatever time is left on this thread it would certainly be nice if we just support our own specific code creators and ignore the code swipers. I would surmise that ignoring this kind of behaviour is also self-serving and surely not conducive to an inspirational open source coding environment for the humans that still take time to create the code we need and use.
No more from me about this though and who knows, as unlikely as it seems at this time, this thread may still live to see another patch or two released. But about this we know precisely 0% as @hackintosh_user wrote. I am regardless happy with what happened during an extra ordinary open source coding run.
It's honestly sad to say I've lost hope in seeing a release ( I'm a user of oclp since the days when big sur was the latest). But miracles happen. And hey maybe if it's taxing the devs mentally then it's better if Tahoe support had to be never supported. Mind you I've never said something negative about OCLP since the days it was a terminal CLI this is the first time for me personally. I'm not the type to lose hope, but for the first time it seems like I've lost hope in OpenCore legacy patcher releasing a Tahoe release. And let's think about the insane ride we had, 5 years of support that's such an honor. The devs are the best people ever for achieving that. I personally thought Sequoia was too hard to patch but we got it. But now looking at it I don't think it's possible for a tahoe release.. with dev departures and each update breaking things I think the chance is even lower now, with how hard developing a patcher is, with tahoe breaking things each update, it IS NOT easy at all. But again, miracles happen.
Last edited:
deeveedee
macrumors 68000
where have I heard that before 😂
firelighter487
macrumors 6502
i have a hackintosh running tahoe, i can confirm it absolutely doesn't need a T2 lol
Yes, but OCLP-Plus doesn't care of the video card. The user should take care in his open core setup.
Depends what you mean by "needs". A Mac that has a T2 runs lots of critical stuff through it like at least
Secure Boot, Hardware Encryption, Touch ID Management, Image Processing and manages various system controllers to and functions like power management and battery charging and it has so far proven rather difficult to patch for OCLP.
That your PC does not require a T2 to run Tahoe is while related, obviously a slightly different issue.
Sure but a T2 Mac that would run Tahoe From OCLP literally Can't boot without the T2 as it handles critical stuff like the SSD Controller, Touch ID, security enclave, etc... But since Hackintoshes dont need a T2 it boots fine.. this is also why iPhone mirrioring doesn't work as that Needs the T2 Chip which older Macs & hacks Don't have.
deeveedee
macrumors 68000
An interesting choice Apple made that created an easier path to macOS Tahoe on an "unsupported" hackintosh than on a real "unsupported" Mac. Hopefully macOS Tahoe will run just as well on unsupported T2 Macs as it does on our hacks.
It's rather funny lol 😆 but it's apple what do we expect?
deeveedee
macrumors 68000
From one of the "unauthorized" OCLP forks:
While I continue to cheer for the original OCLP team's success, I think the competition is healthy. And since the competition is performing development out in the open, maybe there will be lessons learned that benefit the remaining original OCLP developers.
While I continue to cheer for the original OCLP team's success, I think the competition is healthy. And since the competition is performing development out in the open, maybe there will be lessons learned that benefit the remaining original OCLP developers.
basslik
macrumors 6502a
I left a step by step guide below that worked when getting my 2017 iMac 4K. There’s a chance Tahoe could work on your 2012-2016 Mac but I can’t make promises. Check this: https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/releases/tag/4.0.0.16040
Last edited:
On my MacBook Pro 13 2015 I browsed all the forks that were there, so tell me where the patches for Intel Broadwell graphics came from? Or even if these are 2012 2013 2014, 2016 machines, there are no patches for the graphics the graphics that work on 2017 models it's native Tahoe support without any patcher... So don't spread untrue information about 2012 and newer models, write at least 2017 or models that can work...
sorry, I didn't see that, I'll try it as soon as I have access to my pro 13 2015, thanks for the info! I'll post later on what happened.
Pri-est
macrumors regular
Tried on MacMini6,2 and MacMini7,1 - no graphics patches.
For real? Post an issue on Github and hopefully he’ll see it.