[Guide] Patching LAPTOP DSDT/SSDTs

[RehabMan]

Hey guys, I followed the guide to the letter, built the latest iasl and when typing in

iasl -da -dl DSDT.aml SSDT*.aml

I get a message that the -dl flag is not recognized! Should I be using " -d " flag instead?

Here is the terminal output...

Unknown option: -dl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20130117-64 [Jan 19 2013]
Copyright (c) 2000 - 2013 Intel Corporation


Supports ACPI Specification Revision 5.0

Usage: iasl [Options] [Files]
Options:

Global:
  -@ <file>         Specify command file
  -I <dir>          Specify additional include directory
  -T <sig>|ALL|*    Create table template file for ACPI <Sig>
  -v                Display compiler version

Preprocessor:
  -D <symbol>       Define symbol for preprocessor use
  -li               Create preprocessed output file (*.i)
  -P                Preprocess only and create preprocessor output file (*.i)
  -Pn               Disable preprocessor

General Output:
  -p <prefix>       Specify path/filename prefix for all output files
  -va               Disable all errors and warnings (summary only)
  -vi               Less verbose errors and warnings for use with IDEs
  -vo               Enable optimization comments
  -vr               Disable remarks
  -vs               Disable signon
  -w1 -w2 -w3       Set warning reporting level
  -we               Report warnings as errors

AML and Data Output Files:
  -sa -sc           Create assembler or C source file (*.asm or *.c)
  -ia -ic           Create assembler or C include file (*.inc or *.h)
  -ta -tc -ts       Create assembler, C, or ASL hex table (*.hex)

AML Code Generation:
  -oa               Disable all optimizations (compatibility mode)
  -of               Disable constant folding
  -oi               Disable integer optimization to Zero/One/Ones
  -on               Disable named reference string optimization
  -cr               Disable Resource Descriptor error checking
  -in               Ignore NoOp operators
  -r <revision>     Override table header Revision (1-255)

ASL Listing Files:
  -l                Create mixed listing file (ASL source and AML) (*.lst)
  -ln               Create namespace file (*.nsp)
  -ls               Create combined source file (expanded includes) (*.src)

ACPI Data Tables:
  -G                Compile custom table containing generic operators
  -vt               Create verbose templates (full disassembly)

AML Disassembler:
  -d  [file]        Disassemble or decode binary ACPI table to file (*.dsl)
  -da [f1,f2]       Disassemble multiple tables from single namespace
  -db               Do not translate Buffers to Resource Templates
  -dc [file]        Disassemble AML and immediately compile it
                    (Obtain DSDT from current system if no input file)
  -e  [f1,f2]       Include ACPI table(s) for external symbol resolution
  -g                Get ACPI tables and write to files (*.dat)
  -in               Ignore NoOp opcodes
  -vt               Dump binary table data in hex format within output file

Help:
  -h                This message
  -hc               Display operators allowed in constant expressions
  -hf               Display help for output filename generation
  -hr               Display ACPI reserved method names
  -ht               Display currently supported ACPI table names

Debug Options:
  -bf -bt           Create debug file (full or parse tree only) (*.txt)
  -f                Ignore errors, force creation of AML output file(s)
  -n                Parse only, no output generation
  -ot               Display compile times and statistics
  -x <level>        Set debug level for trace output
  -z                Do not insert new compiler ID for DataTables

Your iasl is from 2013.
Clearly not the one linked by the guide.

 

[dbrannon79]

Your iasl is from 2013.
Clearly not the one linked by the guide.

it's the one that was built following your post. I also tried downloading the one linked in the post #1 and still get the same result. did I miss something?

I'm assuming that there is another copy installed somewhere on my pc and it's overriding the one I downloaded or built. any idea where it should be located? the one I downloaded was put in /usr/bin as indicated in the guide.

 

[dbrannon79]

I looked at the links again and there are two iasl files listed. the "iasl" reports from 2013 there is another "iasl51" that reports 2015 I will try with this one. but in the guide building the latest, I get the 2013 version installed!

Thanks

 

[RehabMan]

it's the one that was built following your post.

It is not.

but in the guide building the latest, I get the 2013 version installed!

No.
Use 'which iasl' to determine where iasl is really loading from.

 

[dbrannon79]

It is not.



No.
Use 'which iasl' to determine where iasl is really loading from.

ok I may need some help here!

I verified the iasl that I need to use, placed in /usr/bin but I still get the result in terminal for the 2013 version. searched the hard drive for another iasl and came up with only the one, the 2015 version. I'm thinking that when I built and installed the one from github I did something unintentional. how can I revert back and undo that installation? or find out what is overriding the one downloaded in the link?

Thanks again for your help.

Update: I think I found it located in /usr/local/bin not sure but I believe Xcode may have installed it there.

 

[RehabMan]

ok I may need some help here!

I verified the iasl that I need to use, placed in /usr/bin but I still get the result in terminal for the 2013 version. searched the hard drive for another iasl and came up with only the one, the 2015 version. I'm thinking that when I built and installed the one from github I did something unintentional. how can I revert back and undo that installation? or find out what is overriding the one downloaded in the link?

Thanks again for your help.

Update: I think I found it located in /usr/local/bin not sure but I believe Xcode may have installed it there.

You can use 'which iasl' to determine where iasl is loading.
In Terminal:

which iasl

 

[eddmecha]

@RehabMan I have a question regarding DSDT patching, i have this "firmware error (ACPI): Failure looking up.....(refer screenshot attached) can I just commented it out or otherwise,and herewith I attached my problem reporting files as well.TIA

 

[RehabMan]

@RehabMan I have a question regarding DSDT patching, i have this "firmware error (ACPI): Failure looking up.....(refer screenshot attached) can I just commented it out or otherwise,and herewith I attached my problem reporting files as well.TIA

It has to do with an old iasl bug that generates invalid External opcodes. Evidently, that buggy iasl was used by the OEM that created your native ACPI files. You can just comment it out.

Note: The bz1397 refers to the acpica Bugzilla bug database (bug #1397), where you can find complete details.

 

[eddmecha]

It has to do with an old iasl bug that generates invalid External opcodes. Evidently, that buggy iasl was used by the OEM that created your native ACPI files. You can just comment it out.

ok thank you for the verification.

 

[bortoni]

Question: I need to rename both Intel Graphics and discrete graphics in a sequential way:

1) Rename GFX0 to IGPU
2) Rename PEG0 to GFX0

If I list them in that order in config.plist/ACPI/patched will clover take care things in order or must I extract and patch these 2 renames manually?