From: Blue Raven 67 <blueraven67@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: acpi information
Date: Mon, 10 Nov 2008 20:55:26 +0100 [thread overview]
Message-ID: <491891AE.6020303@gmail.com> (raw)
Hi All,
Looking around in the dmesg output of my Acer PC I found this messages.
I like to help the Linux community, so here is the DMI info.
[ 0.620789] ACPI: EC: Look up EC in DSDT
[ 0.623436] ACPI: BIOS _OSI(Linux) query ignored
[ 0.623438] ACPI: DMI System Vendor: ACER
[ 0.623440] ACPI: DMI Product Name: Aspire M5640
[ 0.623441] ACPI: DMI Product Version: R01-B2
[ 0.623442] ACPI: DMI Board Name: MCP73PV
[ 0.623444] ACPI: DMI BIOS Vendor: American Megatrends Inc.
[ 0.623445] ACPI: DMI BIOS Date: 05/23/2008
[ 0.623446] ACPI: Please send DMI info above to
linux-acpi@vger.kernel.org
[ 0.623448] ACPI: If "acpi_osi=Linux" works better, please notify
[ 0.630986] ACPI: Interpreter enabled
[ 0.630988] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.631006] ACPI: Using IOAPIC for interrupt routing
I'm currently using Ubuntu 8.10 with a standard 2.6.27-7-generic kernel
on this Acer PC.
But that wasn't without some troubles. This motherboard seems to quite
tricky on the ACPI part.
For example : first try with the 2.6.27-7 kernel I got a lot of boot
errors of the following kind :
ACPI : Expecting a [Reference] package element, found type C
I don't know what it means, but the result was nothing less then a
crashing and beeping PC.
Fortunately I could select an older 2.6.24-21-generic kernel with grub
and this one booted correctly.
Then after trial and error I managed to boot with the 2.6.27-7 kernel
only after disabling the "acpi southbridge extensions" in the BIOS.
If this information can help someone or there is an explanation for the
above behaviour ... always interested to hear about it.
Or if I can help with more info ... send me a mail.
Best regards,
Wim
reply other threads:[~2008-11-10 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=491891AE.6020303@gmail.com \
--to=blueraven67@gmail.com \
--cc=linux-acpi@vger.kernel.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