Arch Linux

osi93

Member

From: Drobeta Turnu Severin, Romania

Registered: 2014-09-10

Posts: 16

Buggy DSDT table

Due to my recent ban on the other account (I had forgotten the email), I will now post again about this, hoping that someone must know about this
Every ACPI-related activity freezes this laptop. I tried to use iasl to disassemble and recompile,but it gave me 2 errors. Does any of you at least know a workaround?

Moderator:  Marginally NSFW
http://i.imgur.com/mnOTJOv.jpg
http://i.imgur.com/ZKF1yjg.jpg

Moderator: Converted img tags for over sized pictures to url tags https://wiki.archlinux.org/index.php/Co … s_and_code

Last edited by ewaller (2016-09-11 18:05:12)

Alad

Wiki Admin/IRC Op

From: Bagelstan

Registered: 2014-05-04

Posts: 2,412

Website

Re: Buggy DSDT table

I have trouble reading the light green text on a transparent background to begin with. Post actual text, rather than screenshots ...

---

Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

osi93

Member

From: Drobeta Turnu Severin, Romania

Registered: 2014-09-10

Posts: 16

Re: Buggy DSDT table

Ok, here goes:

[root@laptop dsdt-files]# ls
dsdt.dat
[root@laptop dsdt-files]# iasl -d dsdt.dat 

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20160831-64
Copyright (c) 2000 - 2016 Intel Corporation

Input file dsdt.dat, Length 0xD48C (54412) bytes
ACPI: DSDT 0x0000000000000000 00D48C (v02 HPQOEM SLIC-MPC 00000003 HP   00040000)
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed

Found 2 external control methods, reparsing with new information
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    dsdt.dsl - 491035 bytes

 iASL Warning: There were 2 external control methods found during
 disassembly, but only 0 were 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. 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

 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

[root@laptop dsdt-files]# ls
dsdt.dat  dsdt.dsl
[root@laptop dsdt-files]# iasl -tc dsdt.dsl 

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20160831-64
Copyright (c) 2000 - 2016 Intel Corporation

Compiler aborting due to parser-detected syntax error(s)
dsdt.dsl     82:         }
Error    6126 -         ^ syntax error, unexpected '}'

dsdt.dsl  14992: 
Error    6126 - syntax error, unexpected $end and premature End-Of-File

ASL Input:     dsdt.dsl - 14992 lines, 491035 bytes, 6358 keywords
Hex Dump:      dsdt.hex - 203 bytes

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

brebs

Member

Registered: 2007-04-03

Posts: 3,742

Re: Buggy DSDT table

So check the code around line 82. That's probably the only error.

osi93

Member

From: Drobeta Turnu Severin, Romania

Registered: 2014-09-10

Posts: 16

Re: Buggy DSDT table

Method (ADBG, 1, Serialized)
    {
        If (CondRefOf (MDBG))
        {
            Return (MDBG) /* External reference */
            Arg0
        }

        Return (Zero)
    }

Line 82 is the bracket under Arg0. What now? Googled everything in multiple languages too...to no avail. Please help me, whoever knows ASL.

Last edited by osi93 (2016-09-11 16:52:41)

pypi

Wiki Maintainer

Registered: 2014-04-22

Posts: 250

Re: Buggy DSDT table

Method (ADBG, 1, Serialized)
    {
        If (CondRefOf (MDBG))
        {
            Return (MDBG) /* External reference */
            Arg0
        }

        Return (Zero)
    }

Line 82 is the bracket under Arg0. What now? Googled everything in multiple languages too...to no avail. Please help me, whoever knows ASL.

I don't know much about the language, but Arg0 comes after a return. Consider deleting the line containing Arg0 if it is not doing anything.

osi93

Member

From: Drobeta Turnu Severin, Romania

Registered: 2014-09-10

Posts: 16

Re: Buggy DSDT table

Ok, one more error:

Compiler aborting due to parser-detected syntax error(s)
dsdt.dsl   2817: 
Error    6126 - syntax error, unexpected PARSEOP_NAME, expecting $end and premature End-Of-File

ASL Input:     dsdt.dsl - 2817 lines, 490562 bytes, 663 keywords
Hex Dump:      dsdt.hex - 203 bytes

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

This is line 2817, where the error is listed:

Name (PNL3, 0xFFFFFFFF)
    Scope (\)

Damn, last error and still I don't know how to do it. Please, guys. Here is the entire DSDT table:
http://pastebin.com/JgeEv4T0

Last edited by osi93 (2016-09-11 22:34:01)

osi93

Member

From: Drobeta Turnu Severin, Romania

Registered: 2014-09-10

Posts: 16

Re: Buggy DSDT table

Is there at least some dirty hack to make the laptop not freeze upon even trying to suspend? any other alternative to save battery? Even systemd completely freezes while trying to suspend. If I boot with  laptop-mode-tools service enabled, I have to chroot with the live CD in order to disable it.