DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using Debian Sid xfce on my laptop. When i try to shutdown, the screen always stays on (the fans turn off). It says "reached target shutdown", then this happens: http://oi67.tinypic.com/21o4fon.jpg and then it hangs. I have to press the power button to shut it down. (I have the same problem with restart). I tried various commands (shutdown -h, shutdown -P, systemctl poweroff etc) but all of them failed. I also tried to add acpi=force, acpi=off to /etc/default/grub but the problem persists. I had the same issues with Jessie but other distros work fine. Please help, this is driving me crazy..
I'm using Debian Sid xfce on my laptop. When i try to shutdown, the screen always stays on (the fans turn off). It says "reached target shutdown", then this happens: http://oi67.tinypic.com/21o4fon.jpg and then it hangs
ok, i heard about something like this before, maybe even had it on one of my laptops (this is a laptop, right?).
had something to do with acpi, iirc.
you can try adding some options to your kernel command line (grub) - search your laptop model and similar problems, you will see what i mean.
Distribution: Linux Mint 9, Linux Mint 17.2(xfce), LMDE2(Mate), Debian Jessie minimal (with standalone OBox)
Posts: 299
Rep:
I had the same problem when i did an apt-get dist-upgrade after changing my sources.list to Sid. This will take up a lot of time and diligence, and may or may not work for you. Download the latest stable kernel (i prefer the latest longterm), compile it from source exactly as per the kernel compile guide by @m_yates in the Sticky here in the Debian forum. This should take care of the shutdown/reboot issue permanently, it did for me. But i advise this only after you have explored all other avenues. It will take a lot more time and effort than a simple reinstall so it's your call whether it's worth the trouble.
try adding "acpi=vendor" or some such to your grub command line.
it's probably not the exact right command, but please do some web searches based on that, then come back and tell us what you found & tried.
I had the same problem when i did an apt-get dist-upgrade after changing my sources.list to Sid. This will take up a lot of time and diligence, and may or may not work for you. Download the latest stable kernel (i prefer the latest longterm), compile it from source exactly as per the kernel compile guide by @m_yates in the Sticky here in the Debian forum. This should take care of the shutdown/reboot issue permanently, it did for me. But i advise this only after you have explored all other avenues. It will take a lot more time and effort than a simple reinstall so it's your call whether it's worth the trouble.
I tried to upgrade my kernel from 4.2 to 4.3 but it didn't work. I will try compiling it as a last resort. Thank you.
Quote:
Originally Posted by ondoho
try adding "acpi=vendor" or some such to your grub command line.
it's probably not the exact right command, but please do some web searches based on that, then come back and tell us what you found & tried.
Thanks.
I googled this and someone suggested to edit the /etc/default/grub lines like this:
I did it and it worked 2 times. On the third shutdown it hanged again. I also tried only the "acpi_backlight=vendor" option but it failed. This is getting frustrating
some trial and error is involved, i guess.
how about testing one acpi option first, and only then another one?
This is what i've been doing for some days. I test every acpi option i can find. So far, the only options that worked for a few times are the one i mentioned above and reboot=bios.
I tried acpi=force, acpi=off, acpi=noirq, noapic, reboot=bios, reboot=acpi, reboot=pci, reboot=force
Distribution: Linux Mint 9, Linux Mint 17.2(xfce), LMDE2(Mate), Debian Jessie minimal (with standalone OBox)
Posts: 299
Rep:
Quote:
Originally Posted by kiyop
Then, Alt + sysrq + REISUO may poweroff.
OP's lucky that worked for him, thought i'd try out 4.3 on my Sid install by installing it from the repos and REISUB didn't work at all, system just froze with "watchdog did not shutdown". Neither did adding "reboot=bios" to the "GRUB_CMDLINE_LINUX_DEFAULT" line in /etc/default/grub..Flushed it immediately. It's some bug with systemd and as i said and insist, compiling the kernel from source is the only way a kernel upgrade will work without any glitches..in such cases.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.