I finally upgraded my RH9 to FC4 and was happy to see ACPI actually power off my machine when I did a shut down.

Well that was yesterday. Today no such thing. I have been tweaking things to get things back to my comfort zone, but only with applications. What did I do?

Here is a before and after boot list grep'ed for ACPI

Before:
Jul 2 16:32:04 walden4 kernel: BIOS-e820: 000000000fff0000 - 000000000ffffc00 (ACPI data)
Jul 2 16:32:04 walden4 kernel: BIOS-e820: 000000000ffffc00 - 0000000010000000 (ACPI NVS)
Jul 2 16:32:05 walden4 kernel: ACPI: PM-Timer IO Port: 0x8008
Jul 2 16:32:05 walden4 kernel: ACPI: setting ELCR to 0200 (from 0a00)
Jul 2 16:32:05 walden4 kernel: ACPI: Subsystem revision 20050309
Jul 2 16:32:05 walden4 kernel: ACPI: Interpreter enabled
Jul 2 16:32:05 walden4 kernel: ACPI: Using PIC for interrupt routing
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 14 15)
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 14 15)
Jul 2 16:32:05 walden4 kernel: pnp: PnP ACPI init
Jul 2 16:32:05 walden4 kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.PIB_.SIO0.LPT_._CRS] (Node cfec8440), AE_AML_BUFFER_LIMIT
Jul 2 16:32:05 walden4 kernel: ACPI-0158: *** Error: Method execution failed [\_SB_.PCI0.PIB_.SIO0.LPT_._CRS] (Node cfec8440), AE_AML_BUFFER_LIMIT
Jul 2 16:32:05 walden4 kernel: pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0400
Jul 2 16:32:05 walden4 kernel: pnp: PnP ACPI: found 12 devices
Jul 2 16:32:05 walden4 kernel: PCI: Using ACPI for IRQ routing
Jul 2 16:32:05 walden4 kernel: ACPI wakeup devices:
Jul 2 16:32:05 walden4 kernel: ACPI: (supports S0 S1 S5)
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt 0000:00:11.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt 0000:00:0d.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jul 2 16:32:05 walden4 kernel: ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jul 2 16:32:06 walden4 kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
Jul 2 16:32:06 walden4 kernel: ACPI: PCI Interrupt 0000:00:04.2[D] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
Jul 2 16:32:06 walden4 kernel: ACPI: Power Button (FF) [PWRF]


After:

Jul 3 09:15:43 walden4 kernel: BIOS-e820: 000000000fff0000 - 000000000ffffc00 (ACPI data)
Jul 3 09:15:43 walden4 kernel: BIOS-e820: 000000000ffffc00 - 0000000010000000 (ACPI NVS)
Jul 3 09:15:43 walden4 kernel: ACPI: Disabling ACPI support
Jul 3 09:15:44 walden4 kernel: ACPI: Subsystem revision 20060127
Jul 3 09:15:44 walden4 kernel: ACPI: Interpreter disabled.
Jul 3 09:15:44 walden4 kernel: pnp: PnP ACPI: disabled
Jul 3 09:15:44 walden4 kernel: PCI quirk: region 8000-80ff claimed by vt82c586 ACPI

Hello.

Good idea to include both the before and after logs! It seems to me (in my non-expert opinion) that for some reason, ACPI has been turned off at the kernel level.

First off, did you do any software upgrades? They might have installed a new kernel without ACPI support, not installed the cooresponding modules for that kernel, etc. Also, an update (or a tweak) could have messed with the /boot/grub/menu.lst.

Try posting your /boot/grub/menu.lst so that I (we) can take a look at it. It's possible to disable ACPI at boot by passing GRUB the acpi=off option. It kind-of looks like that's somehow getting passed at boot.

If that isn't the problem, it could be that somehow the ACPI daemon isn't running, or the module isn't getting loaded. Try doing "lsmod | grep acpi" and "ps aux | grep acpi" and posting the results.

--Dane

Nothing in /boot/grub/menu.lst

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.17-1.2139_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2139_FC4 ro root=LABEL=/
initrd /initrd-2.6.17-1.2139_FC4.img
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/
initrd /initrd-2.6.11-1.1369_FC4.img

"lsmod | grep acpi" and "ps aux | grep acpi" are coming up blank. So it looks like acpi is not being loaded. Where do I specify that?

acpi is referenced in modules.alias, modules.dep, modules.symbols. It is not referenced in modprobe.conf or any file in /etc/modprobe.d

Philip

Which modules, specifically, are being referenced in those files you mentioned? Try searching for them using a command like this:

Replace "<modulename>" with whatever the name of the module is that you want to search for. If you can't find it, you need to either download and install it via FC's package manager (preferable), or compile it as a module when you compile your kernel. I'm not really sufficiently versed in Fedora to tell you how to get it from the package manager (yum?), but I'm sure that if you search around on the net you'll be able to figure out how to do it. There's probably a package called something like, "acpimodules".

Anyway, try the "find" command and let me know how it goes.

--Dane

Here is the find output:
[root@walden4 ~]# find / -iname '*acpi*.ko'
lib/modules/2.6.17-1.2139_FC4/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko
/lib/modules/2.6.17-1.2139_FC4/kernel/drivers/acpi/asus_acpi.ko
/lib/modules/2.6.17-1.2139_FC4/kernel/drivers/acpi/toshiba_acpi.ko
/lib/modules/2.6.17-1.2139_FC4/kernel/drivers/acpi/ibm_acpi.ko
/lib/modules/2.6.17-1.2139_FC4/kernel/drivers/pci/hotplug/acpiphp_ibm.ko
/lib/modules/2.6.17-1.2139_FC4/kernel/drivers/pci/hotplug/acpiphp.ko
/lib/modules/2.6.11-1.1369_FC4/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko
/lib/modules/2.6.11-1.1369_FC4/kernel/drivers/acpi/asus_acpi.ko
/lib/modules/2.6.11-1.1369_FC4/kernel/drivers/acpi/toshiba_acpi.ko
/lib/modules/2.6.11-1.1369_FC4/kernel/drivers/acpi/ibm_acpi.ko
/lib/modules/2.6.11-1.1369_FC4/kernel/drivers/pci/hotplug/acpiphp_ibm.ko
/lib/modules/2.6.11-1.1369_FC4/kernel/drivers/pci/hotplug/acpiphp.ko

BTW, the spec sheet says the motherboard supports ACPI.

"AMD Athlon Processor Support: Supports AMD Athlon processor designed for the AMD Athlon Processor Module (242-pin Slot A) and packaged in a plastic ballgrid array (PBGA)...

Enhanced ACPI and Anti-Boot Virus BIOS: Programmable BIOS (Flash EEPROM), offering enhanced ACPI for Windows 98 compatibility, built-in firmware-based virus protection, and autodetection of most devices for virtually automatic setup."

Something I forgot to ask: which kernel are you running? Type "uname -r" to find out. If it says you're running kernel 2.6.17-1.2139_FC4 or 2.6.11-1.1369_FC4, you're in good shape because the ACPI modules seem to already be present. Also, I need to know which brand of motherboard you are using because some motherboards use different ACPI modules. Or, you can just try modprobing all the files it found, minus the .ko at the end. Try this:

...etc. If it lets you insert the modules, chances are the next time you shut down your computer, it'll power off like it's supposed to. I'm not exactly sure where to specify how to autoload them in FC4, but I suspect that it's somewhere like /etc/modules.autoload.d/ or somesuch. (That's where it is on Gentoo.) In Ubuntu, it's in /etc/modules. Just list the module's name (minus the .ko) in the appropriate file, and it should autoload at boot.

Good luck with that.

--Dane

News update, if I boot on the 2.6.11-1.1369_FC4 kernel, then acpi is enabled. It is the later FC4 kernels that disable it. So what changed?

Here is the lsmod and filtered dmesg on the "working" kernel below . Note that no *_acpi modules are loaded. The ibm_acpi module reports "ec object not found", though. The button module is active and shutdown does power down the box. Not sure where to go from here.

[root@walden4 ~]# lsmod
Module Size Used by
lp 13001 0
md5 4033 1
ipv6 268097 14
autofs4 29253 1
sunrpc 167813 1
dm_mod 58101 0
video 15941 0
button 6609 0
battery 9413 0
ac 4805 0
bt878 10457 0
uhci_hcd 35152 0
tuner 27121 0
tvaudio 22757 0
bttv 161393 1 bt878
video_buf 23749 1 bttv
i2c_algo_bit 9289 1 bttv
v4l2_common 5825 1 bttv
btcx_risc 4937 1 bttv
tveeprom 13017 1 bttv
videodev 9537 1 bttv
snd_bt87x 16137 0
shpchp 94405 0
parport_pc 28933 1
parport 40585 2 lp,parport_pc
via686a 18393 0
i2c_sensor 3521 1 via686a
i2c_core 21569 7 tuner,tvaudio,bttv,i2c_algo_bit,tveeprom,via686a,i2c_sensor
snd_cmipci 39905 1
gameport 18633 1 snd_cmipci
snd_seq_dummy 3653 0
snd_seq_oss 37057 0
snd_seq_midi_event 9153 1 snd_seq_oss
snd_seq 62289 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 51185 0
snd_mixer_oss 17857 2 snd_pcm_oss
snd_pcm 100169 3 snd_bt87x,snd_cmipci,snd_pcm_oss
snd_page_alloc 9669 2 snd_bt87x,snd_pcm
snd_opl3_lib 12353 1 snd_cmipci
snd_timer 33605 6 snd_seq,snd_pcm,snd_opl3_lib
snd_hwdep 9057 1 snd_opl3_lib
snd_mpu401_uart 10049 1 snd_cmipci
snd_rawmidi 30305 1 snd_mpu401_uart
snd_seq_device 8781 5 snd_seq_dummy,snd_seq_oss,snd_seq,snd_opl3_lib,snd_rawmidi
snd 57157 16 snd_bt87x,snd_cmipci,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_timer,sn d_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 10913 2 snd
8139too 30017 0
mii 5441 1 8139too
floppy 65269 0
ext3 132553 3
jbd 86233 1 ext3
[root@walden4 ~]# dmesg | grep -i acpi
BIOS-e820: 000000000fff0000 - 000000000ffffc00 (ACPI data)
BIOS-e820: 000000000ffffc00 - 0000000010000000 (ACPI NVS)
ACPI: RSDP (v000 PTLTD ) @ 0x000f8170
ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x0fffd352
ACPI: FADT (v001 HP Pandora 0x06040000 PTL 0x00000001) @ 0x0ffffb65
ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x0ffffbd9
ACPI: DSDT (v001 HPHPD Pandora 0x06040000 MSFT 0x0100000b) @ 0x00000000
ACPI: PM-Timer IO Port: 0x8008
ACPI: setting ELCR to 0200 (from 0a00)
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 14 15)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PPB_._PRT]
pnp: PnP ACPI init
ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.PIB_.SIO0.LPT_._CRS] (Node cfec8440), AE_AML_BUFFER_LIMIT
ACPI-0158: *** Error: Method execution failed [\_SB_.PCI0.PIB_.SIO0.LPT_._CRS] (Node cfec8440), AE_AML_BUFFER_LIMIT
pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0400
pnp: PnP ACPI: found 12 devices
PCI: Using ACPI for IRQ routing
ACPI wakeup devices:
ACPI: (supports S0 S1 S5)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:11.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI Interrupt 0000:00:0d.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: PCI Interrupt 0000:00:04.2[D] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
ACPI: Power Button (FF) [PWRF]
ibm_acpi: ec object not found

O and the motherboard, I am not sure what it is. The box is a HP Pavilion 9695C. The closest I can get to a specification for the motherboard is:

http://h10025.www1.hp.com/ewfrf/wc/g...reg_R1002_USEN

Generically described as "Motherboard and Jumper Settings for Systems with AMD Athlon Processor and an AMD Irongate (AMD-751) Chipset".

I tried googling your motherboard and found that it has an AMD 751 chipset, though I couldn't find anything useful on it.

What are the names of the ACPI modules listed in your /etc module files? Which is the "newer kernel" you would like to use?

Try this (while booted into the old kernel):

Then reboot into the new kernel and type this:

This will produce 3 files in your home directory: oldkernel.txt, newkernel.txt, and diffkernels.txt. Please post the contents of both oldkernel.txt and diffkernels.txt.

--Dane

oldkernel
newkernel
diffkernel

For grins I did a diff with the size column removed. It made the differences easier to see, I thought.

Great idea, removing the size column; I hadn't thought of that. We'll probably both feel really silly if this works, but you should try it anyway:

Some other modules I saw that I noticed that may be helpful are, "battery" and "ac".

Here's the bit about the "button" module found in the kernel configuration ("make menuconfig"):

I currently have this module compiled into the kernel, but I think it'll work just fine as a module. If modprobing it doesn't work (i.e. returns an error), try doing, "find / *button*ko" and post the results. Also, it may need to be put into your initrd image in order for it to work right. If just modprobing it doesn't do the trick, try using the package manager to install all the ACPI-related modules/packages. If that doesn't work, you'll probably have to compile your kernel from source, and either compile the module in or make your own initrd.

Good luck.

--Dane

Well I found something that works.

I added an acpi=force kernel parameter. ACPI loaded and shutdown now powers off the box.

Yeah!

I spotted the work-around in another thread where it is used to get around the ACPI BIOS age cutoff.

Not sure what happen after 2.6.11. I'll try to let the ACPI project know this occured.

Thanks for your help. It made me look in the right places.

Great! I'm glad you got it working.

Have a good one.

--Dane

I found that hibernate stopped working on my IBM t43 laptop running
Fedora 4 on kernel 2.6.17-1.2139_FC4, kernel-2.6.17-1.2141_FC4,
and kernel-2.6.17-1.2142_FC4. The way I was able to work around that
was to use the chvt command. It was mentioned in bugzilla as #196589 at bugzilla.redhat.com.

Here is my sleep.sh:

/usr/sbin/hwclock --systohc
chvt 8 # Required for kernel 2.6.17-1.2139_FC4 and higher!
echo -n mem >/sys/power/state
chvt 8 # Also required for kernel 2.6.17-1.2139_FC4 and higher!
chvt 7 # Also required for kernel 2.6.17-1.2139_FC4 and higher!
/usr/sbin/hwclock --hctosys

Maybe this will help someone else...