I’ve been trying to install Arch on an old laptop for the past few days but for some reason it will not shut down if I’m using any kernel above version 6.7. It goes all the way through and gets to Reached target: System Power Off but then just sits there and never actually powers down. I waited 30 minutes in case it did something and it never did. I don’t believe there is anything useful in the journalctl output as there’s nothing after Reached target System Power Off but I’ll paste it here in case: https://text.is/4KNL
I tried the shutdown troubleshooting steps from here: https://freedesktop.org/wiki/Software/systemd/Debugging/
The debug shell is no help as I can’t access it once it hangs, and since it never finishes shutting down the logging script won’t help. reboot -f and poweroff -f both work which made me think it wasn’t a kernel issue, however it works fine using the linux-lts kernel. Because of this I tried manually downgrading to a few standard kernel versions from 6.6, 6.7 and 6.8 and only the ones above 6.7 had this issue. Specifically the latest lts version (6.6.23 at the time I tested) worked fine, 6.6.9 (the last 6.6 version in the main branch) worked fine, 6.7.arch1-1 and above didn’t.
Weirdly I don’t have any issues with the installation media (currently using the ones from 29th March and 1st April). I also tried Opensuse Tumbleweed which I believe is on the same kernel version and had no issues so it seems to be Arch specific. I also tried linux-zen in case that had any difference but it didn’t help.
I have tried several re-installs with both legacy and UEFI boot, mostly minimal installs (base, linux, linux-firmware, linux-headers and nano). Since the live iso works I also tried installing all the packages from that but it still didn’t work.
I’m completely out of ideas at this point. I can’t see anything obvious in the kernel 6.7 changelog, but then I don’t really know enough to know what to look for there. I know for now I can keep using the lts kernel but presumably at some point that will be upgraded to a version above 6.7 so that doesn’t seem like a good long term solution, I’d also really like to know the root cause behind this as its been bugging me for days! The laptop is an Acer aspire E15 with an Intel 6500U (I have tried with the Intel-ucode package installed) and an Nvidia Geforce 920M.
Edit: somehow installing kde plasma has fixed the issue
You must log in or register to comment.
Which method are you trying that fails? Clicking a menu icon? reboot in terminal? Tty?
What is the status of your systemd ?
systemctl status
Any failed units?
systemctl --failed
Have you tried
systemctl reboot ?
What does your boot log look like?
For maximum fun :
journalctl -xe -b -o verbose -o with-unit -H | grep -i err -C10 --color=always | less --use-color
** corrected
–failed to is-failed(I was right the first time) and --include to -o with-unitwithout any logfile it’s difficult to say where the problem might lie.
I have the same problem on my desktop with both KDE Plasma 5 and Plasma 6 using the Zen kernel and Nvidia GPU. It happens randomly, every 10-20 shutdowns maybe, that my computer hangs on Target reached: System Power Off
I turn off my computer using the button in KDE start menu, which opens the shutdown menu. In there I press the Shutdown icon to turn off my computer.
I still haven’t figured out the issue.
I had something similar happen to me with Debian 12. I believe pressing ALT + F7 after it reached that “power off” message forced the computer to power off. Something caused it to get stuck, but I’m not 100% sure. It may have been some bug with my Samba file share setup, but I have no way of confirming that.
Not sure if this will work for you, but it’s worth a try. Good luck and hope you solve the issue!
I ended up solving it by installing kde plasma. I’d previously tried with as minimal an install as possible to narrow down the problem, but it seems all I had to do was carry on setting things up as I’d originally wanted!
I realized shortly after posting my reply that your post was created 30 days ago. Not 30 minutes lol. Glad you got it fixed!
Well, actually … As the Internet gets older (and more filled with ads and pop up windows and cookie banners and “Do not forget to subscribe!”) we’ll see the day that some people will answer Linux questions from 30 years ago, especially when the OP did forget a [Solved!] in the post title :-)
I would just use the older kernel until a newer one comes out that works again. Is there some reason you need the newer kernel?
Nah I don’t really need the latest kernel, I’m just worried the it’s kernel will eventually be updated and get the same problem
This was a bug in the latest kernel I believe. I was having this problem for about a week but updated Sunday and haven’t encountered it since.
Yeah I was having the same issue but the latest kernel update (6.8.4) fixed it for me.
