随着macOS Catalina(卡塔利娜) 10.15发行正式版本的临近，各种安装常见问题也需要同步更新，本篇文章就是针对10.15的常见问题的汇总，我会持续不间断更新，敬请期待

随着macOS Catalina(卡塔利娜) 10.15发行正式版本的临近，各种安装常见问题也需要同步更新，本篇文章就是针对10.15的常见问题的汇总，我会持续不间断更新，敬请期待 打开`beta 安装提示安装macOS 应用程序副本已损坏，不能用来安装macOS的解决方法该错误会经常出现于旧版中，根源是苹果的安装镜像中的. MultiBeast for Catalina is an all-in-one post-installation tool designed to enable boot from hard drive, and install support for Audio, Network, and Graphics. In addition, it includes System Utilities to rebuild caches and repair permissions and a collection of drivers, bootloaders, boot time config files, and handy software. I noticed the Hackintosher-Catalina-10.15-EFI was configured for a dedicated graphics card, so i changed that value to the integrated graphics card value and tried applying some of the old configs ( from the Mojave guide) that used to work but i am still seeing the screen like in a “pink” color.

打开`beta

安装提示安装macOS 应用程序副本已损坏，不能用来安装macOS的解决方法

该错误会经常出现于旧版中，根源是苹果的安装镜像中的证书过期导致的。解决方法如下：

• 实用工具-终端，输入命令：date 0201010116，回车后关闭终端，可继续安装进程；
• 新版本10.15.5系统的安装如果提示上述信息，大概率是你的CMOS时间是错的，这常见于使用双系统导致的；
  • 解决方案：可以将时间设置为当前时间，格式：date 月月日日时时分分年年年年.秒秒，比如我现在编辑这段文字的时间为：2020年5月28日04:50:45，那么就输入命令：date 052804502020.45，回车后关闭终端即可继续安装进程；【黑果小兵亲测有效】
• 另一种方法：BIOS中修正系统时间，误差不要多于5秒，应该能解决该提示信息【黑果小兵亲测有效】
• 安装过程中全程断开网络

关于Clover Bootloader的版本

想要正确地安装macOS Catalina 10.15.4，它要求你的Clover Bootloader版本不低于v5.0 r5107。Clover Bootloader最新版本下载

安装/更新黑屏问题

• boot args添加引导参数：agdpmod=pikera
• 更新WhateverGreen到v1.3.4，下载链接

关于数字音频中断，导致内核崩溃的解决方案

• KernelToPatch中添加：

  • Find: 636F6D2E 6170706C 65005F5F 6B65726E 656C5F5F 00

  • Replace: 6E6F742E 6170706C 65005F5F 6B65726E 656C5F5F 00

    详见：https://github.com/acidanthera/bugtracker/issues/513#issuecomment-542838126

Mac软件应用程序打开出现意外退出、崩溃解决怎么办？

去年7月12日苹果在悄悄升级系统后导致部分软件签名失效，很多软件用不了。打开后提示意外退出，还有的软件会提示崩溃。

导致此次TNT部分签名失效的事件起因

北京时间7月11日早间消息，据美国科技媒体Engadget报道，视频会议软件开发商Zoom此前发布紧急补丁，修复Mac摄像头漏洞。而苹果也在悄悄升级macOS，剔除隐藏的网络服务器。此前Zoom被曝出漏洞。当用户安装Zoom视频会议应用时，隐藏服务器会悄悄植入用户的Mac设备，让摄像头有被黑客劫持的风险。Zoom已经发布补丁，因此苹果并不是必须更新系统，不过升级之后更安全，即使用户使用旧版Zoom也能避开攻击。Zoom还与苹果合作测试修复补丁。补丁不会影响正常功能，只是启动App时需要获得用户的许可。

Mac应用程序崩溃解决办法

安装 Apple Command Line Tools

如果已经安装过，请直接跳到下一节

打开终端，输入命令：

弹出窗口

点击 安装，弹出窗口

点击 同意 继续，等待安装完成

修复签名方法：

终端里继续输入：

收工

注意事项

• 在HFS +上安装macOS Catalina时，通过系统偏好设置自动更新系统的功能会消失。

  解决方案：使用脚本下载10.15Beta更新包，原帖：https://github.com/Gengik84/MacOS_Updater

• 从第三方来源安装程序：

• 关闭Thunderbolt更新：

• 为第三方SSD启用TRIM

取消4位数密码限制

10.15 Beta5无法更新/安装的解决方法

另一种格式：

安装卡在最后2分钟的解决方法

• 断开网络

• 使用OsxAptioFixDrv-64.efi或者OsxAptioFixDrv3-64.efi替换AptioMemoryFix.efi，每次只可以用一个驱动

• 抹盘直接选择APFS格式，减少HFS+转换成APFS的过程

z390主板安装卡在apfs_module_start的解决方法

请于Acpi - DSDT - Patches中添加：

找不到安装器资源的解决方法

• 断网
• 删除drivers64UEFI目录下的EmuVariableUefi-64.efi
• 修改机型为最近三年，比如MacBootPro13,1MacBookPro14,1iMac17,1 等等
• 如果是双硬盘，拔掉那个不安装的，待安装完后再插回去
• 检查镜像的md5值

关于HD3000平台

macOS Catalina 10.15已经不支持Sandy Bridge平台的安装使用，解决方法有两个：

• 在引导标志(boot args)添加-no_compat_check跳过兼容性检查
• 修改SMBIOS为：MacBookAir5,1

Kaby Lake UHD 620显卡特别说明

部分基于类似AAPLGfxYTile的注入参数在macOS Catalina 10.15中会失效，它要求将Clover Bootloader版本至少更新到r4587或以上，Clover Bootloader最新版本下载

关于声卡注入的ID

Apple已从macOS Catalina 10.15上的AppleHDA.kext中删除了大量的Layouts，因此很多人需要修改/修补当前的AppleHDA.kext / AudioInjector才能使音频恢复到工作状态。
Apple在macOS Catalina上删除的布局ID为：
Layout1,3,8,9,11,12,13,18,22,23,24,25,26,27,28,29,30,31,32,34,36,37,38,39,41， 42,43,44,45,46,47,48,49,50等
要查看已删除的布局的完整列表以及可用于替换已删除的布局的列表，下面是一张可以使用并可在macOS Catalina 10.15上使用的可用布局的图片：

好消息是vit9696通过更新他的AppleALC解决了影响去除布局的问题。AppleALC最新版本的下载：https://github.com/acidanthera/AppleALC/releases

minStolenSize新补丁，用于Broadwell, Skylake 以及Kabylake, Coffeelake

3-24-2020 更新

• Coffee Lake

• Kaby Lake

• Sky Lake

• Broadwell

10.15.x解除USB端口限制补丁 [6-5-2019更新]

经和PMHeart求证后，精简成2条补丁

Intel HD3000显卡驱动

由于macOS Catalina 10.15中已经将AppleIntelHD3000Graphics.kext等相关驱动移除，一个折衷的解决方案是复制一份macOS Sierra 10.12.x的驱动到/System/Library/Extensions，重建缓存后重启即可享用。详见https://www.tonymacx86.com/threads/success-lenovo-b570e.255129/page-2#post-1770059

找回丢失的DW1560/Brcm94352Z驱动

Mojave系统下的蓝牙会失效，截止到目前的解决方法是：将文件BrcmFirmwareData.kext和BrcmPatchRAM2.kext复制到/Library/Extensions目录下。联想版请使用BrcmFirmwareRepo.kext

当然，在重启前，还要重建一下系统的缓存，命令为：

如果嫌输入命令麻烦，也可以使用应用Kext Utility重建缓存。

重启你的系统，检查WIFI/蓝牙是否工作正常。

关于10.15高通无线失效无法驱动的问题的解决方案[来自套路]

升级到Mojave的大家应该都看到了，14的驱动删掉了好多，最惹人注意的就是A卡的一堆、hd3000的几个、N卡的几个加上高通的无线网卡驱动，用了很久也琢磨了好久后，终于找到了解决高通无线挂的解决方案，下面是方法：

由于14系统内删除了Airport40的驱动，而ath9k插件又正是对其起的作用，因此前提条件是我们需要将13的这个kext拿来用，后面我会给出附件，ath9k插件的作者很久没有维护了，目前为止，作者源码只支持到10.13，因此需要我们手动修改源码使其能够支持到10.15，这里不做过多介绍，有兴趣的可以在下面评论，我会尽量解答，这里只把需要的附件做简要说明，大家也就不用再去clone源码修改编译了，附件主要包括3个，第一个是AtherosAirport40驱动，是我从13.6beta4中提取出来的，大家直接将其安装到/Library/Extensions/即可，然后就是我基于作者源码修改后的ath9k插件和最新的lilu（也是最新源码修改的），将这两个插件放到CLOVER，最后，为了保险起见，在config加上两个boot参数，分别是-lilubetaall 和 -ath9565，当然这是9565的参数，其余参数参见ath9k的说明文档，下面有链接，然后重建缓存、修复权限重启就可以了。详见：http://bbs.pcbeta.com/viewthread-1790406-1-1.html 感谢套路athlonreg

APFS转换解决方法

Apple已经删除了我们必须避免APFS转换的选项，常规的方法已经无法避免安装过程中自动将分区转换为APFS格式，包括在硬盘上安装以及SSD上面安装。
以下是一些目前已知的替代品：
1.使用Carbon Copy Cloner（CCC）应用程序格式驱动器备份到HFS + J并恢复备份。
2.使用此应用程序将APFS分区转换为HFS + J：https：//www.paragon-software.com/home/apfs-hfs-converter/
3.使用USB转SATA电缆从外部卸下HDD / SSD并安装macOS（似乎避免了APFS转换）。
4.修补安装程序，由你来找到这个方法。

安装中出现的IOConsoleUsers: time(0) 0->0, lin 0, llk 1, IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, nov 0, sm 0x0错误的临时解决方法

群里最常见的安装过程中出现的一个错误是：

原因是系统无法识别出你的显卡驱动，临时的解决方法是：

• 取消勾选Inject Intel
• 或者将platform-id修改为0x12345678
• 两种方法二选一，不知道如何操作的请移步Clover使用教程

安装完成后再通过Clover Configurator设置正确的FakeID和ig-plaform-id驱动你的显卡。

去掉Lilu的输出信息,还原10.13/10.14 内核崩溃(kernel pance)的真相

原文出处：https://applelife.ru/threads/ustanovka-macos-high-sierra-10-13-na-intel-pc.2210706/page-358#post-686953

**方法1：**使用文本编辑器，在KernelToPatch段落添加内容：

**方法2：**使用Clover Configurator打开config.plist - Kernel and Kext Patches - kernelToPatch，新添加：

其它的内核补丁备用，请自行食用：

引用链接：https://www.insanelymac.com/forum/topic/339035-pre-release-macos-catalina/?page=2&tab=comments#comment-2676147

Block injected kexts 禁用无效的、未知的驱动程序

当你面对这么一堆驱动的时候，如何让它们有条不紊地正常工作呢？万一出现问题的时候又如何让这些驱动在Clover引导的时候禁用它们呢？这个时候 Block injected kexts 就派上用场了。新版的 Clover Bootloader 已经将 Block injected kexts 放到了 macOS 系统分区的图标下面了。

• 操作方法：
  • 开机进入clover引导界面，要引导的分区卷标上按 空格 即可进入
    
  • 光标移动到 Block injected kexts 回车进入
    
  • 选择当前系统加载的驱动程序目录
    
  • 勾选禁用的驱动程序
    
  • 按 ESC 退出该子菜单

选择-v时出现Attempting system restart...MACH Reboot的解决方法

在安装High Sierra启动过程中，选择-v跑时会出现

而不用-v图跑直接显示苹果标志时则不会出现。

解决方法

在config.plist配置文件DropTables下添加以下代码：

抹盘时提示'MediaKit报告设备上的空间不足以执行请求的操作'的原因及解决方法

群里遇到最多的问题就是抹盘时提示'MediaKit报告设备上的空间不足以执行请求的操作',一直想就此写个解决方法

原因

出现该提示最根本的原因就是你之前的磁盘分区中ESP分区的尺寸小于200MB

解决方法

• Windows下使用diskgenius删除掉MSR分区,将多出来的分区合并到ESP,正好凑成200MB,以满足安装macOS的基本需求.
• macOS下可以直接使用磁盘工具进行抹盘,它会自动生成一个200MB的EFI分区,当然前提条件是你需要先备份好磁盘里的数据,否则会造成全盘数据的丢失,请谨慎操作.

关于macOS Catalina 10.15下修改显存以及帧缓存、显示接口

请移步另一篇教程：Coffee Lake帧缓冲区补丁及UHD630 Coffee Lake ig-platform-id数据整理

教你将U盘上的EFI复制到磁盘的EFI分区,脱离USB运行[macOS篇]

新的系统安装成功后，EFI还位于U盘里，总不能一直挂着U盘使用系统吧。这个时候如果你想将U盘里的EFI复制到磁盘的EFI分区里，却苦于找不到看不见EFI分区，这个时候是该让diskutil登场了。

diskutil命令的基本用法：

查看磁盘分区表

/dev/disk0(internal, physical):

/dev/disk1(internal, physical):

挂载磁盘EFI分区

挂载U盘EFI分区

打开Finder，注意后面有个.

左侧会显示挂载了两个EFI分区，将U盘EFI目录全部复制到磁盘的EFI分区即可。

合并EFI分区

这里有一点需要注意:如果之前安装过Windows系统的话,会存在EFI的目录,只是EFI的目录下面只有BOOT和Microsoft这两个目录,如果希望添加macOS的Clover引导的话,可以将USB的EFI分区里面的EFI目录下面的CLOVER复制到磁盘里的EFI目录下,也就是执行的是**合并**的操作,让EFI同时支持WINDOWS和macOS的引导.千万不要全部复制,否则有可能造成EFI无法启动Windows.

复制EFI分区

如果磁盘上的EFI分区里为空的,可以直接将USB的EFI分区下面的EFI目录直接复制到磁盘上的EFI分区里.

教你将U盘上的EFI复制到磁盘的EFI分区,脱离USB运行[Windows篇]

挂载EFI分区

Kext Wizard Catalina

Windows操作系统下面,打开cmd窗口,输入命令:

您可以重复输入命令同时挂载USB的EFI分区和磁盘的EFI分区
打开资源管理器，会出现一个盘符为X的磁盘，格式化为fat32格式,将USB的EFI分区下面的EFI目录复制到安装磁盘的EFI分区下

合并EFI分区

这里有一点需要注意:如果之前安装过Windows系统的话,会存在EFI的目录,只是EFI的目录下面只有BOOT和Microsoft这两个目录,如果希望添加macOS的Clover引导的话,可以将USB的EFI分区里面的EFI目录下面的CLOVER复制到磁盘里的EFI目录下,也就是执行的是**合并**的操作,让EFI同时支持WINDOWS和macOS的引导.千万不要全部复制,否则有可能造成EFI无法启动Windows.

复制EFI分区

如果磁盘上的EFI分区里为空的,可以直接将USB的EFI分区下面的EFI目录直接复制到磁盘上的EFI分区里.

添加UEFI引导选项

使用工具:BOOTICE

操作过程:

1. 打开BOOTICE软件,选择物理磁盘,选择欲操作的目标磁盘,点击分区管理,弹出分区管理的窗口,点击分配盘符,为ESP分区分配一个盘符,点击确定
   
2. 选择UEFI,点击修改启动序列,点击添加按钮,菜单标题填写:CLOVER,选择启动文件,在打开的窗口里选择ESP分区下的目录EFICLOVERCLOVERX64.EFI,点击保存当前启动项设置
   

重建缓存的命令

打开终端，输入命令：

感谢名单

• Apple 的 macOS
• RehabMan维护的项目：OS-X-Clover-Laptop-ConfigLaptop-DSDT-PatchOS-X-USB-Inject-All等
• Acidanthera 维护的项目：OpenCorePkgliluAirportBrcmFixupWhateverGreenVirtualSMCAppleALCBrcmPatchRAMMaciASL 等
• headkaze 提供的工具：hackintoolPinConfiguratorBrcmPatchRAM
• CloverHackyColor维护的项目：CloverBootloaderCloverThemes
• 宪武整理的：P-littleOC-little
• chris1111维护的项目：VoodooHDAWireless USB Adapter Clover
• zxystd开发的itlwmIntelBluetoothFirmware
• lihaoyun6提供的工具：CPU-SmacOS-Displays-iconSidecarPatcher
• sukka更新维护的从 Clover 到 OpenCore —— Clover 迁移 OpenCore 指南
• xzhih提供的工具：one-key-hidpi
• Bat.bat更新维护的精解OpenCore
• shuiyunxc 更新维护的OpenCore配置错误、故障与解决办法
• athlonreg更新维护的OpenCore 0.5+ 部件补丁Common-patches-for-hackintosh

参考及引用：

• Hervé 更新的Broadcom 4350:https://osxlatitude.com/forums/topic/12169-bcm4350-cards-registry-of-cardslaptops-interop/
• Hervé 更新的DW1820A支持机型列表:https://osxlatitude.com/forums/topic/11322-broadcom-bcm4350-cards-under-high-sierramojave/
• nickhx 提供的蓝牙驱动：https://osxlatitude.com/forums/topic/11540-dw1820a-for-7490-help/?do=findComment&comment=92833
• xjn819： 使用OpenCore引导黑苹果300系列主板正确使用AptioMemoryFix.efi的姿势(重写版）

关于打赏

您的支持就是我更新的动力！
如果不希望看到博主停更的话，请点击下方的 打赏 支持一下，有钱的捧个钱场，没钱的捧个人场，谢谢大家！

It's that time of year again and with it, and a new macOS beta has been dropped. Here's all the info you need to get started.

Reminder

This page will be a small discussion on exactly what you need to prepare for Big Sur, a more in depth look into what's changed on Big Sur can be found here:

# Table of Contents

• Prerequisites
• Troubleshooting

# Prerequisites

Before we can jump head first into installing Big Sur, we need to go over a few things:

# A supported SMBIOS

Big Sur dropped a few Ivy Bridge and Haswell based SMBIOS from macOS, so see below that yours wasn't dropped:

• iMac14,3 and older
  • Note iMac14,4 is still supported
• MacPro5,1 and older
• MacMini6,x and older
• MacBook7,1 and older
• MacBookAir5,x and older
• MacBookPro10,x and older

If your SMBIOS was supported in Catalina and isn't included above, you're good to go!

SMBIOS still supported in macOS Big Sur:

• iMac14,4 and newer
• MacPro6,1 and newer
• iMacPro1,1 and newer
• MacMini7,1 and newer
• MacBook8,1 and newer
• MacBookAir6,x and newer
• MacBookPro11,x and newer

For full list of supported SMBIOS including OS support, see here: Choosing the right SMBIOS

For those wanting a simple translation for their Machines:

• iMac13,1 should transition over to using iMac14,4
• iMac13,2 should transition over to using iMac15,1
• iMac14,2 and iMac14,3 should transition over to using iMac15,1
  • Note: AMD CPU users with Nvidia GPUs may find MacPro7,1 more suitable
• iMac14,1 should transition over to iMac14,4

# Supported hardware

Not much hardware has been dropped, though the few that have:

• Official Ivy Bridge U, H and S CPUs.
  • These CPUs will still boot without much issue, but note that no Macs are supported with consumer Ivy Bridge in Big Sur.
  • Ivy Bridge-E CPUs are still supported thanks to being in MacPro6,1
• Ivy Bridge iGPUs slated for removal
  • HD 4000 and HD 2500, however currently these drivers are still present in 11.0.1
• BCM4331 and BCM43224 based WiFi cards.
  • See Wireless Buyers guide(opens new window) for potential cards to upgrade to.
  • Potential work-around is to inject a patched IO80211Family, see here for more details: IO80211 Patches(opens new window)
• Certain SATA controllers dropped
  • For some reason, Apple removed the AppleIntelPchSeriesAHCI class from AppleAHCIPort.kext. Due to the outright removal of the class, trying to spoof to another ID (generally done by SATA-unsupported.kext) can fail for many and create instability for others.
  • A partial fix is to inject Catalina's version with any conflicting symbols being patched. You can find a sample kext here: Catalina's patched AppleAHCIPort.kext(opens new window)
  • We recommend setting the MinKernel value to 20.0.0 for the kext CtlnaAHCIPort.kext to avoid any potential conflicts. This way, it will work in both Catalina and Big Sur so you can remove SATA-unsupported if you want.

Kext Utility Catalina Download

Other notable changes:

• MSI Navi users no longer require the ATY,rom/-wegnoegpu patch to boot the installer
• Stage 2 installation requiring working NVRAM
  • Asus 9 series: For more info, see here: Haswell ASUS Z97 Big Sur Update Thread(opens new window)
  • X99 and X299 users with broken NVRAM will need to install on another machine and move the SSD when done

# Up-to-date kexts, bootloader and config.plist

Ensure that you have the latest version of OpenCore, kexts and config.plist so it won't have any odd compatibility issues. You can simply download and update OpenCore and kexts as mentioned here:

If you're unsure what version of OpenCore you're using, you can run the following in terminal:

• Note: The about command will require you to include bit 0x2 in Misc -> Security -> ExposeSensitiveData, recommended values for ExposeSensitiveData is 0x6 which includes bits 0x2 and 0x4.

# AMD Note

Reminder for AMD Users: Don't forget to update your kernel patches with those provided by AMD OS X, otherwise you'll be unable to boot Big Sur:

# Intel HEDT Note

For X79, X99 and X299 users, pay close attention to the below. Big Sur has added new requirements for ACPI, so you'll need to grab some new SSDTs:

• X79
• X99
• X299

For those who'd like precompiled files, see here:

# Known issues

With Big Sur, quite a bit broke. Mainly the following:

• Lilu
  • Mainly user-space patching has severely broke, meaning certain functionality may have broken
  • These include:
    • DiskArbitrationFixup
    • MacProMemoryNotificationDisabler
    • SidecarEnabler
    • SystemProfilerMemoryFixup
    • NoTouchID
    • WhateverGreen's DRM and -cdfon patches
• AirportBrcmFixup
  • Forcing a specific driver to load with brcmfx-driver= may help
    • BCM94352Z users for example may need brcmfx-driver=2 in boot-args to resolve this, other chipsets will need other variables.
  • Setting MaxKernel to 19.9.9 for AirPortBrcm4360_Injector.kext may help. More information from the repo(opens new window)
• SATA Support broken
  • Due to Apple dropping the AppleIntelPchSeriesAHCI class in AppleAHCIPort.kext
  • To resolve, add Catalina's patched AppleAHCIPort.kext(opens new window) with the MinKernel set to 20.0.0

And while not an issue, SIP has now gained a new bit so to properly disable SIP you need to set csr-active-config to FF0F0000. See here for more info: Disabling SIP

# Installation

Guides have been updated to accommodate Big Sur, see the applicable OS environment for you:

# Troubleshooting

# Stuck at Forcing CS_RUNTIME for entitlement

This is actually the part at where macOS will seal the system volume, and where it may seem that macOS has gotten stuck. DO NOT RESTART thinking you're stuck, this will take quite some time to complete, otherwise you'll break your installation.

# Stuck at PCI Configuration Begins for Intel's X99 and X299 boards

As previously mentioned, Intel HEDT motherboards may have some issues revolving around their RTC device in ACPI. To resolve, you'll need to look at your RTC device and see which regions are missing. For more information, see here: SSDT-RTC0-RANGE.dsl(opens new window)

# Stuck on ramrod(^^^^^^^^^^^^^)

If you get stuck around the ramrod section (specifically, it boots, hits this error, and reboots again back into this, causing a loop), this hints that your SMC emulator is broken. To fix this, you have 2 options:

• Ensure you're using the latest builds of VirtualSMC and Lilu, with the vsmcgen=1 boot-arg
• Switch over to Rehabman's FakeSMC(opens new window) (you can use the MinKernel/MaxKernel trick mentioned above to restrict FakeSMC to Big Sur and up)

And when switching kexts, ensure you don't have both FakeSMC and VirtualSMC enabled in your config.plist, as this will cause a conflict.

# X79 and X99 Kernel Panic on IOPCIFamily

This is due to an unused uncore PCI Bridges being enabled in ACPI, and so IOPCIFamily will kernel panic when probing unknown devices. To resolve, you'll need to add SSDT-UNC(opens new window) to your system

# DeviceProperties injection failing

With Big Sur, macOS has become much pickier with devices being present in ACPI. Especially if you're injecting important properties for WhateverGreen or AppleALC, you may find they're no longer applying. To verify whether your ACPI defines your hardware, check for the acpi-path property in IORegistryExplorer(opens new window):

If no property is found, you'll need to create an SSDT that provides the full pathing as you likely have a PCI Bridge that is not documented in your ACPI tables. An example of this can be found here: SSDT-BRG0(opens new window)

• Note: This issue may also pop up in older versions of macOS, however Big Sur is most likely to have issues.

# Keyboard and Mouse broken

For certain legacy systems, you may notice that while the USB ports work your HID-based devices such as the keyboard and mouse may be broken. To resolve this, add the following patch:

config.plist -> Kernel -> Patch:

# Early Kernel Panic on max_cpus_from_firmware not yet initialized

If you receive an early kernel panic on max_cpus_from_firmware not yet initialized, this is due to the new acpi_count_enabled_logical_processors method added in macOS Big Sur's kernel. To resolve, please ensure you're on OpenCore 0.6.0 or newer with the AvoidRuntimeDefrag Quirk enabled.

• Note: Due to how early this kernel panic happens, you may only be able to log it either via serial or rebooting in a known working install of macOS and checking your panic logged in NVRAM.
  • Most users will see this panic simply as [EB|#LOG:EXITBS:START]

On-screen:

Via serial logging or NVRAM:

On certain hardware, mainly the HP DC7900, the kernel still can't determine exactly how many threads your hardware supports. This will result in the aforementioned kernel panic and so we need to hard code the CPU core's value.

To do this, Add the following patch(replacing the 04 from B8 04 00 00 00 C3 with the amount of CPU threads your hardware supports):

# Cannot update to newer versions of Big Sur

Generally there's 2 main culprits:

Kext Utility Catalina

• Broken Update Utility
  • Most common error if running a beta, try this first

# Broken Update Utility

Kext Utility For Catalina

Generally seen with every beta cycle, simply unenroll and enroll again:

Then check back with settings, and it should pop up. If not, run the following:

This should help kick the update utility back into gear. If you still have issues, check the Broken Seal section.

# Broken Seal

With Apple's new snapshotting for the system drive, they now depend heavily on this for OS updates to apply correctly. So when a drove's seal is broken, macOS will refuse to update the drive.

To verify yourself, check that Snapshot Sealed returns as YES:

If it returns Snapshot Sealed: Broken, then you'll want to go through the following:

Kext Utility Mac Os Catalina

• Update to OpenCore 0.6.4 or newer
  • Specifically commit ba10b5d(opens new window) or newer is required
• Revert to older snapshots
  • Mainly for those who have tampered with the system volume
  • See here how to revert: Rolling back APFS Snapshots

# Kernel Panic on Rooting from the live fs

Full error:

This is due to issues around Secure Boot boot being enabled in Beta 10 with older versions of OpenCore. Simply update to 0.6.4 to resolve

• Specifically commit ba10b5d(opens new window) or newer is required

# Asus Z97 and HEDT(ie. X99 and X299) failing Stage 2 Installation

With Big Sur, there's a higher reliance on native NVRAM for installation otherwise the installer will get stuck in a reboot loop. To resolve this you'll need to either:

• Install Big Sur on another machine, then transfer the drive
• Fix the motherboard's NVRAM
  • mainly applicable with Asus's Z97 series

For the latter, see here: Haswell ASUS Z97 Big Sur Update Thread(opens new window)

# Laptops kernel panicking on cannot perform kext scan

This is due to multiple copies of the same kext being in your kernel cache, and to be more specific having multiple copies of VoodooInput. Look over your Kernel -> Add and verify you only have 1 copy of VoodooInput enabled.

• Note: Both VoodooI2C and VoodooPS2 have a bundled copy of VoodooInput, which you disable is up to personal preference