diff options
| author | Anthony Godshall, Ampro Computers, Inc <agodshall@ampro.com> | 2007-03-09 21:19:05 -0500 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2007-03-09 21:19:05 -0500 |
| commit | 5b27b176da6cc83b0f904c7e0aabd9362d70bf70 (patch) | |
| tree | 99d15494bbc88317c046d49ca4840dbb2a7bec11 /drivers/acpi/blacklist.c | |
| parent | f110ef58e6c9bd562999247c5e8a5b8e722fbd11 (diff) | |
| download | op-kernel-dev-5b27b176da6cc83b0f904c7e0aabd9362d70bf70.zip op-kernel-dev-5b27b176da6cc83b0f904c7e0aabd9362d70bf70.tar.gz | |
ACPI: make blacklist more verbose
IMHO, ACPI disabled due to DMI failure or blacklisted year should be noted,
as is done with other ACPI blacklisting.
This will help people troubleshoot when ACPI isn't working. Status quo is
a mysterious "ACPI Disabled" message without explanation on BIOS that
implements ACPI but not DMI. This is actually fairly common on embedded
x86 boards.
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/acpi/blacklist.c')
| -rw-r--r-- | drivers/acpi/blacklist.c | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c index f289fd4..3ec110c 100644 --- a/drivers/acpi/blacklist.c +++ b/drivers/acpi/blacklist.c @@ -79,11 +79,17 @@ static int __init blacklist_by_year(void) { int year = dmi_get_year(DMI_BIOS_DATE); /* Doesn't exist? Likely an old system */ - if (year == -1) + if (year == -1) { + printk(KERN_ERR PREFIX "no DMI BIOS year, " + "acpi=force is required to enable ACPI\n" ); return 1; + } /* 0? Likely a buggy new BIOS */ - if (year == 0) + if (year == 0) { + printk(KERN_ERR PREFIX "DMI BIOS year==0, " + "assuming ACPI-capable machine\n" ); return 0; + } if (year < CONFIG_ACPI_BLACKLIST_YEAR) { printk(KERN_ERR PREFIX "BIOS age (%d) fails cutoff (%d), " "acpi=force is required to enable ACPI\n", |
