I have dual boot setup. I have Windows 11 (upgraded months ago) as the main OS and partition. I installed Windows first then installed Manjaro. Hibernate and sleep on Windows are working fine by the way.
When I use the suspend command from the terminal or the suspend from Power Off menu, the laptop screen goes black. It seems like it’s suspending. When I move the touchpad to wake it up, it boots the laptop like I restarted it. It displays the login screen. When I log in, all the previously opened applications before suspend are closed.
When I use the hibernate command from the terminal, it seems like it shuts down. When I touch the touchpad or press any key, it doesn’t do anything.
I read other posts and some solutions are for Intel CPUs. I wonder if it will work on AMD.
For example, this one:
Not sure really if it’s a BIOS as stated here. I am hesitant in updating it. It may break things.
This might have to do with the kind of setting in the bios. And to get it to work you might need to upgrade the Bios. Reference from the Ubuntu forum for the exact type of hardware:
The other suggestion from vegard.net seems to work. I still have to monitor it because I only tested it once with the battery unplugged. For around 30 minutes, only 2 percent of the battery was used while hibernated. Would you still recommend updating the BIOS?
This is safe to ignore. It’s just a warning. Nothing serious.
Likewise, these are just warnings and, probably, safe to ignore. If it affected you, you would have known it, AFAIK. Check previous #announcements for more information.
That is because it seems that you have an old, EOL kernel installed. If you use it, you should change to a still supported one. I recommend 5.15 as it’s LTS:
mhwd-kernel -install linux515
Reboot into it, and remove kernel 5.8:
mhwd-kernel --remove linux58
If you don’t actively use it, simply remove it when booted into another kernel:
By the way, would you know how to make “suspend” work? I have the sleep button (Fn F1) which I sometimes press accidentally. The issue is that it somehow sleeps because when I press the Esc key, it’ll turn the laptop on but it seems like the laptop restarted because all apps are closed. Nothing is saved.
I don’t want to use hibernate if I’m just eating lunch or dinner too. Closing the lid doesn’t suspend/sleep as well.
I disabled suspend when closing the lid from Gnome Tweaks. I have also disabled the “power-button-action” using dconf editor. It’s set to “nothing” instead of “suspend”. I disabled it because it doesn’t work. I’m just preventing it to suspend because it doesn’t save the state of the opened applications.
From system-inhibit:
WHO UID USER PID COMM WHAT WHY MODE
ModemManager 0 root 548 ModemManager sleep ModemManager needs to reset devices delay
NetworkManager 0 root 536 NetworkManager sleep NetworkManager needs to turn off networks delay
UPower 0 root 964 upowerd sleep Pause device polling delay
GNOME Shell 1000 b 1398 gnome-shell sleep GNOME needs to lock the screen delay
b 1000 b 1579 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block
b 1000 b 1579 gsd-media-keys sleep GNOME handling keypresses delay
b 1000 b 1580 gsd-power sleep GNOME needs to lock the screen delay
gnome-tweak-tool-lid-inhibitor 1000 b 4679 python3 handle-lid-switch user preference block
8 inhibitors listed.
It would seem there are artefacts of kernel version 5.8 left over. Compared to mine:
$ ls /boot
drwx------ root root 4.0 KB Thu Jan 1 02:00:00 1970 efi
drwxr-xr-x root root 4.0 KB Mon Oct 17 09:12:30 2022 grub
.rw------- root root 30 MB Mon Oct 17 08:47:45 2022 initramfs-5.10-x86_64-fallback.img
.rw------- root root 8.1 MB Mon Oct 17 08:47:34 2022 initramfs-5.10-x86_64.img
.rw------- root root 35 MB Mon Oct 17 08:47:58 2022 initramfs-5.15-x86_64-fallback.img
.rw------- root root 8.2 MB Mon Oct 17 08:47:47 2022 initramfs-5.15-x86_64.img
.rw------- root root 40 MB Mon Oct 17 09:12:27 2022 initramfs-6.0-x86_64-fallback.img
.rw------- root root 8.5 MB Mon Oct 17 09:12:18 2022 initramfs-6.0-x86_64.img
.rw-r--r-- root root 4.9 MB Tue Aug 9 20:43:42 2022 intel-ucode.img
.rw-r--r-- root root 23 B Sat Oct 15 15:40:00 2022 linux510-x86_64.kver
.rw-r--r-- root root 22 B Sat Oct 15 15:38:02 2022 linux515-x86_64.kver
.rw-r--r-- root root 20 B Sat Oct 15 15:31:02 2022 linux60-x86_64.kver
drwxr-xr-x root root 4.0 KB Wed Jul 14 09:25:18 2021 memtest86+
.rw-r--r-- root root 9.3 MB Mon Oct 17 08:47:31 2022 vmlinuz-5.10-x86_64
.rw-r--r-- root root 10 MB Mon Oct 17 08:47:31 2022 vmlinuz-5.15-x86_64
.rw-r--r-- root root 11 MB Mon Oct 17 09:12:15 2022 vmlinuz-6.0-x86_64
I would think it safe to remove your artefacts. But just in case I’m wrong, lets rather just move them somewhere and reboot. If everything works after rebooting, we can permanently delete them. So:
Let’s make a directory to create the backups in:
mkdir ~/kernelbackups
Let’s move the artefacts there:
sudo mv /boot/*-5.8-* ~/kernelbackups
Followed by a reboot.
If successful, check that the artefacts are no longer there:
sudo ls /boot
If not, I suspect it’s safe to remove the backups:
sudo rm -r ~/kernelbackups
If you are unable to boot, I suggest chrooting and reinstalling the kernel(s).