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 <[email protected]>
I have the same problem on a sager 5600D that's only 8 months old. It
didn't happen with 2.4.22-rc2, I missed -rc3, but it happens in -rc4. I
also get it in 2.6.0-test4. Was something back-ported?
Here's my grepped dmesg:
$ dmesg |grep ACPI
BIOS-e820: 000000003fef0000 - 000000003fefb000 (ACPI data)
BIOS-e820: 000000003fefb000 - 000000003ff00000 (ACPI NVS)
ACPI: have wakeup address 0xc0001000
ACPI disabled because your bios is from 92 and too old
ACPI: RSDP (v000 PTLTD ) @
0x000f6360
ACPI: RSDT (v001 PTLTD Sheeks 0x06040000 LTP 0x00000000) @
0x3fef6ae7
ACPI: FADT (v001 Clevo 845MP 0x06040000 PTL 0x00000050) @
0x3fefaf2d
ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @
0x3fefafa1
ACPI: DSDT (v001 INTEL 845M 0x06040000 MSFT 0x0100000d) @
0x00000000
ACPI: MADT not present
ACPI: Subsystem revision 20030813
ACPI: Interpreter disabled.
PCI: ACPI tables contain no PCI IRQ routing entries
On Tue, 2003-08-26 at 14:36, Ian Kumlien wrote:
> 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)
Boot the kernel using "acpi=force"...
On Tue, 2003-08-26 at 10:04, Felipe Alfaro Solana wrote:
>
> Some new ACPI stuff went into 2.4.22 final. Try booting the kernel with
> "acpi=force".
Using this boot option brings ACPI back to life here. Thanks!
On Tue, 2003-08-26 at 15:12, Tony A. Lambley wrote:
> I have the same problem on a sager 5600D that's only 8 months old. It
> didn't happen with 2.4.22-rc2, I missed -rc3, but it happens in -rc4. I
> also get it in 2.6.0-test4. Was something back-ported?
Some new ACPI stuff went into 2.4.22 final. Try booting the kernel with
"acpi=force".
On Tue, 2003-08-26 at 16:03, Felipe Alfaro Solana wrote:
> On Tue, 2003-08-26 at 14:36, Ian Kumlien wrote:
>
> > 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)
>
> Boot the kernel using "acpi=force"...
Yes, but are all y2k bioses blacklisted now?
I mean, why was this list added, i thought that most bios manuf. ppl.
mainly used Windows "compatible" acpi anyways.. (ie still flawed) so
whats so magic with y2k?
--
Ian Kumlien <[email protected]>