Mine also has no icon, i think they Apple just forgot to put it this time. But my install didn't have issues
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
I'm sure there are differences that would explain being stuck at login, but I've only tested Beta 3 on two hacks (one with SMBIOS MacMini8,1 and one with SMBIOS MBP6,2), so I don't have much of a sample size. Both of my hacks installed smoothly with one issue: When I logged into my HackBookPro6,2 for the first time after upgrading from Beta 2 -> Beta 3, the login appeared to fail (login returned to the login screen), but after waiting for a minute, the desktop appeared.
After the first login, Beta 3 starts up and logins in without issues.
Note that on my HackBookPro6,2 (which will need OCLP patches for non-metal Nvidia graphics, sound and Wi-Fi), I configured Wallpaper to a static color in Beta 1 before upgrading to Beta 2 and then to Beta 3.
EDIT: The installation of Beta 3 on my HackBookPro6,2 was V-E-R-Y S-L-O-W. I needed to wait longer than expected at several installation milestones. At one point when the Beta 3 upgrade was nearing completion, I waited at a black screen with just a mouse cursor for what seemed like 10 minutes (I didn't time it). Navigation once logged in is painfully slow.
Note that I'm not complaining (and anyone who is complaining about Tahoe on their unsupported Intel Mac needs to learn patience and silence). I'm just reporting my findings for those who are interested.
After the first login, Beta 3 starts up and logins in without issues.
Note that on my HackBookPro6,2 (which will need OCLP patches for non-metal Nvidia graphics, sound and Wi-Fi), I configured Wallpaper to a static color in Beta 1 before upgrading to Beta 2 and then to Beta 3.
EDIT: The installation of Beta 3 on my HackBookPro6,2 was V-E-R-Y S-L-O-W. I needed to wait longer than expected at several installation milestones. At one point when the Beta 3 upgrade was nearing completion, I waited at a black screen with just a mouse cursor for what seemed like 10 minutes (I didn't time it). Navigation once logged in is painfully slow.
Note that I'm not complaining (and anyone who is complaining about Tahoe on their unsupported Intel Mac needs to learn patience and silence). I'm just reporting my findings for those who are interested.
Last edited:
Boot to recovery and from there disable FileVault that did it for me.
You could say that - I use the same source for the DL and my installer created via terminal had a beautiful blue icon.
Finally I found an explanation. Everything was so slow that getting desktop and Dock could take until 15 minutes. I had not been patient enough. The reason of that is that the hack GoAwayLiquidGlass has been removed by installation of beta 3, after reinstalling everything is much, much faster!
I don't want to get into a discussion of OCLP basics, so forgive what may be a remedial question: are you using OCLP to generate your Open Core EFI?
@sinbad21 In Tahoe Beta 3, my /Applications folder looks "normal" on both my HackMini8,1 and my HackBookPro6,2. The applications in my /Applications folder are not links and are not in a subfolder.
EDIT: Note that I have not migrated to Tahoe, so all of my Tahoe apps have been installed in Tahoe. Also, I have only a single user (my Admin user) in Tahoe. My Tahoe installation started as a clean installation of Tahoe Beta 1, which I upgraded to Beta 2 and then to Beta 3. I did not upgrade Tahoe from a previous version of macOS.
EDIT: Note that I have not migrated to Tahoe, so all of my Tahoe apps have been installed in Tahoe. Also, I have only a single user (my Admin user) in Tahoe. My Tahoe installation started as a clean installation of Tahoe Beta 1, which I upgraded to Beta 2 and then to Beta 3. I did not upgrade Tahoe from a previous version of macOS.
Last edited:
Wouldn't it be better if we left the hackintoshes out of this thread, which is essentially about real Macs @Tahoe?
It wouldn't be the first time that the OpenCore configurations for hacks and those for OCLP for pure Macs differ. Mixing the two and the resulting tips could be a bit confusing for less experienced users.
It wouldn't be the first time that the OpenCore configurations for hacks and those for OCLP for pure Macs differ. Mixing the two and the resulting tips could be a bit confusing for less experienced users.
This is an important observation. All my Applications have been installed in Sequoia or even before. And I have two users.
Edit: I downloaded an App from App Store, it has been stored in /Applications folder. So you're right, only Apps installed before Tahoe are located in Shared folder.
That's strange.
Last edited:
I agree that it could be confusing. I'll refrain from any hackintosh-specific posts, while posting macOS Tahoe observations that are not hack-specific.
Until there is an OCLP, everyone should assume that Tahoe posts to date have been produced without an officially released version of OCLP for Tahoe.
What is a Mac? I always learn a lot from Deeveedee despite the hardware and the differences.
In the end, even the new user will look for his specific problem and skip over those posts he’s not interested in. I suggest to keep everything in one thread. What do you think?
I tend to agree. Where things are (or may be) hack-specific it would be in the interests of clarity to mention it. That seems to be happening already. It probably helps the OCLP devs when looking for points of failure.
Even though I was active in the Hackintosh scene for a long time (and I'm still active), gaining my first OC experience there after Clover and then turning to genuine Macs, I think it's better if Hackintoshers and Mac users interact in their own threads.
By the way: it says here - macOS Tahoe 26 on Unsupported Macs Discussion.
The approach with the Hackintosh is different, significantly more complex, and you're almost not "served" anything, but rather fill the folders yourself.
OCLP for genuine Macs is almost like a ready-made meal - it requires almost no changes from the user if they don't want to.
The causes of error messages also usually have different reasons. Because they are so different and require different approaches, I see separating them as a sensible measure. It prevents users from getting confused.
As I said before: Explanations for troubleshooting can be misinterpreted by inexperienced users and the majority of Mac users simply want to use their Mac but aren't familiar with all the relevant aspects.
On Discord these two topics are rigidly separated. FWIW 🤷♂️Even though I was active in the Hackintosh scene for a long time (and I'm still active), gaining my first OC experience there after Clover and then turning to genuine Macs, I think it's better if Hackintoshers and Mac users interact in their own threads.
By the way: it says here - macOS Tahoe 26 on Unsupported Macs Discussion.
The approach with the Hackintosh is different, significantly more complex, and you're almost not "served" anything, but rather fill the folders yourself.
OCLP for genuine Macs is almost like a ready-made meal - it requires almost no changes from the user if they don't want to.
The causes of error messages also usually have different reasons. Because they are so different and require different approaches, I see separating them as a sensible measure. It prevents users from getting confused.
As I said before: Explanations for troubleshooting can be misinterpreted by inexperienced users and the majority of Mac users simply want to use their Mac but aren't familiar with all the relevant aspects.
Discord should be the model for all forums
I'm hoping that Macrumors starts allowing profanity. That is something I do miss from Discord.
I'm hoping that Macrumors starts allowing profanity. That is something I do miss from Discord.
Discord should be the model for all forums
I'm hoping that Macrumors starts allowing profanity. That is something I do miss from Discord.
I sure as h--- hope they are smart enough not to.
Last edited:
To avoid incurring the wrath of our beloved thread police with an unsanctioned discussion or an OT post, I'll assign the proper classification to this post as "Possibly OT if you're anal-retentive, tested on a Hackintosh but first proven on a real Mac."
Your suggestion to use GoAwayLiquidGlass works well. Thank you.
EDIT: I also enable "system settings > accessibility > display > reduce transparency" to improve performance on this under-powered platform.
EDIT2: It appears that the bulk of the OCLP changes (at the time of this writing) are occuring in the 'macos-next' branch.
Last edited:
Latest kext updates and OCLP and keyboard and mouse are working on the mid 2014 MacBook Pro (again not much else you can do as mentioned by deeveedee ) but nice to see it working sort of . Same as the Mac mini takes a while on first attempt for desktop to appear doesn’t take as long on any other reboots after the first one.
Attachments
Anyone knows if the latest OCLP 3.0.0 fixes the issues we were having with FileVault 2 in these old machines on Sequoia as well (from the Changelog: Restore support for FileVault 2 on macOS 26)?
I'm afraid if I turn it on on Sequoia, I will be locked out as before.
Thank you,
EDIT: Unfortunately, FileVault 2 still does not work in Sequoia (and if I understood correctly, it will never work) Even Big Sur has problems now.
I had to manually decrypt the Data partition to be able to login again...
I'm afraid if I turn it on on Sequoia, I will be locked out as before.
Thank you,
EDIT: Unfortunately, FileVault 2 still does not work in Sequoia (and if I understood correctly, it will never work) Even Big Sur has problems now.
I had to manually decrypt the Data partition to be able to login again...
Last edited:
To be certain that I don't confuse novice and experienced OCLPers with this post, this post does NOT claim to have a functioning OCLP patcher for macOS Tahoe. I built the current OCLP source to learn more about OCLP and to view the state of development. It is very cool to see this patching screen with 'Modern Audio" for MBP6,2 after running the new build:
This post is NOT intended to suggest that OCLP is ready to patch any platforms.
This post is NOT intended to suggest that OCLP is ready to patch any platforms.