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:
Hey there fellow Manjaroers! Hope you’ll are doing great…
So I just upgraded my PC and did a fresh dual-boot UEFI install of Windows 11/Manjaro GNOME. I have a strange issue that makes my PC not wake up after it goes to sleep/suspend.
Things to note:
PC wakes up from Windows normally.
It’s a fresh install with just a few GNOME Extensions installed and some apps; in short, I haven’t touched the kernel or anything. No such app or extension installed that might inhibit wake-up.
When the system …
Not sure really if it’s a BIOS as stated
here. I am hesitant in updating it. It may break things.
I have swap partition.
Hope someone can shed a light.
Here’s system info from INXI:
Kernel: 5.15.74-3-MANJARO arch: x86_64 bits: 64
Desktop: GNOME v: 42.5 Distro: Manjaro Linux
Type: Laptop System: Acer product: Swift SF314-42 v: V1.03
Mobo: RO model: Kona_RN v: V1.03
UEFI: Insyde v: 1.03 date: 04/07/2020
ID-1: BAT1 charge: 32.3 Wh (72.3%) condition: 44.7/47.9 Wh (93.3%)
Info: 6-core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64
type: MCP cache: L2: 3 MiB
Device-1: AMD Renoir driver: amdgpu v: kernel
Device-2: Chicony HD User Facing type: USB driver: uvcvideo
Display: x11 server: X.org v: 220.127.116.11 with: Xwayland v: 22.1.3 driver:
X: loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
Message: Unable to show GL data. Required tool glxinfo missing.
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_rn_pci_acp3x
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
Sound API: ALSA v: k5.15.74-3-MANJARO running: yes
Sound Server-1: PulseAudio v: 16.1 running: yes
Sound Server-2: PipeWire v: 0.3.58 running: yes
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
IF: wlp1s0 state: up
Device-1: Intel AX200 Bluetooth type: USB driver: btusb
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Local Storage: total: 476.94 GiB used: 44.29 GiB (9.3%)
ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM512GDJTNI-82A0A
size: 476.94 GiB
ID-1: / size: 31.79 GiB used: 26.3 GiB (82.8%) fs: ext4 dev: /dev/nvme0n1p5
ID-2: /boot/efi size: 96 MiB used: 64.9 MiB (67.6%) fs: vfat
ID-3: /home size: 27.33 GiB used: 17.92 GiB (65.6%) fs: ext4
ID-1: swap-1 type: partition size: 11.46 GiB used: 0 KiB (0.0%)
I might be completely blind, but from that
inxi output, I can’t see how much RAM you have there.
Also, have a look at:
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:
Thanks. I’ll try this when I get home.
Thank you so much.
article/guide from vegard.net seems to work but I have a few errors. I wasn’t able to save all of the text though.
I restarted the laptop and fortunately, both Windows and Manjaro are working.
Should just I ignore these?
After executing sudo grub-mkconfig -o /boot/grub/grub.cfg
warning: fgrep is obsolescent; using grep -F
sudo mkinitcpio -P
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla2xxx
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'default'
-> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: '/lib/modules/5.8.18-1-MANJARO' is not a valid kernel module directory
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
# for more information. announcements
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
as it’s LTS:
mhwd-kernel -install linux515
Reboot into it, and remove kernel
mhwd-kernel --remove linux58
If you don’t actively use it, simply remove it when booted into another kernel:
mhwd-kernel --remove linux58
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.
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.
About the kernel, I have 5.15.74-3 based on INXI. “uname -a” returned “5.15.74-3-MANJARO”.
Can you please elaborate? Maybe I am missing something.
From mhwd-kernel --listinstalled:
Currently running: 5.15.74-3-MANJARO (linux515)
The following kernels are installed in your system:
That looks fine to me.
This also looks fine to me. Please provide the output of:
Nope. No idea. Don’t use it since I don’t have a laptop. Have never used it back when I had one, anyway.
Thanks for the quick reply. Here’s the output of “ls /boot”:
amd-ucode.img initramfs-5.15-x86_64-fallback.img initramfs-5.8-x86_64.img memtest86+
efi initramfs-5.15-x86_64.img linux510-x86_64.kver vmlinuz-5.10-x86_64
grub initramfs-5.4-x86_64-fallback.img linux510-x86_64.kver.old vmlinuz-5.15-x86_64
initramfs-5.10-x86_64-fallback.img initramfs-5.4-x86_64.img linux515-x86_64.kver vmlinuz-5.4-x86_64
initramfs-5.10-x86_64.img initramfs-5.8-x86_64-fallback.img linux54-x86_64.kver vmlinuz-5.8-x86_64
It would seem there are artefacts of kernel version
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:
Let’s move the artefacts there:
sudo mv /boot/*-5.8-* ~/kernelbackups
Followed by a
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).
Hope it helps!
What about the 5.4? Should that be removed too?
…that it’s listed as installed, no.
I moved the *5.8 kernel artefacts to a folder. Rebooted and everything is working fine so far.
Once again, thank you so much for the help.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.