![]() 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. Note that this guide is only applicable for Intel users."index 0" is an NVRAM volume that changes every boot, because the system writes last known boot configuration there.This guide is only recommended for users who have already installed macOS, for users who are installing for the first time enable AppleCpuPmCfgLock and AppleXcpmCfgLock under Kernel -> Quirks "Index 1" is a copy of NVRAM volume done by BIOS Setup where you've selected "Save Changes and Reset", that is why both backups you have made are fine.įPT is in fact more reliable then AFU, because it's much simpler and does no changes to input file, while AFU tries to preserve ROM holes, transfer some files and do other things no one really needs. Then it uses SMM-based flasher to do real writes to SPI chip, which can be handy on boards with BIOS Lock, but again more complex then FPT, that just uses chipset registers directly to write to SPI chip. You don't have to worry about FPT or AFU. If writing with FPT works for you - go use it, if not - just use AFU, either way is please update your Clover to the latest version, NVRAM problems are gone now thanks to dmazar. You can also experience problems with iMessage after this update, so I recommend to read this topic to the looks like it's already unlocked, nothing to patch there. I wrote an utility to patch modern UEFI BIOSes from different vendors to prevent them from locking MSR 0圎2 and therefore make the system with patched BIOS compatible with native OS X power management. It's tested on AMI, Phoenix and Insyde UEFI BIOSes and it works. This patch works on boards based on 5th, 6th, 7th and 8th series of Intel chipsets, so NM10 and similar ones are supported - there is nothing to patch in that BIOSes. Usage: pmpatch /path/to/original.bios /path/to/patched.bios The utility is BSD-licensed and available on GitHub.Ĭompiled versions for Windows and OS X are here. This program can produce corrupt BIOS images, try them on your own risk. not found" messages in program output, is it bad? Please attach AIDA64's or DarwinDumper's report file to your "PMPatch didn't work for me" message.ġ. I have patched my BIOS, can you guarantee it will work after flashing? No, if the last message is "Output file generated", it's OK to have any other messages.Ģ. I can't flash my patched BIOS due to "security verification failed", what can I do? No, but there are many people with patched BIOSes of all kinds, and very few negative reports.ģ. If you have ASUS board with USB BIOS Flashback support, use it to flash your modified BIOS. If you have AMI UEFI BIOS (all modern desktop boards now have one, DO NOT TRY IT ON NOTEBOOKS), then you can use this method. Program version for OS X crashes with "Segmentation fault" message, what to do now? If you have non-AMI BIOS, I don't know any 100% working method except using external programmer, which are cheap and fast nowadays.Ĥ. It's a known issue with LZMA compression code compiled by Apple compilers, please try using version for Windows. Alpha, result is the same? Or one of two is a better solution? There is a guide to use UEFIPatch? I actually use SSDTPRGen script from Pike R. Hi CodeRush - thanks for the great work here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |