From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: bulk-wOwPqRMbTBJeoWH0uzbU5w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI errors on ECS G220 laptop
Date: Thu, 06 Oct 2005 18:44:35 +0200 [thread overview]
Message-ID: <43455473.6040209@suse.de> (raw)
In-Reply-To: <1128480553.11538.9.camel-HeUoCuMXkaHnRTjf+tVgBKY7qTmLiVr45NbjCUgZEJk@public.gmane.org>
Junk Mail Recipient wrote:
> I recently purchased an ECS G220 laptop with the hopes of running Suse
> 9.3 on it. I am pretty well outta luck as far as acpi goes though. The
> battery monitor doesn't work at all. It perpetually shows a 1% charge.
> It also doesn't seem to be getting any thermal information. CPU scaling
> can be done manually, but is not happening automatically.
>
> I followed the how-to on broken dsdt and from iasl I get 1 error and no
> warnings. Unfortunately this seems to be a pretty generic syntax error
> and I am at a loss on how to track it down or where to go from here.
>
> Intel ACPI Component Architecture
> ASL Optimizing Compiler / AML Disassembler version 20050309 [Mar 19
> 2005]
> Copyright (C) 2000 - 2005 Intel Corporation
> Supports ACPI Specification Revision 3.0
>
> dsdt.dsl 1901: If (SS1)
> Error 1037 - ^ syntax error, unexpected PARSEOP_IF
Create an _INI function in \_SB scope (if there is not already one) and place
the If(SSX){...} code there.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
next prev parent reply other threads:[~2005-10-06 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 2:49 ACPI errors on ECS G220 laptop Junk Mail Recipient
[not found] ` <1128480553.11538.9.camel-HeUoCuMXkaHnRTjf+tVgBKY7qTmLiVr45NbjCUgZEJk@public.gmane.org>
2005-10-06 16:44 ` Thomas Renninger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-07 21:55 Moore, Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43455473.6040209@suse.de \
--to=trenn-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bulk-wOwPqRMbTBJeoWH0uzbU5w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.