From: Jan Slezak <jan.slezak-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
To: Stephen Dawkins <stephen-d-1bEbUFD75cm9FHfhHBbuYA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Dell Latitude C600 Problems
Date: Mon, 17 Feb 2003 17:27:21 +0100 [thread overview]
Message-ID: <3E510D69.AA5BA254@centrum.cz> (raw)
In-Reply-To: 20030217140246.GA371@freya.elandtech.co.uk
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Try this.
You can find a few words about this fix here:
http://sourceforge.net/mailarchive/message.php?msg_id=3649920
Regards
Jan
Stephen Dawkins píše:
>
> Hi
>
> I'm running kernel 2.4.21-pre3, with the last ACPI patch and the lastest
> version of my BIOS (A22). The problem I am having is that all the information
> in my /proc/acpi/battery/BAT0/* is blank, or set to 0 (apart from wether
> or not it's present).
>
> There was someone one the list a while ago who had the same problem with
> a dell. Does anyone know how I can fix it? or where I can get the
> relavent knowledge on how to fix it?
>
> Regards
> Stephen
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
[-- Attachment #2: dsdt.dsl.dell.gz --]
[-- Type: application/x-gzip, Size: 8204 bytes --]
[-- Attachment #3: dsdt.dsl.dell.patch.gz --]
[-- Type: application/x-gzip, Size: 748 bytes --]
prev parent reply other threads:[~2003-02-17 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 14:02 Dell Latitude C600 Problems Stephen Dawkins
2003-02-17 16:27 ` Jan Slezak [this message]
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=3E510D69.AA5BA254@centrum.cz \
--to=jan.slezak-arb0bu7prfprbkcemvbida@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stephen-d-1bEbUFD75cm9FHfhHBbuYA@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