Ok wow.. did I jinx myself with this post. Immediately after posting here, I began the install/config phase of a fresh reformat. Encountered a weirdness that the system couldn't sleep/suspend - immediately woke up. 8 hours later... After installing 5 different distros to confirm it was ALL linux versions (even debian)...

I spent the entire day, 8 hours, searching and referencing and troubleshooting. FINALLY one very random corner of the internet, on an ARCH-LINUX forum, a small comment mentioned that my Gigabyte B550 "had a problem" with sleep. SO THEN I had to start cross-referencing those words (couldn't "use" the Arch guide, since I was on Pop), and my dude/dudette... I was up to 1am.

Ultimately, I had to COMBINE the "solutions" of FOUR different results, across 2017-2020 (none actually on Ubuntu 22.04) to get the fix to work. Like one taught me the script, but the locations were wrong, one taught me the service I needed, but it was outdated, and then another taught how to fix a service, etc etc, cascading solutions.

SO at close to 2AM - after documenting my own guide, another raw metal install of PopOS, wrote my script & service... and... "it just works!" (pun intended). It works. It sleeps. Have to disable the Gigabyte B550M "GPP0 and GPP8" device, which are bridges to the NVMe drives.

Funny enough though, as much as this is "yup, thats Linux!" I feel like it's not fair, and not Linux's fault. This is a random, and really unlucky, issue with my specific board. I am typing this to you, while on my new PopOS install, and sleep/suspend still works.

What a ride!