@Luckygreek He doesn't need to speculate given the amount of progress made since Tahoe Beta 1 was released. He should update his list.
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 he'll update his list, I'd say more of a heads up rather than speculating, to be fair some degree of speculation, which he's more than entitled to. Yes we're only in the first beta and a long way to go. So we'll see what the Dev's come up with with. As I said I hope he's wrong.
He is talking about Macs that contain a T2 chip. These are the ones that may be most problematic, chances are these machines won’t be able to run Tahoe with OCLP. From the various half-working successes on other older Macs without those pesky T2 chips, it seems not too unrealistic to get them to a usable state in the end. Just let’s wait and see what the devs come up with down the road.
Last edited:
Like I said a couple of times, we'll see what happens and I hope he's wrong as we go down the road and the Dev's have more time to work on OCLP.
Hackintoshes (which don't have T2) are running Tahoe with SMBIOS MacMini8,1 (which has a T2).
EDIT: If T2 were an issue that couldn't be addressed, hackintoshes wouldn't work.
EDIT: If T2 were an issue that couldn't be addressed, hackintoshes wouldn't work.
Last edited:
I don't use it, but I opened the Music app on my HackMini8,1 (hackintosh without T2 chip configured with SMBIOS MM8,1) and unpurchased song samples play without issues.
EDIT: I'm not an Apple Music expert, so forgive a naive question: could this be the problem?
OT- Just spent the weekend auditioning MacOS 26b1 on a fully supported M4 Mini and found the experience underwhelming. Migration Assistant migrates everything whether it runs on Apple Silicon or not. Non-compatible apps are outlined in grey, locating suitable replacements was tedious and inconclusive. Apple Intelligence can be toggled on and off but as a Beta it is incomplete and haphazard. I suspect Tahoe on OCLP will not be their finest hour. IMHO YMMV
Last edited:
Doesn't anyone here use a late 2013 (27-inch) iMac?
I'd be interested to know how to get Ethernet working again.
I looked at the IOnetworking.kext in System/Library/extensin, and it seems to
be the "Plugin" folder with all the Ethernet drivers.
Is it somehow possible to copy the entire IONetworking.kext from Sequoia 15.5 into Tahoe,
in the hope that the Ethernet network will then work?
I would be very happy if users of a late 2013 (27-inch) iMac would share
more details about their progress with Tahoe 26.
I'd be interested to know how to get Ethernet working again.
I looked at the IOnetworking.kext in System/Library/extensin, and it seems to
be the "Plugin" folder with all the Ethernet drivers.
Is it somehow possible to copy the entire IONetworking.kext from Sequoia 15.5 into Tahoe,
in the hope that the Ethernet network will then work?
I would be very happy if users of a late 2013 (27-inch) iMac would share
more details about their progress with Tahoe 26.
A year ago I was looking for an answer to this question. No one could answer.
Hackintoshes do not play Apple Music content. There is only one way - to use SMBIOS iMac Pro 2017.
Any old mac plays it without problems.
@Dimvol Try boot-arg unfairvga=7
My hackintoshes do play Apple Music and Apple TV content. But for Video, I need to use Firefox to watch it since it uses a software decoder. Support for most hardware decodes on GPUs were dropped in Big Sur, iirc.
My hackintoshes do play Apple Music and Apple TV content. But for Video, I need to use Firefox to watch it since it uses a software decoder. Support for most hardware decodes on GPUs were dropped in Big Sur, iirc.
Apple Music works fine for me on my Hackintosh with Tahoe, still trying to get it to install in my 2013 MacBook Pro
I had a look too on my MBP 16,1 2019 that barely made the Tahoe cut, and would agree. Also not convinced that the new "liquid glass" element is a great idea and to my eyes GUI-wise feels like a step back and a little dated as compared to Sequoia. The greatest feature is Intel support which maybe gives the OCLP devs a decent chance for at least another year of OCLP support>> OT- I suspect Tahoe on OCLP will not be their finest hour. IMHO YMMV
Last edited:
MBP11,1 and MBP5,2: success with installing, booting and logging into Tahoe 26b1.
In both cases, using external SSD connected to onboard USB and made clean install. EFIs generated with OCLP 2.4.0 and modified in-place (on target SSD) to use OC 1.0.5 and the respective Info.plist in USB-Map.kext. Thanks again deveedee and others! See post #67.
Also in both cases, needed to first install Sequoia 15.5 from USB installer, and do all the fresh setup (no data migration), and then install 26b1 over it from USB installer. Without first having Sequoia, after clean install of 26b1 I was unable to proceed beyond login as it seemed that system assistant got stuck (3rd picture, from MBP5,2) - maybe it would just have taken longer than the 1hr I waited. Thanks to Larsvonhier for his remark earlier in the Tahoe posts.
So far so good or even excellent for this 1st beta - didn't expect more at this point.
Attachments
Last edited:
This article helped me to restore the old LaunchPad to Tahoe. After executing the specified terminal commands and rebooting, I dragged LaunchPad from Applications to the Dock. I haven't tested for long, but so far, the Tahoe LaunchPad is identical to previous macOS LaunchPads.
I find Launchpad and other software features completely unimportant in a Beta 1!
What's more important is that ALL hardware, like USB ports and Ethernet, works,
even on unsupported Macs like my late 2013 iMac, where NO networking,
neither Wi-Fi nor Ethernet, works.
@Oxygen-X1 I think you're saying that Launchpad is not important until the basics (like Ethernet and Wi-Fi) works. I understand. Tahoe Beta 1 is brand new. It's amazing that Intel is still supported. Be patient and be encouraged by the rapid progress that is being made. Sorry I can't help you with your 2013 iMac.
No, that's an issue that can be resolved by resetting that counter by accessing Music/Account/Authorisation/(De)authorise. If I am not mistaken this can be done accessing AppleID using Safari and the related web app as well. The latter would give more options to deauthorize more devices in one go as far as I remember.
I’ve got some updates on the MBA M2 migration. The migration assistant generated a lot of junk from the internal storage (without Intel Apps from the source). It also messed up the permissions of my files and folders. On top of that, the Z-Shell stopped running, and the CPU was constantly at 15-20% load. But guess what? (And this is a big surprise!) On the Hackintosh without T2, everything works perfectly. The flickering GUI doesn’t happen, and the WLAN works fine. BT doesn’t work yet, but that’s okay. Overall, I’m really impressed with how well everything works on the Hackintosh.OT- Just spent the weekend auditioning MacOS 26b1 on a fully supported M4 Mini and found the experience underwhelming. Migration Assistant migrates everything whether it runs on Apple Silicon or not. Non-compatible apps are outlined in grey, locating suitable replacements was tedious and inconclusive. Apple Intelligence can be toggled on and off but as a Beta it is incomplete and haphazard. I suspect Tahoe on OCLP will not be their finest hour. IMHO YMMV
I'm attempting to build OCLP from source using Python 11 (from python.org) as specified here, but not having much luck. For those that are able to build OCLP 2.4.0 from source, what version of Python 3.11 are you using? Any special tricks to get it working?
EDIT: I fixed the build problem in my build environment. I edited the file OpenCore-Patcher-GUI.spec and changed the target_arch from 'universal2' to 'x86_64'
EDIT: I fixed the build problem in my build environment. I edited the file OpenCore-Patcher-GUI.spec and changed the target_arch from 'universal2' to 'x86_64'
Last edited: