It is easy to see which are duplicates by looking at the file sizes. If you run into issues (duplicate definitions) during disassembly, you will need to analyse all SSDTs to eliminate the files which are duplicate. These duplicates will cause problems during disassembly. Sometimes, Clover F4 will write duplicate SSDTs. The delay is more noticeable if they are being written to USB, as would be the case when booting from a Clover USB. There is no feedback during or after the dump, just a slight delay as the files are written. Note that some BIOS implementations reverse the function of Fn+F4 with F4, so when in doubt, press both Fn+F4 and F4. You can then access them after you boot OS X to disassemble them and patch. The others are provided for your information only.Įxtracting with Clover F4 is recommended, due to ease of extraction, and due to ease of comparison between ACPI/origin and ACPI/patched (for troubleshooting).Īt the main Clover bootloader screen, you can press F4 and Clover will dump the native ACPI files to EFI/Clover/ACPI/origin. Only the first is the recommended method. This guide will focus on three methods of extraction: using F4 with Clover, using patchmatic in OS X, or using Linux.
SAVE DSDT WINDOWS SOFTWARE
Native files extracted are generally identical, although because of the software used to extract, they may be named differently. Extraction can therefore be done on Linux, OS X, Windows, or even in the Clover bootloader. So, on any OS, you can extract them for patching later. The process of patching involves several steps:Īll BIOS implementations provide ACPI files to the OS. changing hardware or memory configuration If any of the following is changed, you must re-extract, re-patch, as these changes may cause significant changes to the native ACPI (especially SystemMemory regions): Keep in mind that even changes you make to your own system (BIOS, hardware, etc.) will require re-extract, re-patch. It is also not uncommon for the same laptop model to be produced in different runs with different motherboards, and potentially incompatible ACPI files. Such differences can make various OperationRegion addresses different, which makes a patched DSDT for one system incompatible with another. Even minor differences in hardware configuration (BIOS version, amount of memory installed, BIOS options selected, and other hardware differences such as which WiFi card is installed) can make for differences that cause instability and weird bugs if you use foreign ACPI files. You simply cannot be certain it is valid to use ACPI files from another computer. See guide here: Īlthough you may be tempted to use a DSDT from another computer, it will almost always end in failure. The purpose of this guide is to provide a foundation for proper patching of your OEM DSDT/SSDTs.Īdvanced users may wish to implement hotpatching via Clover. In order to make many OS X features work well on a laptop, you will always need a properly patched DSDT (and maybe some of the SSDTs).
0 kommentar(er)
