3plus Hr Syn Failure

# Kernel Issues

Issues surrounding from initial booting the macOS installer to right before the install GUI pops upward.

• Stuck on [EB|#LOG:EXITBS:Beginning]
  • Booter Issues
  • Kernel Patch Bug
  • UEFI Issues
• Stuck on EndRandomSeed
• Stuck after selecting macOS partitioning in OpenCore
• Kernel Panic on Invalid frame pointer
• Stuck on [EB|LD:OFS] Err(0xE) when booting preboot volume
• Stuck on OCB: LoadImage failed - Security Violation
• Stuck on OCABC: Memory puddle allocation failure - Not Found
• Stuck on Buffer Also Small
• Stuck on Plist only kext has CFBundleExecutable key
• Stuck on This version of Mac Os X is not supported: Reason Mac...
• Couldn't allocate runtime surface area errors
• Stuck on RTC..., PCI Configuration Begins, Previous Shutdown..., HPET, HID: Legacy...
• Stuck at ACPI table loading on B550
• "Waiting for Root Device" or Prohibited Sign mistake
  • USB Issues
  • SATA Problems
• Kernel panic with IOPCIFamily on X99
• Stuck on or virtually IOConsoleUsers: gIOScreenLock.../gIOLockState (3...
• Scrambled Screen on laptops
• Blackness screen after IOConsoleUsers: gIOScreenLock... on Navi
• Kernel Panic Cannot perform kext summary
• Kernel Panic AppleIntelMCEReporter
• Kernel Panic AppleIntelCPUPowerManagement
• Kernel Panic AppleACPIPlatform in x.13
• macOS frozen correct earlier login
• Keyboard works but trackpad does non
• kextd stall[0]: AppleACPICPU
• Kernel Panic on AppleIntelI210Ethernet
• Kernel panic on "Wrong CD Clock Frequency" with Icelake laptop
• Kernel panic on "cckprngintgen"
• Stuck at Forcing CS_RUNTIME for entitlement in Big Sur
• Stuck on ramrod(^^^^^^^^^^^^^)
• Virtual Car Issues
• Reboot on "AppleUSBHostPort::createDevice: failed to create device" on macOS 11.three+

# Stuck on [EB|#LOG:EXITBS:START]

This department will be split into three parts, and so pay close attention:

• Booter Bug
• Kernel Patch Issues
• UEFI Issues
• Virtual Auto Problems

# Booter Issues

The main culprits to watch for in the Booter section are:

• DevirtualiseMmio

  • Certain MMIO spaces are still required to office correctly, so you'll need to either exclude these regions in Booter -> MmioWhitelist or disable this quirk outright. More than info here: Using DevirtualiseMmio
  • For TRx40 users, enable this quirk
  • For X99 users, disable this quirk every bit it breaks with some firmwares

• SetupVirtualMap

  • This quirk is required for the majority of firmwares and without it it's very common to kernel panic here, so enable it if not already
    • Mainly Z390 and older require this quirk enabled
    • Nonetheless, sure firmwares(mainly 2020+) practise not work with this quirk so may actually cause this kernel panic:
      • Intel'due south Ice Lake serial
      • Intel's Comet Lake series(B460, H470, Z490, etc)
      • AMD'southward B550 and A520(Latest BIOS on X570 are as well included now)
        • Many B450 and X470 boards with late 2020 BIOS updates are also included
      • AMD's TRx40
      • VMs like QEMU
      • X299 2020+ BIOS updates(This applies to other X299 boards on the latest BIOS that released either in tardily 2019 or 2020+)

• EnableWriteUnprotector

  • Some other result may be that macOS is conflicting with the write protection from CR0 register, to resolve this nosotros have 2 options:
    • If your firmware supports MATs(2018+ firmwares):
      • EnableWriteUnprotector -> False
      • RebuildAppleMemoryMap -> True
      • SyncRuntimePermissions -> True
    • For older firmwares:
      • EnableWriteUnprotector -> Truthful
      • RebuildAppleMemoryMap -> False
      • SyncRuntimePermissions -> False
    • Note: Some laptops(ex. Dell Inspiron 5370) fifty-fifty with MATs support volition halt on boot upward, in these cases you'll have 2 options:
      • Boot with the old firmware quirk combo(ie. With EnableWriteUnprotector and disable RebuildAppleMemoryMap + SyncRuntimePermissions)
      • Enable DevirtualiseMmio and follow MmioWhitelist guide (opens new window)

Regarding MATs support, firmwares built against EDK 2018 will back up this and many OEMs have even added back up all the way back to Skylake laptops. Issue is it'south not e'er obvious if an OEM has updated the firmware, yous can bank check the OpenCore logs whether yours supports it(Meet here how to become a log):

• Note: i means it supports MATs, while 0 means it does not.

# Kernel Patch Bug

This department will be split between Intel and AMD users:

# AMD Users

• Missing kernel patches (opens new window) (only applies for AMD CPUs, make sure they're OpenCore patches and not Clover. Clover uses MatchOS while OpenCore has MinKernel and Maxkernel)
  • Note outdated kernel patches will too have the same result delight ensure you're using the latest patches from AMD Bone X

# Intel Users

• AppleXcpmCfgLock and AppleCpuPmCfgLock
  • Missing CFG or XCPM patches, please enable AppleXcpmCfgLock and AppleCpuPmCfgLock
    • Haswell and newer merely need AppleXcpmCfgLock
    • Ivy Bridge and older simply need AppleCpuPmCfgLock
      • Broadwell and older need AppleCpuPmCfgLock if running 10.10 or older
  • Alternatively you can properly disable CFG-Lock: Fixing CFG Lock (opens new window)
• AppleXcpmExtraMsrs
  • May also be required, this is generally meant for Pentiums, HEDT and other odd systems non natively supported in macOS.

# Legacy Intel users

For macOS Big Sur, many firmwares accept problems determining the CPU core count and thus will kernel panic as well early for screen press. Via series, you can see the following panic:

To resolve:

• Enable AvoidRuntimeDefrag nether Booter -> Quirks
  • This should work for most firmwares

Yet on certain machines like the HP Compaq DC 7900, the firmware will even so panic and so nosotros need to forcefulness a CPU cadre count value. Only use the beneath patch if AvoidRuntimeDefrag didn't work:

Legacy CPU Cadre patch

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

Fundamental	Type	Value
Base	String	_acpi_count_enabled_logical_processors
Count	Integer	1
Enabled	Boolean	Truthful
Find	Data
Identifier	String	Kernel
Limit	Integer	0
Mask	Data
MaxKernel	String
MinKernel	String	20.0.0
Replace	Data	B804000000C3
ReplaceMask	Data
Skip	Integer	0

# UEFI Issues

• ProvideConsoleGop
  • Needed for transitioning to the next screen, this was originally part of AptioMemoryFix but is now inside OpenCore as this quirk. Can be found nether UEFI -> Output
  • Note every bit of 0.five.6, this quirk is enabled by default in the sample.plist
• IgnoreInvalidFlexRatio
  • This is needed for Broadwell and older. Not for AMD and Skylake or newer

# Stuck on EndRandomSeed

Same issues above, encounter hither for more than details: Stuck on [EB|#LOG:EXITBS:Offset]

# Stuck after selecting macOS partition in OpenCore

Same bug above, meet here for more than details: Stuck on [EB|#LOG:EXITBS:Beginning]

• Note: Enabling DEBUG OpenCore can help shed some light as well

# Kernel Panic on Invalid frame pointer

So this is due to some issue around the Booter -> Quirks you set, chief things to check for:

• DevirtualiseMmio

  • Sure MMIO spaces are nonetheless required to role correctly, so y'all'll need to either exclude these regions in Booter -> MmioWhitelist or disable this quirk outright
  • More info here: Using DevirtualiseMmio

• SetupVirtualMap

  • This quirk is required for the majority of firmwares and without it information technology's very mutual to kernel panic here, and so enable it if not already
    • Nevertheless, sure firmwares do not work with this quirk and and then may really cause this kernel panic:
      • Intel's Water ice Lake series
      • Intel's Comet Lake series
      • AMD's B550
      • AMD's A520
      • AMD's TRx40
      • VMs similar QEMU

Another issue may be that macOS is conflicting with the write protection from CR0 register, to resolve this we have ii options:

• If your firmware supports MATs(2018+ firmwares):
  • EnableWriteUnprotector -> Simulated
  • RebuildAppleMemoryMap -> Truthful
  • SyncRuntimePermissions -> Truthful
• For older firmwares:
  • EnableWriteUnprotector -> True
  • RebuildAppleMemoryMap -> False
  • SyncRuntimePermissions -> False

Regarding MATs support, firmwares built against EDK 2018 will support this and many OEMs have even added back up all the manner back to Skylake laptops. Result is it's not e'er obvious if an OEM has updated the firmware, yous can check the OpenCore logs whether yours supports it:

Note: 1 means information technology supports MATs, while 0 means it does not.

# Stuck on [EB|LD:OFS] Err(0xE) when booting preboot volume

Full error:

This can happen when the preboot book isn't properly updated, to gear up this you'll need to boot into recovery and repair information technology:

1. Enable JumpstartHotplug nether UEFI -> APFS(Recovery may not kick on macOS Large Sur without this option)
2. Kicking into recovery
3. Open the last, and run the following:

Then finally reboot

# Stuck on OCB: LoadImage failed - Security Violation

This is due to missing outdated Apple Secure Boot manifests present on your preboot volume resulting is a failure to load if you have SecureBootModel set, reason for these files being missing is actually a issues in macOS.

To resolve this y'all can practice one of the following:

• Disable SecureBootModel
  • ie. set Misc -> Security -> SecureBootModel -> Disabled
• Reinstall macOS with the latest version
• Or copy over the Secure Kick manifests from /usr/standalone/i386 to /Volumes/Preboot/<UUID>/Arrangement/Library/CoreServices
  • Note you lot will virtually likely need to exercise this via concluding equally the Preboot volume isn't easily editable via the Finder

To practise this via terminal:

# Stuck on OCABC: Memory pool allotment failure - Not Establish

This is due to incorrect BIOS settings:

• Above4GDecoding is Enabled
• CSM is Disabled(Enabling Windows8.i/10 WHQL Mode can do the aforementioned on some boards)
  • Annotation on some laptops, CSM must be enabled
• BIOS is upward-to-appointment(Z390 and HEDT are known for having poorly written firmwares)

# Stuck on Buffer Too Small

• Enable Above4GDecoding in the BIOS

# Stuck on Plist just kext has CFBundleExecutable key

Missing or wrong Executable path in your config.plist, this should be resolved by re-running ProperTree's snapshot tool(Cmd/Ctrl+R).

# Stuck on This version of Mac OS X is non supported: Reason Mac...

This error happens when SMBIOS is one no longer supported by that version of macOS, make sure values are set in PlatformInfo->Generic with Automated enabled. For a full listing of supported SMBIOS and their OSes, see here: Choosing the right SMBIOS

Supported SMBIOS in macOS 10.xv, Catalina

• iMac13,ten+
• iMacPro1,1
• MacPro6,1+
• Macmini6,x+
• MacBook8,1+
• MacBookAir5,10+
• MacBookPro9,ten+

Supported SMBIOS in macOS 11, Big Sur

• iMac14,four+
• iMacPro1,1
• MacPro6,one+
• Macmini7,one+
• MacBook8,one+
• MacBookAir6,x+
• MacBookPro11,x+

Supported SMBIOS in macOS 12, Monterey

• iMac16,1+
• iMacPro1,ane
• MacPro6,1+
• Macmini7,1+
• MacBook9,1+
• MacBookAir7,i+
• MacBookPro11,3+

# Couldn't classify runtime area errors

Encounter Fixing KASLR slide values

Well this general area is where a lot of PCI devices are first setup and configured, and is where most booting problems will happen. Other names include:

• apfs_module_start...,
• Waiting for Root device,
• Waiting on...IOResources...,
• previous shutdown crusade...

The primary places to check:

• Missing EC patch:

  • Make certain yous accept your EC SSDT both in EFI/OC/ACPI and ACPI -> Add, double cheque it's enabled.
  • If you don't have one, catch it here: Getting started with ACPI (opens new window)

• IRQ conflict:

  • Most common on older laptops and pre-builts, run SSDTTime'due south FixHPET option and add the resulting SSDT-HPET.aml and ACPI patches to your config( the SSDT volition not work without the ACPI patches)

• PCI allocation consequence:

  • UPDATE YOUR BIOS, brand certain it'due south on the latest. Near OEMs have very cleaved PCI allocation on older firmwares, particularly AMD
  • Make certain either Above4G is enabled in the BIOS, if no selection bachelor then add npci=0x2000 to kicking args.
    • Some X99 and X299 boards(ie. GA-X299-UD4) may require both npci kicking-arg and Above4G enabled
    • AMD CPU Annotation: Do non have both the Above4G setting enabled and npci in boot args, they will conflict
    • 2020+ BIOS Notes: When enabling Above4G, Resizable BAR Support may go an bachelor. Please ensure that Booter -> Quirks -> ResizeAppleGpuBars is set to 0 if this is enabled.
  • Other BIOS settings that are important: CSM disabled, Windows eight.i/10 UEFI Fashion enabled

• NVMe or SATA upshot:

  • Sometimes if either a bad SATA controller or an unsupported NVMe drive are used, y'all can usually get stuck here. Things yous can check:
    • Not using either a Samsung PM981 or Micron 2200S NVMe SSD
    • Samsung 970 EVO Plus running the latest firmware(older firmwares were known for instability and stalls, encounter hither for more than info (opens new window) )
    • SATA Hot-Plug is disabled in the BIOS(more commonly to crusade problems on AMD CPU based systems)
    • Ensure NVMe drives are prepare as NVMe mode in BIOS(some BIOS take a bug where y'all can set NVMe drives as SATA)

• NVRAM Failing:

  • Mutual issue HEDT and 300 series motherboards, you lot have a couple paths to go down:
    • 300 Series Consumer Intel: Encounter Getting started with ACPI (opens new window) on making SSDT-PMC.aml
    • HEDT(ie. X99): See Emulating NVRAM (opens new window) on how to stop NVRAM write, note that for install you do non need to run the script. Only setup the config.plist

• RTC Missing:

  • Commonly constitute on Intel'south 300+ series(ie. Z370, Z490), acquired by the RTC clock being disabled by default. See Getting started with ACPI (opens new window) on creating an SSDT-AWAC.aml
  • X99 and X299 accept broken RTC devices, so will need to exist fixed with SSDT-RTC0-RANGE. See Getting started with ACPI (opens new window) on creating said file
  • Some boozer firmware author at HP also disabled the RTC on the HP 250 G6 with no way to actually re-enable it
    • Known afflicted models: HP xv-DA0014dx, HP 250 G6
    • For users cursed with such hardware you'll need to create a fake RTC clock for macOS to play with. Run into getting started with ACPI for more details, as well every bit below image instance:

Example of what a disabled RTC with no style to enable looks like(note that at that place is no value to re-enable information technology like STAS):

# Stuck at ACPI table loading on B550

If you're getting stuck at or near ACPI tabular array loading with an AMD B550 or A520 motherboard, add the following SSDT:

• SSDT-CPUR.aml (opens new window)

And delight think to add this SSDT to both EFI/OC/ACPI and your config.plist under ACPI -> Add together(ProperTree'due south snapshot function can do this for you)

# "Waiting for Root Device" or Prohibited Sign error

• Other names: End Sign, Scrambled

This is generally seen as a USB or SATA error, couple means to prepare:

# USB Issues

This assumes yous're only booting the installer USB and not macOS itself.

• If you're hitting the 15 port limit, yous can temporarily get effectually this with XhciPortLimit but for long term utilize, nosotros recommend making a USBmap (opens new window)

  • Kernel -> Quirks -> XhciPortLimit -> True

• Some other consequence tin can exist that certain firmware won't pass USB ownership to macOS

  • UEFI -> Quirks -> ReleaseUsbOwnership -> True
  • Enabling XHCI Handoff in the BIOS can set up this as well

• Sometimes, if the USB is plugged into a iii.x port, plugging it into a 2.0 port tin can prepare this fault.

• For AMD'south 15h and 16h CPUs, you may demand to add the post-obit:

  • XLNCUSBFix.kext (opens new window)

• If XLNCUSBFix even so doesn't work, then try the following:

  • AMD StopSign-fixv5 (opens new window)

• X299 Users: Enable Above4G Decoding

  • Odd firmware bug on X299 where USB breaks otherwise

• Missing USB ports in ACPI:

  • For Intel'due south Coffee Lake and older, we recommend using USBInjectAll (opens new window)
  • For Intel'south Ice Lake and Comet Lake, we recommend SSDT-RHUB (opens new window)
    • SSDTTime'due south seven. USB Reset pick tin do the same
  • For AMD, run SSDTTime's 7. USB Reset choice and add together the provided SSDT-RHUB to your EFI and config.plist

# SATA Issues

On rare occasions(mainly laptops), the SATA controller isn't officially supported past macOS. To resolve this, nosotros'll want to do a few things:

• Prepare SATA to AHCI fashion in the BIOS
  • macOS doesn't support hardware RAID or IDE manner properly.
  • Annotation drives already using Intel Rapid Storage Technology(RST, soft RAID for Windows and Linux) will non be attainable in macOS.
• SATA-unsupported.kext (opens new window)
  • Adds support to obscure SATA controllers, commonly beingness laptops.
  • For very legacy SATA controllers, AHCIPortInjector.kext (opens new window) may be more suitable.
• Catalina's patched AppleAHCIPort.kext (opens new window)
  • For users running macOS 11, Large Sur and having problems. This backports the known working Catalina kext, SATA-unsupported is not needed with this kext

Note that you will only feel this issue after installing macOS onto the drive, booting the macOS installer will non fault out due to SATA issues.

# Kernel panic with IOPCIFamily on X99

For those running the X99 platform from Intel, delight go over the post-obit:

• The post-obit kernel patches are enabled:
  • AppleCpuPmCfgLock
  • AppleXcpmCfgLock
  • AppleXcpmExtraMsrs
• Y'all have the following SSDTs:
  • SSDT-UNC(if non, see Getting started with ACPI (opens new window) on creating said file)

# Stuck on or near IOConsoleUsers: gIOScreenLock.../gIOLockState (3...

This is right before the GPU is properly initialized, verify the following:

• GPU is UEFI capable(GTX 7XX/2013+)
• CSM is off in the BIOS
  • May need to be enabled on laptops
• Forcing PCIe 3.0 link speed
• Double check that ig-platform-id and device-id are valid if running an iGPU.
  • Desktop UHD 630'south may demand to apply 00009B3E instead
• Trying diverse WhateverGreen Fixes (opens new window)
  • -igfxmlr kick argument. This can as well manifest as a "Divide by Naught" error.
• Coffee Lake iGPU users may also need igfxonln=1 in 10.15.4 and newer

# Scrambled Screen on laptops

Enable CSM in your UEFI settings. This may appear every bit "Boot legacy ROMs" or other legacy setting.

# Black screen subsequently IOConsoleUsers: gIOScreenLock... on Navi

• Add together agdpmod=pikera to kicking args
• Switch between different display outputs
• Try running MacPro7,i SMBIOS with the boot-arg agdpmod=ignore

For MSI Navi users, yous'll need to utilize the patch mentioned here: Installer not working with 5700XT #901 (opens new window)

Specifically, add the following entry under Kernel -> Patch:

MSI Navi Patch

Notation: macOS 11, Big Sur no longer requires this patch for MSI Navi.

# Kernel Panic Cannot perform kext summary

More often than not seen every bit an issue surrounding the prelinked kernel, specifically that macOS is having a hard time interpreting the ones nosotros injected. Verify that:

• Your kexts are in the correct social club(master and then plugins, Lilu always before the plugins)
• Kexts with executables take them and plist only kexts don't(ie. USBmap.kext, XHCI-unspported.kext, etc does non contain an executable)
• Don't include multiple of the same kexts in your config.plist(ie. including multiple copies of VoodooInput from multiple kexts, nosotros recommend choosing the start kext in your config'due south array and disable the rest)

Note: this mistake may also look very similar to Kernel Panic on Invalid frame arrow

# Kernel Panic AppleIntelMCEReporter

With macOS Catalina, dual socket support is broken, and a fun fact well-nigh AMD firmware is that some boards volition actually report multiple socketed CPUs. To prepare this, add together AppleMCEReporterDisabler (opens new window) to both EFI/OC/Kexts and config.plist -> Kernel -> Add

# Kernel Panic AppleIntelCPUPowerManagement

This is likely due to faulty or outright missing NullCPUPowerManagement. To prepare the issue, remove NullCPUPowerManagement from Kernel -> Add and EFI/OC/Kexts then enable DummyPowerManagement under Kernel -> Emulate

• Note: On older Intel CPUs(ie. Penryn and older), information technology may be due to IRQ conflicts or the HPET device beingness disabled. To resolve, you have 2 options:
  • SSDTTime'southward FixHPET Option (opens new window)
  • Forcing the HPET Device on

Forcing the HPET Device on

Under ACPI -> Patch:

Annotate	String	Force HPET Online
Enabled	Boolean	YES
Count	Number	0
Limit	Number	0
Detect	Data	A010934F53464C00
Replace	Data	A40A0FA3A3A3A3A3

# Kernel Panic AppleACPIPlatform in ten.13

On macOS ten.13, High Sierra the Bone is much stricter with ACPI tables, specifically a issues with how headers were handled (opens new window) . To resolve, enable NormalizeHeaders under ACPI -> Quirks in your config.plist

# macOS frozen right before login

This is a common example of screwed up TSC, for most organization add CpuTscSync (opens new window)

The nearly common way to come across the TSC outcome:

Example 1	Case two

# Keyboard works but trackpad does not

Make sure that VoodooInput is listed before VoodooPS2 and VoodooI2C kexts in your config.plist.

VoodooI2C Troubleshooting

Check the guild that your kexts load - make they friction match what is shown under Gathering Files:

1. VoodooGPIO, VoodooInput, and VoodooI2CServices in whatsoever order (Found under VoodooI2C.kext/Contents/PlugIns)
2. VoodooI2C
3. Satellite/Plugin Kext

Make certain yous have SSDT-GPIO in EFI/OC/ACPI and in your config.plist nether ACPI -> Add in your config.plist. If you are even so having problems, reference the Getting Started With ACPI GPIO page (opens new window) .

# kextd stall[0]: AppleACPICPU

This is due to either a missing SMC emulator or broken one, make sure of the following:

• Lilu and VirtualSMC are both in EFI/OC/kexts and in your config.plist
• Lilu is before VirtualSMC in the kext listing
• Concluding resort is to attempt FakeSMC instead, exercise not have both VirtualSMC and FakeSMC enabled

# Kernel Panic on AppleIntelI210Ethernet

For those running Comet lake motherboards with the I225-V NIC, you lot may feel a kernel panic on boot due to the I210 kext. To resolve this, brand sure you have the correct PciRoot for your Ethernet. This commonly existence either:

• PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0, 0x0)
  • By default, this is what Asus and Gigabyte motherboards use
• PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)
  • Some OEMs may utilize this instead

For those who can to your PciRoot manually, y'all'll want to install macOS fully and run the following with gfxutil (opens new window) :

This should spit out something like this:

The catastrophe PciRoot(0x0)/Pci(0x1F,0x6) is what you want to add in your config.plist with device-id of F2150000

# Kernel panic on "Incorrect CD Clock Frequency" with Icelake laptop

To resolve this kernel panic, ensure you have -igfxcdc in your kick-args.

# Kernel panic on "cckprng_int_gen"

Full panic:

This is likely to be i of two things:

• Missing SMC Emulator(ie. no VirtualSMC in your config.plist or EFI)
  • Add VirtualSMC.kext (opens new window) to your config.plist and EFI
• Incorrect SSDT usage with SSDT-CPUR

For the latter, ensure yous're just using SSDT-CPUR with B550 and A520. Do non utilize on X570 or older hardware(ie. B450 or A320)

# Stuck at Forcing CS_RUNTIME for entitlement in Big Sur

This is really the part at where macOS will seal the system volume, and where information technology may seem that macOS has gotten stuck. Do NOT RESTART thinking you lot're stuck, this will have quite some time to complete.

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

If y'all get stuck around the ramrod section (specifically, information technology boots, hits this error, and reboots once more dorsum into this, causing a loop), this hints that your SMC emulator is broken. To fix this, you accept 2 options:

• Ensure y'all're using the latest builds of VirtualSMC and Lilu, with the vsmcgen=1 kick-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 volition crusade a disharmonize.

# Virtual Machine Issues

• VMWare 15 is known to become stuck on [EB|#LOG:EXITBS:Commencement]. VMWare 16 resolves the problem.

# Reboot on "AppleUSBHostPort::createDevice: failed to create device" on macOS xi.three+

This is due to XhciPortLimit breaking with macOS 11.3 and newer (opens new window) , to resolve you must disable XhciPortLimit under Kernel -> Quirks. Please ensure yous've mapped your USB ports correctly (opens new window) before doing so.

• Alternatively, you lot can boot macOS 11.two.3 or older to resolve
  • For educational purposes, we've provided some images:
    • macOS 11.2.3 InstallAssistant(macOS) (opens new window)

nortoncoudes.blogspot.com

Source: https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html

Share this post