public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: ultrakorne <ultrakorne-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: can't read battery, dsdt bugged?
Date: Tue, 23 Nov 2004 16:53:10 +0100	[thread overview]
Message-ID: <41A35CE6.90803@paranoici.org> (raw)

Hi, i have a acer laptop (travelmate 4501LCi) and i have installed 
ubuntu warty 4.10 (kernel 2.6.8.1)
the battery applet didnt works... this because /proc/acpi/battery/ is empty!
ps -e | grep acpi
     5 ?        00:00:00 kacpid
  3977 ?        00:00:00 acpid

so i disassembled my dsdt to see if i get compiling errors.. i only get 
3 warnings. here comes the first question, i got only warning no 
errors.. so my dsdt is ok or the cause i cant read my battery is those 3 
warnings?

i tryed to fix this out, i fix the first, but not the last 2.

first warning:
dsdt.dsl   245:     Method (_WAK, 1, NotSerialized)
Warning  2026 -                ^ Reserved method must return a value (_WAK)

i fix this adding this line at the end of the involved method
Return(Package(0x02){0x00, 0x00})
just before the last }

the others to warning are on the same line:
dsdt.dsl  4508:                         Method (_STA, 0, NotSerialized)
Warning  2019 -                                    ^ Not all control 
paths return a value (_STA)

dsdt.dsl  4508:                         Method (_STA, 0, NotSerialized)
Warning  2026 -                                    ^ Reserved method 
must return a value (_STA)

this is a big if statment with an else Return (0x08)

i just remove the last else return and i left only the return...

now compiling error are 0. are those fixes correct?
and the most important thing, could those warnings be my problem... if 
not what should i check?



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

             reply	other threads:[~2004-11-23 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 15:53 ultrakorne [this message]
     [not found] ` <41A35CE6.90803-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>
2004-11-23 16:06   ` can't read battery, dsdt bugged? Pedro Venda
     [not found]     ` <41A36560.90701@paranoici.org>
     [not found]       ` <41A36560.90701-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>
2004-11-23 16:52         ` Pedro Venda
     [not found]           ` <41A3709F.7020404@paranoici.org>
     [not found]             ` <41A3709F.7020404-XtQPfPCVGG7srOwW+9ziJQ@public.gmane.org>
2004-11-23 18:11               ` Pedro Venda

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=41A35CE6.90803@paranoici.org \
    --to=ultrakorne-xtqpfpcvgg7sroww+9zijq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox