From: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
To: Cüneyt <cu_lists-iP/H7R5l9gZBDgjK7y7TUQ@public.gmane.org>
Cc: Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Is it possible for ACPI to blow up the battery?
Date: Fri, 28 Jan 2005 09:41:17 -0500 [thread overview]
Message-ID: <41FA4F0D.2050104@bartol.udel.edu> (raw)
In-Reply-To: <41F7FD56.8090309-iP/H7R5l9gZBDgjK7y7TUQ@public.gmane.org>
Cüneyt wrote:
> Hi all,
>
> It may be really a dumb question, but I've really no idea.
>
> I have a Samsung P10 and found at behnel.de & SF-ACPI page some
> instructions to patch the DSDT table under Suse 9.1pro. I followed those
> as close as I can and I guess ACPI works somehow. Well, wakeup after
> sleep and CPU-throttling doesn't work though :(
>
> Now to my dismay the battery stopped charging at all, it is completely
> empty. No matter what I do, it doesn't get charged. The battery is about
> 2 yrs old but was pretty OK before, i.e. lasted about 1.5 hrs unplugged.
> Is it possible for DSDT patches to blow up the battery & charging units
> or you think the battery's (physically) died all of a sudden?
Can I make a gess that your battery is Lithium Ion? LiIon batteries
typically last for 2 years *after manufacture*, irrespective of how many
times they are charged and/or discharged. See:
http://www.batteryuniversity.com/parttwo-34.htm
It may be that your battery has reached the end of its life, nothing to
do with ACPI.
cheers,
Rich
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-28 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 20:28 Is it possible for ACPI to blow up the battery? Cüneyt
[not found] ` <41F7FD56.8090309-iP/H7R5l9gZBDgjK7y7TUQ@public.gmane.org>
2005-01-28 12:04 ` Pavel Machek
2005-01-28 14:41 ` Rich Townsend [this message]
[not found] ` <41FA4F0D.2050104-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
2005-01-30 22:19 ` Cüneyt
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=41FA4F0D.2050104@bartol.udel.edu \
--to=rhdt-obnux95toyn10jlvftc4ga@public.gmane.org \
--cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=cu_lists-iP/H7R5l9gZBDgjK7y7TUQ@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.