Within this file, search for OCCPU: EIST CFG Lock: This should provide you with a file in the format of opencore-YYYY-MM-DD-hhmmss.txt on the root of the drive. Use a tool called ControlMsrE2 which will speed up the whole checking processįor users who prefer using DEBUG release, you'll want to enable the DEBUG variant of OpenCore with Target set to 67 and boot OpenCore.Use the DEBUG version of OpenCore and check what the log says about CFG Lock.To check it, you can proceed into two ways: Note: Penyrn based machines actually don't need to worry about unlocking this register # Checking if your firmware supports CFG Lock unlockingīefore proceeding with the rest of this guide, you'll first need to check if your firmware supports CFG Lock unlocking. Very much preferred, as avoids patching allowing for greater flexibility regarding stability and OS upgrades.Patch our firmware to support MSR E2 write AppleCpuPmCfgLock for AppleIntelPowerManagement.kext.This creates instability and unnecessary patching for many.Instead both the Kernel (XNU) and AppleIntelPowerManagement want this register. And why we care about it is that macOS actually wants to write to this variable, and not just one part of macOS. By default, most motherboards lock this variable with many even hiding the option outright in the GUI. AMD users don't have any type of CFG LockĬFG-Lock is a setting in your BIOS that allows for a specific register(in this case the MSR 0圎2) to be written to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |