Contribute
Register

[Guide] Disabling discrete graphics in dual-GPU laptops

How can I know which ssdt do I have to patch?

It depends on the content of the SSDTs (you have to use your brain).

Have you worked through the example yet? Do you understand why the patches were done to certain files?
 
It depends on the content of the SSDTs (you have to use your brain).

Have you worked through the example yet? Do you understand why the patches were done to certain files?

CAant get throught in the example...

RehabMan said:
SSDT-2x, SSDT-3x, SSDT-4x are not included as they are dynamically loaded.
SSDT-1, SSDT-5, SSDT-6, SSDT-8 require no patches.

this applies only for this example right?
 
Why?



SSDT names and purposes will vary by laptop. General guidelines are in the guide: http://www.tonymacx86.com/yosemite-laptop-support/152573-guide-patching-laptop-dsdt-ssdts.html

right at the start i got this in terminal

Code:
Parsing completed
Disassembly completed
ASL Output:    SSDT-9.dsl - 109423 bytes

iASL Warning: There were 7 external control methods found during
disassembly, but additional ACPI tables to resolve these externals
were not specified. The resulting disassembler output file may not
compile because the disassembler did not know how many arguments
to assign to these methods. To specify the tables needed to resolve
external control method references, the -e option can be used to
specify the filenames. Example iASL invocations:
    iasl -e ssdt1.aml ssdt2.aml ssdt3.aml -d dsdt.aml
    iasl -e dsdt.aml ssdt2.aml -d ssdt1.aml
    iasl -e ssdt*.aml -d dsdt.aml

In addition, the -fe option can be used to specify a file containing
control method external declarations with the associated method
argument counts. Each line of the file must be of the form:
    External (<method pathname>, MethodObj, <argument count>)
Invocation:
    iasl -fe refs.txt -d dsdt.aml
Aldos-MacBook-Pro:origin Aldo$

should that warning appear?

RehabMan said:
For DSDT.dsl:
"Fix PARSEOP_ZERO Error" (be sure to uncommment the "more agressive" patches)
"Fix ADBG Error"
"Remove _DSM methods"
"IRQ Fix"
"SMBUS Fix"
"OS Check Fix (Windows 8)"
"Add IMEI"
"RTC Fix"
"Fix _WAK Arg0 v2"
"Fix _WAK IAOE" (new patch)
"Rename GFX0 to IGPU"
"Rename B0D3 to HDAU" (new patch)
"ASUS N55SL/VivoBook"
"USB3 _PRW(0x6D) and Rename XHC to XHC1" (new patch)
can't apply the "Fix PARSEOP_ZERO Error" and "Fix _WAK IAOE" (new patch) it won't allow me..
 
right at the start i got this in terminal

Code:
Parsing completed
Disassembly completed
ASL Output:    SSDT-9.dsl - 109423 bytes

iASL Warning: There were 7 external control methods found during
disassembly, but additional ACPI tables to resolve these externals
were not specified. The resulting disassembler output file may not
compile because the disassembler did not know how many arguments
to assign to these methods. To specify the tables needed to resolve
external control method references, the -e option can be used to
specify the filenames. Example iASL invocations:
    iasl -e ssdt1.aml ssdt2.aml ssdt3.aml -d dsdt.aml
    iasl -e dsdt.aml ssdt2.aml -d ssdt1.aml
    iasl -e ssdt*.aml -d dsdt.aml

In addition, the -fe option can be used to specify a file containing
control method external declarations with the associated method
argument counts. Each line of the file must be of the form:
    External (<method pathname>, MethodObj, <argument count>)
Invocation:
    iasl -fe refs.txt -d dsdt.aml
Aldos-MacBook-Pro:origin Aldo$

should that warning appear?

It is normal.

can't apply the "Fix PARSEOP_ZERO Error" and "Fix _WAK IAOE" (new patch) it won't allow me..

If a patch doesn't apply, it may not be needed or may need to be tweaked for your own files.

Only apply patches that you need.
 
It is normal.



If a patch doesn't apply, it may not be needed or may need to be tweaked for your own files.

Only apply patches that you need.

it does need the "Fix PARSEOP_ZERO Error" patch, but dont allow e to apply... i remove it manually...
 
it does need the "Fix PARSEOP_ZERO Error" patch, but dont allow e to apply... i remove it manually...

Sorry, not clairvoyant here...

Post your native files if you need help.
 
i wast talking about the example from the post1...

Perhaps you are attempting to apply the patch to the wrong file. Read the guide carefully.
 
Back
Top