From: Ian Kumlien <pomac@vapor.com>
To: linux-kernel@vger.kernel.org
Cc: Ian Kumlien <pomac@vapor.com>
Subject: [ACPI] 2.4.22, My bios is to old?
Date: Tue, 26 Aug 2003 14:36:28 +0200 [thread overview]
Message-ID: <1061901388.7167.19.camel@big.pomac.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Hi,
I just updated $other machine to 2.4.22, and now i have several ACPI
tools screaming at me because /proc/acpi dosn't exist.
(it was running 2.4.21-pre1, it has aslo been running with several acpi
patches)
And then:
dmesg |grep ACPI
BIOS-e820: 0000000027fec000 - 0000000027fef000 (ACPI data)
BIOS-e820: 0000000027fff000 - 0000000028000000 (ACPI NVS)
ACPI: have wakeup address 0xc0001000
ACPI disabled because your bios is from 2000 and too old <- WTF?
ACPI: RSDP (v000 ASUS ) @
0x000f6580
ACPI: RSDT (v001 ASUS K7V 0x30303031 MSFT 0x31313031) @
0x27fec000
ACPI: FADT (v001 ASUS K7V 0x30303031 MSFT 0x31313031) @
0x27fec080
ACPI: BOOT (v001 ASUS K7V 0x30303031 MSFT 0x31313031) @
0x27fec040
ACPI: DSDT (v001 ASUS K7V 0x00001000 MSFT 0x0100000b) @
0x00000000
ACPI: MADT not present
ACPI: Subsystem revision 20030813
ACPI: Interpreter disabled.
PCI: ACPI tables contain no PCI IRQ routing entries
I assure you that this machine has been running with acpi enabled for
years without a problem. The latest bios is from "2000/08/04" according
to asus' website.
Is it me or is this check unwarranted? Or does it actually catch bad
bisoses?
PS. Keep me in the CC:
DS.
--
Ian Kumlien <pomac@vapor.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-08-26 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 12:36 Ian Kumlien [this message]
2003-08-26 14:03 ` [ACPI] 2.4.22, My bios is to old? Felipe Alfaro Solana
2003-08-26 15:55 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2003-08-26 13:12 Tony A. Lambley
2003-08-26 14:04 ` Felipe Alfaro Solana
2003-08-26 14:16 ` Tony A. Lambley
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=1061901388.7167.19.camel@big.pomac.com \
--to=pomac@vapor.com \
--cc=linux-kernel@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.