macOS Tahoe 26 on Unsupported Macs Discussion

[hvds]

Updated my MBP5,2 to 26.0b3 from b1. Running as expected now.

Using OCLP 3.0.0n branch macos-next from source. The last commit from 14 July is relevant because it is a USB1.1 machine. The generated EFI could‘t boot Tahoe b1 or the b3 installer. Commenting out the last commit fixed it. - All OK on MBP11,1 as it should when looking at the source.

No patching attempted yet on the 5,2. Partial patching (camera only) fine on 11,1.

As always, big thank you developers!

MBP5,2 running 26b3: now trying root patching.

During patching, some files missing as expected with the existing (non-Tahoe) Universal-Binaries.dmg. Added missing paths while patcher active as follows, naively:
cd /var/folders/3h/kf6jzpcn01g9lyb37m6ystn80000gn/T/tmp0foem7_w/payloads/Universal-Binaries
# for missing wps (etc...)
cp -Rp 12.7.2-24 12.7.2-25
# for missing AppleHDA.kext (taken from 26b1)
mkdir -p 26.0\ Beta\ 1/System/Library/Extension
cd 26.0\ Beta\ 1/System/Library/Extensions
cp -Rp /Users/hvds/Desktop/exp/AppleHDA.kext .
then patcher proceeded to the end.
Patched system did boot. Needed a bootloader enabling the pre-Tahoe usb map as foreseen by the developers (previously mentioned bootloader without commit from 14 July needed for nonpatched system and installer).

Booted upto password entering. On the way: keyboard backlight went on, and internal keyboard/trackpad worked! Didn't get beyond password entering yet - system doesn't proceed but mouse pointer still moving - and quickly! But can't test graphics, internal audio, wifi so far.

 

[rehkram]

My policy with beta macOS's on unsupported Macs is to 1) leave them alone and 2) wait for the public release. This is usually followed by 3) the new public version of OCLP that goes with it.

This gives the Dortania devs time to break- and hopefully fix- or enhance OCLP to solve the problems. That's what betas are for.

I've been burned by my own impatience too often to waste any more of my machine time on unsupported macOS's in beta, and OCLP nightlies.

The only time I consider it is when the current macOS is a dog and the reviews for a beta and/or nightly OCLP are good. The warnings are pretty clear from Dortania, we're on our own.

 

[deeveedee]

The warnings are pretty clear from Dortania, we're on our own.

For some, this is a comfort zone.

 

[OKonnel]

My policy with beta macOS's on unsupported Macs is to 1) leave them alone and 2) wait for the public release. This is usually followed by 3) the new public version of OCLP that goes with it.

This gives the Dortania devs time to break- and hopefully fix- or enhance OCLP to solve the problems. That's what betas are for.

I've been burned by my own impatience too often to waste any more of my machine time on unsupported macOS's in beta, and OCLP nightlies.

The only time I consider it is when the current macOS is a dog and the reviews for a beta and/or nightly OCLP are good. The warnings are pretty clear from Dortania, we're on our own.

Thank you @rehkram ! You have expressed exactly the most pertinent thought and I would also say the reality.

As a matter of fact, to my knowledge, there has never been and there is no invitation from the OCLP Developers to experiment with the versions of macOS + OCLP still in Beta let alone delude themselves and the forum’s users… —> …that this will help the development.

Obviously everyone is free to try any experience and share it but, as you say, it is a waste of time since naive attempts are made and no action is taken on the OCLP Code.
Conversely, those who are really capable of programming can safely join the development of OCLP through GitHub.

[A small note. I made a small addition to the Code when OCLP was still in its infancy, but it was a very small change that was accepted by @khronokernel and was removed, later, because it did not work also in Safe Mode.
Perhaps it could work now, after a way was implemented, in the OCLP App, not to demand Admin passwords where it is not needed; but one can dispense with the above addition in the Code and accept that writing the EFI partition will leave some "junk" files preceded by "._" inside it, which do no harm.]

 

[iDonev]

Hey everyone, apologies if this question has been raised previously, but I could not find it.

Since Tahoe will be the last macOS to officially support Intel, what does that mean for the future of Intel Macs? Will we see another update after Tahoe through the OpenCore Legacy Patcher?

 

[deeveedee]

@rehkram I think your view is very important and I fully understand why your position is consistent with that of many others in this thread. I think it's important to consider that there are different use cases and objectives represented here. While some contributors are understandably interested in the safest path to upgrading their Macs, other contributors are motivated by the sense of adventure and the desire to explore, experiment and learn. For the latter, it's more about the journey than the destination. And for those who enjoy the experimentation without concern for wasted time (because for them, it's not wasted time), there are many safe ways to play in a sandbox with little to no risk.

I have many things in my life that are governed by efficiency and risk aversion, but my Tahoe experimentation isn't one of them. I'm glad that there is room in this thread for multiple views, opinions and approaches.

EDIT: BTW - I have some computing platforms that are for work and some that are for play, so I fully appreciate both sides of this. I'm not playing with OCLP and Tahoe Beta on my work platforms that require high availability, reliability and security.

 

[ronton3]

@rehkram I think your view is very important and I fully understand why your position is consistent with that of many others in this thread. I think it's important to consider that there are different use cases and objectives represented here. While some contributors are understandably interested in the safest path to upgrading their Macs, other contributors are motivated by the sense of adventure and the desire to explore, experiment and learn. For the latter, it's more about the journey than the destination. And for those who enjoy the experimentation without concern for wasted time (because for them, it's not wasted time), there are many safe ways to play in a sandbox with little to no risk.

I have many things in my life that are governed by efficiency and risk aversion, but my Tahoe experimentation isn't one of them. I'm glad that there is room in this thread for multiple views, opinions and approaches.

On Point.

 

[Payne Mononymous Bachman]

Hey everyone, apologies if this question has been raised previously, but I could not find it.

Since Tahoe will be the last macOS to officially support Intel, what does that mean for the future of Intel Macs? Will we see another update after Tahoe through the OpenCore Legacy Patcher?

What this will mean is after Tahoe there will be no new operating systems for Intel Macs however, Tahoe should continue to receive security updates for about 2-3 years. Once those 2-3 years are up you can continue to use intel Macs but be aware that they will be a security risk. You will probably also see more and more applications start to not support Intel since it is an X86 platform and the new Apple Silicon processors are based on ARM. Hopefully those who have MACS with 8th gen Intel processors or newer will get a little bit more support on the Security side if they use Windows 11 via boot camp or Windows 10 LTSC or Linux. For me I will probably take my old Intel Macs and make them Linux test machines for all of the different versions of Linux. My hope though is that someone from the OCLP team will be able to reverse engineer Rosetta and somehow find a way to get newer MAC OS versions to boot on Intel Macs. But after talking to developers the chance of that being successful is unfortunately less than 10%.

Side note this may also be the last version you see supporting Hackintoshes but I could be wrong on that.

 

[ADGrant]

Hey everyone, apologies if this question has been raised previously, but I could not find it.

Since Tahoe will be the last macOS to officially support Intel, what does that mean for the future of Intel Macs? Will we see another update after Tahoe through the OpenCore Legacy Patcher?

No we will not. Tahoe is the last version of MacOS that will be supported on Intel Macs through the legacy patcher. It's also important to note that T2 Intel Macs are not currently supported by OCLP (a moot point for the final four T2 Macs officially supported by Tahoe).

 

[TOM1211]

@rehkram I think your view is very important and I fully understand why your position is consistent with that of many others in this thread. I think it's important to consider that there are different use cases and objectives represented here. While some contributors are understandably interested in the safest path to upgrading their Macs, other contributors are motivated by the sense of adventure and the desire to explore, experiment and learn. For the latter, it's more about the journey than the destination. And for those who enjoy the experimentation without concern for wasted time (because for them, it's not wasted time), there are many safe ways to play in a sandbox with little to no risk.

I have many things in my life that are governed by efficiency and risk aversion, but my Tahoe experimentation isn't one of them. I'm glad that there is room in this thread for multiple views, opinions and approaches.

EDIT: BTW - I have some computing platforms that are for work and some that are for play, so I fully appreciate both sides of this. I'm not playing with OCLP and Tahoe Beta on my work platforms that require high availability, reliability and security.

Commenting on if you should or should not install betas and OCLP betas = no probably not however it does remind me of installing one of the OCLP betas and getting green screen on videos reverting to a earlier version videos fine mentioned on discord and Devs hadn’t experienced it and came up with a fix in a few days/hours so my point being not a lot but there are many different environments out there and experiences may differ even from test environments so maybe it can be helpful somewhat maybe.

 

[houser]

> after talking to developers the chance of that being successful is unfortunately less than 10%.

I like those odds as they are better than I expected. I have heard zero chance but we will see down the road I guess

 

[amaze1499]

/deleted

 

[hvds]

MBP5,2 running 26b3: now trying root patching.

During patching, some files missing as expected with the existing (non-Tahoe) Universal-Binaries.dmg. Added missing paths while patcher active as follows, naively:
cd /var/folders/3h/kf6jzpcn01g9lyb37m6ystn80000gn/T/tmp0foem7_w/payloads/Universal-Binaries
# for missing wps (etc...)
cp -Rp 12.7.2-24 12.7.2-25
# for missing AppleHDA.kext (taken from 26b1)
mkdir -p 26.0\ Beta\ 1/System/Library/Extension
cd 26.0\ Beta\ 1/System/Library/Extensions
cp -Rp /Users/hvds/Desktop/exp/AppleHDA.kext .
then patcher proceeded to the end.
Patched system did boot. Needed a bootloader enabling the pre-Tahoe usb map as foreseen by the developers (previously mentioned bootloader without commit from 14 July needed for nonpatched system and installer).

Booted upto password entering. On the way: keyboard backlight went on, and internal keyboard/trackpad worked! Didn't get beyond password entering yet - system doesn't proceed but mouse pointer still moving - and quickly! But can't test graphics, internal audio, wifi so far.

MBP5,2 26.0b3: got beyond this login stall.

Disabled the WIFI patching in the source of OCLP 3.0.0n macos-next branch and left the other patches intact, esp. nvidia tesla graphics.

Now writing this from Firefox on that machine, didn't get Safari to work yet. Graphics is reasonably fast, internal keyboard and trackpad work, as does keyboard backlight and facetime camera. Internal audio doesn't (AppleHDA). Wifi doesn't, using Ethernet cable instead.

It seems the existing non-metal patches still work well in Tahoe. I can also use my MBP11,1 (Haswell) in Tahoe but without graphics acceleration so far.

Thanks developers!


Edit: also modern audio patching disabled in the source. Existing Universal-Binaries.dmg then contains all things needed, no massaging needed during root patching.
As a few iterations were needed with unbootable systems, I had a lot of benefit of the unpatching method deeveedee recalled in post #154 (in recovery mount -uw /Volumes/xx; bless --mount /Volumes/xx --bootefi --last-sealed-snapshot). Thanks!

 

[ADGrant]

I like those odds as they are better than I expected. I have heard zero chance but we will see down the road I guess

0% is less than 10%.

 

[mizhidr]

I found that in the macos26 beta3 version, some navi core driver-free graphics cards have a long black screen, even if I disable the Framebuffer

 

[ADGrant]

I found that in the macos26 beta3 version, some navi core driver-free graphics cards have a long black screen, even if I disable the Framebuffer

What does "navi core driver-free" mean?

 

[deeveedee]

@hvds Congrats on your progress with Tahoe Beta experimentation! I'm not so lucky with non-metal Nvidia Tesla patches for MBP6,2, as the OCLP Sequoia graphics framework patches don't work in Tahoe Beta 3, so I'll patiently wait for more progress on OCLP 3.0.0.

Still amazing that this 2010 MBP6,2 continues to receive Apple updates for Tahoe via the normal OTA process:

EDIT: The Command Line Tools update finished in 5 minutes - not 14 hours 🤣

 

[hvds]

@hvds Congrats on your progress with Tahoe Beta experimentation! I'm not so lucky with non-metal Nvidia Tesla patches for MBP6,2, as the OCLP Sequoia graphics framework patches don't work in Tahoe Beta 3, so I'll patiently wait for more progress on OCLP 3.0.0.

Still amazing that this 2010 MBP6,2 continues to receive Apple updates for Tahoe via the normal OTA process:

View attachment 2530284

EDIT: The Command Line Tools update finished in 5 minutes - not 14 hours 🤣

Yes - amazing and very useful to still receive those updates so easily. And I also had the many-hours display.

For the MBP5,2, don't know why it works in my case and not for your 6,2. For completeness I've added to my post above the log of the patching process from the OCLP patching window (and also the changes made to the source, 2nd txt file, which cover both the 5,2 and the MBP11,1).

 

[rehkram]

@rehkram I think your view is very important and I fully understand why your position is consistent with that of many others in this thread.

I should have stated that my post was intended as a public service announcement for folks new to OCLP. Simply put, newbies should not feel pressured into doing this now.

Hence my confession to waiting until both Tahoe 26 and OCLP 3.0.0 are out of beta. Which is what I do and so do others.

I'm not risk averse, I just have other more enjoyable things I could be doing, like beating myself with a rubber hose 🤣

This phase we're in, "double beta", occurs with every new macOS major release. Nature hates a vacuum.

 

[mib01]

What this will mean is after Tahoe there will be no new operating systems for Intel Macs however, Tahoe should continue to receive security updates for about 2-3 years. Once those 2-3 years are up you can continue to use intel Macs but be aware that they will be a security risk. You will probably also see more and more applications start to not support Intel since it is an X86 platform and the new Apple Silicon processors are based on ARM. Hopefully those who have MACS with 8th gen Intel processors or newer will get a little bit more support on the Security side if they use Windows 11 via boot camp or Windows 10 LTSC or Linux. For me I will probably take my old Intel Macs and make them Linux test machines for all of the different versions of Linux. My hope though is that someone from the OCLP team will be able to reverse engineer Rosetta and somehow find a way to get newer MAC OS versions to boot on Intel Macs. But after talking to developers the chance of that being successful is unfortunately less than 10%.

Side note this may also be the last version you see supporting Hackintoshes but I could be wrong on that.

The shortest path is to buy a Mac Mini M4 base due to its cost-benefit. Another option is the one you suggested, installing a Linux distro on the Mac, better than resorting to Windows. Intel users still have half of 2028 to decide which path to take. For now, all that's left is to celebrate another macOS update.

 

[paul_bh]

There is any chanse to install macos tahoe on imac 19,1? OCPL 3.0.0n has no this mac in database.

 

[Payne Mononymous Bachman]

There is any chanse to install macos tahoe on imac 19,1? OCPL 3.0.0n has no this mac in database.

Probably still a work in progress. OCLP may just not have gotten around to testing or developing drivers for the iMac 19,1. Since it is still early in development process, I would give it a little bit more time to let the developers continue to design and code the next version of OCLP that is a true public release.

If anyone knows anymore information on this iMac feel free to reply to this comment-post.

 

[macpro_mid2014]

There is any chanse to install macos tahoe on imac 19,1? OCPL 3.0.0n has no this mac in database.

They just added it to the database:

GitHubAPP — 1:12 PM​

Jazzzny
[OpenCore-Legacy-Patcher:macos-next] 1 new commit
1311507 Add iMac19,x SMBIOS - Jazzzny

 

[redpandadev]

Hey everyone, apologies if this question has been raised previously, but I could not find it.

Since Tahoe will be the last macOS to officially support Intel, what does that mean for the future of Intel Macs? Will we see another update after Tahoe through the OpenCore Legacy Patcher?

No. Future releases will not contain any Intel code at all and will not be able to directly boot at all on Intel Macs. It is (and will remain so) possible to boot arm64 macOS on an Intel Mac using emulation on an X86 host OS.

The next conversation we'll be having is running a future macOS (probably 28) on unsupported Apple Silicon hardware, once the M1 series of chips are dropped. macOS 27 will certainly support all generations of Apple Silicon, but macOS 28 and beyond could drop support for M1 or even M2. I could see them dropping M1 and M2 simultaneously because they are extremely similar (not much more than clock speed for differences). M3 is the first major architecture change for the Apple Silicon chips (moving to armv9, significant GPU changes, significant NPU changes). It would be very likely that M1 can support anything M2 can support, but neither supporting things the M3 can support. This is not unlike the Intel transition, where the initial Intel Core and Core 2 chips were dropped aggressively in favor of the vastly improved core-i series.

 

[Portiere]

Tahoe is installable on my mac mini 2012 (external SSD), it boots on configuration window but once i arrive on privacy window it stays few minutes black then it restarts.
Inpossible to install it on mini 2018.