Compaq doesn't turn off after shutdown
 

I recently installed Suse 9.3 on a Compaq Presario 2312 Laptop (Turion) and thanks to the kind folks posting on this site, I've gotten past the odd display resolution (1280x768) and the fast clock.

The next problem on the list is that the laptop doesn't power down after a shutdown. The shutdown appears otherwise be complete -- the screen goes blank and the verbose listing of messages put out during the shutdown ends with a line saying the shutdown is complete or something like that. Problem is that the lights are still on and the fan is running. Holding the power button down for 5 seconds forces a successful power down. The shutdown works when I'm running XP.

The ACPI stuff does seem to be working since it tells me the processor clock rate is changing and the battery capacity indicator looks good.

Upon the advice of the Suse manual, I looked in the /var/log/messages and I don't see any associated with ACPI that would indicate a problem to me, but then I'm a definite novice at this. The ACPI messages are:


Oct 3 21:46:26 linux kernel: ACPI: AC Adapter [ACAD] (off-line)
Oct 3 21:46:26 linux kernel: ACPI: Battery Slot [BAT1] (battery present)
Oct 3 21:46:26 linux kernel: ACPI: Power Button (FF) [PWRF]
Oct 3 21:46:26 linux kernel: ACPI: Sleep Button (CM) [SLPB]
Oct 3 21:46:26 linux kernel: ACPI: Lid Switch [LID]
Oct 3 21:46:26 linux kernel: ACPI: CPU0 (power states: C1[C1] C2[C2])
Oct 3 21:46:26 linux kernel: ACPI: Processor [CPU0] (supports 8 throttling states)
Oct 3 21:46:26 linux kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Oct 3 21:46:26 linux kernel: usbcore: registered new driver usbserial_generic
Oct 3 21:46:26 linux kernel: usbcore: registered new driver usbserial
Oct 3 21:46:26 linux kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
Oct 3 21:46:27 linux kernel: ACPI: Thermal Zone [THRM] (52 C)
Oct 3 21:46:28 linux kernel: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
Oct 3 21:46:28 linux kernel: powernow-k8: 0 : fid 0x8 (1600 MHz), vid 0x4 (1450 mV)
Oct 3 21:46:28 linux kernel: powernow-k8: 1 : fid 0x0 (800 MHz), vid 0x16 (1000 mV)
Oct 3 21:46:28 linux kernel: cpu_init done, current fid 0x8, vid 0x4
Oct 3 21:46:28 linux rcpowersaved: enter 'powernow_k8' into POWERSAVE_CPUFREQD_MODULE in /etc/sysconfig/powersave/cpufreq.
Oct 3 21:46:28 linux rcpowersaved: this will speed up starting powersaved and avoid unnecessary warnings in syslog.

Any suggestions for a cause or cure?
Thanks,
jhw

try that
#chmod +s /sbin/halt

I tried:
#chmod +s /sbin/halt
and it didn't help. File ownership was already root (if that was what that command was supposed to fix. I'm still learning this linux stuff)

Thanks for taking the time to help.

Kernel level ???.
Try poweroff command instead, and see what happens.

I get "command not found" when I type "poweroff"

Where do I find the Kernal level? Looks like it might be 2.6.11.4-20a-default. I see files by that name in /boot and KDE reports that as a release.

Obviously you're dealing with a newbie here.

For kernel level, from a console/terminal typeroot should have access to poweroff - maybe try - will need to be root still.
BTW, how are you getting to root ???. If logged on as root, should be no problem, but if you use "su", try "su -" instead before issuing the commands (man su will explain the difference).

I was using "su" to gain root privileges.

poweroff gives the same result -- screen goes blank after all the shutdown messages scroll by. Lights on on/off switch and some buttons remain on. Fan may come on after a few seconds. Pressing and holding power switch for 5 seconds kills lights and fan.

Kernal level is indeed what I said.

Thanks for your help.

#modprobe apm
Then the halt command will totally shut down your system.

Maybe ....
maybe not.

I thought I saw this (non powering off) issue at 2.6.10, and I think it went away either very late in the 2.6.11 cycle, or maybe early 2.6.12
Poweroff was the only thing that worked for me - others reported the same as jhwhite; nothing worked.

To save a lot of probably needless stress, the best solution might be to update the kernel as soon as you have the opportunity.

# modprobe apm returns
FATAL: Module apm not found.
...but then if the apm stuff were not already there, would the battery monitoring work? The battery monitoring looks good and the clock speed is being changed so I thought the power management was present and working. I guess I shouldn't worry too much about the shutdown problem since I can always use the switch, but I put Linux on this laptop to learn about Linux and I do learn stuff by investigating these problems. I do need to test out the other power features like suspend, etc. I have not yet done that.

Regarding updating the Kernel, I'll probably upgrade stuff before too long. I understand you need to do that with Linux. In the meantime, I'll try to learn how to fix things that are broken so it won't be a big task when I run into it.

Related question: What other features are in the same system with the power down? I want to check out the related stuff and see if the lack of a power-off is just one symptom of a more widespread problem.

acpi - they have a project page on sourceforge. Looks like the fix may have shipped in 2.6.12.3.

shutdown problem
 

While I use fedora they had 3 kernels in a row which wouldn't shutdown my machine. I have 3 hard drives and the windows drives would shutdown the computer. As the shutdown is in the kernel, I would download and install an updated kernel this should correct the problem. Especially if it started after this kernel was installed.

Thanks to all of you for the info. I'll look into what I need to do to upgrade the Kernel that I got from Suse.

The machine is practically new. It came as a Windows XP home machine which I made dual-boot and added Linux. The power features all work under Windows. As I reported at the beginning of the thread, the power down doesn't work under Linux. More recently, I did a quick test, and I don't believe the sleep modes work either. When I get back to it, I'll check the ACPI log files to see if there are any clues, but maybe before I worry too much about it, I'll figure out how to upgrade the Kernel.

Thanks again.

shutdown problems
 

shutdown problem