From: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: foo_bar_baz_boo-acpi-/E1597aS9LQAvxtiuMwx3w@public.gmane.org
Cc: Lukasz Muziol <l.muziol-kecf2yCh/1qFxr2TtlUqVg@public.gmane.org>,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: No ACPI battery events on HP compaq nx9000 (kernel 2.6.14-suspend2-r7)
Date: Fri, 13 Jan 2006 16:51:05 +0100 [thread overview]
Message-ID: <20060113155105.GD25115@poupinou.org> (raw)
In-Reply-To: <20060113092738.64911.qmail-0G5Q3D3iwRWvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
On Fri, Jan 13, 2006 at 01:27:38AM -0800, foo_bar_baz_boo-acpi-/E1597aS9LQAvxtiuMwx3w@public.gmane.org wrote:
> Get the iasl compiler from Intel and recompile your DSDT as your log
> shows it was generated by the buggy Microsoft compiler:
>
> > ACPI: DSDT (v001 ATI MS2_1535 0x06040000 MSFT 0x0100000e) @
> > 0x00000000
>
> hence the MSFT string there. Something is probably broken wrt your
> battery support in that DSDT.
Why are you spreading this FUD?
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-01-13 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 16:01 No ACPI battery events on HP compaq nx9000 (kernel 2.6.14-suspend2-r7) Lukasz Muziol
[not found] ` <20060110160108.09861e96.l.muziol-kecf2yCh/1qFxr2TtlUqVg@public.gmane.org>
2006-01-13 9:27 ` foo_bar_baz_boo-acpi-/E1597aS9LQAvxtiuMwx3w
[not found] ` <20060113092738.64911.qmail-0G5Q3D3iwRWvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2006-01-13 15:51 ` Bruno Ducrot [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-10 16:02 Lukasz Muziol
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=20060113155105.GD25115@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=foo_bar_baz_boo-acpi-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
--cc=l.muziol-kecf2yCh/1qFxr2TtlUqVg@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@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