I started with ~32GiB of swap, and extended to the size in the above picture using a live USB and Gparted.
So I tried:
sudo mkswap /dev/nvme0n1p3 then reboot: still no swapon
swapon in Gparted, sudo grub2-mkconfig -o /boot/grub2/grub.cfg, then reboot: still nothing
added resume=/dev/nvme0n1p3 to the kernel parameters in YaST bootloader, regenerate Grub config then reboot: still nothing
told system to mount swap in YaST partitionning: that did it.
But. The system still takes several minutes to boot, instead of seconds before. What’s going on…? I noticed that even though locked, the swap partitionned is not used (Used: 0.00GiB in Gparted, even after a while)…
Well, when you have in fact only one swap partition, then yes, one entry should be removed.
Do not remove the wrong one!
And IMHO that is the cleanest way to do it. How else?
Here my desktop with tumbleweed does hibernate. Waking up from hibernation takes 1 minute where as
I can boot my machine within 10 seconds. So I pick shutdown rather than hibernate. My two cents.
Oh, my swap partition is 20GB.
@conram I have 128GB in my Desktop But MicroOS runs no swap, I run kubernetes, so no swap there either. Systems are either busy, or off… newer hardware and boot times have improved as well… and then on Tumbleweed with secure boot and kernel lockdown…
Hibernate compresses the memory image when storing in swap so you need just a bit over 1/2 memory size.
Unless you do extreme memory usage 32 gig should not require swap for normal running. A samll amount helps if you run off the top of your memory because when you run out Linux crashes!!!
Erm, no, two days ago… It seems I forgot to mention it here eventually, I apologize ^^’ (though I’m not sure why I have to, what if I didn’t get a chance do restart my computer in the last two days, because of work or something?)