macOS Sequoia and OpenCore Legacy Patcher Support #1136
Description
Another year, another WWDC and macOS version. This time with macOS 15, Sequoia, and a surprising lack of dropped hardware compared to previous years 🎉.
As the OS has been in developer beta for a few weeks now, we've compiled a list of challenges the patcher will need to overcome for this fall. This list will likely expand as we determine more issues with older systems.
- Dropped Models
- T2 MacBook Air and OpenCorePkg Challenge
- Trackpad Support
- MacPro3,1 Dual Socket Support
- New non-functional features
- General patches needing updates:
- Graphics:
Metal 31001Metal 3802Non-Metal
WirelessT1 ChipUSB 1.1
- Graphics:
- Overall timeline for support
Dropped Models
One of the most tame OS releases since macOS Catalina, currently only 2 Macs were dropped:
MacBookAir8,1: MacBook Air (Retina, 13-inch, 2018)
MacBookAir8,2: MacBook Air (Retina, 13-inch, 2019)
T2 MacBook Air and OpenCorePkg Challenge
The current biggest issue we face with supporting the MacBookAir8,x (2018/19) series is the T2 chip's lack of communication when booted through OpenCorePkg.
What happens when one of these units boots through OpenCorePkg is that AppleKeyStore.kext panics due to timeouts with the T2 chip:
"AppleKeyStore":3212:0: sks timeout strike 18
"AppleKeyStore":3212:0: sks timeout strike 19
"AppleKeyStore":3212:0: sks timeout strike 20
panic(cpu 0 caller 0xffffff801cd12509): "AppleSEPManager panic for "AppleKeyStore": sks request timeout" @AppleSEPManagerIntel.cpp:809
This affects not only macOS Sequoia, but macOS Ventura and Sonoma are confirmed to have the same issue. Thus an underlying problem with the MacBookAir8,x's firmware where it is not happy with OpenCorePkg.
- MacBookPro15,2, MacBookPro16,2 and Macmini8,1 do not exhibit these issues in local testing
- MacPro7,1 does seem to surprisingly based on reports: MacPro7,1 - OpenCorePkg
- Notes from this report were unsuccessful locally: Cannot boot MacPro7,1 #1487
We have made some progress on this issue, but panics are still occurring and there is still a significant amount of development work to do before T2 machines may even get to the install screen. We cannot provide any estimate on when T2 machines will be supported.
Trackpad Support
Certain Force Touch Trackpads lost support in macOS Sequoia, namely those used by unsupported Macs. The primary issue is simply the loss of identifiers to match onto older hardware.
For most hardware, this has been resolved with the following commit:
- efi_builder: Add SPI trackpad support to Sequoia (ea12d44)
- MacBookAir8,x is assumed to be broken, however, due to T2 issues, we cannot verify.
MacPro3,1 Dual Socket Support
Currently on macOS Sequoia, MacPro3,1 (2008) fails to boot due to a CPU panic:
processor_boot(): missing for cpu 4 @processor.c:876
This is due to the dual socket nature of the machine, and likely some firmware/ACPI table incompatibility. Temporary solution is to use cpus=4 boot argument (limiting to single socket), proper solution is currently unknown.
New non-functional features
iPhone Mirroring and Apple Intelligence won't be functional on majority of patched Macs.
iPhone Mirroring requires T2 for attestation and Apple Intelligence requires an NPU only found in Apple Silicon, the patcher is unable to provide a fix for these as they're hardware requirements.
General patches needing updates
The following patches have broken either partially or entirely. This will require additional work to properly identify issues and solutions:
- Graphics:
Wireless- Resolved with a32e148
T1 Chip- Resolved with 692c0de
USB 1.1- Resolved with dbae4db
Note that the Photos app is broken on non-Metal Macs
Overall timeline for support
As with every year, we cannot promise when support with be added. However following previous years' predictions, we hope for winter 2024 with OpenCore Legacy Patcher v2.0.0.
Development has been going strong internally and we hope everyone's excited!
For those watching development closely, know there will be a lack of commits for the month of July. This is primarily due to some scheduled surgeries for myself, and other members will be focusing on their amazing research and patch development. Thus the Python patching frontend and likely PatcherSupportPkg will be quiet. We hope to resume commits in August!