* syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
@ 2007-05-01 9:40 Markus Feldmann
2007-05-01 10:08 ` Alexey Starikovskiy
0 siblings, 1 reply; 9+ messages in thread
From: Markus Feldmann @ 2007-05-01 9:40 UTC (permalink / raw)
To: linux-acpi
Hi All,
i bought a Laptop Asus A7Tc and got the first Problem with ACPI and
suspend-to-ram.
My System is Debian Etch with Kernel 2.6.21.
Cpu is AMD Turion(tm) 64 X2 Mobile Technology TL-52
i did the folowing to fix my dsdt Table,
> cat /proc/acpi/dsdt > dsdt.dat
> iasl -d dsdt.dat
> feld-bertlap:/tmp/acpi# iasl -tc dsdt.dsl
> Intel ACPI Component Architecture
> ASL Optimizing Compiler version 20060912 [Dec 20 2006]
> Copyright (C) 2000 - 2006 Intel Corporation
> Supports ACPI Specification Revision 3.0a
> dsdt.dsl 1: ACPI Package (0x04)
> Error 4094 - ^ syntax error, unexpected PARSEOP_NAMESEG,
expecting PARSEOP_DEFINITIONBLOCK
Can anybody explain what i have to do to correct my table?
bye Markus
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-01 9:40 syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK Markus Feldmann
@ 2007-05-01 10:08 ` Alexey Starikovskiy
2007-05-01 10:38 ` Markus Feldmann
[not found] ` <46371966.2020300@gmx.de>
0 siblings, 2 replies; 9+ messages in thread
From: Alexey Starikovskiy @ 2007-05-01 10:08 UTC (permalink / raw)
To: Markus Feldmann; +Cc: linux-acpi
1. why do you think that making custom DSDT is going to help you?
2. please attach your dsdt.dsl, so we could see on what iasl barks...
>From your report it looks like you trying to fed it with some non-aml
code.
Regards,
Alex.
On 5/1/07, Markus Feldmann <feldmann_markus@gmx.de> wrote:
> Hi All,
>
> i bought a Laptop Asus A7Tc and got the first Problem with ACPI and
> suspend-to-ram.
>
> My System is Debian Etch with Kernel 2.6.21.
> Cpu is AMD Turion(tm) 64 X2 Mobile Technology TL-52
>
>
> i did the folowing to fix my dsdt Table,
> > cat /proc/acpi/dsdt > dsdt.dat
> > iasl -d dsdt.dat
> > feld-bertlap:/tmp/acpi# iasl -tc dsdt.dsl
>
> > Intel ACPI Component Architecture
> > ASL Optimizing Compiler version 20060912 [Dec 20 2006]
> > Copyright (C) 2000 - 2006 Intel Corporation
> > Supports ACPI Specification Revision 3.0a
>
> > dsdt.dsl 1: ACPI Package (0x04)
> > Error 4094 - ^ syntax error, unexpected PARSEOP_NAMESEG,
> expecting PARSEOP_DEFINITIONBLOCK
>
> Can anybody explain what i have to do to correct my table?
>
> bye Markus
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-01 10:08 ` Alexey Starikovskiy
@ 2007-05-01 10:38 ` Markus Feldmann
[not found] ` <46371966.2020300@gmx.de>
1 sibling, 0 replies; 9+ messages in thread
From: Markus Feldmann @ 2007-05-01 10:38 UTC (permalink / raw)
To: linux-acpi
Alexey Starikovskiy schrieb:
> 1. why do you think that making custom DSDT is going to help you?
> 2. please attach your dsdt.dsl, so we could see on what iasl barks...
> From your report it looks like you trying to fed it with some non-aml
> code.
>
> Regards,
> Alex.
To 1.) I thought that my dsdt was changed, but that is my mistake. I
compared my dsdt_2.6.18.dsl with my dsdt_2.6.21.dsl and they seems to be
equal.
To 2.) I didnt know aml-code, but i followed the Instructions from
http://acpi.sourceforge.net/ to fix my dsdt-table .
Because the original error Message, can you please tell me what i should
do to correct this?
bye Markus
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
[not found] ` <46371966.2020300@gmx.de>
@ 2007-05-01 13:38 ` Alexey Starikovskiy
2007-05-01 18:43 ` Markus Feldmann
2007-05-03 6:35 ` Markus Feldmann
0 siblings, 2 replies; 9+ messages in thread
From: Alexey Starikovskiy @ 2007-05-01 13:38 UTC (permalink / raw)
To: Markus Feldmann; +Cc: linux-acpi
Please remove error lines at the beginning of the file and try to
compile it again...
On 5/1/07, Markus Feldmann <feldmann_markus@gmx.de> wrote:
> Alexey Starikovskiy schrieb:
> > 1. why do you think that making custom DSDT is going to help you?
> > 2. please attach your dsdt.dsl, so we could see on what iasl barks...
> >> From your report it looks like you trying to fed it with some non-aml
> > code.
> >
> > Regards,
> > Alex.
> >
> Sorry forgot the dsdt.dsl.
> Here it comes.
>
> bye Markus
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-01 13:38 ` Alexey Starikovskiy
@ 2007-05-01 18:43 ` Markus Feldmann
2007-05-03 6:35 ` Markus Feldmann
1 sibling, 0 replies; 9+ messages in thread
From: Markus Feldmann @ 2007-05-01 18:43 UTC (permalink / raw)
To: Alexey Starikovskiy; +Cc: linux-acpi
Alexey Starikovskiy schrieb:
> Please remove error lines at the beginning of the file and try to
> compile it again...
>
Ok here it comes the corrected dsdt_2.6.21.dsl file with the new error
messages,
feld-bertlap:~/acpi/dsdt# iasl -tc dsdt_2.6.21.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20060912 [Dec 20 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
dsdt_2.6.21.dsl 20: Name (_T00, 0x00)
Warning 1097 - ^ Unknown reserved name (_T00)
dsdt_2.6.21.dsl 6218: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6232: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6247: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6262: Acquire (MUTE, 0x0FFF)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6276: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6291: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6306: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6504: Method (WFZF, 1, NotSerialized)
Warning 1086 - ^ Not all control paths return a
value (WFZF)
dsdt_2.6.21.dsl 6519: Return (Stall (0x0F))
Error 4094 - ^ syntax error,
unexpected PARSEOP_STALL
dsdt_2.6.21.dsl 6606: Zero
Error 4094 - ^ syntax error, unexpected PARSEOP_ZERO
dsdt_2.6.21.dsl 6671: Zero
Error 4094 - ^ syntax error, unexpected PARSEOP_ZERO
ASL Input: dsdt_2.6.21.dsl - 7677 lines, 256431 bytes, 2870 keywords
Compilation complete. 3 Errors, 9 Warnings, 0 Remarks, 701 Optimizations
can you help me to fix the errors?
thanks and bye Markus
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-01 13:38 ` Alexey Starikovskiy
2007-05-01 18:43 ` Markus Feldmann
@ 2007-05-03 6:35 ` Markus Feldmann
2007-05-03 16:12 ` Alexey Starikovskiy
1 sibling, 1 reply; 9+ messages in thread
From: Markus Feldmann @ 2007-05-03 6:35 UTC (permalink / raw)
To: Alexey Starikovskiy; +Cc: linux-acpi
Alexey Starikovskiy schrieb:
> Please remove error lines at the beginning of the file and try to
> compile it again...
>
> On 5/1/07, Markus Feldmann <feldmann_markus@gmx.de> wrote:
>> Alexey Starikovskiy schrieb:
>> > 1. why do you think that making custom DSDT is going to help you?
>> > 2. please attach your dsdt.dsl, so we could see on what iasl barks...
>> >> From your report it looks like you trying to fed it with some non-aml
>> > code.
>> >
>> > Regards,
>> > Alex.
>> >
>> Sorry forgot the dsdt.dsl.
>> Here it comes.
>>
>> bye Markus
>>
>>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Where can i upload my dsdt.dsl file ?
Because my Emails which i did send are not arrived in this Newsgroup.
I think its not allowed to send emails to this Newsgroup with Attachment.
bye Markus
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-03 6:35 ` Markus Feldmann
@ 2007-05-03 16:12 ` Alexey Starikovskiy
2007-05-04 16:30 ` Markus Feldmann
2007-05-06 13:32 ` Markus Feldmann
0 siblings, 2 replies; 9+ messages in thread
From: Alexey Starikovskiy @ 2007-05-03 16:12 UTC (permalink / raw)
To: Markus Feldmann; +Cc: linux-acpi
I already received your dsdt.dsl to my mailbox. I answered as well,
but your provider seem to block whole gmail.com domain.
Lets try to go without attachements:
First error -- move Stall() function out of Return().
Second error -- you have wrong length for optional _PSD object, so
iasl puts everything after first item as garbage. just delete whole
Name(_PSD {} from both places, it will ok.
Regards,
Alex.
On 5/3/07, Markus Feldmann <feldmann_markus@gmx.de> wrote:
> Alexey Starikovskiy schrieb:
> > Please remove error lines at the beginning of the file and try to
> > compile it again...
> >
> > On 5/1/07, Markus Feldmann <feldmann_markus@gmx.de> wrote:
> >> Alexey Starikovskiy schrieb:
> >> > 1. why do you think that making custom DSDT is going to help you?
> >> > 2. please attach your dsdt.dsl, so we could see on what iasl barks...
> >> >> From your report it looks like you trying to fed it with some non-aml
> >> > code.
> >> >
> >> > Regards,
> >> > Alex.
> >> >
> >> Sorry forgot the dsdt.dsl.
> >> Here it comes.
> >>
> >> bye Markus
> >>
> >>
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> Where can i upload my dsdt.dsl file ?
> Because my Emails which i did send are not arrived in this Newsgroup.
> I think its not allowed to send emails to this Newsgroup with Attachment.
>
> bye Markus
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-03 16:12 ` Alexey Starikovskiy
@ 2007-05-04 16:30 ` Markus Feldmann
2007-05-06 13:32 ` Markus Feldmann
1 sibling, 0 replies; 9+ messages in thread
From: Markus Feldmann @ 2007-05-04 16:30 UTC (permalink / raw)
To: linux-acpi
Alexey Starikovskiy schrieb:
> I already received your dsdt.dsl to my mailbox. I answered as well,
> but your provider seem to block whole gmail.com domain.
> Lets try to go without attachements:
> First error -- move Stall() function out of Return().
> Second error -- you have wrong length for optional _PSD object, so
> iasl puts everything after first item as garbage. just delete whole
> Name(_PSD {} from both places, it will ok.
>
> Regards,
> Alex.
Hi Alex,
i have changed some settings in my gmx account to receive mails from
gmail.
It should work now.
I have moved out Stall(0x0F),
########################
{
Stall (0x0F)
Return ()
}
########################
and i have deleted,
###########################
Name (_PSD, Package (0x01)
{
Package (0x05)
{
0x05
0x00
0x00000000,
0x000000FD
}
})
#############################
But then i got this errors,
#########################################################
dsdt_2.6.21.dsl 20: Name (_T00, 0x00)
Warning 1097 - ^ Unknown reserved name (_T00)
dsdt_2.6.21.dsl 6218: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6232: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6247: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6262: Acquire (MUTE, 0x0FFF)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6276: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6291: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6306: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6504: Method (WFZF, 1, NotSerialized)
Warning 1086 - ^ Not all control paths return a
value (WFZF)
dsdt_2.6.21.dsl 6520: #Return ()
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6597: #Name (_PSD, Package (0x01)
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6598: #{
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6599: # Package (0x05)
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6600: # {
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6601: # 0x05,
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6602: # 0x00,
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6603: # 0x00000000,
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6604: # 0x000000FD
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6605: # }
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6606: #})
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6607: Zero
Error 4094 - ^ syntax error, unexpected PARSEOP_ZERO
dsdt_2.6.21.dsl 6662: #Name (_PSD, Package (0x01)
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6663: #{
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6664: # Package (0x05)
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6665: # {
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6666: # 0x05,
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6667: # 0x00,
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6668: # 0x00000000,
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6669: # 0x000000FD
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6670: # }
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6671: #})
Error 4094 - ^ Invalid character (0x23), expecting ASL
keyword or name
dsdt_2.6.21.dsl 6672: Zero
Error 4094 - ^ syntax error, unexpected PARSEOP_ZERO
ASL Input: dsdt_2.6.21.dsl - 7678 lines, 256455 bytes, 2870 keywords
Compilation complete. 23 Errors, 9 Warnings, 0 Remarks, 701 Optimizations
#########################################################
bye Markus
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK
2007-05-03 16:12 ` Alexey Starikovskiy
2007-05-04 16:30 ` Markus Feldmann
@ 2007-05-06 13:32 ` Markus Feldmann
1 sibling, 0 replies; 9+ messages in thread
From: Markus Feldmann @ 2007-05-06 13:32 UTC (permalink / raw)
Cc: linux-acpi
Alexey Starikovskiy schrieb:
> I already received your dsdt.dsl to my mailbox. I answered as well,
> but your provider seem to block whole gmail.com domain.
> Lets try to go without attachements:
> First error -- move Stall() function out of Return().
> Second error -- you have wrong length for optional _PSD object, so
> iasl puts everything after first item as garbage. just delete whole
> Name(_PSD {} from both places, it will ok.
>
> Regards,
> Alex.
Hi Alex,
ok i have deleted the second error and moved out the stall() function.
Then i get this messages,
######################################################################
feld-bertlap:~/acpi/dsdt# iasl -tc dsdt_2.6.21.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20060912 [Dec 20 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
dsdt_2.6.21.dsl 20: Name (_T00, 0x00)
Warning 1097 - ^ Unknown reserved name (_T00)
dsdt_2.6.21.dsl 6218: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6232: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6247: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6262: Acquire (MUTE, 0x0FFF)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6276: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6291: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6306: Acquire (MUTE, 0x03E8)
Warning 1103 - Possible operator timeout is ignored ^
dsdt_2.6.21.dsl 6504: Method (WFZF, 1, NotSerialized)
Warning 1086 - ^ Not all control paths return a
value (WFZF)
dsdt_2.6.21.dsl 6598: Zero
Error 4094 - ^ syntax error, unexpected PARSEOP_ZERO
dsdt_2.6.21.dsl 6653: Zero
Error 4094 - ^ syntax error, unexpected PARSEOP_ZERO
ASL Input: dsdt_2.6.21.dsl - 7659 lines, 256009 bytes, 2868 keywords
Compilation complete. 2 Errors, 9 Warnings, 0 Remarks, 701 Optimizations
###################################################################
bye Markus
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2007-05-06 13:32 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-01 9:40 syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK Markus Feldmann
2007-05-01 10:08 ` Alexey Starikovskiy
2007-05-01 10:38 ` Markus Feldmann
[not found] ` <46371966.2020300@gmx.de>
2007-05-01 13:38 ` Alexey Starikovskiy
2007-05-01 18:43 ` Markus Feldmann
2007-05-03 6:35 ` Markus Feldmann
2007-05-03 16:12 ` Alexey Starikovskiy
2007-05-04 16:30 ` Markus Feldmann
2007-05-06 13:32 ` Markus Feldmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox