examine the resulting files to determine the ACPI pathįor this guide, we will use the files from the discrete disable guide: ĭownload the attachment so you can follow along.įirst, we disassemble all the files (see ACPI patching guide for more information on iasl and disassembly):ĭefinitionBlock ("", "SSDT", 2, "hack", "spoof", 0) use Clover F4 to extract native ACPI files to ACPI/origin If you have an ioreg (from a working Sierra install, for example), you can determine the path from that ioreg (if someone has such an ioreg, please attach it, for an example in this post).īut you can also determine it by looking at extracted ACPI files. In order to inject the needed properties using an add-on SSDT, you must first determine the ACPI path of the device. Of course, the ist technique relies on Clover recognizing the discrete device correctly, which does not always work, so if that is your case, continue to follow this guide. The plists in that guide already use ist/AddProperties to inject the required spoofing properties on both the AMD and Nvidia devices (if they exist). Note: If you're using the plists from the Clover laptop guide ( ), you will probably not need to implement the SSDT-DiscreteSpoof.aml as described in this guide. It is the third/last method mentioned that this guide will cover. inject a few properties on the graphics device that prevent the base VESA drivers from loading disable the card in in ACPI as per this guide:
disable the card in BIOS (but not all laptop BIOS implementations provide such an option)
There are essentially three methods you might employ to avoid this: It is a new bug in the system somewhere that stalls boot if the VESA drivers try to connect to the secondary (discrete) graphics device. If you have a dual-GPU (Intel+Nvidia or Intel+AMD Radeon), you may have trouble reaching the macOS High Sierra installer. Building a CustoMac Hackintosh: Buyer's Guide
0 kommentar(er)
