From: Peter Williams <pwil3058@bigpond.net.au>
To: linux-acpi@vger.kernel.org
Subject: Advice on result of using acpi_osi=Linux
Date: Wed, 23 Apr 2008 14:42:57 +1000 [thread overview]
Message-ID: <480EBE51.1000408@bigpond.net.au> (raw)
As requested via syslog message, I'm reporting the results I obtained
using acpi_osi=Linux on the boot command line:
Without this addition to command line, I get:
Apr 23 14:04:38 mudlark kernel: ACPI: BIOS _OSI(Linux) query ignored
Apr 23 14:04:38 mudlark kernel: ACPI: DMI System Vendor:
Apr 23 14:04:38 mudlark kernel: ACPI: DMI Product Name:
Apr 23 14:04:38 mudlark kernel: ACPI: DMI Product Version:
Apr 23 14:04:38 mudlark kernel: ACPI: DMI Board Name: DG31PR
Apr 23 14:04:38 mudlark kernel: ACPI: DMI BIOS Vendor: Intel Corp.
Apr 23 14:04:38 mudlark kernel: ACPI: DMI BIOS Date: 09/28/2007
Apr 23 14:04:38 mudlark kernel: ACPI: Please send DMI info above to
linux-acpi@vger.kernel.org
Apr 23 14:04:38 mudlark kernel: ACPI: If "acpi_osi=Linux" works better,
please notify linux-acpi@vger.kernel.org
With this addition, I get:
Apr 23 14:13:57 mudlark kernel: ACPI: BIOS _OSI(Linux) query honored via
cmdline
Apr 23 14:13:57 mudlark kernel: ACPI: DMI System Vendor:
Apr 23 14:13:57 mudlark kernel: ACPI: DMI Product Name:
Apr 23 14:13:57 mudlark kernel: ACPI: DMI Product Version:
Apr 23 14:13:57 mudlark kernel: ACPI: DMI Board Name: DG31PR
Apr 23 14:13:57 mudlark kernel: ACPI: DMI BIOS Vendor: Intel Corp.
Apr 23 14:13:57 mudlark kernel: ACPI: DMI BIOS Date: 09/28/2007
Apr 23 14:13:57 mudlark kernel: ACPI: Please send DMI info above to
linux-acpi@vger.kernel.org
I'm not sure if this constitutes better but I thought I'd report it anyway.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next reply other threads:[~2008-04-23 4:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 4:42 Peter Williams [this message]
2008-04-24 1:10 ` Advice on result of using acpi_osi=Linux Len Brown
2008-04-25 2:20 ` Peter Williams
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=480EBE51.1000408@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.