You are not logged in.
My config: https://bbs.archlinux.org/viewtopic.php?id=302717.
Whatever Wayland or X11, hibernate doesn't work: it acts like reboot, if I leave some open apps, hibernate then resume, empty desktop.
Same on the CLI, by stopping KDE:
systemctl isolate multi-user
https://wiki.archlinux.org/title/Power_ … nsistently doesn't help me.
Last edited by jebez (2025-01-19 21:03:28)
Offline
echo root=/dev/disk/by-id/usb-JetFlash_Transcend_32GB_01JDP4E3DVWKHULY-0:0-part1 resume=/dev/disk/by-id/usb-JetFlash_Transcend_32GB_01JDP4E3DVWKHULY-0:0-part2 rw>/mnt/etc/kernel/cmdline
Are you trying to boot from/hibernate to some sort of USB key?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Waking from a hibernation will turn into a reboot if the hibernation image cannot be loaded for any reason.
Offline
Are you trying to boot from/hibernate to some sort of USB key?
Yes, why not? I try Arch Linux before I'll install to the NVME of my PC.
http://0x0.st/8Ha1.txt done.
Last edited by jebez (2025-01-19 16:19:41)
Offline
Actually running the OS from a usb key would kill the latter in no time, but on topic, the device might simply show up too late/not at all during the resume (ie. hibernating to a removable device might not be possible with that hardware)
Is that journal supposed to cover an attempt to resume a hibernating system?
Jan 19 16:12:49 archlinux systemd[1]: Starting Clear Stale Hibernate Storage Info...
Jan 19 16:12:49 archlinux systemd[1]: Finished Clear Stale Hibernate Storage Info.
Jan 19 16:12:49 archlinux systemd-hibernate-resume[365]: Reported hibernation image: ID=arch kernel=6.12.9-arch1-1 UUID=47c4ca47-f17a-4c3c-8b68-51be69ac86d1 offset=0
Jan 19 16:12:49 archlinux systemd-hibernate-resume[365]: Successfully cleared HibernateLocation EFI variable.
just clears some residuals?
Offline
Actually running the OS from a usb key would kill the latter in no time
omg why?
So it would work on the NVME ?
It's only for the last boot? I rebooted sorry brb.
Last edited by jebez (2025-01-19 16:53:31)
Offline
Because USB keys aren't cheap ssds - there's no wear leveling, you'll end up overusing isolated cells, they die and the firmware will move the key to read-only.
It's hard to say whether things will just work on your nvme, but the provided log does not look like it's coming out of a hibernation.
Maybe also post the previous to show what's going on there
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
(nb. that if you've meanwhile rebooted the previous log might actuall be the one you've posted before, increase the offset accordingly)
Or post journals from two boots where you're dead sure that you tried to hibernate in the first and resume from that in the second one.
Offline
New http://0x0.st/8Hah.txt after a failed hibernate, h for hibernate I presume?
Good to know, I'll install on the NVME, adios Debian...
Last edited by jebez (2025-01-19 17:06:39)
Offline
I installed on the NVME, same
Offline
Hibernate the system, attempt a resume, then post the journals for those two boots
(sudo journalctl -b -1; sudo journalctl -b) | curl -F 'file=@-' 0x0.st
Offline
The last link isn't useful?
Offline
No, but this one is.
Jan 19 20:33:20 archlinux kernel: PM: Image not found (code -16)
Jan 19 20:33:20 archlinux systemd-sleep[17866]: Performing sleep operation 'hibernate'...
Jan 19 20:33:20 archlinux kernel: PM: hibernation: hibernation entry
Jan 19 19:57:11 archlinux kernel: Kernel command line: root=/dev/disk/by-id/nvme-WDS250G3X0C-00SJG0_185250422455-part1 resume=/dev/disk/by-id/nvme-WDS250G3X0C-00SJG0_185250422455-part2 rw
lsblk -f
Consider addressing it va its UUID, https://wiki.archlinux.org/title/Power_ … e_location and also please post your /etc/mkinitcpio.conf (you didn't just forget to add the resume hook, did you?)
https://wiki.archlinux.org/title/Power_ … _initramfs
Offline
Add resume in /etc/mkinitcpio.conf
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems resume fsck)
then
sudo mkinitcpio -P
works! Thanks!
Sorry I came from Debian, no need to to it, /etc/mkinitcpio.conf doesn't even exist.
Offline
No need to be sorry.
The worst part about arch is that nothing works by itself.
You have to care about everything.
The best part about arch is that nothing works by itself.
You will care about everything.
Offline