Contribute
Register

DSDT PARSEOP_EXP_XOR errors

Status
Not open for further replies.
Joined
Nov 27, 2012
Messages
379
Motherboard
HP 4540s
CPU
i5 2450
Graphics
HD 3000
Did someone try to patch a native DSDT with patchmatic then compile it with iasl 20140926-64? I applied 00_Optimize.txt and 01_compilation.txt and get these errors:

Just to note, when trying to compile the same file with an older iasl 5 version it works and have 0 errors.

./iasl5 -ta DSDT.dsl


Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Oct 16 2014]
Copyright (c) 2000 - 2014 Intel Corporation


Compiler aborting due to parser-detected syntax error(s)
DSDT.dsl 10814: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 10836: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11009: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11031: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11266: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11288: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11538: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11560: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11752: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11774: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11874: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 11896: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 12001: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 12023: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 12134: Notify (^, 0x00)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


DSDT.dsl 12156: Notify (^, 0x02)
Error 6126 - ^ syntax error, unexpected PARSEOP_EXP_XOR


ASL Input: DSDT.dsl - 14133 lines, 472570 bytes, 6586 keywords
Hex Dump: DSDT.hex - 206 bytes


Compilation complete. 16 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
 

Attachments

  • DSDT.dsl.zip
    43.1 KB · Views: 69
Code:
[FONT=Menlo][COLOR=#ce7924]10790 [/COLOR]                Method [COLOR=#d53bd3]([/COLOR]HPLG, 0, Serialized[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10791 [/COLOR]                {[/FONT]
[FONT=Menlo][COLOR=#ce7924]10792 [/COLOR]                    If [COLOR=#d53bd3]([/COLOR]_STA [COLOR=#d53bd3]())[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10793 [/COLOR]                    {[/FONT]
[FONT=Menlo][COLOR=#ce7924]10794 [/COLOR]                        If [COLOR=#d53bd3]([/COLOR]HPSX[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10795 [/COLOR]                        {[/FONT]
[FONT=Menlo][COLOR=#ce7924]10796 [/COLOR]                            Sleep [COLOR=#d53bd3]([/COLOR]0x64[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10797 [/COLOR]                            If [COLOR=#d53bd3]([/COLOR]PDCX[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10798 [/COLOR]                            {[/FONT]
[FONT=Menlo][COLOR=#ce7924]10799 [/COLOR]                                Store [COLOR=#d53bd3]([/COLOR]0x01, PDCX[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10800 [/COLOR]                                Store [COLOR=#d53bd3]([/COLOR]0x01, HPSX[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10801 [/COLOR]                                \_SB.SSMI [COLOR=#d53bd3]([/COLOR]0x5D, 0x00, 0x00, 0x00, 0x00[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10802 [/COLOR]                                Notify [COLOR=#d53bd3]([/COLOR]^, 0x00[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10803 [/COLOR]                            }[/FONT]
[FONT=Menlo][COLOR=#ce7924]10804 [/COLOR]                            Else[/FONT]
[FONT=Menlo][COLOR=#ce7924]10805 [/COLOR]                            {[/FONT]
[FONT=Menlo][COLOR=#ce7924]10806 [/COLOR]                                Store [COLOR=#d53bd3]([/COLOR]0x01, HPSX[COLOR=#d53bd3])[/COLOR][/FONT]
[FONT=Menlo][COLOR=#ce7924]10807 [/COLOR]                            }[/FONT]
[FONT=Menlo][COLOR=#ce7924]10808 [/COLOR]                        }[/FONT]
[FONT=Menlo][COLOR=#ce7924]10809 [/COLOR]                    }[/FONT]
[FONT=Menlo][COLOR=#ce7924]10810 [/COLOR]                }[/FONT]

I receive error at line 10802, ^ syntax error, unexpected PARSEOP_EXP_XOR.
I'm using the newest iasl compiled wiith RehabMan's acpica. I'm not sure which iasl version does the PBI CE use, but the older one I found in dhnguyenit folder worked. This is why I asked if someone used asl the newest iasl 20140926-64.
 
Did someone try to patch a native DSDT with patchmatic then compile it with iasl 20140926-64? I applied 00_Optimize.txt and 01_compilation.txt and get these errors:

Just to note, when trying to compile the same file with an older iasl 5 version it works and have 0 errors.

It is a new bug introduced in iasl. See here: https://github.com/acpica/acpica/issues/56

Use an older version.
 
Thank you.
When I decompile the DSDT is it important to do it with the SSDT files together? /CLOVER/ACPI/origin/SSDT*.aml , something like "iasl -e SSDT*.aml -d DSDT.aml" ?
I used to decompile it just using: iasl -d dsdt.aml then compile back with iasl -ta dsdt.dsdt without having the SSDT files and worked. I'm not sure what the SSDT files have to do with the DSDT file.
 
Thank you.
When I decompile the DSDT is it important to do it with the SSDT files together? /CLOVER/ACPI/origin/SSDT*.aml , something like "iasl -e SSDT*.aml -d DSDT.aml" ?
I used to decompile it just using: iasl -d dsdt.aml then compile back with iasl -ta dsdt.dsdt without having the SSDT files and worked. I'm not sure what the SSDT files have to do with the DSDT file.

I disassemble with -da:
Code:
iasl -da *.aml
 
Thank you.
$ cp /Volumes/CLOVER/EFI/CLOVER/ACPI/origin/DSDT.aml ~/Desktop/test
$ cp /Volumes/CLOVER/EFI/CLOVER/ACPI/origin/SSDT*.aml ~/Desktop/test
$ cd ~/Desktop/test

Screen Shot 2014-10-28 at 10.10.54 PM.png

After iasl -da *.aml I obtain the DSDT.dsl file but when I open it I see these lines:
/*
* iASL Warning: There were 2 external control methods found during
* disassembly, but only 0 was resolved (2 unresolved). Additional
* ACPI tables may be required to properly disassemble the code. This
* resulting disassembler output file may not compile because the
* disassembler did not know how many arguments to assign to the
* unresolved methods.
*
* If necessary, 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
*
* The following methods were unresolved and many not compile properly
* because the disassembler had to guess at the number of arguments
* required for each:
*/

Should I ignore the lines above?
 
Thank you.


View attachment 110500

After iasl -da *.aml I obtain the DSDT.dsl file but when I open it I see these lines:


Should I ignore the lines above?

You will always have unresolved externals. I think it is because they could be in Windows, or are optional with certain models/versions of BIOS/checks by the BIOS provider. The problem is that External declarations do not make their way into the final AML. To resolve externals for disassembly requires a declaration of the symbol somewhere within one of the files, or a separate file to define them (-fe option).
 
Thank you. Your time is greatly appreciated.
The last working iasl seems to be version 20140424-64 [Jun 25 2014]

Newer versions 20140627, 20140724, 20140828, and 20140926 fail to compile the patched ProBook DSDT.
 
Thank you. Your time is greatly appreciated.
The last working iasl seems to be version 20140424-64 [Jun 25 2014]

Newer versions 20140627, 20140724, 20140828, and 20140926 fail to compile the patched ProBook DSDT.

There has been a lot of new features added to iasl lately. I'm keeping my own version where I disable some of the problematic ones. And there are huge changes coming with the disassembler outputting a C-like syntax, but it is fairly buggy right now (you can disable it with -dl). I'm reporting bugs to Intel as I find them.

Bug tracking is here: https://github.com/acpica/acpica/issues
My version is here: https://github.com/RehabMan/acpica
 
They made some changes in the newest version 20141107, and I notice your username is mentioned in the changelog file.
 
Status
Not open for further replies.
Back
Top