Home / ubuntu / Questions / 132143
In Process
Max Beer
Asked: 2012-05-06 07:44:12 +0800 CST

Stuck on reboot and shutdown

  • 772

I've recently installed Ubuntu 12.04 and I love it. However I have one problem- I am unable to shutdown or reboot properly.

When I shutdown my laptop (Acer Aspire 5560) it hangs on the 5 dots and stays there.

When I reboot my laptop it does shutdown but when it boots back up it stay's on the Purple screen (no logo what so ever)

Thing's I've I'd to stop this:

  • sudo service network-manager stop before shutdown - nothing

  • Adding some lines the the GRUB file - nothing

  • installed other Ubuntu versions - nothing
  • sudo shutdown -h now - nothing

and some more.

At the moment I see a black screen in front of me with the text

 Asking all remaining processes to terminate [OK]

And the 5 dots with only the last one orange.

On other tries I got this thing:

modem-manager:could not get the system bus......

I first had Ubuntu dual boot Windows. And then it worked fine. However after a fresh install of Ubuntu alone I got this.

shutdown reboot aspire 12.04

7 Answers

  1. I had a similar problem with a Dell XPS 15z which I resolved by adding acpi=noirq to the kernel arguments:

    sudo editor /etc/default/grub

    set

    GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq quiet splash"

    then

    sudo update-grub

    Note that previously I had been using acpi=off, which permitted me to boot, but not shutdown. Without any acpi flag, I was not able to boot.

    • 17

  2. You may try to these commands into terminal

    For shutdown:

    sudo halt

    For shutdown:

    sudo init 0

    For restart:

    sudo init 6

    For shutdown:

    sudo shutdown -h now

    For hibernate:

    sudo /etc/acpi/hibernate.sh
    • 5

  3. I got a hack from this link -- http://www.pbehnke.com/main/node/11, for some reason if the usb controls are set to auto, the shutdown-reboot loop starts. The solution was to make them on forcefully.

    I have added a function in the /etc/init.d/halt script like this -- 

    # Add this function in the /etc/init.d/halt script
# call before do_stop
set_usbs_on () {
    usbcontrolpath="/sys/bus/usb/devices/*/power/control"
    for dev in $usbcontrolpath;
    do
        echo "Setting $dev: " `cat $dev` "to on"
        echo on > $dev
        echo ""
    done
}

    and I call it before do_stop in case $1 stop switch --

    stop)
    set_usbs_on
    do_stop
    ;;

    Now the machine shuts down.

    • 2

  4. The only thing that I needed to do was to press Ctrl+Alt+T to open the terminal. When it opens, run the command below

    sudo update-grub

    and now it's working fine.

    • 0

  5. Same issue with spurious hangs "on the 5 dots". I've read somewhere (cannot remember where) to first "Log Out" (top right corner menu) and then shutdown. I've been doing this for more than one month now with no more issue.

    • 0

  6. I'm no expert but i loaded BARTpe to get to a command promt and reinstalled bios it booted straight to the hard drive guess it couldnt see it just try to load default in your bios might not have to update

    • 0

  7. I realize this is a super old post, but I found the REAL answer for this model. It's not Ubuntu, it's the Aspire.

    From the ubuntu bug registry: (link)

    It seems that is BIOS/UEFI bug, so there is no solution to fix it on 5560g if planning use efi.

    A user on TomsGuide confirms this is the case even when installing Windows:

    The problem is, that the ACER Aspire 5560G model somehow (don't ask how {maybe BIOS related?}) can't shut down properly (freeze) when the OS is installed in a GPT partition style.

    Again from the bugs page a workaround: (link)

    WORKAROUND: using gdisk convert gpt to mbr, setup boot-repair, restore mbr and then restore grub

    Lot's of work to fix such a small thing. Some users have suggested that a BIOS update my help.

    DISCLAIMER: I cannot confirm any of this outside that the error occurs, and that windows does indeed experience the same issues when installed with gpt. If I do decide to follow the workaround (very risky) or update the BIOS (even more risky) and get some further results I'll update.

    • 0