macOS Tahoe 26 on Unsupported Macs Discussion

[houser]

For those who can run macOS Tahoe on Intel and who are disappointed with their Intel-Tahoe experience (or just don't like Apple any more for whatever reason), I'd suggest that you don't waste any more time here. Your negativity isn't helping anyone.

Since you are not a mod here, please refrain from moderation and directorial suggestions. Pretty sure there is room for both sycophants and people with other opinions. It is also not negativity to suggest freedom and psychological health for devs where others just nag about the next update in other words. Peace on earth.

 

[Gandolf243]

Since you are not a mod here, please refrain from moderation and directorial suggestions. Pretty sure there is room for both sycophants and people with other opinions. It is also not negativity to suggest freedom and psychological health for devs where others just nag about the next update in other words. Peace on earth.

Yes, that is a good point, but this was a forum for help with unsupported macs running Tahoe, so people who can run Tahoe in a Apple supported way shouldn't be on here unless they are helping out.

 

[houser]

Yes, that is a good point, but this was a forum for help with unsupported macs running Tahoe, so people who can run Tahoe in a Apple supported way shouldn't be on here unless they are helping out.

Ok. Since you are new here and I am not.
I have been here since the beginnings helping out and still run 6 legacy OCLP Macs and also one native Tahoe MBA that I simply used as an example for the strain Tahoe puts on old-ish Macs. Thanks.
edit: I checked and just realised I have been on here for 20 years and you since Tuesday 😉

 

[Gandolf243]

Ok. Here's the deal since you are new here and I am not.
I have been here since the beginnings helping out and still run 6 legacy OCLP Macs and also one native Tahoe MBA that I simply used as an example for the strain Tahoe puts on old-ish Macs. Thanks.
edit: I checked and just realised I have been on here for 20 years and you since Tuesday 😉

My apologies. I had no ground to say that on.
Even though I do have more OCLP experience then since last Tuesday, all I have is a macbookpro7,1 running Sonoma, Ubuntu and 20 GB of a broken Tahoe install.

 

[deeveedee]

@Gandolf243 As much as the thread police will allow me to say this as a non-moderator, welcome to the forum.

 

[houser]

My apologies. I had no ground to say that on.
Even though I do have more OCLP experience then since last Tuesday, all I have is a macbookpro7,1 running Sonoma, Ubuntu and 20 GB of a broken Tahoe install.

No worries. Apology unnecessary, yet appreciated. Nothing but broken Tahoe installs in this thread so far as you may have gleaned here that it is not supported by OCLP as yet 😉
FWIW Sequoia works very well here on all our legacy Macs and is the last (so far) OS supported by OCLP and we are running it on a all our legacy Macs these days and see no reason why it would not work well on your MBP 6.1 unless you are doing something specific that is unsupported. Good luck regardless.

 

[basslik]

ALL IS GREAT HERE INDEED.

Some are born to move the world
To live their fantasies
But most of us just dream about
The things we'd like to be

Sadder still to watch it die
Than never to have known it
For you, the blind who once could see
The bell tolls for thee
The bell tolls for

 

[Albert Müller]

Hey, any testing on macbookpro7,1? I have one, and I want to know what to expect when I download Tahoe. Also, can someone update me on the past 72 pages? I decided to stop reading at page 3 and move on with my life.
(Also, if anyone has the ability add me as a contributor to OCLP, that would be great. (Same username as here as on GitHub.))

 

[hackintosh_user]

I still remain optimistic in an OCLP solution for Tahoe

Sure, but how long can we stay optimistic with no updates from the developers? 2.4.1 is now almost a year old at this point. And we don't get development updates for Tahoe. Aside from what we have been told we simply know nothing. 0%. From what we have the developers could be 5% done or 90% done. Anything else we know Nothing. The information we were optimistic about is now over a year old. I without a doubt in my mind still hope for the best for the developers but an update is really needed and would help out, but without a dev seeing this we can just hope.

 

[deeveedee]

I without a doubt in my mind still hope for the best for the developers but an update is really needed and would help out, but without a dev seeing this we can just hope.

With statements like that, you risk the wrath of the self-appointed moderators for nagging. 🤣

I can remain optimistic without status updates from the original OCLP Devs. As long as I see progress made in the "unofficial" forks, I can't help but think that the remaining OCLP Devs are making at least as much progress.

 

[hackintosh_user]

New Sequoia 15.8 beta (24H16) works perfectly on the Mid 2012 Retina MacbookPro 13inch. Honestly never expected to reach 15.8 before OCLP Supporting Tahoe I must admit.

 

[hackintosh_user]

I can remain optimistic without status updates from the original OCLP Devs. As long as I see progress made in the "unofficial" forks, I can't help but think that the remaining OCLP Devs are making at least as much progress.

a good example I take is the T2 fork. the OP behind it is making Very good progress on it honestly. but at least he updates us about it.. which I admit wish the original OCLP devs wish did but hey we can't demand. its volunteers doing the work

 

[funnymacuser]

I'll add my opinion, I still stand by what I wrote earlier that developers can release a beta version of the patcher with patch support for working versions of Tahoe, really, if you look at it like that, we are optimists now and we can be them for the next 10 years and wait for Tahoe, I also had a thought about this, all that has already passed a year, the developers have split up, and I think that maybe the team thought that Sequoia was the last system for Intel and maybe they were going to abandon development, but the release of Tahoe was unplanned, which brought an unexpected nightmare for developers in general, because maybe after Sequoia they had no motivation for the next systems, thinking that sequoia was the last, because I can't explain why Tahoe is not there and Sequoia is there, because Sequoia also removed support for old hardware well, but at the same time in 3-6 months we saw a suitable system for use, so they say be patient, don't write, don't ask, but we are all people and we are them and in fact not hearing anything is very motivating for people than to say that - guys Tahoe there will be no more, we can't work on this anymore and that's it, literally, we wouldn't have hoped for Tahoe anymore, we would have already resigned ourselves to the fact that Sequoia is the ceiling, but we still continue to wait and believe in the developers, and if you look at it from the other side, some developers have left, for example, educovas made graphics patches, wrote how things are with metal (I'll attach a screenshot), I'm not sure but there is one more developer, if I'm wrong, sorry, but we haven't heard anything from him at all about graphics, etc., the best thing that the developers who are there now can do is report how things are, what's happening, etc. and give clear answers and not answers that have already been done as it was before on github, and I'll add that in this post I don't want to humiliate anyone, say that the developers are not working well, this is just an opinion about Tahoe and this situation, for me the sign of the closure of donations has become a beacon that there is little hope for Tahoe and the developers long silence makes this even more certain

Spoiler: educovas about metal

 

[hackintosh_user]

I'll add my opinion, I still stand by what I wrote earlier that developers can release a beta version of the patcher with patch support for working versions of Tahoe, really, if you look at it like that, we are optimists now and we can be them for the next 10 years and wait for Tahoe, I also had a thought about this, all that has already passed a year, the developers have split up, and I think that maybe the team thought that Sequoia was the last system for Intel and maybe they were going to abandon development, but the release of Tahoe was unplanned, which brought an unexpected nightmare for developers in general, because maybe after Sequoia they had no motivation for the next systems, thinking that sequoia was the last, because I can't explain why Tahoe is not there and Sequoia is there, because Sequoia also removed support for old hardware well, but at the same time in 3-6 months we saw a suitable system for use, so they say be patient, don't write, don't ask, but we are all people and we are them and in fact not hearing anything is very motivating for people than to say that - guys Tahoe there will be no more, we can't work on this anymore and that's it, literally, we wouldn't have hoped for Tahoe anymore, we would have already resigned ourselves to the fact that Sequoia is the ceiling, but we still continue to wait and believe in the developers, and if you look at it from the other side, some developers have left, for example, educovas made graphics patches, wrote how things are with metal (I'll attach a screenshot), I'm not sure but there is one more developer, if I'm wrong, sorry, but we haven't heard anything from him at all about graphics, etc., the best thing that the developers who are there now can do is report how things are, what's happening, etc. and give clear answers and not answers that have already been done as it was before on github, and I'll add that in this post I don't want to humiliate anyone, say that the developers are not working well, this is just an opinion about Tahoe and this situation, for me the sign of the closure of donations has become a beacon that there is little hope for Tahoe and the developers long silence makes this even more certain

Spoiler: educovas about metal

View attachment 2653715

Saying from experience, naturally, losing 4 developers in under a year is not easy. Even when the company I worked at lost 4 developers in the IT department it was a mess, dare I say nightmare. Image for a volunteer project that: Lost 4 developers, are not paid, and have to support 80+ unsupported macs. It's not easy. But I still say this applies. I don't think it justifies silence but I remain to say this, it's unpaid developers they literally don't owe us anything. And we aren't entitled to their work.

 

[deeveedee]

Time will tell. I don't blame anyone for losing faith in the Devs. I would still much rather be optimistic and wrong than pessimistic and right. It's a choice that is free to be made.

 

[basslik]

I was able to upgrade to Tahoe's login screen. ( JUST FOR TRYING ) TO SEE IF MY 5,1 WOULD RUN IT.

I get stuck on the start page, and the mouse is non-response.

Is there a work around to get the mouse to move?

 

[deeveedee]

@basslik Without knowing anything about your Open Core EFI, I'm guessing...

• Open Core 1.0.7
• Update Acidanthera kexts including Lilu.kext (1.7.2) and WhateverGreen.kext (1.7.0)
• Confirm that your USB map is updated for Tahoe

If you've already done all that, there is another thread dedicated to the MacPro5,1 that might help.

 

[basslik]

@basslik Without knowing anything about your Open Core EFI, I'm guessing...

• Open Core 1.0.7
• Update Acidanthera kexts including Lilu.kext (1.7.2) and WhateverGreen.kext (1.7.0)
• Confirm that your USB map is updated for Tahoe

If you've already done all that, there is another thread dedicated to the MacPro5,1 that might help.

Thanks for your reply.

OCLP 2.4.1

Always helpful deeveedee.

I'm not tech savvy at ALL. lol

So that's all alien to me. Anyhow if you have the tread handy. I'll see if I can wing it.

 

[Bigwaff]

I get stuck on the start page, and the mouse is non-response.

Is there a work around to get the mouse to move?

As with OCLP supported macOS versions, I imagine you need USB1 hub to get keyboard and mouse to work, at least until the legacy USB driver gets patched in.

 

[kabaldan]

One reason to want to run Tahoe on older Macs is that the 26.4 release added support for Network MIDI 2.0 (with the redesigned MIDI Network Setup panel).

 

[deeveedee]

@kabaldan If you need Network MIDI 2.0 and you can't upgrade to Tahoe 26.4, you can look at this: https://www.bome.com/products/bomenet

It's not the network endpoint equivalent to Apple's Tahoe implementation (still uses MIDI 1.0 data), but depending on your requirements, it may work.

 

[Gandolf243]

OCLP 2.4.1

Always helpful deeveedee.

I'm not tech savvy at ALL. lol

So that's all alien to me. Anyhow if you have the tread handy. I'll see if I can wing it.

You need to somehow get OCLP 3.0.0 (nightly) on your mac. Your mac is the last MacPro to have this issue. 2.5.1 doesn't have the USB maps for Tahoe. What you need is the following:
Note: this is really techy, and will most likely download stuff that you will never use again.


You need to get Python 3.11 or newer installed on your mac (or, if you just have Tahoe on it, you need another mac that has I think it's macOS (10.13.6) High Sierra or later.) download python here.

Go to Dortania's macOS-next branch

Click on code and click download zip. In the downloads folder open the zip (if it doesn't automatically open) and then open the terminal and run pip3 install --upgrade pip && pip3 install -r "~/Downloads/$(ls -d ~/Downloads | grep '*macos-next*')/requrments.txt" Note: you have to be connected to the internet.
What do those commands do? The first one upgrades python's pip, which is basically its installer. The second one installs the components that OCLP requires to run without being compiled (which is the state of being a .app or executable binary)
Now if these have run properly open the opencore folder and click double click on OpenCore-Patcher-GUI.spec, not OpenCore-Patcher-GUI.command. It should open in TextEdit
Now press ⌘ + F and type "universal2" it should only show one option. Replace it with "x86_64" then press ⌘ + S and close TextEdit.
Now, open the terminal and type cd, then in finder navigate to ci_tooling and drag the privileged_helper_tool folder into the terminal window. Back in the terminal press the right arrow key and hit enter. Then type make debug if prompted to install commandline tools, go though with the install, then run make debug again.
Now, back in the opencore folder open the Build-Project.command file and let it run in the terminal. Make sure that you allow it to run if prompted.
When it is done open the dist folder that it generated and and copy OpenCore-Patcher.pkg onto a USB drive.
Back on the 5,1, plug in a USB2 Hub and connect your keyboard and mouse into it. Now you can navigate the interface.
Plug the USB drive into your mac and open it in Finder. Open the Pkg file that you put on it and install opencore. Now you can open opencore-patcher and install root patches.

Note: I am impressed that you got Tahoe installed with OCLP 2.5.1!


Note: yoy also need the KDK, which you can get here, just scroll through the releases until you find the one that is exactly or close to the version of Tahoe that you have. Put it on the USB drive with the OpenCore-Patcher installer.

 

[hackintosh_user]

Time will tell. I don't blame anyone for losing faith in the Devs. I would still much rather be optimistic and wrong than pessimistic and right. It's a choice that is free to be made.

Just how it is really. But for the devs that do see this. i hope you all succed in your work.

 

[basslik]

You need to somehow get OCLP 3.0.0 (nightly) on your mac. Your mac is the last MacPro to have this issue. 2.5.1 doesn't have the USB maps for Tahoe. What you need is the following:
Note: this is really techy, and will most likely download stuff that you will never use again.


You need to get Python 3.11 or newer installed on your mac (or, if you just have Tahoe on it, you need another mac that has I think it's macOS (10.13.6) High Sierra or later.) download python here.

Go to Dortania's macOS-next branch

Click on code and click download zip. In the downloads folder open the zip (if it doesn't automatically open) and then open the terminal and run pip3 install --upgrade pip && pip3 install -r "~/Downloads/$(ls -d ~/Downloads | grep '*macos-next*')/requrments.txt" Note: you have to be connected to the internet.
What do those commands do? The first one upgrades python's pip, which is basically its installer. The second one installs the components that OCLP requires to run without being compiled (which is the state of being a .app or executable binary)
Now if these have run properly open the opencore folder and click double click on OpenCore-Patcher-GUI.spec, not OpenCore-Patcher-GUI.command. It should open in TextEdit
Now press ⌘ + F and type "universal2" it should only show one option. Replace it with "x86_64" then press ⌘ + S and close TextEdit.
Now, open the terminal and type cd, then in finder navigate to ci_tooling and drag the privileged_helper_tool folder into the terminal window. Back in the terminal press the right arrow key and hit enter. Then type make debug if prompted to install commandline tools, go though with the install, then run make debug again.
Now, back in the opencore folder open the Build-Project.command file and let it run in the terminal. Make sure that you allow it to run if prompted.
When it is done open the dist folder that it generated and and copy OpenCore-Patcher.pkg onto a USB drive.
Back on the 5,1, plug in a USB2 Hub and connect your keyboard and mouse into it. Now you can navigate the interface.
Plug the USB drive into your mac and open it in Finder. Open the Pkg file that you put on it and install opencore. Now you can open opencore-patcher and install root patches.

Note: I am impressed that you got Tahoe installed with OCLP 2.5.1!


Note: yoy also need the KDK, which you can get here, just scroll through the releases until you find the one that is exactly or close to the version of Tahoe that you have. Put it on the USB drive with the OpenCore-Patcher installer.

Yeah you folks are really awesome at the techy stuff. Way over my pay grade, LOL

Actually got Tahoe to install with 2.4.1.

I was so close, LOL

I'll just hang on the sidelines, if, and when OCLp is ready. THANK YOU

 

[deeveedee]

I'll just hang on the sidelines, if, and when OCLp is ready. THANK YOU

It's easier than you think, but I understand. Tahoe 26.6.2 is now running as well as Sequoia on my hacks. Apple is doing a great job with its Tahoe refinements. Something to look forward to.

EDIT: Here are the OCLP 3.0.0 nightly build steps posted earlier in this thread.