acpi_power_off called

Sputnikc · 06-17-2006, 12:45 PM

After reading and trying allmost every single thread in the forum that contains the line "acpi_power_off" and also searching a lot on google that could fix it, i'm still stuck with it.

My setup
I have a pointer systems laptop (very recent) which works pretty well in linux so far.
Its a intel pentium mobile 2.0 Ghz cpu (centrino) with a ati x700 radeon mobility and all the other fancy stuff (wuxga tft, 2 gb ram and so on).
For the specs :
http://www.pointersystems.be/prodspecs.php?item=82

I'm using debian etch on it. With a kernel 2.6.16 that i build from source (for all my hardware to work)

Now the problem is when i issue a shutdown -h now command, the laptop hangs just before shutting down : onscreen saying "acpi_power_off called".
Waiting for about 30 minutes didn't switch it off, so it isn't turning off.

When i use the acpi=off in grub it also doesn't switch off but its just saying "power down" if i can recall good enough.

I think it might be some kernel option keeping it from powering off.
Disabling acpi is no option since i use cpufreqd for battery lifetime.

Even with acpi off it doesn't switch off anyway.

Any feedback that isn't written in the forum yet would be appreciated. so far now, i keep experimenting with some kernel options , and recompiling (lucky it only takes about 5 minutes on ths baby.. :P)

If you need to know more for analizing my problem, just let me know.

hgb · 06-17-2006, 02:24 PM

I m translatting some configuration from SDL to Debian XD... because the resolution work there... and the mouse is OK... and the kb is near to be OK....

Anyway.. when do cat to /etc/modules I see the following... and I remember read about it somewhere I guess???

Quote:

apm power_off=1

Perhaps that work... ¿?¿?¿?

Sputnikc · 06-17-2006, 03:13 PM

Sorry, i did try this allready.
It doesn't help, it just says power down, the screen banks, but the laptop isn't switched off.

Sputnikc · 06-27-2006, 12:28 PM

I'm still looking at this problem,

It seems to me to have something todo with Xorg
But i still need to figure out exactly what.

If someone can gimme a pointer it would be nice.

Latest kernel from source installed (2.6.17.1) did't help/fix it.

lugoteehalt · 06-27-2006, 01:02 PM

If you don't need acpi how about using apm instead?

I installed apmd and oldish laptop swithches off after halt command or whatever.

Sputnikc · 06-27-2006, 01:22 PM

I really really need acpi.. otherwise i won't run on battery for a nice period of time with this baby..
even with the acpi=off appended at boor it doesn't power off.

lugoteehalt · 06-29-2006, 08:26 AM

Sorry, should have read your post.

This is probably less than helpfull but aren't you just supposed to hit the power button with acpi - i.e. no shutdown -h now?

Sputnikc · 06-29-2006, 08:39 AM

I've tried that also.. :P
It doesn't work for me ..

I do think it's got something to do with xorg though

lugoteehalt · 06-30-2006, 12:43 PM

Hang on, have you tried acpi=force??

Spelling it out for referrence:

Put acpi=force at the end of Grub's kernel line: hit e, or whatever it is, when the grub menu comes up and edit the line. This can be a bit deceptive - you think you've done it right but you haven't. If it works make the change permanent by doing the same in /boot/grub/menu.lst, often called.

Obviously make sure acpi and the daemon acpid are installed.

Here's something a bit unintelligible from my personal help file: This example - placed in /etc/acpi/events/power - will shut down your system if you press the power button. event=button/power.* [then on the next line] action=/usr/local/sbin/power.sh "%e" - The script power.sh gets called and will see the complete event string as parameter $1. Have done this and the thing shuts down with just pressing the power button. (Don't know it this did it or the vaughly similar thing already in the file.)

For God's sake tell me if this works, cause that'll be just about a first.

Sputnikc · 06-30-2006, 04:28 PM

I've tried playing with all kind of "acpi=" appendixes in de grub loader.
None of them worked.
What i did manage to do once was the following :
When the system started i used kdm so i was seeing the Kdm logon screen and i never logged on, just did the shutdown option, and then the damn thing did a shutdown and all went fine, it even powered off nicely.
It seems to have something to do with having logged onto kde and then i assume somthing todo with vga powersettings.. but i didn't have time to test some more..
Whenever i find a solution, i will post it here. i'll keep trying and looking for new things to try until i solve this..

dracae · 06-30-2006, 09:09 PM

Have a look at /etc/default/halt

Sputnikc · 12-21-2006, 07:36 AM

I was not looking at this problem for a while but now i got 2.6.19 Kernel compiled and still nothing is fixed.

The exact error i get is the following :

Code:

Will now halt.
Synchronizing SCSI cache for disk sda:
ACPI: PCI interupt for device 0000:06:03.0 disabled.
Power Down
acpi_power_off called

When i boot and shutdown immediately after booting then it shuts down the proper way (inclusive the powering off).
So i guess it's something that is running (maybe in KDE) that is causing it not to poweroff properly.

I'm gonna try and disable the cpufreqd but i want it to work to switch off the cpu fan when cooling down the cpu.

If anyone got any ideas yet, i still didn't find the correct answer to the problem in my case

stelek · 01-03-2007, 01:23 PM

I seem to have the same problem. When I boot without entering KDE, the shutdown works properly. But if I enter KDE and then click "shutdown", the systems ends up with "acpi_power_off called" and never powers off. Did you manage to find a solution for this? It could be something wrong with KDE...

My system is Slackware 11, with Kernel 2.6.19.1 and KDE 3.5. Acpi daemon is working...

Sputnikc · 01-03-2007, 02:41 PM

Nope, no solution found yet.
I'm not constantly looking for it anyway.
I think it might have something to do with kde's powermanagement.

stelek · 01-13-2007, 06:16 PM

I just want to let everyone know that in my case the problem is solved now.It was related to Intel HDA / ALSA driver and KDE. It seems that someone has already found a workaround. Please read here:

http://bugzilla.kernel.org/show_bug.cgi?id=7195

I hope it helps...

***

Additional references:

ALSA error report:
https://bugtrack.alsa-project.org/al...ew.php?id=2475

KDE error report:
http://bugs.kde.org/show_bug.cgi?id=134480