public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: Andre Messerschmidt <a.messerschmidt-hi6Y0CQ0nG0@public.gmane.org>
Subject: Re: ASUS M6800N: battery0 not present
Date: Wed, 18 Feb 2004 11:55:24 +0100	[thread overview]
Message-ID: <4033449C.7030403@pca.it> (raw)
In-Reply-To: <200402172143.27818.gielj-TFexGAE6Ty5xRhk+k0m/rQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

on 02/17/04 21:43, Jan Philipp Giel wrote:
> I think Andre meant that the battery things are visible in acpi but
they show
> the battery as absent - so they do not really work.
yes, I know this, but anyway it's better than normal situation ;-)

> There is a BIOS Update available for the M6800N. It was mailed to
someone who
> had problems with some ACPIEC Message while running Windows (ASUSProbe).
> The DSDT (see attachment) has changed with the BIOS Update. Maybe this
helps
> someone to fix the DSDT.
Yes, when I searched for info about GNU/Linux on ASUS M6800N I found
your page and I already upgrade my BIOS to the latest available 0205A.

Now, the strange things:
- - I suppose the DSDT you attached comes from the new BIOS, am I right?
Because in this case, the DSDT I got from my new BIOS (I attacched) is
different from your when I disassemble them with 'iasl-20030918'. In
which way have you caught your DSDT? I did:
	cat /proc/acpi/dsdt > [file]

- - in the 2 cases, the new DSDT has just 5 errors and not >200 as the old
one. ASAP I'll try to correct it to see what changes

Thx, bye,
Gismo / Luca

PS to Andre: I still don't know if you're subscribed to the list...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAM0SbVAp7Xm10JmkRAvZVAJ9UJ9anpV4cUHBrAOU/NGK5/uYU9ACfdUGA
CKvbbc6sxnEru6t46sasXnQ=
=4Qzl
-----END PGP SIGNATURE-----

[-- Attachment #2: ASUS-M6842NWH-M6N_DSDT-BIOS-0205A.001_original.dat.gz --]
[-- Type: application/x-gzip, Size: 10188 bytes --]

  parent reply	other threads:[~2004-02-18 10:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 17:28 ASUS M6800N: battery0 not present Luca Capello
     [not found] ` <40324F44.60006-wlebWZzHoyE@public.gmane.org>
2004-02-17 20:43   ` Jan Philipp Giel
     [not found]     ` <200402172143.27818.gielj-TFexGAE6Ty5xRhk+k0m/rQ@public.gmane.org>
2004-02-18 10:55       ` Luca Capello [this message]
2004-02-18  7:52   ` Andre Messerschmidt
     [not found]     ` <200402180852.16189.a.messerschmidt-hi6Y0CQ0nG0@public.gmane.org>
2004-02-18 11:11       ` Luca Capello
     [not found]         ` <40334874.6000109-wlebWZzHoyE@public.gmane.org>
2004-02-18 18:31           ` Andre Messerschmidt
2004-02-18 17:13   ` Luca Capello
2004-03-04 14:12   ` Luca Capello
2004-03-04 14:39     ` Jan Philipp Giel
     [not found]       ` <002401c401f6$8cfcd920$3a392886-NmZw/y+ms+s@public.gmane.org>
2004-03-20 11:05         ` Luca Capello

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=4033449C.7030403@pca.it \
    --to=luca-wlebwzzhoye@public.gmane.org \
    --cc=a.messerschmidt-hi6Y0CQ0nG0@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