• Become a Premium Member for $25/year with no ads to improve your community experience.

Common Problems in macOS Sequoia (15.0) and Workarounds

This thread is for common problems in macOS Sequoia. The problems listed here are likely to be experienced by users who attempt to install macOS Sequoia 15.0. Possible solutions are available for most of the issues at the moment.

This is not a troubleshooting thread. Please do not ask questions regarding your specific issue in this thread. If you're having an issue, create a separate thread. If you're having a problem to report or have a workaround to resolve the problems listed here, regarding the installation or function in macOS Sequoia, you can reply to this thread.

Special Notes

macOS Sequoia requires the following:
  • OpenCore v1.0.0 or later and Clover (v5158) or later.
  • Updated Kexts (Lilu, VSMC, and WEG)
If you're not aware of building kexts from the source, use the latest kexts from the installation guide.

In addition, please ensure your ports are mapped properly. If you're using a clean install, make sure to use a USB 2.0 Flash Drive.

Unsupported Hardware and workarounds

Like always, Apple has removed support for some older machines. This includes Desktops and Laptops on macOS Sequoia. However, the current beta release is almost similar to macOS Sonoma.


GPUs that does not support Metal. This include IGPUs as well.

There are ways to install macOS Sequoia on unsupported hardware. This isn't a problem on the Desktop side, as long as you have a compatible Graphics Card installed. However, on the Laptop, as the hardware such as CPU and GPU cannot be upgraded, you're left with a very few options: (i) either use the supported macOS on that particular system, (ii) bypass the compatibility check to boot and install (iii) change the SMBIOS to latest to boot and install (iv) root patch if certain hardware or function is not functional.

You can add -no_compat_check boot arg to your config.plist to bypass the compatibility check and continue with the installation. However, you won't have Graphics acceleration, broken WiFi and several other hardware functions. Recent macOS versions do allow to boot the installer, but the installation cannot proceed due to this skip. To combat this, the easiest way is to change the SMBIOS to a supported Mac model and that will let you boot the installer and then you can complete the installation. For example, iMac17,1 is ideal SMBIOS for SKL i5-6500 but that won't let you even boot the installer. Changing the SMBIOS to iMac18,1 or iMacPro1,1 will fix the issue. Still, the Graphics won't work and you'll have to root patch the system volume using OCLP. Another example is and luckily, you can spoof the SKL Graphics to KBL Graphics and that will serve the purpose. See the guides linked below for more information.

Grey Screen after installer boots

With the release of macOS Sequoia, one of the major issues is a grey screen followed by a white screen, when booting the installer. This can be fixed by the following:

- Ensure you're running OpenCore v1.0.0 or later and Clover (v5158).
- Ensure you're using the latest Lilu, VSMC, and WEG kexts
- Ensure your system is connected to the internet.

If you're using AMD APU, use iMacPro1,1 or iMac20,1 SMBIOS to prevent a black screen.

Progress bar stuck during installation or upgrade

During the installation phase or when upgrading to macOS Sequoia, the progress bar might get stuck for several hours. This can be fixed by the following:

- Ensure you're running OpenCore v1.0.0 or later and Clover (v5158).
- Ensure you're using the latest Lilu, VSMC, and WEG kexts
- Set SecureBootModel to Disabled
- Ensure your system is connected to the internet.

If you're using AMD APU, disable NootedRed until the installation is complete.

Black Screen after boot

With the release of macOS Sequoia, one of the major issues is a black screen when booting the installer or after the installation. This can be fixed by the following:

- Ensure you're running OpenCore v0.9.3 or later and Clover (v5152).
- Ensure you're using the latest Lilu, VSMC, and WEG kexts
- Ensure your system is connected to the internet.

If you're using AMD APU, use iMacPro1,1 or iMac20,1 SMBIOS to prevent a black screen.

Kernel Panic on AMD Platforms

If you're trying to boot macOS Sequoia on AMD platforms, there are chances that you'll end up getting Kernel Panic. The fix is to update the AMD Kernel Patches.

Solution: Ensure you're using the latest AMD Kernel Patches, which includes patches for Sequoia

Unable to select the language and continue

When booting the macOS Sequoia installer, there are chances that you might not be able to select the language and continue with the installation further. Although, the language can be selected, but the installation will not continue. This can be fixed by the following:

- Ensure you're running OpenCore v0.9.3 or later and Clover (v5152).
- Ensure you're using the latest Lilu, VSMC, and WEG kexts
- Ensure your system is connected to the internet.

Unable to boot with AMFIPass Enabled


An internet
Even if you're using an offline installer, during the installation stage, you'll get this error

Solution: Your system must be connected to the internet.


IGPU Graphics Acceleration

Apple dropped all the IGPU Graphics support up to Skylake. Users with Skylake and prior would not be able to use their IGPU, until there is a development from OCLP team. To install on systems with unsupported IGPU, use -igfxvesa in boot arg.

For Skylake Users

Fortunately, the KBL drivers are still present in macOS Sequoia Beta. It may be removed in the final release like NVIDIA drivers at the time of Monterey. However, SKL can be spoofed as KBL and acceleration can be achieved.

Stuck at NRed

If you're using AMD APU and trying to boot macOS Sequoia, the installer will stuck and will not progress further. Currently, NootedRed isn't compatible with macOS Sequoia.

NVIDIA Graphics Acceleration

With macOS Monterey, Apple completely removed support for NVIDIA. However, a workaround was to use OCLP, but at the moment, the OCLP is unable to patch the system on macOS Sequoia.

No I2C Device

With macOS Sequoia Beta 1, the I2C device such as Trackpad reported to work on Sonoma, does not work on Sequoia at all. Unless the base kext is updated, the issue will not be fixed. No ETA as of now.


SMBIOS Support
With the release of macOS Sequoia, Apple has dropped support for SMBIOS up to 2017 except for the iMacPro1,1. macOS Sequoia requires 2018 or later SMBIOS. See Setting Up SMBIOS for more info.

No Disk in Disk Utility
Some SATA Controllers are removed in macOS Ventura. The solution is to use CtlnaAHCIPort.kext

No USB Ports
Since macOS Big Sur 11.3, Apple made some changes and the XHCI Port Limit patch was broken. A solution is to map the ports.

Reboot Loop while installing or updating

If you're installing or updating to macOS Sequoia, the system might enter a reboot loop state. Originally discovered on a few HEDT platforms and mostly on macOS Sonoma 14.4. A guide already exist to fix the issue.

See the guide linked below for more information:

No WiFi and Bluetooth

On macOS Sequoia, Apple dropped support for several Broadcom Cards till 2017 Mac models. As a result, a major number of WiFi Cards will not work including supported Broadcom Cards (such as BCM94360NG/Fenvi T919). Users with any WiFi Card at the moment would not be able to use their WiFi, until there is a development from OCLP team. To utilize internet, use Ethernet or USB to Ethernet as a workaround for now.

Followed by Sonoma, macOS Sequoia also has no support for several Broadcom Cards till 2017 Mac models. As a result, a major number of WiFi Cards will not work including supported Broadcom Cards (such as BCM94360NG/Fenvi T919). Users with any WiFi Card at the moment would not be able to use their WiFi, until there is a development from OCLP team. To utilize internet, use Ethernet or USB to Ethernet as a workaround for now.


the WiFi and Bluetooth may not work. A solution is to update Lilu, VirtualSMC, and the Bluetooth related kexts. In addition, the USB ports must be mapped.


IO80211FamilyLegacy.kext has been removed and this is the reason why Broadcom natively supported WiFi isn't working at the moment. It's so much relief that Intel WiFi is still continuing to work. Spoofing the Device ID to a compatible one does not work and adding IO80211FamilyLegacy.kext throws Kernel Panic.

However, the Bluetooth is working absolutely fine with the latest BRCMPatchRAM commits.

Due to the removal of Legacy.kext, the Broadcom WiFi no longer functions.

No Ethernet

On macOS Sequoia, there is a very likely chance that your Ethernet won't work, including built-in, and any PCIe based such as AQuantia. To fix this issue, you'll need to enable VT-d on your System. Note that some systems may require memory mapping (fixing DMAR Table).

In addition, even if you had ethernet working on your previous macOS version, there are chances that during the installation, the built-in ethernet may not work during the installation stage. This is mostly the case with Intel I225 and I226 ethernet chips. The solution is to use USB to Ethernet Adapter or you can use a third-party kext as per the guide linked below:


No Updates in System Settings

If you're not getting OTA updates in System Settings, you'll need to use RestrictEvents to fix the issue. The solution has been included in the guide linked below:

Unable to Mount EFI Partition

Since the release of Sequoia Beta 5, there's an issue with mounting the EFI partition. The solution is described in the guide linked below:

Applications

With the release of macOS Sequoia, there could be a number of applications, audio plugins, and extensions which may not work at the moment, like it has always been for each macOS release. With macOS Sequoia, this is no different. Little Snitch does not work with macOS Sequoia yet.

Audio

Currently, Audio is not working for some Layout IDs on AMD Ryzen.

Solution: Update the AppleALC to the latest nightly version.

NVMe Support
NVMeFix will not work on macOS Sequoia as it is no longer being maintained. This can be an issue for drives like Samsung PM981. You must use a natively supported NVMe Drive.
 
Last edited:
  • Like
Reactions: DAEMONS
Thank you! My Lenovo and Desktops are using Clover 5159 and Opencore 1.0.1. Working fine and good. God Bless You All!!
 
Thank you! My Lenovo and Desktops are using Clover 5159 and Opencore 1.0.1. Working fine and good. God Bless You All!!
Yes, works fine. Sequoia is really fast and smooth. God bless dear!
 
I have some AppleALC situation. Sound does not work at all. it worked on Sonoma
Dang shit. You were supposed to wait. However, a new kext has been released. Try that.
 
  • Haha
Reactions: Sayor0603
Dang shit. You were supposed to wait. However, a new kext has been released. Try that.
yeah i am just commenting. i know i just have yo wait now. do not get angry on me please.. and the update was released 3 days ago and does not work..
 
yeah i am just commenting. i know i just have yo wait now. do not get angry on me please.. and the update was released 3 days ago and does not work..
Not angry at all :)

The Audio worked on 5700G system we tested. Maybe the issue is from something else? Try to boot into Windows, check Audio and if a firmware upgrade is available, do that.
 

Forum statistics

Threads
1,810
Messages
16,924
Members
25,955
Latest member
das_poolboy