Computer doesn't fully shut down nor will reboot

English Install/Boot/Login
1

My computer was shutting down just fine, but now, it goes through the process, the monitor goes off, the keyboard is inactive, but the computer on/off light is still on and the fan is running. I do not find anyone else having this issue recently.

On the grub menu, if I select the advanced options and choose Linux 6.12.0-160000.35-default or the .36 one, it still shuts down. But the .37 one doesn’t. Sounds like caused by an update to the kernel to me. I booted to my 16.1 beta partition and it shut down fine. I then did a system update, rebooted, and now it does not shut down completely, neither.

There is a firmware update to my motherboard I haven’t done, but should that affect shutdown?

The last few lines of : > sudo journalctl --no-pager -b -1

Sep 02 17:16:58 localhost.localdomain systemd[1]: Stopped Create Static Device Nodes in /dev gracefully.
Sep 02 17:16:58 localhost.localdomain systemd[1]: Reached target System Shutdown.
Sep 02 17:16:58 localhost.localdomain systemd[1]: Reached target Late Shutdown Services.
Sep 02 17:16:58 localhost.localdomain systemd[1]: systemd-poweroff.service: Deactivated successfully.
Sep 02 17:16:58 localhost.localdomain systemd[1]: Finished System Power Off.
Sep 02 17:16:58 localhost.localdomain systemd[1]: Reached target System Power Off.
Sep 02 17:16:58 localhost.localdomain systemd[1]: Shutting down.
Sep 02 17:16:58 localhost.localdomain systemd-shutdown[1]: Syncing filesystems and block devices.
Sep 02 17:16:58 localhost.localdomain systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Sep 02 17:16:58 localhost.localdomain systemd-journald[694]: Journal stopped
2

I have had this problem throughout the Leap 16.0 (all kernels). You seem to only have it with the latest kernel.

You might want to add a comment to Bug 1255441.

My current work-around is to use the kernel from Tumbleweed (currently kernel 7.2.2-1). When there’s a new kernel for Leap 16.0, I give that a try. But it always fails to reboot or shutdown, while the Tumbleweed kernel is working without any problems.

3

Done. I noted they did a patch to fix the issues in August. That’s when I started having the problems. And you still have them. So must be something related, but not quite the same.

How do you use a different kernel. My first thought was copy it on, but I see symbolic links to lib/modules with a bunch of stuff, so copying on one vmlinuz file probably wouldn’t work? or installing the .rpm will automatically take care of all that?

1 Like
4

I added the Tumbleweed OSS repo as an additional repo (with poor priority so that nothing is automatically selected from there).

The I use “myrlyn” and the Version tab to install the latest Tumbleweed kernel. And, yes, I have to be careful about doing that when the Tumbleweed kernel changes.

1 Like
5

I was told to check the kernel in OBS Kernel:SL-16.0 repo. Where would I find that? I’m not familiar with all the repositories.

6

Oh, I think I found it in the bug report.

7

I tried kernel-default-6.12.0-160000.326.1.gb6e9e54.x86_64 from https://download.opensuse.org/repositories/Kernel:/SL-16.0/standard/x86_64/ and it shut down completely, so a different problem than others were having. Said it was “a known issue with mt76 driver that prevents shutdown/reboot”. Don’t know what that means, but it works for me.

8

I tried the .341 version and it reboots for me. But I notice with both the .326 and the .341 there is no access to WI-FI from my network icon lower right. Should I be concerned the next release may not have WI-FI? Or are these just testing versions of other things and WI-FI will be included in the final releases?