Find the answer to your Linux question:
Results 1 to 8 of 8
Hey guys, I have been running Debian Etch on my P4 desktop for a few weeks now. Shutting down was working fine until the other night I think when I ...
  1. #1
    Just Joined!
    Join Date
    Feb 2007
    Posts
    6

    Etch not Shutting Down " acpi_power_off called"

    Hey guys,

    I have been running Debian Etch on my P4 desktop for a few weeks now. Shutting down was working fine until the other night I think when I installed KDE. Now when I shut down it does the normal things but gets stuck when it says "acpi_power_off called". Nothing happens and I just have to press the power button to get the computer to turn off. Can anyone help me fix this?

    Cheers

  2. #2
    Just Joined! soccercisco's Avatar
    Join Date
    Dec 2006
    Location
    So. Cal
    Posts
    98
    hi,

    Sorry, but I'm not familiar with this subject, so (I hate doing this because I'd like to help you myself) I googled solutions for your problem and came across this:

    http://www.linuxquestions.org/questi...d.php?t=455713

    Let me know if it helps (Sorry I can't assist you more)

    Cheers,

  3. #3
    Just Joined!
    Join Date
    Feb 2007
    Posts
    6
    Does anyone else have or has had the same issue with acpi_power_off called?

    There isn't a great deal in the way of solutions on the net, and I have tried most of the solutions available with no success.

    I suppose it isn't a cirtical bug but it is just damn annoying to have to hold the power button down for 4-5 secs everytime I shutdown.

    Cheers

  4. #4
    tpl
    tpl is offline
    Linux User
    Join Date
    Jan 2007
    Location
    cleveland
    Posts
    452
    did you check out this thread?

    https://bugzilla.redhat.com/bugzilla....cgi?id=132761

    one possible idea would be

    > On a ThinkPad A22p with a default FC3 install (kernel
    > 2.6.9-1.667), I had the exact same problem. So I
    > edited /etc/inittab:
    >
    > #ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    > ca::ctrlaltdel:/sbin/shutdown -h now
    >
    > and now the laptop shuts down correctly when using the
    > CTL-ALT-DEL sequence.

    another person suggested "acpi=on" in the grub configuration file.
    the sun is new every day (heraclitus)

  5. #5
    Just Joined!
    Join Date
    Feb 2007
    Posts
    6
    Adding "acpi=on" to the kernel line of the grub boot loader doesn't fix it.

    Quote Originally Posted by tpl
    one possible idea would be

    > On a ThinkPad A22p with a default FC3 install (kernel
    > 2.6.9-1.667), I had the exact same problem. So I
    > edited /etc/inittab:
    >
    > #ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    > ca::ctrlaltdel:/sbin/shutdown -h now
    >
    > and now the laptop shuts down correctly when using the
    > CTL-ALT-DEL sequence.

    another person suggested "acpi=on" in the grub configuration file.
    In my /etc/inittab there is the following line:

    ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

    So if I change this to:

    ca:12345:ctrlaltdel:/sbin/shutdown -h now

    Will it work?

    What does the "12345" mean?

  6. #6
    Just Joined!
    Join Date
    Feb 2007
    Posts
    6
    UPDATE: I just tried modifying /etc/inittab and it didn't work either.

    The computer still didn't turn off after the "acpi_power_off called"

    Any other suggestions?

    Cheers

  7. #7
    Just Joined!
    Join Date
    Feb 2007
    Posts
    6
    Is anyone else having the same issues or is it just me?

    I cant seem to find anything that works. All I know is that it must have something to do with a conflict between kde and acpi.

    Anyone got any other ideas on how to fix it?

    Cheers

  8. #8
    Just Joined! razmatei's Avatar
    Join Date
    Jul 2007
    Location
    Espoo, Finland
    Posts
    1
    This problem is cause by a conflict between snd_hda_intel + snd_hda_codec (Intel HD Audio modules) and Xorg. Try removing both modules before shutting down (in Slackware it is done by creating rc.local_shutdown script but in other distros this may vary). You have to remove them in the proper order. Find a way to call "rmmod -f <module_name> in the shutdown sequence and may be it will work.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •