Skip to contentSkip to conversation

broken DSDT on sony vaio pcg-grx500

DISCUSSION asu 2 participants 2 messages Mar 26, 2004 1 message not in the archive ACPI

lore
Share & tools
lore

asu

author
#0 lore raw

Compiling the decompiled DSDT gives me two errors. One error was that it required ByteAcc access which I fixed easily. The other error is:

dsdt.dsl 16: Return (DCST)
Error 1022 - Object does not exist ^ (DCST)

The region of code it corresponds to is:

DefinitionBlock ("DSDT.aml", "DSDT", 1, "SONY", "B0", 537002772)

{
    Scope (_PR)
    {
        Processor (CPU0, 0x00, 0x00001010, 0x06) {}
        Scope (\_PR.CPU0)
        {
            Method (_CST, 0, NotSerialized)
            {
                Return (DCST)
            }
        }

Changing DCST to _CST and compiling it gives me segmentation fault while compiling. Realizing that it is dangerous, I tried various things like DSDT, \_CST, etc. Changing it to 0x0 did not give me any errors or warnings. Then I changed it to 0x033 which also did not give me any error. So, I think changing it to 0x0 or 0x033 is incorrect.

I am using iasl-linux-20030918 to compile my dsl file.

Can anyone point me to the solution to this error?

Thanks,
asubedi

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 23 lines · asu

Compiling the decompiled DSDT gives me two errors. One error was that it required ByteAcc access which I fixed easily. The other error is:

dsdt.dsl 16: Return (DCST)
Error 1022 - Object does not exist ^ (DCST)

The region of code it corresponds to is:

DefinitionBlock ("DSDT.aml", "DSDT", 1, "SONY", "B0", 537002772)

{
    Scope (_PR)
    {
        Processor (CPU0, 0x00, 0x00001010, 0x06) {}
        Scope (\_PR.CPU0)
        {
            Method (_CST, 0, NotSerialized)
            {
                Return (DCST)
            }
        }
Quoted 8 lines

Changing DCST to _CST and compiling it gives me segmentation fault while compiling. Realizing that it is dangerous, I tried various things like DSDT, \_CST, etc. Changing it to 0x0 did not give me any errors or warnings. Then I changed it to 0x033 which also did not give me any error. So, I think changing it to 0x0 or 0x033 is incorrect.

I am using iasl-linux-20030918 to compile my dsl file.

There is good chance that your system do have a table called SSDT, which contains a DCST package.

Try something like
sudo ./acpidmp/acpidmp | grep SSDT
to see if I'm correct.
Then
./acpidmp/acpidmp SSDT > ssdt
hd ssdt

will dump the SSDT. Look then if something like DCST do exist.

In that case, just making something like:

             Method (_CST, 0, NotSerialized)
             {
                 External(DCST)
                 Return (DCST)
             }

should be ok.

If that is not the case, I'm afraid that I need the full dump from acpidmp (no just the DSDT) to look. For this:

wget http://developer.intel.com/technology/iapc/acpi/downloads/pmtools-20010730.tar.gz
tar xzvfp pmtools-20010730.tar.gz
cd pmtools-20010730/acpidmp
make
sudo ./acpidmp > acpidmp.out
gzip acpidmp.out.gz

Signature · 11 lines
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click