I have installed Leap 16 on a new Asus Vivobook with AMD Ryzen processor. It is now dual boot, Windows 11 is the secondary O/S.
When using Windows, or Linux from an USB, the laptop switches off (power off) on shutdown, the LED indicating that power is on is dark/off.
When using Leap 16, when executing a shutdown, restart of update & restart (Discover application) the laptop starts the shutdown process and (very) soon has a blank (black) screen, but the power on LED stays on. Only pressing the on/off switch for 10 seconds will put the laptop really in power off state. The laptop is unresponsive to all other keys/ key combinations.
I do not detect any error message during the shutdown process.
I would like the laptop to shutdown up to and including the last step to power off state, and appreciate any help in achieving this.
Sorry, I made a silly typing error.
My answer should have been
The same behaviour as when shutting down from Plasma as a normal user on the laptop, i.e. the system stops (I cannot see if it hangs as the screen goes black) and the power led stays on. I can’t hear the ventilator running.
Sorry, also some misinterpretation from my side. Thanks for the clarification.
Thus the command does the same as all other trials to shut down from the Leap 16.0 system, contrary to Windows and a “Linux system” booted from another device. What “Linux system” is that?
The journal might show something interesting; here is how a normal sequence looks like after issuing poweroff in a VT:
journalctl -b -1
<snip>
set 17 15:16:24 LT-B login[37228]: ROOT LOGIN ON tty4
set 17 15:16:35 LT-B systemd-logind[872]: poweroff requested from client PID 37390 ('poweroff') (unit session-5.scope)...
set 17 15:16:35 LT-B systemd-logind[872]: The system will power off now!
set 17 15:16:35 LT-B systemd-logind[872]: System is powering down.
set 17 15:16:35 LT-B systemd[1]: Stopping Session 5 of User root...
set 17 15:16:35 LT-B systemd[1]: Stopping Session c2 of User gdm-greeter...
set 17 15:16:35 LT-B login[37228]: pam_unix(login:session): session closed for user root
set 17 15:16:35 LT-B systemd[1]: Removed slice Slice /system/modprobe.
set 17 15:16:35 LT-B systemd[1]: Removed slice Slice /system/polkit-agent-helper.
set 17 15:16:35 LT-B systemd[1]: Stopped target Bluetooth Support.
set 17 15:16:35 LT-B systemd[1]: Stopped target Graphical Interface.
set 17 15:16:35 LT-B systemd[1]: Stopped target Sound Card.
set 17 15:16:35 LT-B systemd[1]: Stopped target Timer Units.
<snip>
set 17 15:16:37 LT-B systemd[1]: Reached target Late Shutdown Services.
set 17 15:16:37 LT-B systemd[1]: systemd-poweroff.service: Deactivated successfully.
set 17 15:16:37 LT-B systemd[1]: Finished System Power Off.
set 17 15:16:37 LT-B systemd[1]: Reached target System Power Off.
set 17 15:16:37 LT-B systemd[1]: Shutting down.
set 17 15:16:37 LT-B systemd-shutdown[1]: Syncing filesystems and block devices.
set 17 15:16:37 LT-B systemd-shutdown[1]: Sending SIGTERM to remaining processes...
set 17 15:16:37 LT-B haveged[658]: haveged: Stopping due to signal 15
set 17 15:16:37 LT-B haveged[658]: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00005
set 17 15:16:37 LT-B haveged[658]: fills: 1, generated: 512 K bytes, RNDADDENTROPY: 73.25 K bytes
set 17 15:16:37 LT-B haveged[658]: haveged starting up
set 17 15:16:37 LT-B systemd-journald[539]: Received SIGTERM from PID 1 (systemd-shutdow).
set 17 15:16:37 LT-B systemd-journald[539]: Journal stopped
I switched to runtime level 3 with init 3 and logged as root: the shutdown behaviour is the same and this time the journal contained 4 extra lines at the end:
Another test I did: I chose not to shutdown but to go to sleep mode (save to disk).
That works, the power led goes off. And on switching on, the laptop loads its saved memory as it should be.
What you see is similar to systemctl halt in which the system stops but power is still on, rather than to systemctl poweroff where power is switched off after the system stops.
Check if you see any difference issuing either command.
Note: the old SystemV style shutdown command might not be as discriminating between the -H and the -P options.
I know that shutdown is (getting) obsolete and that systemctl is the recommended command, I have used shutdown that long that it’s difficult to change.
Anyway, systemctl poweroff bahaves the same as shutdown -P and shutting down by a user in Plasma.
Is there a discrete graphics card (Nvidia?) that refuses to shutdown?
Anything in the BIOS that keeps the system alive, such as wake-on-lan or the like?
The graphic processor is AMD Radeon 660M.
I have made some change to the BIOS, among other things to make the laptop boot from the Leap 16 installation USB.
Secure boot is switched off, there is no wake-on-lan setting that I can find and if som I would have switched it off. The laptop is brand new and received Leap 16 just after Windows 11 was installed (I couldn’t get into the BIOS directly, Microsoft started loading immediately). The laptop is to be used isolated from networks, just connected via wifi to internet.