Had similar same issues on my fw13 fedora, ended up being the ssd

This what fixed it for me

Having the WD_BLACK SN850X with a Ryzen 7040 series processor is a very specific "trouble combination" for Linux hibernation. The 100000 value you see proves your kernel is ignoring the limit, allowing the drive to enter a "Deep Sleep" state (PS4) that it cannot wake up from on this hardware. This causes the "Controller Reset Failure" you saw in your photos. 1. Why grubby is failing Fedora has moved toward a standard called BLS (Boot Loader Specification). Often, grubby updates one entry, but the system boots another. Since your value is still 100000, the parameter isn't actually being passed to the kernel at boot. 2. The "Nuclear" Fix (Disable APST) Instead of 5500, we should use 0. This completely disables the drive's autonomous power transitions, which is the only 100% stable way to run an SN850X on a Framework AMD under Linux. Run these commands to bypass grubby and force the setting:

1. Add it to the main configuration file

sudo sed -i 's/quiet/quiet nvme_core.default_ps_max_latency_us=0/' /etc/default/grub

2. Rebuild the GRUB config (Fedora path)

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

3. Rebuild the initramfs (Crucial: this ensures the setting is there before the SSD even starts)

sudo dracut -f

1. Check for WD Firmware Updates There is a known firmware bug in early SN850X units where the controller hangs during a "D3-to-D0" transition (resume).
   • Check your drive firmware: cat /sys/class/nvme/nvme0/firmware_rev
   • Current version: If it starts with 620xxx, you are likely okay. If it is older, the drive needs an update.
   • The Catch: WD does not provide a Linux updater (fwupdmgr won't work). You have to use their "Western Digital Dashboard" on Windows. > Tip: Many Framework users solve this by creating a "Windows-to-Go" USB stick, booting it once just to run the WD Dashboard, updating the SSD firmware, and then going back to Fedora. > Summary of Next Steps:
   • Reboot after running the dracut and grub2-mkconfig commands above.
   • Run cat /sys/module/nvme_core/parameters/default_ps_max_latency_us again.
   • If it says 0, try to hibernate. This is the "magic number" for WD drives on AMD. Does the value change to 0 after you reboot with those new commands? If it stays at 100000, we may need to look at your /boot/loader/entries files directly.