View previous topic :: View next topic |
Author |
Message |
jyoung Guru
Joined: 20 Mar 2007 Posts: 440
|
Posted: Wed Dec 27, 2023 4:30 am Post subject: no poweroff on reboot or shutdown |
|
|
My system recently picked up a bug where it won't poweroff when I issue either "reboot" or "shutdown -h now". In both cases, it goes through the normal shutdown steps, but halts without an error message at the power-off stage. This sounds nearly identical to this thread:
https://unix.stackexchange.com/questions/264189/computer-doesnt-power-off-at-shutdown-reboot-arch
But their solution, adding "acpi=force" to GRUB_COMMAND_LINE_DEFAULT didn't work for me.
Unfortunately, I don't reboot that often, so I'm not sure when this first started, except that it was in the past few months, so it's hard to say when update(s) might have caused it.
Any ideas? |
|
Back to top |
|
|
jyoung Guru
Joined: 20 Mar 2007 Posts: 440
|
Posted: Thu Dec 28, 2023 10:29 pm Post subject: |
|
|
I also tried setting "acpi=off" in grub. To me, this seems counter intuitive, but I wanted to see what would happen. This had no effect on this issue, and the only change I can see is that the system isn't able to set the hardware clock at boot.
I also looked through the bio settings, and couldn't find anything that seemed related.
One other note: this system is dual-booted with windows, and, although I mostly just use linux, yesterday I had to boot into windows. Windows was able to poweroff without issues, so I doubt that it's a hardware problem. |
|
Back to top |
|
|
entity Tux's lil' helper
Joined: 16 Jun 2002 Posts: 92 Location: Joensuu, Finland
|
Posted: Sun Feb 04, 2024 6:27 pm Post subject: |
|
|
I recently faced similar issue after system update. For me, it was Code: | sys-apps/sysvinit-3.08 | that caused it, and reverting to Code: | sys-apps/sysvinit-3.07 | got poweroff working again.
Edit: this post seems to cover the issue. |
|
Back to top |
|
|
jyoung Guru
Joined: 20 Mar 2007 Posts: 440
|
Posted: Tue Apr 23, 2024 3:50 am Post subject: |
|
|
entity, thanks for chiming in, I'm still scratching my head on this one. I just tried rolling back to
Code: | sys-apps/sysvinit-3.07 |
but no luck. |
|
Back to top |
|
|
amair n00b
Joined: 12 Aug 2003 Posts: 61
|
Posted: Tue Apr 23, 2024 6:09 am Post subject: |
|
|
When I upgraded to sys-apps/sysvinit-3.08 I received this elog message:
Quote: | Previously, the 'halt' command caused the system to power off even if option -p was not given. This long-standing bug has been fixed, and the command now behaves as documented. |
So if I read "man shutdown" correctly, you should run "shutdown -h -P now".
"man halt" says you must run "halt -p" or "poweroff". |
|
Back to top |
|
|
entity Tux's lil' helper
Joined: 16 Jun 2002 Posts: 92 Location: Joensuu, Finland
|
Posted: Tue Apr 23, 2024 1:16 pm Post subject: |
|
|
amair wrote: |
"man halt" says you must run "halt -p" or "poweroff". |
Indeed. But I gotta say, it took a while to override the default behavior between chair and keyboard, since I have been typing "halt" for the past 20+ years to turn off my workstation. |
|
Back to top |
|
|
jyoung Guru
Joined: 20 Mar 2007 Posts: 440
|
Posted: Wed Apr 24, 2024 8:55 pm Post subject: |
|
|
Interesting... I just tried
And for the sake thoroughness
And neither of these worked. |
|
Back to top |
|
|
wjb l33t
Joined: 10 Jul 2005 Posts: 609 Location: Fife, Scotland
|
Posted: Thu Apr 25, 2024 11:50 am Post subject: |
|
|
Just add one line in ~/.bashrc and carry on as normal
Code: |
alias halt="poweroff"
|
|
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Thu Apr 25, 2024 12:27 pm Post subject: |
|
|
Although the timing is unfortunate, it looks to me like OP's problem has nothing to do with the bug fix in sys-apps/sysvinit. OP specifically stated that he tried using the pre-fix version, and it did not help. Additionally, he has tried the elaborated invocation that is supposed to work in the post-fix version, and it does not help. I have used shutdown -h now successfully, and the system powered off, when using =sys-apps/sysvinit-3.08, a version which supposedly requires you to "do it right." Based on all this, I think OPs' problem is not in with the bug fix in sys-apps/sysvinit. Instead, this is some other problem. OP: if you increase the kernel's output verbosity, do the final lines left on screen provide anything useful? Does the sysrq that forces an immediate poweroff (without syncing, so you must save your data first!) turn off power in the bad case? Based on your kernel upgrade history, is there a last known good / first known bad kernel? |
|
Back to top |
|
|
|