Filtrete 16x25x1 How To Install

Donation with Paypal https://tinyurl.com/r7fchn9

Donation with Binance0xdbe48ef6b158f1dd0035d7f49555c99e52f72714

Donation with Stripe https://tinyurl.com/2ssnydn6

Donation with BuyMeaCoffee https://tinyurl.com/bvsbpf6e

Donation with BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3

Donation with PicPay @danielnmaldonado

Donation with PiX @[e-mail protected]

Donation with Mercado Livre https://tinyurl.com/y9evkj5u

- Video Tutorial OpenCore Vanilla Guide -

https://tinyurl.com/yyfa7mfa

- OpenCore Premade EFI Folders - (*Just paste EFI folder into EFI division and offset a fine melody*)

https://tinyurl.com/ybr968w3

- Useful Links -
https://tinyurl.com/43t5m6d4

Let'due south start

1- Download Oc Vanilla and check video blare

https://www.olarila.com/topic/10371-oc-vanilla/

Root configuration entries consist of the following:
• ACPI
• Booter
• DeviceProperties

• Kernel
• Misc
• NVRAM
• PlatformInfo
• UEFI

Oc Manual generated in Docs binder

two- Now we need a proficient plist editor, my suggestion is Clover.app.

a- Download Clover.app
https://tinyurl.com/ydbyczzn

b- Download PlistEdit Pro
https://www.fatcatsoftware.com/plisteditpro/

c- Download OpenCore Configurator by mackie100 (utilize concluding version always to avoid some bugs)
https://tinyurl.com/ybdqc4cz

3- Open your config.plist with Clover.app

a- Delete Alert entries and salve

4- Now let's check a skilful config for our hardware

a- Open up OpenCore Configurator and go to Tools carte,  Config Checker

b- Select your CPU

c- Select OpenCore Version

d- Select "Import", "Choose"

e- Load your config.plist and beginning "Check" what y'all need

f- Open your config.plist with OpenCore Configurator(is a easy manner. Your can edit with Clover app or any other editor)

5- Applying correct config for your hardware in all tabs, bellow is case with Booter Quirks

6- Boot Arguments

a- Go to NVRAM tab

*** Some Variables ***

– acpi_layer=0xFFFFFFFF
– acpi_level=0xFFFF5F (implies ACPI_ALL_COMPONENTS)
– batman=VALUE (AppleSmartBatteryManager debug mask)
– batman-nosmc=1 (disable AppleSmartBatteryManager SMC interface)
– cpus=VALUE (maximum number of CPUs used)
– debug=VALUE (debug mask)
– io=VALUE (IOKit debug mask)
– keepsyms=1 (show panic log debug symbols)
– kextlog=VALUE (kernel extension loading debug mask)
– nv_disable=one (disables NVIDIA GPU dispatch)
– nvda_drv=1 (legacy mode to enable NVIDIA spider web driver, removed in 10.12)
– npci=0x2000 (legacy, disables kIOPCIConfiguratorPFM64)
– lapic_dont_panic=1
– slide=VALUE (manually ready KASLR slide)
– smcdebug=VALUE (AppleSMC debug mask)
– -amd_no_dgpu_accel (alternative to WhateverGreen'due south -radvesa for new GPUs)
– -no_compat_check (disable model checking)
– -southward (single mode)
– -v (verbose mode)
– -x (safe mode)

7- ACPI

a- Copy .aml to OC/ACPI folder

b- Add entry in config.plist ACPI tab

*** Easy mode to kicking ***

Copy SSDT-OLA.aml to OC/ACPI folder

SSDT-OLA.aml.zip

Add and enable RTC _STA patch fix in config.plist

8- Generating SMBIOS

a- Go to PlatformInfo tab and generate

9- Kernel Extensions(Kexts)

a- Knowing your hardware

-Download Hackintool
https://tinyurl.com/yamzbgd6

Become to PCIe tab and Update PCIIDs. Everything you lot need to know about your hardware!

*** Instance / Removing unused kexts ***

My Lan carte is Intel

I can remove some unused kexts about Lan in OC/Kexts Folder, my Lan card employ IntelMausi.kext

Other unused kexts is removed

AMDRyzenCPUPowerManagement.kext / for AMD Processors
SMCAMDProcessor.kext / monitoring of AMD processors
SMCBatteryManager.kext / Battery Plugin for Mobiles

At present looks skillful for my hardware

b- Add kexts entries in config.plist

Go to Kernel/Add tab and Browse

Select Kexts and Open

Done

10- Drivers

a- Go to OC/Drivers and use only necessary drivers ( HfsPlus.efi , OpenCanopy.efi and OpenRuntime.efi )

b- Add entries drivers config.plist UEFI/Drivers tab and Browse

 c- Select Drivers in your OpenCore EFI folder and Open up

Done

11- Audio Solution

https://tinyurl.com/y8nnbsap

a- Check your sound codec and layout-ids in tutorial to a higher place and add in NVRAM tab

12- Mobile Video Solution

https://tinyurl.com/y954utg3

a- Apply video patch in your config.plist, use i good .txt app, utilize TextMate

https://tinyurl.com/y9vpmefc

b- Open config.plist with TextMate and add video patch, DevicesProperties/Add

Now we accept a EFI OpenCore with good, clean and correct config. Permit's go to fine tune!

13- Fine Tune DSDT - SSDT

-DSDT (Full SOLUTION)
DSDT (Differentiated System Clarification Tabular array) is a part of the ACPI specification. Information technology supplies data most supported power events in a given arrangement. ACPI tables are provided in firmware from the manufacturer. A common MacOS problem is missing ACPI functionality, such as: fans not running, screens non turning off when the lid is closed, shutdown, kick fast without any ACPI error or warnings, sata, usb, firewire conflicts, etc.

-SSDT (Non FULL SOLUTION)
SSDT (Secondary System Descriptor Tabular array) It acts as a supplement to the DSDT.

To start this section we need check some things in real Mac tables and tables from 1 non-apple tree in same chipset and processor, in this case let'due south cheque Chipset Serie 300 with Coffelake Processor i9 9900k

Real Mac iMac19,1 tables, Chipset Serie 300 (8816 lines)

DSDT.Real iMac CoffeLake serie 300.nil

Mobo Chipset Serie 300 non-apple (59775 lines)

DSDT.Mobo serie 300.zip

The conclusion is: Apple apply a very custom DSDT, no unused devices, no trash is establish there. On our motherboard things are dissimilar, we have more than 50 thousand lines of a lot of garbage and devices for windows and non for MacOS.

Allow'south bank check one perfect hack with my Dell with Intel(R) Core(TM) i7-10510U and OpenCore Bootloader and Total DSDT Patched

Work similar 1 Existent Mac!

-Olarila common patches for one perfect Hackintosh-

--DSDT Patches--

-FIX ERRORS AND WARNINGS

-FIX ACPI ERRORS

-REMOVE UNUSED SCOPES / DEVICES

-HIGH PRECISION EVENT TIMER

-SATA SERIE ID

-DMAC

-REMOVE LINES, PROBLEMATIC and UNUSED

-FIX 1000.P in REBOOT

-NVRAM

-REAL TIME CLOCK

-SLPB

-DARWIN / WINDOWS 2022

-XHCI

-PLUGIN Type

-HDAS to HDEF

-HDEF

-ARTC

-IPIC

-TIMR

-SBUS

-BUS1

-MCHC

-ALS0

-SHUTDOWN

-UAR1

-LAN

-FWHD

-USBX

-PMCR

-PPMC

-XSPI

-GMM

-IMEI

-EC

-PNLF

-ARPT

-GFX0

-NVME

-DTGP

-ACQUIRE MUT0 0XFFFF

-OPERATION REGION GPIO

-MUTEX MUT0 0x00

-EXTERNAL REFERENCES

-UNKNOWNOBJ

-HDMI / HDAU

-Full RENAMED DEVICES

a- If you lot demand a full solution with one full DSDT patched, extract one SendMe with OpenCore running with this app and post here or in DSDT Patch Requests topic, check video showtime for extract with ioreg

Run_Me.app
https://tinyurl.com/y9562hz7

Video Tutorial

https://tinyurl.com/y74onhto

b- Paste DSDT.aml in OC/ACPI binder

c- Add entry in config.plist, reboot and done

d- If you like a SSDT style use SSDT Olarila with Bones patches for 1 good hack (Skylake+ but)

SSDT-OLARILA.aml.zip

14- AMD Processors with Vanilla patches

Download Patches from Github

https://github.com/AMD-OSX/AMD_Vanilla

*** 15h and 16h / Bulldozer / FX Series / Jaguar / A Series (including AM4 A-Series) ***

*** 17h / Ryzen, Threadripper, Athlon 2xxGE

a- Open 17h folder

b- Open patches.plist with TextMate.app and re-create all patches

c- Open your config.plistand paste all patches in Kernel/Patche tab and save

15-  FakeCPUID with OpenCore

a- Open your config.plist

b- Go to Kernel tab and add together properties

Instance
Haswell-East (0x0306F2) to Haswell ( 0 x 03 06 C3 )
Cpuid1Data: C3 06 03 00 00 00 00 00 00 00 00 00 00 00 00 00
Cpuid1Mask: FF FF FF FF 00 00 00 00 00 00 00 00 00 00 00 00

16- Theme OpenCore

a- Download OcBinaryData
https://tinyurl.com/y899xbde

b- Copy Resources folder to your OpenCore Folder

c- Open your config.plist, Get to Misc tab and fix Picker Way to External

17- Copying EFI folder to EFI Sectionalization

a- Download ESP Mounter Pro and install this app

https://tinyurl.com/y7q4z4lg

b- Mount EFI partition

c- Paste your EFI folder there

d- Reboot and Enjoy!

*** Some explanations about OpenCore ***

a- Drivers

-AudioDxe

HDA sound support driver in UEFI firmwares for most Intel and another analog sound controllers. Staging commuter, refer to acidanthera/bugtracker#740 for known issues in AudioDxe.

-CrScreenshotDxe
Screenshot making driver saving images to the root of OpenCore sectionalization (ESP) or any avail- able writeable filesystem upon pressing F10. This is a modified version of CrScreenshotDxe driver by Nikolaj Schlej.

-ExFatDxe
Proprietary ExFAT file system driver for Bootcamp support commonly found in Apple firmwares. For Sandy Span and earlier CPUs ExFatDxeLegacy driver should be used due to the lack of RDRAND instruction back up.

-HfsPlus
Proprietary HFS file organisation driver with bless back up commonly found in Apple firmwares. For Sandy Bridge and earlier CPUs HfsPlusLegacy driver should be used due to the lack of RDRAND educational activity support.

-HiiDatabase
HII services support driver from MdeModulePkg. This driver is included in most firmwares starting with Ivy Bridge generation. Some applications with the GUI like UEFI Shell may need this commuter to piece of work properly.

-EnhancedFatDxe
Fat filesystem driver from FatPkg. This commuter is embedded in all UEFI firmwares, and cannot be used from OpenCore. Information technology is known that multiple firmwares accept a bug in their Fatty back up implementation, which leads to corrupted filesystems on write attempt. Embedding this driver inside the firmware may be required in case writing to EFI division is needed during the kick process.

-NvmExpressDxe
NVMe support driver from MdeModulePkg. This driver is included in almost firmwares starting with Broadwell generation. For Haswell and earlier embedding it within the firmware may be more favourable in case a NVMe SSD bulldoze is installed.

-OpenCanopy
OpenCore plugin implementing graphical interface.

-OpenRuntime
OpenCore plugin implementing OC_FIRMWARE_RUNTIME protocol.

-OpenUsbKbDxe
USB keyboard driver adding the support of AppleKeyMapAggregator protocols on meridian of a custom USB keyboard driver implementation. This is an alternative to builtin KeySupport, which may work better or worse depending on the firmware.

-PartitionDxe
Proprietary partition management driver with Apple Partitioning Scheme support commonly institute in Apple tree firmwares. This commuter tin exist used to support loading older DMG recoveries such as macOS 10.9 using Apple Partitioning Scheme. For Sandy Bridge and earlier CPUs PartitionDxeLegacy driver should be used due to the lack of RDRAND education support.

-Ps2KeyboardDxe
PS/2 keyboard driver from MdeModulePkg. OpenDuetPkg and some firmwares may not include this driver, merely it is necessary for PS/ii keyboard to work. Note, unlike OpenUsbKbDxe this commuter has no AppleKeyMapAggregator support and thus requires KeySupport to be enabled.

-Ps2MouseDxe
PS/two mouse commuter from MdeModulePkg. Some very old laptop firmwares may not include this driver, just it is necessary for touchpad to work in UEFI graphical interfaces, such as OpenCanopy.

-UsbMouseDxe
USB mouse driver from MdeModulePkg. Some virtual machine firmwares like OVMF may not include this commuter, merely it is necessary for mouse to piece of work in UEFI graphical interfaces, such as OpenCanopy.

-VBoxHfs
HFS file system commuter with bless support. This driver is an alternative to a closed source HfsPlus driver commonly establish in Apple tree firmwares. While it is feature complete, information technology is approximately 3 times slower and is notwithstanding to undergo a security inspect.

-XhciDxe
XHCI USB controller support driver from MdeModulePkg. This driver is included in most firmwares starting with Sandy Bridge generation. For earlier firmwares or legacy systems information technology may be used to support external USB 3.0 PCI cards.

b- Booter Quirks Properties

one. AvoidRuntimeDefrag
Description: Protect from kick.efi runtime memory defragmentation.
This option fixes UEFI runtime services (engagement, time, NVRAM, ability command, etc.) support on many firmwares using SMM backing for select services like variable storage. SMM may effort to access physical addresses, simply they get moved past kicking.efi.
Note: Most but Apple and VMware firmwares demand this quirk.

ii. DevirtualiseMmio
Description: Remove runtime attribute from select MMIO regions.
This option reduces stolen memory footprint from the retention map by removing runtime flake for known memory regions. This quirk may result in the increase of KASLR slides available, just is not necessarily compatible with the target board without additional measures. In full general this frees from 64 to 256 megabytes of memory (present in the debug log), and on some platforms it is the only way to boot macOS, which otherwise fails with allocation error at bootloader stage.
This option is more often than not useful on all firmwares except some very old ones, similar Sandy Span. On select firmwares information technology may crave a list of exceptional addresses that still need to get their virtual addresses for proper NVRAM and hibernation functioning. Use MmioWhitelist department to practise this.

3. DisableSingleUser
Description: Disable single user mode.
This is a security option allowing i to restrict single user way usage by ignoring CMD+S hotkey and -due south kick argument. The behaviour with this quirk enabled is supposed to match T2-based model behaviour. Read this article to understand how to use single user mode with this quirk enabled.

4. DisableVariableWrite
Description: Protect from macOS NVRAM write access.
This is a security option allowing one to restrict NVRAM admission in macOS. This quirk requires OC_FIRMWARE_RUNTIME protocol implemented in OpenRuntime.efi.
Note: This quirk can too exist used as an ugly workaround to buggy UEFI runtime services implementations that fail to write variables to NVRAM and break the residuum of the operating system.
17

5. DiscardHibernateMap
Description: Reuse original hibernate memory map.
This option forces XNU kernel to ignore newly supplied memory map and assume that it did not change later waking from hibernation. This behaviour is required to work past Windows, which mandates to preserve runtime memory size and location after S4 wake.
Note: This may be used to workaround buggy memory maps on older hardware, and is at present considered rare legacy. Examples of such hardware are Ivy Bridge laptops with Insyde firmware, like Acer V3-571G. Exercise not employ this unless you fully understand the consequences.

6. EnableSafeModeSlide
Description: Patch bootloader to have KASLR enabled in safety mode.
This option is relevant to the users that have issues booting to safe way (e.g. by holding shift or using -ten boot argument). Past default safe mode forces 0 slide as if the arrangement was launched with slide=0 kicking statement. This quirk tries to patch boot.efi to elevator that limitation and allow some other value (from one to 255) be used. This quirk requires ProvideCustomSlide to be enabled.
Annotation: The necessity of this quirk is determined by safe mode availability. If booting to safe mode fails, this option tin exist tried to exist enabled.

7. EnableWriteUnprotector
Clarification: Permit write access to UEFI runtime services code.
This option bypasses RX permissions in lawmaking pages of UEFI runtime services by removing write protection (WP)
flake from CR0 register during their execution. This quirk requires OC_FIRMWARE_RUNTIME protocol implemented in OpenRuntime.efi.
Note: This quirk may potentially weaken firmware security, please use RebuildAppleMemoryMap if your firmware supports retentiveness attributes table (MAT).

8. ForceExitBootServices
Description: Retry ExitBootServices with new memory map on failure.
Try to ensure that ExitBootServices phone call succeeds even with outdated MemoryMap cardinal argument by obtaining current memory map and retrying ExitBootServices phone call.
Note: The necessity of this quirk is adamant past early on boot crashes of the firmware. Do not use this unless you lot fully empathise the consequences.

nine. ProtectMemoryRegions
Description: Protect retention regions from incorrect access.
Some firmwares incorrectly map select retentivity regions:
• CSM region can be marked every bit kick services lawmaking or data, which leaves it as free retention for XNU kernel. • MMIO regions tin can exist marked every bit reserved memory and stay unmapped, but may be required to be accessible
at runtime for NVRAM support.
This quirk attempts to prepare types of these regions, e.g. ACPI NVS for CSM or MMIO for MMIO.
Note: The necessity of this quirk is determined by artifacts, sleep wake bug, and kick failures. In full general only very old firmwares need this quirk.

10. ProtectSecureBoot
Clarification: Protect UEFI Secure Kicking variables from being written.
Reports security violation during attempts to write to db, dbx, PK, and KEK variables from the operating arrangement. Note: This quirk mainly attempts to avert issues with NVRAM implementations with problematic defragmentation,
such as select Insyde or MacPro5,1.

11. ProtectUefiServices
Clarification: Protect UEFI services from being overridden by the firmware.
Some mod firmwares including both hardware and virtual machines, like VMware, may update pointers to UEFI services during driver loading and related actions. Consequentially this directly breaks other quirks that touch memory management, like DevirtualiseMmio, ProtectMemoryRegions, or RebuildAppleMemoryMap, and may also break other quirks depending on the furnishings of these.
Note: On VMware the need for this quirk may be diagnosed by "Your Mac OS guest might run unreliably with more than one virtual core." message.

12. ProvideCustomSlide
Clarification: Provide custom KASLR slide on low retentiveness.
This option performs retentivity map analysis of your firmware and checks whether all slides (from ane to 255) can be used. Every bit boot.efi generates this value randomly with rdrand or pseudo randomly rdtsc, there is a gamble of boot failure when information technology chooses a conflicting slide. In case potential conflicts exist, this option forces macOS to utilize a pseudo random value among the available ones. This also ensures that slide= argument is never passed to the operating system for security reasons.
Annotation: The necessity of this quirk is determined by OCABC: But N/256 slide values are usable! message in the debug log. If the message is present, this pick is to be enabled.

13. RebuildAppleMemoryMap
Description: Generate Retentiveness Map compatible with macOS.
Apple kernel has several limitations in parsing UEFI memory map:
• Retention map size must not exceed 4096 bytes as Apple tree kernel maps it equally a single 4K folio. Since some firmwares have very large memory maps (approximately over 100 entries) Apple kernel will crash at boot.
• Memory attributes table is ignored. EfiRuntimeServicesCode memory statically gets RX permissions, and all other memory types get RW permissions. Since some firmware drivers may write to global variables at runtime, Apple kernel will crash at calling UEFI runtime services, unless driver .data section has EfiRuntimeServicesData type.
To workaround these limitations this quirk applies memory attributes table permissions to retentivity map passed to Apple kernel and optionally attempts to unify contiguous slots of similar types if the resulting memory map exceeds 4 KB.
Note 1: Since many firmwares come with incorrect memory protection table this quirk often comes in pair with SyncRuntimePermissions.
Note 2 : The necessity of this quirk is determined by early boot failures. This quirk replaces EnableWriteUnprotector on firmwares supporting memory attributes tabular array (MAT).

14. SetupVirtualMap
Description: Setup virtual retentivity at SetVirtualAddresses.
Select firmwares access retentivity by virtual addresses later on SetVirtualAddresses call, which results in early kick crashes. This quirk workarounds the trouble by performing early boot identity mapping of assigned virtual addresses to physical retention.
Annotation: The necessity of this quirk is adamant by early boot failures. Currently new firmwares with memory protection support (like OVMF) do not support this quirk due to acidanthera/bugtracker#719.

xv. SignalAppleOS
Description: Report macOS being loaded through OS Info for whatever OS.
This quirk is useful on Mac firmwares, which behave differently in different OS. For instance, information technology is supposed to enable Intel GPU in Windows and Linux in some dual-GPU MacBook models.

16. SyncRuntimePermissions
Description: Update retention permissions for runtime environment.
Some firmwares either fail to properly handle runtime permissions:
• They incorrectly mark OpenRuntime as non executable in the memory map.
• They incorrectly marking OpenRuntime as not executable in the memory attributes table. • They lose entries from the memory attributes table after OpenRuntime is loaded.
• They marker items in the retention attributes tabular array as read-write-execute.
This quirk tries to update memory map and retention attributes tabular array to correct this.
Notation: The necessity of this quirk is determined past early boot failures either in macOS or in Linux/Windows. In general merely firmwares released in 2022 or subsequently are affected.

c- Kernel Quirks Properties

ane. AppleCpuPmCfgLock
Description: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in AppleIntelCPUPowerManage- ment.kext, commonly causing early on kernel panic, when it is locked from writing.
Certain firmwares lock PKG_CST_CONFIG_CONTROL MSR register. To check its state one can use bundled VerifyMsrE2 tool. Select firmwares have this register locked on some cores only.
As mod firmwares provide CFG Lock setting, which allows configuring PKG_CST_CONFIG_CONTROL MSR register lock, this choice should be avoided whenever possible. For several APTIO firmwares non displaying CFG Lock setting in the GUI it is possible to access the selection direct:
(a) Download UEFITool and IFR-Extractor.
(b) Open your firmware image in UEFITool and find CFG Lock unicode string. If it is not present, your firmware
may not have this option and you lot should finish.
(c) Extract the Setup.bin PE32 Prototype Section (the i UEFITool constitute) through Extract Torso carte option.
(d) Run IFR-Extractor on the extracted file (due east.g. ./ifrextract Setup.bin Setup.txt).
(e) Find CFG Lock, VarStoreInfo (VarOffset/VarName): in Setup.txt and remember the commencement right afterward
it (eastward.chiliad. 0x123).
(f) Download and run Modified GRUB Beat out compiled by brainsucker or utilise a newer version by datasone.
(thou) Enter setup_var 0x123 0x00 command, where 0x123 should exist replaced by your actual first, and reboot.
Alarm: Variable offsets are unique not only to each motherboard but even to its firmware version. Never
ever try to use an offset without checking.

2. AppleXcpmCfgLock
Clarification: Disables PKG_CST_CONFIG_CONTROL (0xE2) MSR modification in XNU kernel, commonly causing early on kernel panic, when it is locked from writing (XCPM ability management).
Notation: This option should be avoided whenever possible. See AppleCpuPmCfgLock description for more than details.

3. AppleXcpmExtraMsrs
Description: Disables multiple MSR access disquisitional for select CPUs, which have no native XCPM support.
This is normally used in conjunction with Emulate section on Haswell-E, Broadwell-E, Skylake-SP, and like CPUs. More details on the XCPM patches are outlined in acidanthera/bugtracker#365.
Note: Additional not provided patches will be required for Ivy Bridge or Pentium CPUs. It is recommended to use AppleIntelCpuPowerManagement.kext for the former.

four. AppleXcpmForceBoost
Description: Forces maximum operation in XCPM fashion.
This patch writes 0xFF00 to MSR_IA32_PERF_CONTROL (0x199), effectively setting maximum multiplier for all the time.
Annotation: While this may increase the performance, this patch is strongly discouraged on all systems simply those explicitly dedicated to scientific or media calculations. In general only certain Xeon models do good from the patch.

5. CustomSMBIOSGuid
Description: Performs GUID patching for UpdateSMBIOSMode Custom style. Normally relevant for Dell laptops.

half-dozen. DisableIoMapper
Clarification: Disables IOMapper back up in XNU (VT-d), which may conflict with the firmware implementation.
Notation: This option is a preferred culling to deleting DMAR ACPI tabular array and disabling VT-d in firmware preferences, which does not break VT-d support in other systems in case they need information technology.

7. DisableRtcChecksum
Type: plist boolean
Failsafe: false
Description: Disables primary checksum (0x58-0x59) writing in AppleRTC.
Note 1: This option volition not protect other areas from being overwritten, see RTCMemoryFixup kernel extension if this is desired.
Note two: This option will non protect areas from being overwritten at firmware stage (e.g. macOS bootloader), see AppleRtc protocol description if this is desired.

8. DummyPowerManagement
Description: Disables AppleIntelCpuPowerManagement.
Note: This option is a preferred culling to NullCpuPowerManagement.kext for CPUs without native power management driver in macOS.

9. ExternalDiskIcons
Description: Use icon type patches to AppleAHCIPort.kext to force internal deejay icons for all AHCI disks.
Notation: This option should be avoided whenever possible. Modern firmwares unremarkably have compatible AHCI controllers.

10. IncreasePciBarSize
Description: Increases 32-bit PCI bar size in IOPCIFamily from ane to 4 GBs.
Note: This option should exist avoided whenever possible. In general the necessity of this pick ways misconfigured or broken firmware.

xi. LapicKernelPanic
Description: Disables kernel panic on LAPIC interrupts.

12. PanicNoKextDump
Description: Prevent kernel from printing kext dump in the panic log preventing from observing panic details. Affects 10.xiii and above.

13. PowerTimeoutKernelPanic
Description: Disables kernel panic on setPowerState timeout.
An additional security measure was added to macOS Catalina (10.15) causing kernel panic on ability change timeout for Apple drivers. Sometimes it may cause issues on misconfigured hardware, notably digital sound, which
sometimes fails to wake upward. For debug kernels setpowerstate_panic=0 kick argument should be used, which is otherwise equivalent to this quirk.

14. ThirdPartyDrives
Description: Apply vendor patches to IOAHCIBlockStorage.kext to enable native features for tertiary-party drives, such as TRIM on SSDs or hibernation back up on 10.15 and newer.
Note: This choice may be avoided on user preference. NVMe SSDs are uniform without the change. For AHCI SSDs on modern macOS version in that location is a dedicated congenital-in utility called trimforce. Starting from 10.15 this utility creates EnableTRIM variable in APPLE_BOOT_VARIABLE_GUID namespace with 01 00 00 00 value.

15. XhciPortLimit
Description: Patch various kexts (AppleUSBXHCI.kext, AppleUSBXHCIPCI.kext, IOUSBHostFamily.kext) to remove USB port count limit of fifteen ports.
Note: This option should be avoided whenever possible. USB port limit is imposed past the corporeality of used bits in locationID format and in that location is no possible way to workaround this without heavy Os modification. The only valid solution is to limit the amount of used ports to 15 (discarding some).

-Credits

• The HermitCrabs Lab
• All projects providing third-political party lawmaking (refer to file headers)
• AppleLife  team and user-contributed resource
• Chameleon and Clover teams for hints and legacy
• al3xtjames
• Andrey1970AppleLife
• Download-Fritz
• Goldfish64
• nms42
• PMHeart
• savvamitrofanov
• vit9696

Piece, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Squad, Pike R. Blastoff, lvs1974, Austere.J, CVad, headkaze, onemanosx, erroruser, Jenny David, Sampath007, Facebook Hackintosh community, Facebook Olarila customs and many, many, many others!

We're all here to have fun and larn from each other!

Source: https://www.olarila.com/topic/8918-hackintosh-opencore-vanilla-guide-step-by-step-full-dsdt-patched-or-ssdt/

Posted by: coburnreamost.blogspot.com

Share this post