macOS Tahoe 26 on Unsupported Macs Discussion

[Dimvol]

The name Intel Iris Plus Graphics 640 is confusing. But it's not Haswell, it's Kaby Lake.
Kaby Lake is already supported in general, no patches are needed. I don't know how it will be with this PID specifically, you need to try. These systems are well adapted for 8 GB.
In general, you need to try. Wi-Fi won't work. LAN should work, as you can handle USB setup.
The system board 820-00629-A that is installed in it allows you to increase the memory capacity to 32 GB. You just have to want it.
The main problem with this system board is that it may not have NVMe soldered on it, and then there is only a slow HDD. If so, there is no point in doing anything with it without replacing it with an SSD. But maybe this has already been done. How should I know?

 

[PotentPeas]

The main problem with this system board is that it may not have NVMe soldered on it, and then there is only a slow HDD. If so, there is no point in doing anything with it without replacing it with an SSD. But maybe this has already been done. How should I know?

If you pull up the "System Information" app and go to SATA, you should be able to tell what model drive is in there. If it is not immediately obvious, then just Google the model number to find if it is a HDD or SSD.

It looks like this system supports Thunderbolt, so you could attach a NVMe drive that way. It's Thunderbolt 1 though so you would need an adapter. It wouldn't be as fast as it "could" be in a system with a PCIe3 or PCIe4 four-lane slot, but it still may well be a bit faster than a SATA SSD.

 

[Dimvol]

Thanks. I know that, I didn't ask that question. You're right, an external Thunderbolt SSD will must give about 3000 Mb/s, while an internal NVMe SSD will give half that. If it's there.
Internal SATA will give no more than 600 Mb/s.
But we can't know what's in someone else's computer. We can look into the magic ball...

 

[deeveedee]

We don't need to look in someone else's computer. The OP asked if Tahoe would run as well as Sequoia. With performance tweaks mentioned earlier in this thread, the answer is "probably" and the OP should be optimistic that it will. If the OP were asking about the absolute performance of Tahoe (not relative performance), then maybe we'd have to "look in" their computer.

 

[Dimvol]

I have used this computer. If I had it now, I would definitely install the Tahoe Beta in it and show it off to you all here. Unfortunately, it is not a high-performance system. Mail, news, photos and UHD videos. Good picture, good sound. It is not capable of more. The beauty of the Tahoe interface will complement the beauty of this thing well. Also, the owner will have to make an effort to make it a little faster. A little. You won’t get much from the dual-core Intel i5 7360U. It’s not even an i5 7500. Intel has never had good processors for this socket. Also, the processor is soldered to the motherboard and cannot be replaced.
Nevertheless, this is a beautiful thing that should not be thrown away. The Tahoe would be very appropriate there, in my opinion.

 

[LuckyOldMan]

an external Thunderbolt SSD will must give about 3000 Mb/s, while an internal NVMe SSD will give half that.

I don't think so. PCI Express 3.0 x4 Lanes determines the speed.
Too it depends on the M.2-NVMe-SSD that's installed.

A WD Black SN850X in my upgraded iMac 18.3 achieves about 3,000 MB/s, while a WD Black SN770 in my upgraded iMac 18.2 achieves 2,500 MB/s.

The main problem with this system board is that it may not have NVMe soldered on it,

You're right.
That's the reason I looked for a iMac18.2 with at least a Apple SM0256L-SSD as a better chance for Upgrades.

 

[Oxygen-X1]

I don't think so. PCI Express 3.0 x4 Lanes determines the speed.
Too it depends on the M.2-NVMe-SSD that's installed.

A WD Black SN850X in my upgraded iMac 18.3 achieves about 3,000 MB/s, while a WD Black SN770 in my upgraded iMac 18.2 achieves 2,500 MB/s.

View attachment 2537534


You're right.
That's the reason I looked for a iMac18.2 with at least a Apple SM0256L-SSD as a better chance for Upgrades.

Hello Lucky, how's your iMac 14,3 working with Tahoe?
Are USB, Ethernet, and sound working for you?
Everything's working fine on my 14.2 iMac.
It's just a shame that Nvidia Kepler doesn't have full graphics support, which makes it less fun to work with Tahoe.

 

[LuckyOldMan]

how's your iMac 14,3

I didn't install Tahoe there - just Ventura. For Tahoe I use my iMac 18.3. (more powerfull).

 

[Oxygen-X1]

I didn't install Tahoe there - just Ventura. For Tahoe I use my iMac 18.3. (more powerfull).

Yes, I know you have AMD Radeon Pro and is this graphics card fully supported?

 

[LuckyOldMan]

is this graphics card fully supported?

Yes - supported. That's what the system information shows.

 

[garrettmcavoy]

similarly MBP5,2: updated to 26.0b5 from b4, external SSD, with USB installer.
OCLP 3.0.0n used with slight source modifications (see 2nd text file below) to disable patching of wifi and audio. USB1.1, keyboard backlight and non-metal graphis patching left in place.
So internal keyboard/trackpad, backlight, facebook camera work.
Graphics is fast enough to write this (Firefox) but maybe slower than it was with b4. There are occasional window server crashes.
Anyway patched system boots (for this it needs the EFI with legacy USB map, installer and system without USB patches need EFI without legacy map).
Had difficulty to get a valid KDK so made the change to kdk_handler as shown. Maybe I was not waiting for long enough at the beginning of root patching (took more than 1/2hr for kdk finding).

No problems like with MBP11,1/26.0b5 during installation and power-off.

Still enjoying the MBP5,2 from 2009.
And the 2013 MBP11,1 is still my production system (with Sequoia).
Thanks developers!

Great work - did you sign your modified OCLP install yourself? I’m running into issues running root patches after building from source myself. It fails to mount the root volume due to signing issues.

 

[hvds]

MBP11,1: updated to 26.0b5 from b3, external SSD, with USB installer.
OCLP 3.0.0n used with slight source modifications to disable patching of Haswell graphics, wifi, audio so only Facebook camera patched (which works).
Also manually put the two kexts for HD5000 and Framebuffer into /Library/Extensions (auxiliary kernel collection) where they live in Sequoia and earlier for this MBP11,1. This "clearly seems" to speed up graphics. If that impression reflects reality, part of the Haswell graphics patches may still be fine in Tahoe.
Installation was not so smooth this time: didn't reboot to the next step, so force powered-off then manually booted each time, but that proceeded to a bootable system. The public b2 has a slightly different build number as developer b5, will repeat with this one when InstallAssistant becomes available.

But good enough to write tihis in Safari 26.0. System quite usable overall. Thanks developers!

PS: system doesn't power off the normal way, consistent with the observation during installation.

MBP11,1 updated to 26.0 b6 (25A5338b, like public b3) with USB installer, on external SSD.
Modified OCLP 3.0.0n (14 August) used for very limited root patching as in previous post.
Again manual power-off and reboot after each installation step, and normal power-off doesn't work, but resulting system is OK.
System usable and graphics looks OK (transparency reduced).
The log of the KP while powering off is attached.

Edit:

MBP5,2 too updated to 26.0 b6. USB installer, external SSD.
Same modified OCLP 3.0.0n used for limited patching (non-metal graphics, but no wifi, audio).
Almost-smooth installation, failed once, resulting in the undesired extra - Data in volume naming, but no other negative effects.

 

[deeveedee]

Great work - did you sign your modified OCLP install yourself? I’m running into issues running root patches after building from source myself. It fails to mount the root volume due to signing issues.

https://forums.macrumors.com/threads/macos-tahoe-26-on-unsupported-macs-discussion.2458481/post-34029215

 

[Adora]

Direct link to full installer 26.0 (25A5338b) Beta 6:

https://swcdn.apple.com/content/downloads/53/57/093-05406-A_Z86UYLLWT1/mvyry04zoqzut3y603cqyip334134g5ccz/InstallAssistant.pkg

 

[hvds]

Great work - did you sign your modified OCLP install yourself? I’m running into issues running root patches after building from source myself. It fails to mount the root volume due to signing issues.

I didn't sign but like in deeveedee's post above, I used the make debug. This is also in the README.md of ci_tooling/privileged_helper_tool. Note the word of warning there related to make debug. Don't forget to run the OCLP package installer OpenCore-Patcher.pkg so privileged_helper_tool also gets installed.

 

[Muhammad Arham]

MBP11,1 updated to 26.0 b6 (25A5338b, like public b3) with USB installer, on external SSD.
Modified OCLP 3.0.0n (14 August) used for very limited root patching as in previous post.
Again manual power-off and reboot after each installation step, and normal power-off doesn't work, but resulting system is OK.
System usable and graphics looks OK (transparency reduced).
The log of the KP while powering off is attached.

Can you please elaborate, what type of patches are available in nightly version ?

 

[Muhammad Arham]

Can you please elaborate, what type of patches are available in nightly version ?

According to the latest build ?

 

[Oxygen-X1]

https://down.chengdu.simplehac.cn/d/SHOSS/macOS/RES/Kernel_Debug_Kit_26.0_build_25A5338b.dmg

Would installing this KDK change the graphics support for my late 2013 iMac with GeForce nVidia Kepler graphics card?

 

[Muhammad Arham]

I want any moderator from OCLP Discord Server to clear my confusion. We have seen no commits on GitHub from macOS-next branch. Will this effect oclp work? Does it mean, patcher is in progress even though there are no commits ?

 

[crystall1nedev]

As has happened with Sonoma and Sequoia, patches are being developed and tested internally amongst the developers and trusted contributors. This isn't currently being reflected in the GitHub source tree, however I can share a screenshot to at least satiate the "is stuff happening" comments:

Note: I share this screenshot with permission from the developers to do so publicly - but it doesn't mean that I (or anyone else) will be sharing the patches at this time. Also, ignore the Space Gray icon - this Mac mini (Late 2014) is spoofed so I can use Universal Control.

Let this remind you that things are going - and the developers are working quite hard! Just be patient and respectful to them during this time (and refrain from asking questions like that, "wen eta", etc...)

You can also keep up to date via the GitHub issue for Tahoe support.

 

[Muhammad Arham]

As has happened with Sonoma and Sequoia, patches are being developed and tested internally amongst the developers and trusted contributors. This isn't currently being reflected in the GitHub source tree, however I can share a screenshot to at least satiate the "is stuff happening" comments:

View attachment 2538193
Note: I share this screenshot with permission from the developers to do so publicly - but it doesn't mean that I (or anyone else) will be sharing the patches at this time. Also, ignore the Space Gray icon - this Mac mini (Late 2014) is spoofed so I can use Universal Control.

Let this remind you that things are going - and the developers are working quite hard! Just be patient and respectful to them during this time (and refrain from asking questions like that, "wen eta", etc...)

You can also keep up to date via the GitHub issue for Tahoe support.

Thank you ! If you don't mind, are you a developer ?

 

[Pri-est]

Maybe its being interesting for somebody else...
OS macOS Tahoe 26 Beta6
BootLoader compiled by OCLP 3.0.0 NB
MacPro 5,1 (flashed 4.1)
System boots with PCI-Express x8 SSD Samsung PM7125
As i know - its first macOS, that support this SSD OOB (also tryed on RaptorLake Hackintosh - works great!).

 

[amaze1499]

A bit off topic, but isn't it amazing how the M1 will become obsolete pretty soon?

 

[F1Mac]

As has happened with Sonoma and Sequoia, patches are being developed and tested internally amongst the developers and trusted contributors. This isn't currently being reflected in the GitHub source tree, however I can share a screenshot to at least satiate the "is stuff happening" comments:

Let this remind you that things are going - and the developers are working quite hard! Just be patient and respectful to them during this time (and refrain from asking questions like that, "wen eta", etc...)

You can also keep up to date via the GitHub issue for Tahoe support.

Words of wisdom...
Thank you for sharing this!! 🙏 Fun times ahead...

 

[hvds]

https://down.chengdu.simplehac.cn/d/SHOSS/macOS/RES/Kernel_Debug_Kit_26.0_build_25A5338b.dmg

Would installing this KDK change the graphics support for my late 2013 iMac with GeForce nVidia Kepler graphics card?

I‘m not an OCLP developer, but as far is I understand, KDK is needed for the mechanics of patching (kmutil), not for the contents of the patches. So my answer is no.