Note that the _OFF method may be in DSDT or may have a different name (GPOF, OPOF, _PS3, etc.)Ĭertain implementations of _OFF cannot be called from _INI as they access the EC (Embedded Controller) space. The easiest fix is to call _OFF from the corresponding _INI method. These machines provide an _OFF method, usually in an SSDT, that can be called to power down the discrete device. Note: There is also a full hotpatch guide (for this same computer) here: The Clover F4 extracted tables (ACPI/origin directory) are provided in an attachment to this post. The laptop being used for this guide/example is an "Asus UX303LN" with Intel HD4400 + Nvidia. You should follow this walkthrough with the example before patching your own. The example DSDT/SSDT set that this guide uses is one of the more complex setups, so it covers most of the issues you might run into with your own. Also, certain machine/ACPI configurations require different approaches, leading to more complexity. Although the device can usually be disabled in BIOS, it is better to disable it with a custom ACPI setup so the device can still be used when booting Windows.Īlthough it is a relatively simple patch (sometimes only a one line change), because of the fact that the patch is done to one or more SSDTs, there are many pitfalls to fall into. Intel+Nvidia and Intel+Radeon).īecause only the Intel device can be used in these laptops, the discrete device is generally left active and using power, contributing to heat, noise, and battery usage.
The purpose of this guide is to show you how to disable the discrete graphics device with DSDT/SSDT edits in "switched" dual-GPU laptops (eg. Building a CustoMac Hackintosh: Buyer's Guide