public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Volcko <konference-X2ABGLaSPc4@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: A30-303 - acpi-20040211-2.4.25 - battery state error
Date: Sun, 29 Feb 2004 20:50:38 +0100	[thread overview]
Message-ID: <4042428E.8000702@pcs.cz> (raw)

Hello all!!

  On my Toshiba A30-303 - vanilla kernel 2.4.25 (acpi 20040116) or 
kernel 2.4.25 + acpi-20040211-2.4.25.diff.bz2
or kernel 2.4.24 + acpi-20040211-2.4.24.diff.bz2 I have problem with 
battery state monitoring ...  aproximately after 15-45 minutes of 
computer running I don't get right battery state. For monitoring I am 
using KDE Kapacity program, which check state of battery each 60 s. 
(errors described below)

[root-BuUY8psAA2Y@public.gmane.org /]# cat /proc/acpi/battery/BAT1/state
present:                 yes
ERROR: Unable to read battery status

/var/log/messages is full of folowing messages:
Feb 29 19:13:22 sys kernel: acpi_battery-0195 [998] 
acpi_battery_get_statu: Error evaluating _BST
Feb 29 19:13:42 sys kernel:  dswload-0279: *** Error: Looking up [PBST] 
in namespace, AE_ALREADY_EXISTS
Feb 29 19:13:42 sys kernel:  psparse-0588 [1005] ps_parse_loop         : 
During name lookup/catalog, AE_ALREADY_EXISTS

I found thread with similar problem (2.6.3 + D600 + battery state + 
BUG?? [Was] Battery status sometimes missing), but no solution.

Any idea what is wrong?

With regard Vladimir Volcko

PS: sorry for my english ;-)




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

                 reply	other threads:[~2004-02-29 19:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4042428E.8000702@pcs.cz \
    --to=konference-x2abglaspc4@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