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: Re: ASUS M6800N: battery0 not present
Date: Wed, 18 Feb 2004 12:11:48 +0100 [thread overview]
Message-ID: <40334874.6000109@pca.it> (raw)
In-Reply-To: <200402180852.16189.a.messerschmidt-hi6Y0CQ0nG0@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 02/18/04 08:52, Andre Messerschmidt wrote:
> I don't have any errors if I use my DSDT. See the attached output from
dmesg
> for how it looks here with a 2.4.21.
yes, I saw, and this is the same I'd like to have. Anyway, I forgot to
advise that I upgraded to the new BIOS (0205A.001) and so maybe this is
a problem or cause something strange. I even tried a kernel-2.4.21 +
ACPI-20030619 + 'ACPI DSDT in initrd', but nothing changed, so maybe the
problem in my case is different.
Just to avoid mistackes: can you attach you customized compiled DSDT?
I'll give it a try and report the results.
> I reckon that you are right with your assumption that the new DSDT
table is
> not used, but I don't know why, since I have no insights in ACPI.
Another strange thing is this one: as I reported in my first post, the
DSDT I've in /proc/acpi/dsdt if I boot with your customized compiled
DSDT and you customized DSDT are different. I mean:
- - ./iasl -c [your DSDT].dsl
- - cp DSDT.aml /boot/
- - reboot
- - cat /proc/acpi/dsdt > 2.6.2-initrd.dat
- - ./iasl -d 2.6.2-initrd.dat
- - diff [your DSDT].dsl 2.6.2-initrd.dsl > andre_luca.diff (attached)
As I wrote in the last post, I'll try to correct the new DSDT from BIOS
0205A.001: it has just 5 errors, so maybe there're good improvements.
Anyway, as above, I'd like to try your DSDT in .aml format, compiled by
you, if you could attach it.
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAM0hzVAp7Xm10JmkRAhVmAJ9X+R49FMnhQtMFDXmc9f2K3Izw4wCeLpNl
c9gw1mApcLxO+0y80ik4BlU=
=ZH3O
-----END PGP SIGNATURE-----
[-- Attachment #2: andre_luca.diff.gz --]
[-- Type: application/x-gzip, Size: 14888 bytes --]
next prev parent reply other threads:[~2004-02-18 11:11 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
2004-02-18 7:52 ` Andre Messerschmidt
[not found] ` <200402180852.16189.a.messerschmidt-hi6Y0CQ0nG0@public.gmane.org>
2004-02-18 11:11 ` Luca Capello [this message]
[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=40334874.6000109@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