Ivy bridge mac os

Ivy bridge mac os

I like to start with either the stock config.plist that Clover gives you, or with just a blank canvas. In the next examples, I’ll show you how I set things up from scratch; if you start from somewhere else, you may have more things checked/set than I do — but you’ll want to follow along with what I do.

I’ll also include the raw xml examples too in order to show those that work with a text editor (as I prefer to).

The default Clover settings are pretty overdone and can cause some issues. We’ll keep this section fairly minimal, and I’ll go through a bit of why we do that for each part as well.

Clover Configurator Screenshots

The first thing we’ll go over is the Patches section. This section allows us to dynamically rename parts of the DSDT via Clover. Since we’re not running a real mac, and macOS is pretty particular with how things are named, we can make non-destructive changes to keep things mac-friendly. We have three entries here:

• change EHC1 to EH01 — helps avoid a conflict with built-in USB injectors
• change EHC2 to EH02 — helps avoid a conflict with built-in USB injectors
• change XHC1 to XHC — helps avoid a conflict with built-in USB injectors
• change XHCI to XHC — helps avoid a conflict with built-in USB injectors
• change SAT0 to SATA — for potential SATA compatibility

If we look then at the Fixes section, we’ll see that we have a few things checked (there are 2 pages, so I included 2 screenshots):

• FixShutdown — this can help with some boards that prefer to restart instead of shutdown. Sometimes it can cause shutdown issues on other boards (ironic, right?), so if you have issues shutting down with this enabled, look at disabling it.
• The remaining fixes help avoid IRQ conflicts and etc, and are not known to cause issues. They may not be necessary for all hardware, but do not negatively impact anything if applied.

Note: If you use an Ivy Bridge CPU with a 6-series motherboard, you will also need to enable AddDTGP and AddIMEI, and you will have to fake the IMEI to 0x1e3a8086 (I will go over this in the Devices section).

We touched in gently on DSDT with our Patches section — and this is a a bit of an extension of that. SSDT is like a sub-section of DSDT. The Drop Tables section allows us to omit certain SSDT tables from loading (as I mentioned before, mac and PC DSDT is different, and macOS can be rather picky). The two that I’ve added are as follows:

• CpuPm and Cpu0Ist — these drop tables related to CPU power management which allow us to supplement the data by generating an SSDT.aml via Pike’s ssdtPRGen.sh script.
• DMAR — this prevents some issues with Vt-d; which is PCI passthrough for VMs, and not very functional (if at all?) on Hackintoshes.
• MATS — with High Sierra on up this table is parsed, and can sometimes contain unprintable characters that can lead to a kernel panic.

FixHeaders and Generate:

The only other things we’ve done on this page are enable these two checkboxes.

• FixHeaders — this is just a double-up of our MATS table dropping. This checkbox tells Clover to sanitize headers to avoid kernel panics related to unprintable characters.
• Generate — this is set to an empty dictionary (you can acheive the same by ticking any of the Generate options, then unticking them in CC) which prevents Clover from generating any C or P states, and also prevents it from adding PluginType (as that’s for Haswell and newer CPUs).

We don’t need to do too much here, but we’ll tweak a few things.

Источник

Первый тест Ivy Bridge в OS X

Владельцы компьютеров Mac снисходительно относятся к «хакинтошникам» — пользователям компьютеров PC-формата, работающих на модифицированной версии Mac OS. Правильный хакинтош нужно натурально собирать руками, и лишь в редких случаях установленная ОС сможет похвастаться стабильностью и полным отсутствием багов. Зато железо обходится заметно дешевле, и зачастую превосходит параметрами топовые конфигурации компьютеров из Купертино. Сегодня мир хакинтоша стал полезным и для сообщества маководов.

Энтузиасты раздобыли процессор Intel Core i7-3770K из новейшей серии чипов Ivy Bridge, которые уже очень скоро появятся во всех новых компьютерах Mac. i7-3770K является одним из топовых решений в линейке Ivy Bridge и имеет частоту в 3,5 гигагерц. Первые тесты производительности нового процессора были проведены в программе Geekbench на модифицированной версии OS X Lion 10.7.3. Полученный результат — 13453 очка. Процессор Core i7-2600, установленный в топовых iMac последних поколений, набрал 12452 очка. Разница производительности между ними составила меньше 10 процентов.

Кликабельно

Сама Intel обещает, что новые чипы Ivy Bridge будут быстрее, чем Sandy Bridge в среднем на 15 процентов. Есть ли смысл ждать обновления линеек Mac ради одних лишь новых процессоров? Если судить по результатам теста — нет. Гораздо более серьёзным подспорьем может стать улучшенный видеоускоритель внутри процессора — Intel HD4000, производительность которого превышает показатели нынешнего HD3000 на 55 процентов. Если добавить к этому слухи о скором прекращении выпуска 13- и 15-дюймовых MacBook Pro, получается, что сегодня лучше подождать с покупкой «прошки» и даже Air, ибо его обновление должно состояться уже в конце этой весны. [ap]

Источник

# Desktop Ivy Bridge

Support	Version
Initial macOS Support	OS X 10.7, Lion

# Starting Point

So making a config.plist may seem hard, it’s not. It just takes some time but this guide will tell you how to configure everything, you won’t be left in the cold. This also means if you have issues, review your config settings to make sure they’re correct. Main things to note with OpenCore:

• All properties must be defined, there are no default OpenCore will fall back on so do not delete sections unless told explicitly so. If the guide doesn’t mention the option, leave it at default.
• The Sample.plist cannot be used As-Is, you must configure it to your system
• DO NOT USE CONFIGURATORS, these rarely respect OpenCore’s configuration and even some like Mackie’s will add Clover properties and corrupt plists!

Now with all that, a quick reminder of the tools we need

And read this guide more than once before setting up OpenCore and make sure you have it set up correctly. Do note that images will not always be the most up-to-date so please read the text below them, if nothing’s mentioned then leave as default.

This is where you’ll add SSDTs for your system, these are very important to booting macOS and have many uses like USB maps

(opens new window) , disabling unsupported GPUs and such. And with our system, it’s even required to boot. Guide on making them found here: Getting started with ACPI

For us we’ll need a couple of SSDTs to bring back functionality that Clover provided:

Required SSDTs	Description
SSDT-PM (opens new window)	Needed for proper CPU power management, you will need to run Pike’s ssdtPRGen.sh script to generate this file. This will be run in post install (opens new window)	Fixes the embedded controller, see Getting Started With ACPI Guide (opens new window) for more details.
SSDT-IMEI (opens new window)	Needed to add a missing IMEI device on Ivy Bridge CPU with 6 series motherboards

Note that you should not add your generated DSDT.aml here, it is already in your firmware. So if present, remove the entry for it in your config.plist and under EFI/OC/ACPI.

For those wanting a deeper dive into dumping your DSDT, how to make these SSDTs, and compiling them, please see the Getting started with ACPI

(opens new window) page. Compiled SSDTs have a .aml extension(Assembled) and will go into the EFI/OC/ACPI folder and must be specified in your config under ACPI -> Add as well.

# Delete

This blocks certain ACPI tables from loading, for us we really care about this. Main reason is that Apple’s XCPM does not support IvyBridge all too well and can cause AppleIntelCPUPowerManagement panics on boot. To avoid this we make our own PM SSDT in Post-Install

(opens new window) and drop the old tables(Note that this is only temporary until we’ve made our SSDT-PM, we’ll re-enable these tables later):

Key	Type	Value
All	Boolean	YES
Comment	String	Delete CpuPm
Enabled	Boolean	YES
OemTableId	Data	437075506d000000
TableLength	Number	0
TableSignature	Data	53534454

Key	Type	Value
All	Boolean	YES
Comment	String	Delete Cpu0Ist
Enabled	Boolean	YES
OemTableId	Data	4370753049737400
TableLength	Number	0
TableSignature	Data	53534454

# Patch

This section allows us to dynamically modify parts of the ACPI (DSDT, SSDT, etc.) via OpenCore. For us, our patches are handled by our SSDTs. This is a much cleaner solution as this will allow us to boot Windows and other OSes with OpenCore

# Quirks

Settings relating to ACPI, leave everything here as default as we have no use for these quirks.

# Booter

This section is dedicated to quirks relating to boot.efi patching with OpenRuntime, the replacement for AptioMemoryFix.efi

# MmioWhitelist

This section is allowing spaces to be passthrough to macOS that are generally ignored, useful when paired with DevirtualiseMmio

# Quirks

Settings relating to boot.efi patching and firmware fixes, for us, we leave it as default

# DeviceProperties

Sets device properties from a map.

This section is set up via WhateverGreen’s Framebuffer Patching Guide

(opens new window) and is used for setting important iGPU properties.

The AAPL,ig-platform-id we use is as follows:

AAPL,ig-platform-id	Comment
0A006601	Used when the iGPU is used to drive a display
07006201	Used when the iGPU is only used for computing tasks and doesn’t drive a display

Key	Type	Value
AAPL,ig-platform-id	Data	0A006601

(This is an example for a desktop HD 4000 without a dGPU)

This is needed if you’re pairing an Ivy Bridge CPU with a 6 series motherboard(ie. H61, B65, Q65, P67, H67, Q67, Z68), specifically needed to spoof your IMEI device into being supported. Note this property is still required with or without SSDT-IMEI.

Key	Type	Value
device-id	Data	3A1E0000

Note: This is not needed if you have a 7 series motherboard(ie. B75, Q75, Z75, H77, Q77, Z77)

Applies AppleALC audio injection, you’ll need to do your own research on which codec your motherboard has and match it with AppleALC’s layout. AppleALC Supported Codecs

(opens new window) .

You can delete this property outright as it’s unused for us at this time

For us, we’ll be using the boot-arg alcid=xxx instead to accomplish this. alcid will override all other layout-IDs present. More info on this is covered in the Post-Install Page

# Delete

Removes device properties from the map, for us we can ignore this

# Kernel

Here’s where we specify which kexts to load, in what specific order to load, and what architectures each kext is meant for. By default we recommend leaving what ProperTree has done, however for 32-bit CPUs please see below:

More in-depth Info

The main thing you need to keep in mind is:

• Load order
  • Remember that any plugins should load after its dependencies
  • This means kexts like Lilu must come before VirtualSMC, AppleALC, WhateverGreen, etc

A reminder that ProperTree

(opens new window) users can run Cmd/Ctrl + Shift + R to add all their kexts in the correct order without manually typing each kext out.

• Arch
  • Architectures supported by this kext
  • Currently supported values are Any , i386 (32-bit), and x86_64 (64-bit)
• BundlePath
  • Name of the kext
  • ex: Lilu.kext
• Enabled
  • Self-explanatory, either enables or disables the kext
• ExecutablePath
  • Path to the actual executable is hidden within the kext, you can see what path your kext has by right-clicking and selecting Show Package Contents . Generally, they’ll be Contents/MacOS/Kext but some have kexts hidden within under Plugin folder. Do note that plist only kexts do not need this filled in.
  • ex: Contents/MacOS/Lilu
• MinKernel
  • Lowest kernel version your kext will be injected into, see below table for possible values
  • ex. 12.00.00 for OS X 10.8
• MaxKernel
  • Highest kernel version your kext will be injected into, see below table for possible values
  • ex. 11.99.99 for OS X 10.7
• PlistPath
  • Path to the info.plist hidden within the kext
  • ex: Contents/Info.plist

Kernel Support Table

OS X Version	MinKernel	MaxKernel
10.4	8.0.0	8.99.99
10.5	9.0.0	9.99.99
10.6	10.0.0	10.99.99
10.7	11.0.0	11.99.99
10.8	12.0.0	12.99.99
10.9	13.0.0	13.99.99
10.10	14.0.0	14.99.99
10.11	15.0.0	15.99.99
10.12	16.0.0	16.99.99
10.13	17.0.0	17.99.99
10.14	18.0.0	18.99.99
10.15	19.0.0	19.99.99
11	20.0.0	20.99.99

# Emulate

Needed for spoofing unsupported CPUs like Pentiums and Celerons

• Cpuid1Mask: Leave this blank
• Cpuid1Data: Leave this blank

# Force

Used for loading kexts off system volume, only relevant for older operating systems where certain kexts are not present in the cache(ie. IONetworkingFamily in 10.6).

For us, we can ignore.

# Block

Blocks certain kexts from loading. Not relevant for us.

# Patch

Patches both the kernel and kexts.

# Quirks

Settings relating to the kernel, for us we’ll be enabling the following:

Quirk	Enabled	Comment
AppleCpuPmCfgLock	YES	Not needed if CFG-Lock is disabled in the BIOS
DisableIoMapper	YES	Not needed if VT-D is disabled in the BIOS
LapicKernelPanic	NO	HP Machines will require this quirk
PanicNoKextDump	YES
PowerTimeoutKernelPanic	YES
XhciPortLimit	YES	Disable if running macOS 11.3+

(opens new window) We recommend users either disable this quirk and map before upgrading or map from Windows

(opens new window) . You may also install macOS 11.2.3 or older.

The reason being is that UsbInjectAll reimplements builtin macOS functionality without proper current tuning. It is much cleaner to just describe your ports in a single plist-only kext, which will not waste runtime memory and such

# Scheme

Settings related to legacy booting(ie. 10.4-10.6), for majority you can skip however for those planning to boot legacy OSes you can see below:

More in-depth Info

FuzzyMatch: True

• Used for ignoring checksums with kernelcache, instead opting for the latest cache available. Can help improve boot performance on many machines in 10.6

KernelArch: x86_64

• Set the kernel’s arch type, you can choose between Auto , i386 (32-bit), and x86_64 (64-bit).
• If you’re booting older OSes which require a 32-bit kernel(ie. 10.4 and 10.5) we recommend to set this to Auto and let macOS decide based on your SMBIOS. See below table for supported values:
  • 10.4-10.5 — x86_64 , i386 or i386-user32
    • i386-user32 refers 32-bit userspace, so 32-bit CPUs must use this(or CPUs missing SSSE3)
    • x86_64 will still have a 32-bit kernelspace however will ensure 64-bit userspace in 10.4/5
  • 10.6 — i386 , i386-user32 , or x86_64
  • 10.7 — i386 or x86_64
  • 10.8 or newer — x86_64

KernelCache: Auto

• Set kernel cache type, mainly useful for debugging and so we recommend Auto for best support

Settings for boot screen (Leave everything as default).

# Debug

Helpful for debugging OpenCore boot issues(We’ll be changing everything but DisplayDelay ):

Quirk	Enabled
AppleDebug	YES
ApplePanic	YES
DisableWatchDog	YES
Target	67

These values are based of those calculated in OpenCore debugging

# Security

Security is pretty self-explanatory, do not skip. We’ll be changing the following:

Quirk	Enabled	Comment
AllowNvramReset	YES
AllowSetDefault	YES
BlacklistAppleUpdate	YES
ScanPolicy	0
SecureBootModel	Default	This is a word and is case-sensitive, set to Disabled if you do not want secure boot(ie. you require Nvidia’s Web Drivers)
Vault	Optional	This is a word, it is not optional to omit this setting. You will regret it if you don’t set it to Optional, note that it is case-sensitive

AllowNvramReset: YES

• Allows for NVRAM reset both in the boot picker and when pressing Cmd+Opt+P+R

AllowSetDefault: YES

• Allow CTRL+Enter and CTRL+Index to set default boot device in the picker

ApECID: 0

• Used for netting personalized secure-boot identifiers, currently this quirk is unreliable due to a bug in the macOS installer so we highly encourage you to leave this as default.

AuthRestart: NO

• Enables Authenticated restart for FileVault 2 so password is not required on reboot. Can be considered a security risk so optional

BlacklistAppleUpdate: YES

• Used for blocking firmware updates, used as extra level of protection as macOS Big Sur no longer uses run-efi-updater variable

DmgLoading: Signed

• Ensures only signed DMGs load

ExposeSensitiveData: 6

• Shows more debug information, requires debug version of OpenCore

Vault: Optional

• We won’t be dealing vaulting so we can ignore, you won’t boot with this set to Secure
• This is a word, it is not optional to omit this setting. You will regret it if you don’t set it to Optional , note that it is case-sensitive

ScanPolicy: 0

0 allows you to see all drives available, please refer to Security

(opens new window) section for further details. Will not boot USB devices with this set to default

SecureBootModel: Disabled

Controls Apple’s secure boot functionality in macOS, please refer to Security

(opens new window) section for further details.

Note: Users may find upgrading OpenCore on an already installed system can result in early boot failures. To resolve this, see here: Stuck on OCB: LoadImage failed — Security Violation

# Tools

Used for running OC debugging tools like the shell, ProperTree’s snapshot function will add these for you.

# Entries

Used for specifying irregular boot paths that can’t be found naturally with OpenCore.

Won’t be covered here, see 8.6 of Configuration.pdf

# NVRAM

Used for OpenCore’s UI scaling, default will work for us. See in-depth section for more info

Booter Path, mainly used for UI Scaling

UIScale:

• 01 : Standard resolution
• 02 : HiDPI (generally required for FileVault to function correctly on smaller displays)

DefaultBackgroundColor: Background color used by boot.efi

• 00000000 : Syrah Black
• BFBFBF00 : Light Gray

OpenCore’s NVRAM GUID, mainly relevant for RTCMemoryFixup users

System Integrity Protection bitmask

• General Purpose boot-args:

boot-args	Description
-v	This enables verbose mode, which shows all the behind-the-scenes text that scrolls by as you’re booting instead of the Apple logo and progress bar. It’s invaluable to any Hackintosher, as it gives you an inside look at the boot process, and can help you identify issues, problem kexts, etc.
debug=0x100	This disables macOS’s watchdog which helps prevents a reboot on a kernel panic. That way you can hopefully glean some useful info and follow the breadcrumbs to get past the issues.
keepsyms=1	This is a companion setting to debug=0x100 that tells the OS to also print the symbols on a kernel panic. That can give some more helpful insight as to what’s causing the panic itself.
alcid=1	Used for setting layout-id for AppleALC, see supported codecs (opens new window) to figure out which layout to use for your specific system. More info on this is covered in the Post-Install Page (opens new window)

• GPU-Specific boot-args:

boot-args	Description
agdpmod=pikera	Used for disabling board ID checks on Navi GPUs(RX 5000 series), without this you’ll get a black screen. Don’t use if you don’t have Navi(ie. Polaris and Vega cards shouldn’t use this)
nvda_drv_vrl=1	Used for enabling Nvidia’s Web Drivers on Maxwell and Pascal cards in Sierra and High Sierra
-wegnoegpu	Used for disabling all other GPUs than the integrated Intel iGPU, useful for those wanting to run newer versions of macOS where their dGPU isn’t supported

csr-active-config: 00000000

• Settings for ‘System Integrity Protection’ (SIP). It is generally recommended to change this with csrutil via the recovery partition.
• csr-active-config by default is set to 00000000 which enables System Integrity Protection. You can choose a number of different values but overall we recommend keeping this enabled for best security practices. More info can be found in our troubleshooting page: Disabling SIP

run-efi-updater: No

• This is used to prevent Apple’s firmware update packages from installing and breaking boot order; this is important as these firmware updates (meant for Macs) will not work.

prev-lang:kbd: <>

• Needed for non-latin keyboards in the format of lang-COUNTRY:keyboard , recommended to keep blank though you can specify it(Default in Sample config is Russian):
• American: en-US:0 ( 656e2d55533a30 in HEX)
• Full list can be found in AppleKeyboardLayouts.txt

(opens new window)

• Hint: prev-lang:kbd can be changed into a String so you can input en-US:0 directly instead of converting to HEX

Key	Type	Value
prev-lang:kbd	String	en-US:0

# Delete

Forcibly rewrites NVRAM variables, do note that Add will not overwrite values already present in NVRAM so values like boot-args should be left alone. For us, we’ll be changing the following:

Quirk	Enabled
WriteFlash	YES

LegacyEnable: NO

• Allows for NVRAM to be stored on nvram.plist, needed for systems without native NVRAM

LegacyOverwrite: NO

• Permits overwriting firmware variables from nvram.plist, only needed for systems without native NVRAM

LegacySchema

• Used for assigning NVRAM variables, used with LegacyEnable set to YES

WriteFlash: YES

• Enables writing to flash memory for all added variables.

# PlatformInfo

For setting up the SMBIOS info, we’ll use CorpNewt’s GenSMBIOS

For this Ivy Bridge example, we’ll chose the iMac13,2 SMBIOS — this is done intentionally for compatibility’s sake. There are 3 main SMBIOS used for Ivy Bridge:

SMBIOS	Hardware
iMac13,1	Used for computers utilizing the iGPU for displaying
iMac13,2	Used for computers using a dGPU for displaying, and an iGPU for computing tasks only

Note: The following SMBIOS are only supported up-to and including macOS 10.15, Catalina. For cases where you must boot Big Sur, see below:

Big Sur SMBIOS table

Note choosing a SMBIOS from the list below for Catalina or older is not recommended, as Power Management and such can break when using unoptimized SMBIOS.

SMBIOS	Hardware
iMac14,4	Used for computers utilizing the iGPU for displaying
iMac15,1	Used for computers using a dGPU for displaying, and an iGPU for computing tasks only

Run GenSMBIOS, pick option 1 for downloading MacSerial and Option 3 for selecting out SMBIOS. This will give us an output similar to the following:

The Type part gets copied to Generic -> SystemProductName.

The Serial part gets copied to Generic -> SystemSerialNumber.

The Board Serial part gets copied to Generic -> MLB.

The SmUUID part gets copied to Generic -> SystemUUID.

We set Generic -> ROM to either an Apple ROM (dumped from a real Mac), your NIC MAC address, or any random MAC address (could be just 6 random bytes, for this guide we’ll use 11223300 0000 . After install follow the Fixing iServices

(opens new window) page on how to find your real MAC Address)

Reminder that you want either an invalid serial or valid serial numbers but those not in use, you want to get a message back like: «Invalid Serial» or «Purchase Date not Validated»

Automatic: YES

• Generates PlatformInfo based on Generic section instead of DataHub, NVRAM, and SMBIOS sections

# Generic

AdviseFeatures: NO

• Used for when the EFI partition isn’t first on the Windows drive

MaxBIOSVersion: NO

• Sets BIOS version to Max to avoid firmware updates in Big Sur+, mainly applicable for genuine Macs.

ProcessorType: 0

Set to 0 for automatic type detection, however this value can be overridden if desired. See AppleSmBios.h

SpoofVendor: YES

• Swaps vendor field for Acidanthera, generally not safe to use Apple as a vendor in most case

SystemMemoryStatus: Auto

• Sets whether memory is soldered or not in SMBIOS info, purely cosmetic and so we recommend Auto

UpdateDataHub: YES

• Update Data Hub fields

UpdateNVRAM: YES

UpdateSMBIOS: YES

UpdateSMBIOSMode: Create

• Replace the tables with newly allocated EfiReservedMemoryType, use Custom on Dell laptops requiring CustomSMBIOSGuid quirk
• Setting to Custom with CustomSMBIOSGuid quirk enabled can also disable SMBIOS injection into «non-Apple» OSes however we do not endorse this method as it breaks Bootcamp compatibility. Use at your own risk

ConnectDrivers: YES

• Forces .efi drivers, change to NO will automatically connect added UEFI drivers. This can make booting slightly faster, but not all drivers connect themselves. E.g. certain file system drivers may not load.

# Drivers

Add your .efi drivers here.

Only drivers present here should be:

Relating to APFS driver loader settings, for us we’ll be changing the following:

Setting	Value	Comment
MinDate	-1	Not needed if not booting High Sierra — Catalina
MinVersion	-1	Not needed if not booting High Sierra — Catalina

MinDate: -1

• Sets the minimum date required for APFS drivers to load. The default in OpenCore is 2021-01-01, which limits booting High Sierra — Catalina when you don’t have an APFS driver that satisifes the requirements (aka having Big Sur installed).
• If you’d like to boot High Sierra — Catalina, set this to -1 , otherwise you don’t need to change it

MinVersion: -1

• Sets the minimum version required for APFS drivers to load. The default in OpenCore is versions from Big Sur and above, which limits booting High Sierra — Catalina when you don’t have an APFS driver that satisifes the requirements (aka having Big Sur installed).
• If you’d like to boot High Sierra — Catalina, set this to -1 , otherwise you don’t need to change it

# Audio

Related to AudioDxe settings, for us we’ll be ignoring(leave as default). This is unrelated to audio support in macOS.

For further use of AudioDxe and the Audio section, please see the Post Install page: Add GUI and Boot-chime

# Input

Related to boot.efi keyboard passthrough used for FileVault and Hotkey support, leave everything here as default as we have no use for these quirks. See here for more details: Security and FileVault

# Output

Relating to OpenCore’s visual output, leave everything here as default as we have no use for these quirks.

# ProtocolOverrides

Mainly relevant for Virtual machines, legacy macs and FileVault users. See here for more details: Security and FileVault

# Quirks

Relating to quirks with the UEFI environment, for us we’ll be changing the following:

Quirk	Enabled	Comment
IgnoreInvalidFlexRatio	YES
UnblockFsConnect	NO	Needed mainly by HP motherboards

IgnoreInvalidFlexRatio: YES

• Fix for when MSR_FLEX_RATIO (0x194) can’t be disabled in the BIOS, required for all pre-Skylake based systems

DisableSecurityPolicy: NO

• Disables platform security policy in firmware, recommended for buggy firmwares where disabling Secure Boot does not allow 3rd party firmware drivers to load.
• If running a Microsoft Surface device, recommended to enable this option

RequestBootVarRouting: YES

• Redirects AptioMemoryFix from EFI_GLOBAL_VARIABLE_GUID to OC_VENDOR_VARIABLE_GUID . Needed for when firmware tries to delete boot entries and is recommended to be enabled on all systems for correct update installation, Startup Disk control panel functioning, etc.

UnblockFsConnect: NO

• Some firmware block partition handles by opening them in By Driver mode, which results in File System protocols being unable to install. Mainly relevant for HP systems when no drives are listed

# ReservedMemory

Used for exempting certain memory regions from OSes to use, mainly relevant for Sandy Bridge iGPUs or systems with faulty memory. Use of this quirk is not covered in this guide

# Cleaning up

And now you’re ready to save and place it into your EFI under EFI/OC.

For those having booting issues, please make sure to read the Troubleshooting section first and if your questions are still unanswered we have plenty of resources at your disposal:

# Intel BIOS settings

• Note: Most of these options may not be present in your firmware, we recommend matching up as closely as possible but don’t be too concerned if many of these options are not available in your BIOS

# Disable

• Fast Boot
• Secure Boot
• Serial/COM Port
• Parallel Port
• VT-d (can be enabled if you set DisableIoMapper to YES)
• CSM
• Thunderbolt(For initial install, as Thunderbolt can cause issues if not setup correctly)
• Intel SGX
• Intel Platform Trust
• CFG Lock (MSR 0xE2 write protection)(This must be off, if you can’t find the option then enable AppleCpuPmCfgLock under Kernel -> Quirks. Your hack will not boot with CFG-Lock enabled)

# Enable

• VT-x
• Above 4G decoding
• Hyper-Threading
• Execute Disable Bit
• EHCI/XHCI Hand-off
• OS type: Windows 8.1/10 UEFI Mode
• DVMT Pre-Allocated(iGPU Memory): 32MB
• SATA Mode: AHCI

# Now with all this done, head to the Installation Page

Источник