Jump to content

[Release] macOS Tahoe 26.2

fantomas

By fantomas,
in New Releases and Updates

 Share
228 posts in this topic

Recommended Posts

Ludox
Ludox
Posted
Posted
7 hours ago, MakAsrock said:

macOS Tahoe is compatible with these devices.

Explore Mac

All you had to do was share the official Apple link.

https://support.apple.com/it-it/122867

  • Thanks 1
MakAsrock
MakAsrock
Posted
Posted (edited)
30 minutes ago, Ludox said:

All you had to do was share the official Apple link.

https://support.apple.com/it-it/122867

Okay. Accepted your information. The post has been edited as I see fit. 😉

Edited by MakAsrock
  • Like 1
vamose
vamose
Posted
Posted
3 hours ago, Thebes Knossos said:

At all situations I would mean, it is not working for Vamoze.

Yes true, no go for @vamose macro 7,1 with any config file.

 

with revised SMBIOS of iMac 2020, no GPU boot flag required, no need to disable internal GPU.  All works, so far in sync.

  • Like 1
SavageAUS
SavageAUS
Posted
Posted

Hello all,

 

I have been away from the scene for a bit but am looking to update my rig but before I do I'd like to ask what changes have possibly occured since I installed Tahoe.

I am looking to update my AMD desktop so if this is the wrong place I apologize.

I have X570 motherboard and a Ryzen 9 5900x coupled with a RX6800xt.

I currently have installed Sequoia and Tahoe on seperate drives.

I am running OCLP version 2.4.0.

The version of Tahoe i have is 26.0 Beta 25A5351b.

 

I am just wondering besides the usual kext and OC updates what else should i look out for? Have the AMD patched been updated? Perhaps i can tag @Shaneee for this one. But I can see the patches have sat still for about 7 months.

Does OCLP now have support for broadcom wifi? If so where? I only see 2.4.1 which does not look like a wifi release.

 

Are we able to manually download the full installer from anywhere?

 

Do I need to disable any kexts to update?

 

Again, if this is posted in the wrong place please let me know and feel free to move it to where appropriate and I appreciate the help.

 

I have attached a reduced OC folder for additional information.

oc.zip

  • Like 1
Thebes Knossos
Thebes Knossos
Posted
Posted (edited)
Le 23/01/2026 à 11h49, vamose a dit :

Oui, c'est vrai, de @vamose la macro 7.1 ne fonctionne pas avec aucun fichier de configuration.

 

Avec la mise à jour du SMBIOS de l'iMac 2020, aucun paramètre de démarrage GPU n'est requis, ni la désactivation du GPU interne. Tout fonctionne parfaitement, la synchronisation est impeccable.

Just a question, with your Haswell, get you delta updates (releases, not developers ones) ? I get no ones fom 26.0.

Edited by Thebes Knossos
  • Like 1
Thebes Knossos
Thebes Knossos
Posted
Posted (edited)

It's a laptop with SMBIOS MacBookPro16,1 . Restrictevents is loaded yes. revpatch=sbvmm I had try on my desktop here and wasn't working. Isn't id for developers (beta) updates ? I search about regular delta updates, i's working on Sequoia with same EFI (without revpatch=sbvmm). Something is new on Tahoe with Haswell.

Edit:

Just tried with revpatch=sbvmm added to boot-args, did not work better.

Edited by Thebes Knossos
  • Sad 1
MakAsrock
MakAsrock
Posted
Posted
20 hours ago, Thebes Knossos said:

It's a laptop with SMBIOS MacBookPro16,1 . Restrictevents is loaded yes. revpatch=sbvmm I had try on my desktop here and wasn't working. Isn't id for developers (beta) updates ? I search about regular delta updates, i's working on Sequoia with same EFI (without revpatch=sbvmm). Something is new on Tahoe with Haswell.

Edit:

Just tried with revpatch=sbvmm added to boot-args, did not work better.

For delta updates you need csr-active-config data 00000000 and nothing more.

  • Confused 1
Thebes Knossos
Thebes Knossos
Posted
Posted

Changing from 03 08 00 00 (Sequoia working updates , OCLP config) to 00 00 00 00 changes nothing.

No full nor delta releases updates found on Tahoe 26.0.1 (fresh install, no OCLP never installed).

Something is new as requirement(s) on Haswell . Changes from Sequoia : no audio without OCLP , same as Sequoia: no Metal & no wifi & no bluetooth (I don't need it)

  • Sad 1
MakAsrock
MakAsrock
Posted
Posted (edited)
1 hour ago, Thebes Knossos said:

Changing from 03 08 00 00 (Sequoia working updates , OCLP config) to 00 00 00 00 changes nothing.

No full nor delta releases updates found on Tahoe 26.0.1 (fresh install, no OCLP never installed).

Something is new as requirement(s) on Haswell . Changes from Sequoia : no audio without OCLP , same as Sequoia: no Metal & no wifi & no bluetooth (I don't need it)

Open the terminal and paste into it: softwareupdate --fetch-full-installer --full-installer-version 26. < Substitute the required version.
1. No sound without OCLP, that's nothing new.
2. No metal, but why would there be when there are no drivers?
3. No Wi-Fi. Everyone doesn't have it, not just Haswell.
4. No Bluetooth. If it's Broadcom, that is.

Edited by MakAsrock
Thebes Knossos
Thebes Knossos
Posted
Posted (edited)

To get the full installer, I can with some applications, this is not a problem. Installing each release need around 40 Gb of free space, I don't have it on this laptop. I really need delta updates for MacOS releases, like Sequoia offer. 

The real question is : what is changing for delta updates and Haswell platform, what new request ?

Edited by Thebes Knossos
  • Sad 1
MakAsrock
MakAsrock
Posted
Posted (edited)
23 minutes ago, Thebes Knossos said:

To get the full installer, I can with some applications, this is not a problem. Installing each release need around 40 Gb of free space, I don't have it on this laptop. I really need delta updates for MacOS releases, like for Sequoia.

Well, I can't help here. I see incremental updates if I reverse the OCLP root patch. (Via a wired network.)
The only way out, as it seems to me, is to create a new partition and select it for installation. (There is no need to delete the previous one.)
I installed Tahoe this way when I wasn't sure it would work on my RIG.

Edited by MakAsrock
Thebes Knossos
Thebes Knossos
Posted
Posted

It's a fresh install and I don't want do a fresh install at each release, I stay on Sequoia for the moment, this Tahoe is not ready for my machine. I think I must wait news from OCLP team, some times they give compatibility news and not only for patches.

  • Like 1
verdazil
verdazil
Posted
Posted

Just my opinion.
Given that Tanoe isn't a sufficiently mature and stable system today, we can use previous, more stable systems for at least another year. These systems provide official support for our legacy WiFi devices via OCLP. Sonoma and Sequoia support all modern versions of third-party apps. Personally, I'm looking forward to the official release of OCLP 3.0. After that, we will be able to use macOS Tahoe for a few more years as the last compatible macOS for our Intel based systems...

  • Like 1
notobo
notobo
Posted
Posted (edited)
1 hour ago, verdazil said:

Just my opinion.
Given that Tanoe isn't a sufficiently mature and stable system today, we can use previous, more stable systems for at least another year. These systems provide official support for our legacy WiFi devices via OCLP. Sonoma and Sequoia support all modern versions of third-party apps. Personally, I'm looking forward to the official release of OCLP 3.0. After that, we will be able to use macOS Tahoe for a few more years as the last compatible macOS for our Intel based systems...

Use Sequoia without OCLP and without wifi for next two years. You will not have AirDrop, a small price for csr 00000000. Tahoe is not stable just like ios26. Nobody for day to day use Mac or iPhone use those OSs, except for testing reasons.

Edited by notobo
  • Like 2
Thebes Knossos
Thebes Knossos
Posted
Posted

Concerning my OTA update, I've have a look at logs with:  log show --predicate 'process == "softwareupdated"' --last boot

I get, extract:

[com.apple.SoftwareUpdateMacController:SU] [EVENT_REPORTER] UPLOADING | sending [UUID: F00BB192-8700-58E5-8922-BF95DC4A3C11] file: 3C7B1DDA-62D8-4072-A553-C5F734C9FD59 payload: {
    clientId = "F00BB192-8700-58E5-8922-BF95DC4A3C11";
    events =     (
                {
            UUID = "F00BB192-8700-58E5-8922-BF95DC4A3C11";
            batteryIsCharging = 0;
            batteryLevel = 100;
            catalogURL = "https://swscan.apple.com/content/catalogs/others/index-26-15-14-13-12-10.16-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz";
            currentBaseOSVersion = 25A362;
            currentOSType = user;
            currentOSVersion = 25A362;
            currentProductVersionExtra = Unknown;
            dataFsCapacity = 26965;
            dataFsFree = 20003;
            deviceClass = Mac;
            deviceModel = "Mac-E1008331FDC96864";           <--- correspond to MacbookPro16,1
            event = "com.apple.SoftwareUpdate.Scans";
            eventObject = SUTelemetryScanEvent;
            eventTime = 1769509534503;
            initiatedBy = foreground;
            lowPowerMode = false;
            macPlatform = unknown;                                           <--- but for some reason 
            previousBuildVersion = "26.0.1 (25A362)";
            project = "com.apple.SoftwareUpdate";
            rapidSecurityResponseInstalled = 0;
            rapidSecurityResponseSemiSplat = 0;
            reportVersion = "1.2";
            result = success;
            storageCapacity = 228936;
            sucoreVersion = "SUCore-2.1.0";
            systemFsCapacity = 11476;
            systemFsFree = 0;
            timeElapsed = "-7.2";
            timeSinceLastScan = "195.3";
        }
    );
}

 

so later it found only: (no new release)

2026-01-27 11:25:34.546531+0100 0x1ff3     Default     0x80ed               288    30   softwareupdated: (SoftwareUpdate) [com.apple.SoftwareUpdate:SoftwareUpdate] 4 updates found:
012-04872     | MRTConfigData 1.93
047-34130     | XProtectPlistConfigData 5326
061-06985     | Gatekeeper Compatibility Data 1.0
089-06171     | XProtectPayloads 156

 

My question to people who get OTA update:

What have you at line macPlatform  ?? Does it match to deviceModel ?

 

Thebes Knossos
Thebes Knossos
Posted
Posted (edited)

Thanks mate. Hum I have RestrictEvents (1.1.6 release) too, my post is without sbvmm but has no OTA with.

So macPlatform = unknown seems not to be the problem.

Waiting other responses...

Edited by Thebes Knossos
Thebes Knossos
Thebes Knossos
Posted
Posted

I think I have found the problem, but not solved.

I've add revpatch=sbvmm to boot-args, but RestrictEvents did not apply, instead deviceModel = "VMM-x86_64" (emulating a Virtual machine) I still get deviceModel = "Mac-E1008331FDC96864".

Bug with RestrictEvents + Tahoe + Haswell ?

Thebes Knossos
Thebes Knossos
Posted
Posted (edited)

Thanks I will try. Have you SIP = 03080000 or 00000000 ?

Tried with MacBookPro 17,1 it don't boot even with no compat check (normal model don't exist)

Tried with MacBookPro 11,1 no "VMM-x86_64". seems Restrictevents don't apply for DeviceModel in my case

Edited by Thebes Knossos
Thebes Knossos
Thebes Knossos
Posted
Posted (edited)

I've found the problem. https://github.com/acidanthera/RestrictEvents/commits/master/

For Tahoe you need latest 1.1.7 but only 1.1.6 is archived on Github page.

Added -revbeta and delta update is available.

 

 

update.png

Edited by Thebes Knossos
  • Like 1
LockDown
LockDown
Posted
Posted (edited)
24 minutes ago, Thebes Knossos said:

For Tahoe you need latest 1.1.7 but only 1.1.6 is archived on Github page.

1.1.6 is tahoe compatible.

You can grab 1.1.7 in artifacts if its still available or here https://dortania.github.io/builds/?product=RestrictEvents&viewall=true

Edited by LockDown
  • Like 1
 Share
Go to topic listing
×
×
  • Create New...