Machine won't power down
The good news is that I finally got kernel 2.6.1 running. My machine is now blazing fast, in comparison to the 2.4.22 Mandrake 9.2 stock kernel. (Disk i/o in particular seems to be much better, less thrashing and such. Applications seem to launch faster as well.)
But my machine won’t power down properly anymore, no matter how I do it (halt, shutdown, using the GUI in either GNOME or KDE). There are no special error messages displayed; the console just spits out “Power down” as the last line and sits there. Of course, all I have to do is hit the hard power switch on my box to finish the job, but it’d be much nicer if Linux could do it by itself. (In other words, the runlevel 0 scripts seem to do everything right, except for actually powering the machine down. I don’t get any messages about an unclean shutdown on the next boot or anything like that.)
I compiled my kernel with ACPI support, but without APM (thought I wouldn’t need it). Could that have anything to do with it? Or maybe I neglected to pass a special argument to the kernel on boot? At any rate, TIA for any assistance you can render.
Update: I ran dmesg | grep ACPI and got the following:
BIOS-e820: 000000001ffc0000 - 000000001fff8000 (ACPI data)
BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS)
ACPI: RSDP (v000 AMI ) @ 0x000ff980
ACPI: RSDT (v001 DELL ZUUL 0x20010703 MSFT 0x00001011) @ 0x1fff0000
ACPI: FADT (v001 DELL ZUUL 0x20010703 MSFT 0x00001011) @ 0x1fff1000
ACPI: BOOT (v001 DELL ZUUL 0x20010703 MSFT 0x00001011) @ 0x1fff4000
ACPI: DSDT (v001 D815EA EA81510A 0x00000012 MSFT 0x0100000b) @ 0x00000000
ACPI: Subsystem revision 20031002
ACPI: Interpreter disabled.
ACPI: ACPI tables contain no PCI IRQ routing entries
PCI: Invalid ACPI-PCI IRQ routing table
Update 2: I fixed it! It turns out that although I compiled ACPI support into the kernel, I never actually switched it on. (Apparently, it's not active by default, even on the 2.6 branch. Something to keep in mind if you're planning a kernel upgrade of your own.) So I checked my kernel arguments and found a line that said acpi=ht (not even sure what that's supposed to mean), then changed it to acpi=on. That did the trick.
If you're also having this problem, make sure that you get a successful activation of the ACPI daemon on boot. If you are, and the problem persists, peruse the comments on this post.
Thanks so much for your help!
But my machine won’t power down properly anymore, no matter how I do it (halt, shutdown, using the GUI in either GNOME or KDE). There are no special error messages displayed; the console just spits out “Power down” as the last line and sits there. Of course, all I have to do is hit the hard power switch on my box to finish the job, but it’d be much nicer if Linux could do it by itself. (In other words, the runlevel 0 scripts seem to do everything right, except for actually powering the machine down. I don’t get any messages about an unclean shutdown on the next boot or anything like that.)
I compiled my kernel with ACPI support, but without APM (thought I wouldn’t need it). Could that have anything to do with it? Or maybe I neglected to pass a special argument to the kernel on boot? At any rate, TIA for any assistance you can render.
Update: I ran dmesg | grep ACPI and got the following:
BIOS-e820: 000000001ffc0000 - 000000001fff8000 (ACPI data)
BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS)
ACPI: RSDP (v000 AMI ) @ 0x000ff980
ACPI: RSDT (v001 DELL ZUUL 0x20010703 MSFT 0x00001011) @ 0x1fff0000
ACPI: FADT (v001 DELL ZUUL 0x20010703 MSFT 0x00001011) @ 0x1fff1000
ACPI: BOOT (v001 DELL ZUUL 0x20010703 MSFT 0x00001011) @ 0x1fff4000
ACPI: DSDT (v001 D815EA EA81510A 0x00000012 MSFT 0x0100000b) @ 0x00000000
ACPI: Subsystem revision 20031002
ACPI: Interpreter disabled.
ACPI: ACPI tables contain no PCI IRQ routing entries
PCI: Invalid ACPI-PCI IRQ routing table
Update 2: I fixed it! It turns out that although I compiled ACPI support into the kernel, I never actually switched it on. (Apparently, it's not active by default, even on the 2.6 branch. Something to keep in mind if you're planning a kernel upgrade of your own.) So I checked my kernel arguments and found a line that said acpi=ht (not even sure what that's supposed to mean), then changed it to acpi=on. That did the trick.
If you're also having this problem, make sure that you get a successful activation of the ACPI daemon on boot. If you are, and the problem persists, peruse the comments on this post.
Thanks so much for your help!
