Contribute
Register

Getting 1 single error compilating DSDT

Status
Not open for further replies.
Joined
Jan 7, 2018
Messages
8
Motherboard
HP 841C (HP Pavilion 15-ck013nl) (Clover)
CPU
Intel Core i5 8250U
Graphics
nVidia 940MX, Intel UHD Graphics 620 1920x1080
Mac
  1. iMac
Mobile Phone
  1. iOS
Hi everyone
It's the first time for me patching DSDT and SSDT files but Rehabman's guide on how to do it makes it somewhat easy to do.

I've stepped on a few rocks along the way: first of all, I can't seem to disassemble my ACPI .aml files using refs.txt, I get a segmentation fault and the process terminates.
I tried going around this using iasl -da -dl DSDT.aml SSDT*.aml and I extracted my files.

Now, if I open my untouched and unpatched DSDT.dsl file I see a lot of Firmware errors on top of it, I guess that's because I didn't extract it with refs.txt as all those errors refer to unresolved externals.
If I try to compile the DSDT still unpatched, I get a single error:

1, 6126, syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITION_BLOCK and premature End-Of-File

And the error persists throught the patching process.
I should point out I'm using the last version of iasl and MacIasl with 6.2 ACPI.

What's the cause of this? Thank you very much!
I'm attaching my origin folder from Clover with the .dsl files included and still unpatched.
 

Attachments

  • origin.zip
    210 KB · Views: 85

RehabMan

Moderator
Joined
May 2, 2012
Messages
184,103
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hi everyone
It's the first time for me patching DSDT and SSDT files but Rehabman's guide on how to do it makes it somewhat easy to do.

I've stepped on a few rocks along the way: first of all, I can't seem to disassemble my ACPI .aml files using refs.txt, I get a segmentation fault and the process terminates.
I tried going around this using iasl -da -dl DSDT.aml SSDT*.aml and I extracted my files.

Now, if I open my untouched and unpatched DSDT.dsl file I see a lot of Firmware errors on top of it, I guess that's because I didn't extract it with refs.txt as all those errors refer to unresolved externals.
If I try to compile the DSDT still unpatched, I get a single error:

1, 6126, syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITION_BLOCK and premature End-Of-File

And the error persists throught the patching process.
I should point out I'm using the last version of iasl and MacIasl with 6.2 ACPI.

What's the cause of this? Thank you very much!
I'm attaching my origin folder from Clover with the .dsl files included and still unpatched.

Disasemble: iasl -dl DSDT.aml SSDT*.aml

Then remove the extra lines at the top of the file (Firmware error lines).
Result: no errors.
 
Joined
Jan 7, 2018
Messages
8
Motherboard
HP 841C (HP Pavilion 15-ck013nl) (Clover)
CPU
Intel Core i5 8250U
Graphics
nVidia 940MX, Intel UHD Graphics 620 1920x1080
Mac
  1. iMac
Mobile Phone
  1. iOS
Disasemble: iasl -dl DSDT.aml SSDT*.aml

Then remove the extra lines at the top of the file (Firmware error lines).
Result: no errors.

Thank you very much Rehab, that worked!
I've now spent some time patching the DSDT and was starting to save all the files back to .aml but the SSDT-5 is giving me a few syntax errors related to unexpected parenthesis I can't figure out. For my previous (but not extensive) experiences with coding to me the code looks to be written correctly but if the compiler thinks otherwise maybe it's really not.

I'm attaching my origin folder again with patched .dsls
 

Attachments

  • origin.zip
    360.2 KB · Views: 67

RehabMan

Moderator
Joined
May 2, 2012
Messages
184,103
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Thank you very much Rehab, that worked!
I've now spent some time patching the DSDT and was starting to save all the files back to .aml but the SSDT-5 is giving me a few syntax errors related to unexpected parenthesis I can't figure out. For my previous (but not extensive) experiences with coding to me the code looks to be written correctly but if the compiler thinks otherwise maybe it's really not.

I'm attaching my origin folder again with patched .dsls

No need to patch SSDT-5 nor include it in ACPI/patched, so why are you trying to compile it?
 
Status
Not open for further replies.
Top