I’m using a Lenovo ideapad 5 14ARE05 based on an AMD R5 4600U (Renoir).
The Laptop is one of those which don’t properly support S3 for sleep but rather the non-sensical “modern standby” and don’t have a BIOS-switch for it. Luckily, I could get it to suspend properly by using this recipe from the arch wiki.
Unfortunately they now mention that this stopped working with 5.11.10 (imo it might have happened earlier).
My experience with 5.11 series so far:
With 5.11.2, the laptop would enter suspend/sleep, but not wake up properly, all I would get was a corrupted screen and eventually the laptop would hang.
With 5.11.6 everything worked again, interestingly
With 5.11.10 it was back to 5.11.2 behavior, so I downgraded to 5.11.6.
Now with 5.11.14, the laptop refuses to properly go to sleep at all (which could be seen by a slowly pulsing power LED). The screen does turn of, but not much more apparently?
When waking from sleep, I briefly get the corrupted screen again, then it recovers and I can lock back in (so there’s at least one improvement). Apparently only once, though - subsequent tries would make it lock up with a black screen.
Interestingly the latest 5.10 Kernels have the same issue (previously 5.10 seemed unaffected).
The straightforward solution for now is to downgrade again, but that’s not very satisfying and certainly not future-proof.
I would like to understand what’s going on there, is it potentially connected to efforts to support modern standby on Linux? Latest Kernel patches mention S0iX.
After some more research, it might be two issues behind it - one with amdgpu causing the lock-up and one with recent kernels not properly supporting S3 (or having changed something about it), which caused the initial fix to stop working. It also affects 5.10.28 and onward.
See this topic on the Arch Forums.
It seems that 5.11.6 works because it still properly supports S3, but also has a patch against the amdgpu issue that was later reverted for some reason and has not yet reappeared in 5.11.