Can't compile extracted DSDT

[Anonymouslemming]

Hi all,

I'm trying to compile and patch my DSDT on an MSI Z87-GD65 gaming motherboard. I've extracted the DSDT file on Windows using Read Write Anywhere, and decompiled it on the mac using iasl. However, the resulting file does not compile. I get the following errors:

6270, 6126, syntax error, unexpected PARSEOP_ZERO
10628, 6126, syntax error, unexpected '}'
15036, 6126, syntax error, unexpected $end and premature End-Of-File

When I decompiled the DSDT file, I got the following output from iasl:

 iASL Warning: There were 12 external control methods found during
 disassembly, but only 0 were resolved (12 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. Note: SSDTs can be dynamically loaded at
 runtime and may or may not be available via the host OS.

 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

I then tried the following, using the ACPI directory I got by booting clover with F4 and copying out of the EFI directory:

iasl -e SSDT* -d ~/Desktop/DSDT.aml

This generated the same result.

Does anyone have any advice for how I can get a healthy DSDT extracted and compiled ?

Thanks,

 

[RehabMan]

Hi all,

I'm trying to compile and patch my DSDT on an MSI Z87-GD65 gaming motherboard. I've extracted the DSDT file on Windows using Read Write Anywhere, and decompiled it on the mac using iasl. However, the resulting file does not compile. I get the following errors:

6270, 6126, syntax error, unexpected PARSEOP_ZERO
10628, 6126, syntax error, unexpected '}'
15036, 6126, syntax error, unexpected $end and premature End-Of-File

When I decompiled the DSDT file, I got the following output from iasl:

 iASL Warning: There were 12 external control methods found during
 disassembly, but only 0 were resolved (12 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. Note: SSDTs can be dynamically loaded at
 runtime and may or may not be available via the host OS.

 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

I then tried the following, using the ACPI directory I got by booting clover with F4 and copying out of the EFI directory:

iasl -e SSDT* -d ~/Desktop/DSDT.aml

This generated the same result.

Does anyone have any advice for how I can get a healthy DSDT extracted and compiled ?

Thanks,

PARSEOP_ZERO errors are very common.
There is a patch for it in my laptop rep... refer to the guide:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

Or you can just remove the 'Zero' lines you see... they are placeholders for dynamically generated code from BIOS.

 

[Anonymouslemming]

PARSEOP_ZERO errors are very common.
There is a patch for it in my laptop rep... refer to the guide:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

Or you can just remove the 'Zero' lines you see... they are placeholders for dynamically generated code from BIOS.

I recaptured my DSDT by booting and pressing F4. I've disassembled it with iasl, and I now get the following exceptions when trying to compile:

I don't really know where to start with this, or why it's different from the last time I generated it. Any advice would be much appreciated!

 

[RehabMan]

I recaptured my DSDT by booting and pressing F4. I've disassembled it with iasl, and I now get the following exceptions when trying to compile:

I don't really know where to start with this, or why it's different from the last time I generated it. Any advice would be much appreciated!

I think you are not using the correct tools (perhaps using ACPI 4.0). Make sure you use the tools linked by my guide (with ACPI 6.1). And you probably forgot to use "-dl" flag when you disassembled.

 

[Anonymouslemming]

I think you are not using the correct tools (perhaps using ACPI 4.0). Make sure you use the tools linked by my guide (with ACPI 6.1). And you probably forgot to use "-dl" flag when you disassembled.

Thanks - that was it. I now have a clean DSDT. Let's see if it fixes the issues I was having