public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Miguel Pires Neves <lneves-3+EeCmRbAIo+BYJ/izffpQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Problems with battery info
Date: Mon, 26 Aug 2002 23:31:39 +0100	[thread overview]
Message-ID: <E17jSOa-0000F3-00@incognito> (raw)

Hi everybody,

It is not the first time I post this subject but until now I got no answer, 
perhaps because I included it in the middle of others.

I'm still using the 20020403 acpi patch on top of 2.4.18 because with recent 
versions I don't get a correct battery info (it says that the battery is NiMH 
of 4500 mWh instead of the 3200 mWh my LiIon battery really has, causing a 
wrong battery level information trough WMACPI). 

This behaviour used to happen with the acpi code before february, but then I 
used to change a constant value in ectransx.c (a timeout if I remember) from 
100 to 500 (us ???) to solve it. With the acpi code between February and 
April this wasn't necessary anymore.

I must admit I've not tried all versions from April till now, but I tried 
several, 20020716 as the last one, and the problem reappeared, and I don't 
know what I can do to overcome it.

In dmesg I found the following messages:

[ACPI Debug] String: ========= BAT1 UPBI =========
dsmthdat-0433 [22] Ds_method_data_get_val: Uninitialized Local[3] at node 
c7b6b54c
dsmthdat-0433 [22] Ds_method_data_get_val: Uninitialized Local[3] at node 
c7b6b54c

My laptop is a COMPAQ Presario 12XL515 (1200 series) and as it is known, I 
have to override the DSDT in order to have battery status and info. I patched 
the DSDT following some instructions from Paul Diefenbaugh, but probably I 
let some bugs untouched. I don't know if any of these can cause problems.

My original dsdt disassembled with AD.EXE from PHOENIX, my patched dsdt 
(dsdt_n.asl) and dmesg after booting kernel 2.4.18 + acpi-20020726 + 
swsusp-beta11 are on :

http://www.estg.iplei.pt/~lneves/files-cpq12xl515.tgz

Another persistent problem is the absence of events. My machine probably has 
the firmware bugs Juliuzs pointed out. I tried the kacpid patch some time ago 
but it conflicted with swsusp. With a more recent version which was supposed 
to cooperate with swsusp I get a defunct kacpid task. This is not so 
important to me as the battery info, but of course it limits the usefulness 
of ACPI.

I would appreciate any help to overcome these problems. A second analysis on 
my DSDT would be helpful.

Best regards and keep up the good work.

Luís Neves





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2002-08-26 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 22:31 Luis Miguel Pires Neves [this message]
     [not found] ` <E17jSOa-0000F3-00-MNhIyYEChGthl2p70BpVqQ@public.gmane.org>
2002-08-30 17:41   ` Problems with battery info Ducrot Bruno
  -- strict thread matches above, loose matches on Subject: below --
2002-08-30 15:35 Black, Richard (Hou)
2002-08-30 20:44 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=E17jSOa-0000F3-00@incognito \
    --to=lneves-3+eecmrbaio+byj/izffpq@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