S3 Sleep on AMD always freezing the Desktop
S3 Sleep on AMD always freezing the Desktop
I dont know if this is pretty common? I reported a bug about this an eternity ago on Fedora, but it is still happening.
I am also not sure what project is responsible, mesa?
Whenever I sleep my Fedora KDE Laptop, close the lid, open it and it turns on but no input works.
Sometimes my entire screen is corrupted too, like this and often only a hard shutdown fixes it, sometimes it reacts by itself.
Do you know something similar? Where should I report it and how can I circumvent this by now, disable S3 sleep?
Many modern laptops no longer support S3 sleep at all. It is likely to be an issue with the bios rather than a linux project. On my laptop, with Ryzen 7 5825U, I had to give up on S3 and use s2idle. Also had to pass "pcie_aspm=off" as a kernel parameter because it would take ages to wake the ssd without it. Overall works ok. Not as good as S3 but better than nothing.
Pcie ASPM off would hurt battery life a lot wouldn't it? What sad do you have?
I haven't really noticed much of a difference. I figured it was probably worth actually being able to wake the laptop from sleep rather than having to restart it every time.
Thank you! How do you activate s2idle?
So to check what suspend states your laptop supports run
cat /sys/power/mem_sleep. It should print something likes2idle shallow [deep]with the option that is enabled having [] around it. To change the enabled option runecho "s2idle" > /sys/power/mem_sleep.
https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate has more info.
Microsoft has pushed OEM's to stop supporting S3 in bios, instead wanting hybrid sleep. Microsoft wants this because hybrid sleep allows waking for sending telemetry to Microsoft all the dang time, like cell phones do. I curse the day they did this.
Wtf this really sucks.
Are you sure S3 sleep is enabled in the bios? On most machines it's one or the other, not both at the same time. On some Intel machines you can still enable S3 standby, but I know AMD killed it a lot sooner than Intel did.
Windows has powercfg /availablesleepstates to show what states are supported. I'm sure there's something like that for linux but I'm not 100% sure. You could try
dmesg | grep -i "acpi: (supports"No seems I use s2idle.
What are real reasons for that killing?
Microsoft says it’s more secure. and that since it stays on its 100% the OSes control which is supposed to be much more secure”reliable” than S3 standby.
Nevermind that S0 standby is so incredibly buggy and awful on windows where it’s supposed to be best. My i9 Thinkpad drops 20% battery in 15 minutes, then goes into hibernation. It has a 50% chance of overheating in my bag and crashing when trying to get in to hibernation.