macOS Tahoe 26 on Unsupported Macs Discussion

[TOM1211]

installing beta 4 Tahoe beta over 3 on my mid 2014 no issues updating with a full installer from a sequoia install . Mouse and keyboard still working .

 

[sinbad21]

Thanks. But no go. Always bumping into:

import py_sip_xnu
ModuleNotFoundError: No module named 'py_sip_xnu'

Did run requirement.txt numerous times. sip:xnu is not available http error 404

python3.11
Python 3.11.13 (main, Jun 3 2025, 18:38:25) [Clang 16.0.0 (clang-1600.0.26.6)] on darwin

Maybe you guys still have it installed from previous sessions.

Requirements must be installed in the version of Python that you use. To be sure, try

pip3.11 install -r requirements.txt

 

[amaze1499]

Is that on a USB1.1 machine?

Mbp 9,2

 

[macpro_mid2014]

Mbp 9,2

I had some issues with multiple versions of Python installed on my MBP11,2 in the past.
Check for that on /Library/Frameworks/Python.framework/Versions
What I did: removed all versions there and in /usr/bin and reinstalled version 11 from python.org

 

[hvds]

Mbp 9,2

...so I was on a wrong track

 

[amaze1499]

...so I was on a wrong track

no worries, I’m pretty sure the 3.0.0 is not too far out

 

[mizhidr]

What does "navi core driver-free" mean?

I mean navi10, navi21, navi23 graphics cards

 

[deeveedee]

I am still using Python 3.11.9 (the last version of Python 3.11 available from python.org with an installer). I have not yet applied the 3.11.13 security update (which does not have a downloadable installer from python.org). Here are the steps of my OCLP build that work for me (summarized from here)

• Remove previous versions of Python
• Install Python 3.11.9 from python.org. Be sure to follow post-install instructions for updating path, etc.
• Confirm Python installation with 'which python3' and 'python3 --version'
  • /Library/Frameworks/Python.framework/Versions/3.11/bin/python3
  • Python 3.11.9
• git clone https://github.com/dortania/OpenCore-Legacy-Patcher --branch <developer branch>
  • Using branch macos-next at the time of this post
• cd OpenCore-Legacy-Patcher
• in file OpenCore-Legacy-Patcher/OpenCore-Patcher-GUI.spec, change target_arch from universal2 -> x86_64
• Since we're building OCLP without Dortania's code signature, do the following:
  • cd ci_tooling/privileged_helper_tool
  • make debug
  • cd ../..
• pip3 install -r requirements.txt
• pip3 install pyinstaller
• python3 ./Build-Project.command

After building, the build products are in the dist folder

 

[amaze1499]

I am still using Python 3.11.9 (the last version of Python 3.11 available from python.org with an installer). I have not yet applied the 3.11.13 security update (which does not have a downloadable installer from python.org). Here are the steps of my OCLP build that work for me (summarized from here)

• Remove previous versions of Python
• Install Python 3.11.9 from python.org. Be sure to follow post-install instructions for updating path, etc.
• Confirm Python installation with 'which python3' and 'python3 --version'
  • /Library/Frameworks/Python.framework/Versions/3.11/bin/python3
  • Python 3.11.9
• git clone https://github.com/dortania/OpenCore-Legacy-Patcher --branch <developer branch>
  • Using branch macos-next at the time of this post
• cd OpenCore-Legacy-Patcher
• in file OpenCore-Legacy-Patcher/OpenCore-Patcher-GUI.spec, change target_arch from universal2 -> x86_64
• Since we're building OCLP without Dortania's code signature, do the following:
  • cd ci-tooling/privileged_helper_tool
  • make debug
  • cd ../..
• pip3 install -r requirements.txt
• pip3 install pyinstaller
• python3 ./Build-Project.command

After building, the build products are in the dist folder


View attachment 2531852

Great follow up, thanks!

However:

import py_sip_xnu
ModuleNotFoundError: No module named 'py_sip_xnu'

 

[deeveedee]

Great follow up, thanks!

However:

import py_sip_xnu
ModuleNotFoundError: No module named 'py_sip_xnu'

The OCLP build process is going to require each of us to be self sufficient and able to resolve issues with our own build environments. The best way to do this is to perform searches using your favorite search engine or AI chatbot.

I just entered your error in ChatGPT and see a solution. What does ChatGPT tell you when you perform your own query? Does the recommended fix work for you?

EDIT: When following my OCLP build process posted previously, start with a fresh download of OCLP source (not with source that you have previously downloaded and attempted to build).

EDIT2: I just repeated my previously posted build steps with a fresh download of OCLP source. Build completed without any issues. I corrected one typo in my posted build steps (changed 'ci-tooling' to 'ci_tooling').

 

[amaze1499]

The OCLP build process is going to require each of us to be self sufficient and able to resolve issues with our own build environments. The best way to do this is to perform searches using your favorite search engine or AI chatbot.

I just entered your error in ChatGPT and see a solution. What does ChatGPT tell you when you perform your own query? Does the recommended fix work for you?

EDIT: When following my OCLP build process posted previously, start with a fresh download of OCLP source (not with source that you have previously downloaded and attempted to build).

EDIT2: I just repeated my previously posted build steps with a fresh download of OCLP source. Build completed without any issues. I corrected one typo in my posted build steps (changed 'ci-tooling' to 'ci_tooling').

Thanks, your reply is much appreciated. However the module is not even available on GitHub.It gives a 404.
No worries, I'll wait for the 3.0.0 release.

Cheers!

 

[deeveedee]

@amaze1499 If anyone else experiences this same problem, that might help. Patiently waiting for 3.0.0 release is going to be best for most people.

 

[hvds]

Great follow up, thanks!

However:

import py_sip_xnu
ModuleNotFoundError: No module named 'py_sip_xnu'

Just as a hint, in may case the package py_sip_xnu.py is at: /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages

 

[sinbad21]

Thanks, your reply is much appreciated. However the module is not even available on GitHub.It gives a 404.
No worries, I'll wait for the 3.0.0 release.

Cheers!

I disagree, it is available on Github.

GitHub - khronokernel/py_sip_xnu

Contribute to khronokernel/py_sip_xnu development by creating an account on GitHub.

github.com

 

[internetzel]

Great follow up, thanks!

However:

import py_sip_xnu
ModuleNotFoundError: No module named 'py_sip_xnu'

I have never built OCLP yet, nor do I know much about python, just programming in general - but I followed the instructions from the py_sip_xnu GitHub site: https://github.com/khronokernel/py_sip_xnu

After installing the module py_sip_xnu using the command

pip3 install py_sip_xnu

I was able to use the module by issuing the following python commands in the python interpreter (invoked by the command "python3"):

import py_sip_xnu
sip_config = py_sip_xnu.SipXnu().get_sip_status()
sip_config.__dict__
sip_config.breakdown.__dict__

The last two lines return the following output for me:

{'value': 2051, 'breakdown': <py_sip_xnu.SipXnu._XnuSipStatus object at 0x108f4c550>, 'can_edit_root': True, 'can_write_nvram': False, 'can_load_arbitrary_kexts': True}

{'csr_allow_untrusted_kexts': True, 'csr_allow_unrestricted_fs': True, 'csr_allow_task_for_pid': False, 'csr_allow_kernel_debugger': False, 'csr_allow_apple_internal': False, 'csr_allow_unrestricted_dtrace': False, 'csr_allow_unrestricted_nvram': False, 'csr_allow_device_configuration': False, 'csr_allow_any_recovery_os': False, 'csr_allow_unapproved_kexts': False, 'csr_allow_executable_policy_override': False, 'csr_allow_unauthenticated_root': True}

That means that the py_sip_xnu module itself is actually working as intended!

 

[macpro_mid2014]

Thanks, your reply is much appreciated. However the module is not even available on GitHub.It gives a 404.
No worries, I'll wait for the 3.0.0 release.

Cheers!

Maybe it is the version of pip you are using. Mine:
% pip --version
pip 25.1.1 from /Users/user_me/Library/Python/3.11/lib/python/site-packages/pip (python 3.11)

If you are not at this version, you can do
% pip install --upgrade pip
to upgrade to the latest.

 

[mikezang]

Did anyone install MacOS Tahoe 26 to mac mini (3,1) Late 2009 without any problems?

 

[amaze1499]

Maybe it is the version of pip you are using. Mine:
% pip --version
pip 25.1.1 from /Users/user_me/Library/Python/3.11/lib/python/site-packages/pip (python 3.11)

If you are not at this version, you can do
% pip install --upgrade pip
to upgrade to the latest.

Thanks for your reply:

Requirement already satisfied: pip in /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages (23.2.1)

maybe the python versions on this system don't play along.

 

[amaze1499]

Great support everybody, thanks to that I figured it out eventually. Much appreciated!

 

[ronton3]

I have made many OCLP/USB installers in the past and all have worked. Using 3.0.0n and the download, with OCLP installed also, shown in file doesn't, I get the crossed circle Apple support message. Has anyone got it to work. It is just for experimenting.

 

[amaze1499]

I have made many OCLP/USB installers in the past and all have worked. Using 3.0.0n and the download, with OCLP installed also, shown in file doesn't, I get the crossed circle Apple support message. Has anyone got it to work. It is just for experimenting.

Out of curiosity: when using 3.0.0n does it say so in the UI?

 

[hvds]

Out of curiosity: when using 3.0.0n does it say so in the UI?

Yes. I've built it from source.
When following https://github.com/dortania/OpenCore-Legacy-Patcher/blob/macos-next/SOURCE.md to get to the prebuilt nightly, in the link given there it seems the main needs to be replaced by macos-next to get to 3.0.0n, even when looking at the SOURCE.md from the macos-next branch.

 

[ADGrant]

I mean navi10, navi21, navi23 graphics cards

So you are saying that Macs with some Navi baed cards are showing a black screen? Which Macs are those? Navi GPUs were introduced at the tail end of the Intel Macs, the ones I am aware of still seem to be supported by Apple for the macos26 release and also have T2 coprocessors (unsupported currently by OCLP).

 

[ronton3]

I have made many OCLP/USB installers in the past and all have worked. Using 3.0.0n and the download, with OCLP installed also, shown in file doesn't, I get the crossed circle Apple support message. Has anyone got it to work. It is just for experimenting.

It does work, I think I may have erased and not put OS extended back. At any rate OCLP/Tahoe26 is now on, and the mouse and keyboard, both types work, system settings work. I installed over a test volume of Sonoma. The dtop is dark gray, and the dock is not present, the desk top just changed to white, I am waiting to see if OCLP asks to patch. This is from my iPad mini 6. This is worth the effort on a disposable volume. I can’t believe it. Nothing special programming wise, just regular Wonderful OCLP.

Thanks again Devs.

The dock just appeared. Took about 15 minutes.
.

 

[ronton3]

This is from FireFox on 26Tahoe, I am going to let it set for awhile before I open OCLP to see if a patch is available, right now it is working just about like an unpatched Seq or Sonoma. After I logged back in from the Tahoe screensaver the Tahoe desktop was their briefly and then disappeared.