Any one else running an AMD - AM5 chipset motherboard having problems with suspend?

My AMD AM5 motherboard (Gigabyte A520I-AX) with Ryzen 8600G reboots 30 seconds after coming out of suspend.

I run AMD’s amd_s2idle.py Python script and comes back with an error “System isn’t configured for s2idle in firmware setup” yet power managment suspend script has the mode listed. It also says this kernel is “tainted” and that I had to run the command with “—force” to allow it run the timed suspend/wake process, which I did, but it only ran twice before rebooting, which was 30 seconds into the loops. The log file shows the results up to the point of the reboot, and then stops.”

I am hoping someone else can duplicate this and report it to find out what the problem is. This is the only thing holding me back from introducing the “Steam Pail” A retro gaming system actually built into old timer style tin lunchbox with 10.1” 2.5K IPS touch display attached to the back. The latch front cover folds open to allow access a perforated plastic mesh with enough space to hold foldable keyboard and tiny 8bitGo gamepad. Underneath the mesh is the microITX motherboard with CPU fan directly pressed into a foam duct attached a hole and filter screening in that front cover. Further cooling exhaust is handled by two 50mm 3-wire fans in the side allowing it to operate at its full 65W TDP, which is about 110W powered by custom Li-ION power pack (inside lunchbox thermos) or AC to 12VDC custom power supply that fits neatly into its own 4”x2.5”x1.25 tin container. I can achieve up to 45fps on medium settings in Alan Wake Remake with the ‘Steam Pail’ at 1920x1200.

Oh yea, launching a KickStarter next week it I can get this figured out.

I’m not sure if the issue is the same but I used this post to fix the issue on my Gigabyte board.

Thank you and read your previous post on this and sadly this is not the problem since it has no problem staying suspended (many hours) then waking up and acting normal for 30 seconds, even in the middle of a game. It just reboots, no errors, and no further log entries. And the fact it happens at a really low levelbacross a number Linux variants makes feel it is Linux kernal/AMD based, which I reporting on their forums as well.