Suspend/sleep works terribly out of the box

Recently installed OPENSUSE and this seems like a very weird behavior that doesn’t happen in different distros. Not even LIVE distros.

If I set energy settings to sleep, the lights stay on and turning the power button on the distro comes to life.
In windows the recovery process is slower, but the entire computer was shut down. There was no CPU lights.

If I set energy configs to hibernate after x minutes, it prompts some CMD pci error after having the screen turned down, repeats this once or twice, and then puts to hibernate. But after turning the power button on, it inicializes the entire boot process, becoming even worse/slower than just shutting down. Specially because it keeps consuming energy.

What kind of sleep mode is your device using? S3 deep or S2idle modern standby? You can check that by opening the file /sys/power/mem_sleep.

Are you using some kind of power management tool? tlp, power-profiles-daemon, or something else. One time I messed something up in tlp configuration which caused my device to get permanently stuck in sleep mode. Maybe some configuration is preventing your device from sleeping.

You mention hibernation not working. Did you set it up according to openSUSE documentation? (must have swap, set the resume kernel argument, etc.). A bad configuration in tlp also caused this process to not work like it should for me.

See: Power management - openSUSE User Documentation Project

For me, hibernation works like it should now. It gets stuck and becomes unresponsive for a bit, but it does shut down and does return directly to openSUSE with apps previously opened after turning the laptop on again.

It’s s2idle [deep]
I tried to change through the KDE power managing.

After hibernation (after suspension) there’s a blinking prompt, that I’ll need to push again the power button to release itself from hibernation and a sudden return is possible.

I couldn’t agree more. There is something really wrong in this aspect with openSUSE. I spend several hours trying to figure out why it happens but ended with a workaround, some people even change the hardware.

Please show the output of: sudo inxi -Faz