* DSDT on Averatec 1050
@ 2006-05-11 15:55 Paul Wagner
2006-05-11 16:42 ` Thomas Renninger
2006-08-30 19:07 ` newhren
0 siblings, 2 replies; 10+ messages in thread
From: Paul Wagner @ 2006-05-11 15:55 UTC (permalink / raw)
To: linux-acpi
Hi Folks,
tried to get Linux (Slackware 10.1 with Kernel 2.6.13) to run on my
Averatec 1050. Unfortunately, ACPI doesn't work as supposed: No thermal
zones, no fan, no CPU temperature, kernel error messages (see below).
I disassembled the DSDT, and recompiled it using Intels iasl, and got a
bunch of error and warnings (see below). Unfortunately, I do not
understand a single bit of this ASL code, and the manual doesn't really
help me much. I figured out how to get rid of one error (the field
thing), but I do not have the slightest idea how to handle the others.
Can anybody please help or point me to some source of help with this
damn DSDT thing? I googled a lot last night, but weren't too successful.
Thanks a lot,
Paul
--------------------------- 8< ------------------------
iasl -tc complains about:
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20060421 [May 10 2006]
Copyright (C) 2000 - 2006 Intel Corporation
Supports ACPI Specification Revision 3.0a
dsdt.dsl 20: Name (_T04, 0x00)
Warning 1097 - ^ Unknown reserved name (_T04)
dsdt.dsl 21: Name (_T03, 0x00)
Warning 1097 - ^ Unknown reserved name (_T03)
dsdt.dsl 22: Name (_T02, 0x00)
Warning 1097 - ^ Unknown reserved name (_T02)
dsdt.dsl 23: Name (_T01, 0x00)
Warning 1097 - ^ Unknown reserved name (_T01)
dsdt.dsl 24: Name (_T00, 0x00)
Warning 1097 - ^ Unknown reserved name (_T00)
dsdt.dsl 513: C0E0, 8,
Error 4027 - ^ Access width of Field Unit
extends beyond region limit
dsdt.dsl 514: C0E1, 8
Error 4027 - ^ Access width of Field Unit
extends beyond region limit
dsdt.dsl 1545: Acquire (\ECMX, 0xA000)
Warning 1103 - Possible operator timeout is ignored ^
dsdt.dsl 1559: Acquire (\MUEC, 0x8000)
Warning 1103 - Possible operator timeout is ignored ^
dsdt.dsl 1649: OperationRegion (IO, SystemIO,
DPRT, 0x05)
Error 4094 - ^ parse error,
unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
PARSEOP_NAMESTRING
dsdt.dsl 1650: Field (IO, ByteAcc, Lock, Preserve)
Error 4094 - ^ parse error,
unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
PARSEOP_NAMESTRING
dsdt.dsl 1657: Field (IO, ByteAcc, Lock, Preserve)
Error 4094 - ^ parse error,
unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
PARSEOP_NAMESTRING
dsdt.dsl 1666: Return (LNot (INPS))
Error 4062 - Object does not exist ^ (INPS)
dsdt.dsl 1671: Return (OUTS)
Error 4062 - Object does not exist ^ (OUTS)
dsdt.dsl 1917: Store (DAT0, Local0)
Error 4062 - Object does not exist ^ (DAT0)
dsdt.dsl 1926: Store (0x80, CMD0)
Error 4062 - Object does not exist ^ (CMD0)
dsdt.dsl 1929: Store (Arg0, DAT0)
Error 4062 - Object does not exist ^
(DAT0)
dsdt.dsl 1932: Store (DAT0, Local0)
Error 4062 - Object does not exist ^ (DAT0)
dsdt.dsl 1947: Store (0x81, CMD0)
Error 4062 - Object does not exist ^ (CMD0)
dsdt.dsl 1950: Store (Arg0, DAT0)
Error 4062 - Object does not exist ^
(DAT0)
dsdt.dsl 1953: Store (Arg1, DAT0)
Error 4062 - Object does not exist
^ (DAT0)
ASL Input: dsdt.dsl - 4588 lines, 159794 bytes, 2285 keywords
Compilation complete. 14 Errors, 7 Warnings, 0 Remarks, 791 Optimizations
--------------------------- 8< ------------------------
The kernel sometimes (at boot and during operation) says:
ACPI-0142: *** Error: Store into Alias - should never happen
ACPI-1172: *** Error: Method execution failed
[\_SB_.PCI0.SBRG.EC0_._Q0C] (Node c14b4c20), AE_AML_INTERNAL
--------------------------- 8< ------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: DSDT on Averatec 1050
2006-05-11 15:55 DSDT on Averatec 1050 Paul Wagner
@ 2006-05-11 16:42 ` Thomas Renninger
2006-05-11 17:17 ` Paul-Jürgen Wagner
2006-08-30 19:07 ` newhren
1 sibling, 1 reply; 10+ messages in thread
From: Thomas Renninger @ 2006-05-11 16:42 UTC (permalink / raw)
To: Paul Wagner; +Cc: linux-acpi, robert.moore
On Thu, 2006-05-11 at 17:55 +0200, Paul Wagner wrote:
> Hi Folks,
>
> tried to get Linux (Slackware 10.1 with Kernel 2.6.13) to run on my
> Averatec 1050. Unfortunately, ACPI doesn't work as supposed: No thermal
> zones, no fan, no CPU temperature, kernel error messages (see below).
>
> I disassembled the DSDT, and recompiled it using Intels iasl, and got a
> bunch of error and warnings (see below). Unfortunately, I do not
> understand a single bit of this ASL code, and the manual doesn't really
> help me much. I figured out how to get rid of one error (the field
> thing), but I do not have the slightest idea how to handle the others.
>
> Can anybody please help or point me to some source of help with this
> damn DSDT thing? I googled a lot last night, but weren't too successful.
>
> dsdt.dsl 1649: OperationRegion (IO, SystemIO,
> DPRT, 0x05)
> Error 4094 - ^ parse error,
> unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> PARSEOP_NAMESTRING
>
> dsdt.dsl 1650: Field (IO, ByteAcc, Lock, Preserve)
> Error 4094 - ^ parse error,
> unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> PARSEOP_NAMESTRING
>
> dsdt.dsl 1657: Field (IO, ByteAcc, Lock, Preserve)
> Error 4094 - ^ parse error,
> unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> PARSEOP_NAMESTRING
You can workaround by renaming the field to XIO...
I send a patch to fix that long time ago... cannot find it anymore.
The problem is that IO is a keyword and the compiler does not notice
that it should be taken as a new Field definition here (same for REG and
DMA keywords?).
I thought this was added to acpica? Hopefully someone still has it lying
around or I can redo if it will be picked up.
---------------------------------------------------------------
For these object not exist messages:
dsdt.dsl 1929: Store (Arg0, DAT0)
Error 4062 - Object does not exist ^
(DAT0)
You need to add addtional external (DAT0) statements at the beginning of
your DSDT.
These variables are probably defined in SSDT. I think you have to
replace DAT0 with the whole path e.g. \_SB.xy.DAT0.
---------------------------------------------------------------
You probably have to increase the Operation Region size of the Operation
Region that corresponds to that field.
dsdt.dsl 513: C0E0, 8,
Error 4027 - ^ Access width of Field Unit
extends beyond region limit
Correct Example (Operation Region size is 0x1 byte (this is the one you
have to increase) and Field \DEBG is one byte (DBGP has 8 bit):
OperationRegion (\DEBG, SystemIO, 0x1080, 0x01)
Field (\DEBG, ByteAcc, NoLock, Preserve)
{
DBGP, 8
}
Incorrect Example (Operation Region size is 1 byte and Field \DEBG has
two bytes):
OperationRegion (\DEBG, SystemIO, 0x1080, 0x01)
Field (\DEBG, ByteAcc, NoLock, Preserve)
{
DBGP, 8
DBXY, 8
}
---------------------------------------------------------------
The kernel sometimes (at boot and during operation) says:
ACPI-0142: *** Error: Store into Alias - should never happen
ACPI-1172: *** Error: Method execution failed
[\_SB_.PCI0.SBRG.EC0_._Q0C] (Node c14b4c20), AE_AML_INTERNAL
This sounds unrelated to your DSDT errors, but sever. Robert extended
the Alias stuff some months ago, maybe something slipped in...
Best is you point us to the whole acpidump and whole dmesg output.
Thomas
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: DSDT on Averatec 1050
2006-05-11 16:42 ` Thomas Renninger
@ 2006-05-11 17:17 ` Paul-Jürgen Wagner
0 siblings, 0 replies; 10+ messages in thread
From: Paul-Jürgen Wagner @ 2006-05-11 17:17 UTC (permalink / raw)
To: trenn; +Cc: linux-acpi
Hi Thomas,
thanks for your prompt reply!
>>dsdt.dsl 1657: Field (IO, ByteAcc, Lock, Preserve)
>>Error 4094 - ^ parse error,
>>unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
>>PARSEOP_NAMESTRING
>
>
> You can workaround by renaming the field to XIO...
I thought of that for a microsecond, but was to anxious to rename things
I do not understand ;-)
> For these object not exist messages:
> dsdt.dsl 1929: Store (Arg0, DAT0)
> Error 4062 - Object does not exist ^
> (DAT0)
>
> You need to add addtional external (DAT0) statements at the beginning of
> your DSDT.
> These variables are probably defined in SSDT. I think you have to
> replace DAT0 with the whole path e.g. \_SB.xy.DAT0.
Sorry, but what is 'xy'?
> The kernel sometimes (at boot and during operation) says:
>
> ACPI-0142: *** Error: Store into Alias - should never happen
> ACPI-1172: *** Error: Method execution failed
> [\_SB_.PCI0.SBRG.EC0_._Q0C] (Node c14b4c20), AE_AML_INTERNAL
>
> This sounds unrelated to your DSDT errors, but sever. Robert extended
> the Alias stuff some months ago, maybe something slipped in...
>
> Best is you point us to the whole acpidump and whole dmesg output.
OK, will do that when I'm on my laptop again; may take some days.
BTW, does it hurt that I'm not using the latest kernel?
Paul
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DSDT on Averatec 1050
@ 2006-05-11 17:56 Moore, Robert
2006-05-19 13:02 ` Thomas Renninger
0 siblings, 1 reply; 10+ messages in thread
From: Moore, Robert @ 2006-05-11 17:56 UTC (permalink / raw)
To: trenn, Paul Wagner; +Cc: linux-acpi
May have gotten lost in the noise, please send to me.
Bob
> -----Original Message-----
> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> owner@vger.kernel.org] On Behalf Of Thomas Renninger
> Sent: Thursday, May 11, 2006 9:43 AM
> To: Paul Wagner
> Cc: linux-acpi@vger.kernel.org; Moore, Robert
> Subject: Re: DSDT on Averatec 1050
>
> On Thu, 2006-05-11 at 17:55 +0200, Paul Wagner wrote:
> > Hi Folks,
> >
> > tried to get Linux (Slackware 10.1 with Kernel 2.6.13) to run on my
> > Averatec 1050. Unfortunately, ACPI doesn't work as supposed: No
thermal
> > zones, no fan, no CPU temperature, kernel error messages (see
below).
> >
> > I disassembled the DSDT, and recompiled it using Intels iasl, and
got a
> > bunch of error and warnings (see below). Unfortunately, I do not
> > understand a single bit of this ASL code, and the manual doesn't
really
> > help me much. I figured out how to get rid of one error (the field
> > thing), but I do not have the slightest idea how to handle the
others.
> >
> > Can anybody please help or point me to some source of help with this
> > damn DSDT thing? I googled a lot last night, but weren't too
successful.
> >
> > dsdt.dsl 1649: OperationRegion (IO,
SystemIO,
> > DPRT, 0x05)
> > Error 4094 - ^ parse
error,
> > unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> > PARSEOP_NAMESTRING
> >
> > dsdt.dsl 1650: Field (IO, ByteAcc, Lock,
> Preserve)
> > Error 4094 - ^ parse error,
> > unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> > PARSEOP_NAMESTRING
> >
> > dsdt.dsl 1657: Field (IO, ByteAcc, Lock,
> Preserve)
> > Error 4094 - ^ parse error,
> > unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> > PARSEOP_NAMESTRING
>
> You can workaround by renaming the field to XIO...
>
> I send a patch to fix that long time ago... cannot find it anymore.
> The problem is that IO is a keyword and the compiler does not notice
> that it should be taken as a new Field definition here (same for REG
and
> DMA keywords?).
>
> I thought this was added to acpica? Hopefully someone still has it
lying
> around or I can redo if it will be picked up.
>
>
> ---------------------------------------------------------------
>
> For these object not exist messages:
> dsdt.dsl 1929: Store (Arg0, DAT0)
> Error 4062 - Object does not exist ^
> (DAT0)
>
> You need to add addtional external (DAT0) statements at the beginning
of
> your DSDT.
> These variables are probably defined in SSDT. I think you have to
> replace DAT0 with the whole path e.g. \_SB.xy.DAT0.
>
> ---------------------------------------------------------------
>
> You probably have to increase the Operation Region size of the
Operation
> Region that corresponds to that field.
>
> dsdt.dsl 513: C0E0, 8,
> Error 4027 - ^ Access width of Field
Unit
> extends beyond region limit
>
> Correct Example (Operation Region size is 0x1 byte (this is the one
you
> have to increase) and Field \DEBG is one byte (DBGP has 8 bit):
> OperationRegion (\DEBG, SystemIO, 0x1080, 0x01)
> Field (\DEBG, ByteAcc, NoLock, Preserve)
> {
> DBGP, 8
> }
>
> Incorrect Example (Operation Region size is 1 byte and Field \DEBG has
> two bytes):
> OperationRegion (\DEBG, SystemIO, 0x1080, 0x01)
> Field (\DEBG, ByteAcc, NoLock, Preserve)
> {
> DBGP, 8
> DBXY, 8
> }
>
> ---------------------------------------------------------------
>
> The kernel sometimes (at boot and during operation) says:
>
> ACPI-0142: *** Error: Store into Alias - should never happen
> ACPI-1172: *** Error: Method execution failed
> [\_SB_.PCI0.SBRG.EC0_._Q0C] (Node c14b4c20), AE_AML_INTERNAL
>
> This sounds unrelated to your DSDT errors, but sever. Robert extended
> the Alias stuff some months ago, maybe something slipped in...
>
> Best is you point us to the whole acpidump and whole dmesg output.
>
> Thomas
>
> -
> 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] 10+ messages in thread
* RE: DSDT on Averatec 1050
@ 2006-05-11 18:50 Moore, Robert
0 siblings, 0 replies; 10+ messages in thread
From: Moore, Robert @ 2006-05-11 18:50 UTC (permalink / raw)
To: Paul Wagner, linux-acpi
Please send the raw (undisassembled) DSDT.
> -----Original Message-----
> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> owner@vger.kernel.org] On Behalf Of Paul Wagner
> Sent: Thursday, May 11, 2006 8:56 AM
> To: linux-acpi@vger.kernel.org
> Subject: DSDT on Averatec 1050
>
> Hi Folks,
>
> tried to get Linux (Slackware 10.1 with Kernel 2.6.13) to run on my
> Averatec 1050. Unfortunately, ACPI doesn't work as supposed: No
thermal
> zones, no fan, no CPU temperature, kernel error messages (see below).
>
> I disassembled the DSDT, and recompiled it using Intels iasl, and got
a
> bunch of error and warnings (see below). Unfortunately, I do not
> understand a single bit of this ASL code, and the manual doesn't
really
> help me much. I figured out how to get rid of one error (the field
> thing), but I do not have the slightest idea how to handle the others.
>
> Can anybody please help or point me to some source of help with this
> damn DSDT thing? I googled a lot last night, but weren't too
successful.
>
> Thanks a lot,
>
> Paul
>
> --------------------------- 8< ------------------------
>
> iasl -tc complains about:
>
> Intel ACPI Component Architecture
> ASL Optimizing Compiler version 20060421 [May 10 2006]
> Copyright (C) 2000 - 2006 Intel Corporation
> Supports ACPI Specification Revision 3.0a
>
> dsdt.dsl 20: Name (_T04, 0x00)
> Warning 1097 - ^ Unknown reserved name (_T04)
>
> dsdt.dsl 21: Name (_T03, 0x00)
> Warning 1097 - ^ Unknown reserved name (_T03)
>
> dsdt.dsl 22: Name (_T02, 0x00)
> Warning 1097 - ^ Unknown reserved name (_T02)
>
> dsdt.dsl 23: Name (_T01, 0x00)
> Warning 1097 - ^ Unknown reserved name (_T01)
>
> dsdt.dsl 24: Name (_T00, 0x00)
> Warning 1097 - ^ Unknown reserved name (_T00)
>
> dsdt.dsl 513: C0E0, 8,
> Error 4027 - ^ Access width of Field
Unit
> extends beyond region limit
>
> dsdt.dsl 514: C0E1, 8
> Error 4027 - ^ Access width of Field
Unit
> extends beyond region limit
>
> dsdt.dsl 1545: Acquire (\ECMX, 0xA000)
> Warning 1103 - Possible operator timeout is ignored ^
>
> dsdt.dsl 1559: Acquire (\MUEC, 0x8000)
> Warning 1103 - Possible operator timeout is ignored ^
>
> dsdt.dsl 1649: OperationRegion (IO, SystemIO,
> DPRT, 0x05)
> Error 4094 - ^ parse
error,
> unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> PARSEOP_NAMESTRING
>
> dsdt.dsl 1650: Field (IO, ByteAcc, Lock,
> Preserve)
> Error 4094 - ^ parse error,
> unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> PARSEOP_NAMESTRING
>
> dsdt.dsl 1657: Field (IO, ByteAcc, Lock,
> Preserve)
> Error 4094 - ^ parse error,
> unexpected PARSEOP_IO, expecting error or PARSEOP_NAMESEG or
> PARSEOP_NAMESTRING
>
> dsdt.dsl 1666: Return (LNot (INPS))
> Error 4062 - Object does not exist ^ (INPS)
>
> dsdt.dsl 1671: Return (OUTS)
> Error 4062 - Object does not exist ^ (OUTS)
>
> dsdt.dsl 1917: Store (DAT0, Local0)
> Error 4062 - Object does not exist ^ (DAT0)
>
> dsdt.dsl 1926: Store (0x80, CMD0)
> Error 4062 - Object does not exist ^
(CMD0)
>
> dsdt.dsl 1929: Store (Arg0, DAT0)
> Error 4062 - Object does not exist ^
> (DAT0)
>
> dsdt.dsl 1932: Store (DAT0,
> Local0)
> Error 4062 - Object does not exist ^
> (DAT0)
>
> dsdt.dsl 1947: Store (0x81, CMD0)
> Error 4062 - Object does not exist ^
(CMD0)
>
> dsdt.dsl 1950: Store (Arg0, DAT0)
> Error 4062 - Object does not exist ^
> (DAT0)
>
> dsdt.dsl 1953: Store (Arg1,
DAT0)
> Error 4062 - Object does not
exist
> ^ (DAT0)
>
> ASL Input: dsdt.dsl - 4588 lines, 159794 bytes, 2285 keywords
> Compilation complete. 14 Errors, 7 Warnings, 0 Remarks, 791
Optimizations
>
> --------------------------- 8< ------------------------
>
> The kernel sometimes (at boot and during operation) says:
>
> ACPI-0142: *** Error: Store into Alias - should never happen
> ACPI-1172: *** Error: Method execution failed
> [\_SB_.PCI0.SBRG.EC0_._Q0C] (Node c14b4c20), AE_AML_INTERNAL
>
> --------------------------- 8< ------------------------
>
> -
> 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] 10+ messages in thread
* RE: DSDT on Averatec 1050
@ 2006-05-15 15:46 Moore, Robert
0 siblings, 0 replies; 10+ messages in thread
From: Moore, Robert @ 2006-05-15 15:46 UTC (permalink / raw)
To: Paul Wagner, linux-acpi; +Cc: trenn
>From dmesg:
> ACPI: Subsystem revision 20050408
> ACPI-0142: *** Error: Store into Alias - should never happen
I believe this problem was fixed in 20060127:
27 January 2006. Summary of changes for version 20060127:
1) ACPI CA Core Subsystem:
Fixed a problem where Alias ASL operators are sometimes not correctly
resolved, in both the interpreter and the iASL compiler.
> -----Original Message-----
> From: Paul Wagner [mailto:paul_spam@gmx.at]
> Sent: Monday, May 15, 2006 4:53 AM
> To: linux-acpi@vger.kernel.org
> Cc: Moore, Robert; trenn@suse.de
> Subject: Re: DSDT on Averatec 1050
>
> Robert, Thomas,
>
> attached you'll find the raw dsdt, the output of acpidump and dmesg.
>
> Note: This was my first try on a self-compiled kernel, and apparently
I
> forgot some things (e.g. NTFS support, which is requested by an
> fstab-entry). Some modules seem to be missing, too. But I suppose that
> these errors are unrelated to the ACPI troubles.
>
> Thanks for your support,
>
> Paul
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DSDT on Averatec 1050
2006-05-11 17:56 Moore, Robert
@ 2006-05-19 13:02 ` Thomas Renninger
0 siblings, 0 replies; 10+ messages in thread
From: Thomas Renninger @ 2006-05-19 13:02 UTC (permalink / raw)
To: Moore, Robert; +Cc: Paul Wagner, linux-acpi
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
On Thu, 2006-05-11 at 10:56 -0700, Moore, Robert wrote:
> May have gotten lost in the noise, please send to me.
Attached are two patches:
1) Fixes compiler nameclash if IO keyword is used as field declaration
2) If (generic, dsdt.dsl) output file is already created with
insufficient
privileges to the current user, iasl -d dsdt segfaults.
This patch makes iasl to exit gracefully.
Thomas
[-- Attachment #2: fix_IO_nameclash.patch --]
[-- Type: text/x-patch, Size: 614 bytes --]
Fixes compiler nameclash if IO keyword is used as field declaration
Signed-off-by: Thomas Renninger <trenn@suse.de>
--- acpica-unix-20050624/compiler/aslcompiler.y.orig 2005-09-06 16:46:21.000000000 +0200
+++ acpica-unix-20050624/compiler/aslcompiler.y 2005-09-06 15:40:37.000000000 +0200
@@ -2951,6 +2951,7 @@
NameString
: NameSeg {}
| PARSEOP_NAMESTRING {$$ = TrCreateValuedLeafNode (PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) AslCompilerlval.s);}
+ | PARSEOP_IO {$$ = TrCreateValuedLeafNode (PARSEOP_IO, (ACPI_NATIVE_INT) "IO");}
;
NameSeg
[-- Attachment #3: iasl_invalid_output_file.patch --]
[-- Type: text/x-patch, Size: 1085 bytes --]
If (generic, dsdt.dsl) output file is already created with insufficient
privileges to the current user, iasl -d xy segfaults.
This patch fixes that.
Reference: https://bugzilla.novell.com/show_bug.cgi?id=152112
Signed-off-by: Thomas Renninger <trenn@suse.de>
acpica-unix-20060127/common/adisasm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: acpica-unix-20060127/common/adisasm.c
===================================================================
--- acpica-unix-20060127/common/adisasm.c
+++ acpica-unix-20060127/common/adisasm.c
@@ -125,6 +125,7 @@
#include "acapps.h"
#include <stdio.h>
+#include <stdlib.h>
#include <string.h>
#include <time.h>
@@ -549,9 +550,8 @@ AdAmlDisassemble (
File = fopen (DisasmFilename, "w+");
if (!File)
{
- fprintf (stderr, "Could not open output file\n");
- Status = AE_ERROR;
- goto Cleanup;
+ fprintf (stderr, "Could not open output file %s\n", DisasmFilename);
+ exit (EXIT_FAILURE);
}
AcpiOsRedirectOutput (File);
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: DSDT on Averatec 1050
@ 2006-05-23 20:33 Moore, Robert
0 siblings, 0 replies; 10+ messages in thread
From: Moore, Robert @ 2006-05-23 20:33 UTC (permalink / raw)
To: trenn; +Cc: Paul Wagner, linux-acpi
+ | PARSEOP_IO {$$ = TrCreateValuedLeafNode
(PARSEOP_IO, (ACPI_NATIVE_INT) "IO");}
I would imagine that we would want to type the node as
PARSEOP_NAMESTRING.
I think there are a few more like this, "DMA" comes to mind immediately.
Bob
> -----Original Message-----
> From: Thomas Renninger [mailto:trenn@suse.de]
> Sent: Friday, May 19, 2006 6:03 AM
> To: Moore, Robert
> Cc: Paul Wagner; linux-acpi@vger.kernel.org
> Subject: RE: DSDT on Averatec 1050
>
> On Thu, 2006-05-11 at 10:56 -0700, Moore, Robert wrote:
> > May have gotten lost in the noise, please send to me.
>
> Attached are two patches:
> 1) Fixes compiler nameclash if IO keyword is used as field
declaration
> 2) If (generic, dsdt.dsl) output file is already created with
> insufficient
> privileges to the current user, iasl -d dsdt segfaults.
> This patch makes iasl to exit gracefully.
>
> Thomas
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: DSDT on Averatec 1050
2006-05-11 15:55 DSDT on Averatec 1050 Paul Wagner
2006-05-11 16:42 ` Thomas Renninger
@ 2006-08-30 19:07 ` newhren
2006-09-01 9:39 ` Paul Wagner
1 sibling, 1 reply; 10+ messages in thread
From: newhren @ 2006-08-30 19:07 UTC (permalink / raw)
To: linux-acpi
Paul Wagner <paul_spam <at> gmx.at> writes:
>
> Hi Folks,
>
> tried to get Linux (Slackware 10.1 with Kernel 2.6.13) to run on my
> Averatec 1050. Unfortunately, ACPI doesn't work as supposed: No thermal
> zones, no fan, no CPU temperature, kernel error messages (see below).
>
Hi, Paul
I also recently faced the same problem when trying to compile DSDT for
Averatec 1020. I fixed all the errors (unfortunately, before I found
this thread). The patched DSDT is posted at
http://acpi.sourceforge.net/dsdt/view.php?id=667 . For the record, can
you also post your original raw (non-decompiled) DSDT for av1050 there?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: DSDT on Averatec 1050
2006-08-30 19:07 ` newhren
@ 2006-09-01 9:39 ` Paul Wagner
0 siblings, 0 replies; 10+ messages in thread
From: Paul Wagner @ 2006-09-01 9:39 UTC (permalink / raw)
To: linux-acpi
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Hi newhren,
here you are :-)
I read that you mapped Fn+F3 and Fn+F4 to adjust fan speed. On the
AV1050, these keys should switch display and send the unit to suspend
mode (not yet implemented on my box), so I personaly do not really dig
your mapping.
Paul
newhren wrote:
> Paul Wagner <paul_spam <at> gmx.at> writes:
>
>
>>Hi Folks,
>>
>>tried to get Linux (Slackware 10.1 with Kernel 2.6.13) to run on my
>>Averatec 1050. Unfortunately, ACPI doesn't work as supposed: No thermal
>>zones, no fan, no CPU temperature, kernel error messages (see below).
>>
>
>
> Hi, Paul
>
> I also recently faced the same problem when trying to compile DSDT for
> Averatec 1020. I fixed all the errors (unfortunately, before I found
> this thread). The patched DSDT is posted at
> http://acpi.sourceforge.net/dsdt/view.php?id=667 . For the record, can
> you also post your original raw (non-decompiled) DSDT for av1050 there?
>
>
>
> -
> 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
>
>
>
[-- Attachment #2: averatec_1050.dsdt --]
[-- Type: application/octet-stream, Size: 21289 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2006-09-01 9:39 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-11 15:55 DSDT on Averatec 1050 Paul Wagner
2006-05-11 16:42 ` Thomas Renninger
2006-05-11 17:17 ` Paul-Jürgen Wagner
2006-08-30 19:07 ` newhren
2006-09-01 9:39 ` Paul Wagner
-- strict thread matches above, loose matches on Subject: below --
2006-05-11 17:56 Moore, Robert
2006-05-19 13:02 ` Thomas Renninger
2006-05-11 18:50 Moore, Robert
2006-05-15 15:46 Moore, Robert
2006-05-23 20:33 Moore, Robert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).