From: Len Brown <lenb@kernel.org>
To: Philippe <pdidier@neptuneconcept.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: dmidecode (Acer Aspire 5050)
Date: Fri, 18 Jan 2008 17:28:39 -0500 [thread overview]
Message-ID: <200801181728.40046.lenb@kernel.org> (raw)
In-Reply-To: <1195031290.6446.1.camel@ITmanager>
> kernel: [ 0.652000] ACPI: System BIOS is requesting _OSI(Linux)
> kernel: [ 0.652000] ACPI: Please test with "acpi_osi=!Linux"
> kernel: [ 0.652000] Please send dmidecode to
> linux-acpi@vger.kernel.org
Manufacturer: Acer, inc.
Product Name: Aspire 5050
With 2.6.22, did you notice any functional difference with "acpi_osi=!Linux"?
(or since the default changed at 2.6.23, with 2.6.23 or later
do you notice any difference with "acpi_osi=Linux"?)
Please send me the output from acpidump.
If you don't have acpidump, you can get it from pmtools here:
http://www.lesswatts.org/projects/acpi/utilities.php
thanks,
-Len
next prev parent reply other threads:[~2008-01-18 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 9:08 dmidecode Philippe
2008-01-18 22:28 ` Len Brown [this message]
[not found] ` <47946846.8090105@neptuneconcept.com>
2008-01-22 2:33 ` dmidecode (Acer Aspire 5050) Len Brown
[not found] ` <47955F6E.1090208@neptuneconcept.com>
2008-01-22 4:55 ` Len Brown
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=200801181728.40046.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=pdidier@neptuneconcept.com \
/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;
as well as URLs for NNTP newsgroup(s).