From Fedora 33 IMHO if secure boot is set, then suspend to DISK is disabled. But suspend to RAM should work. Why is swap space on disk needed to enable suspend to RAM?
I have two machines, first is older, an Intel i5(?) quad core dual thread, 8Gb RAM, 1TB Magnetic hdd. This is dual boot with Windows 10, so Windows esp partition mounted to /boot/efi a /boot partition a swap partition 16GB and about 400GB of / on btrfs file system, and default zram swap from Anaconda installation. Zram has higher priority than disk partition. This system will NOT suspend to disk, message to effect that suspend to disk is prevented by Locking out. I think this is by design, I am not interested in going around the designers intentions… My IT department just barely let me install fedora and insists on secure boot active. (Also insists on frequent BIOS updates, my mfr only publishes BIOS upgrades on Windows, which is why I dual boot, only ever use Windows to upgrade BIOS.)
Second machine is brand new and is the one in question: AMD Ryzen Pro 7 processor, 64GB RAM, 1 TB SSD, also dual booting with Windows. Windows made esp partition is mounted to /boot/efi. /boot partition and a then / partition is mounted to btrfs. NO swap partition, but standard zram swap size. I left about 60 GB of free space at the last install, I’ll use mkswap and create swap partition kind of 1X RAM and see what happens. Again with secure boot enabled swap to DISK is not expected to function by design. For swap to zram, that is supposed to be compressed somehow, perhaps adding more zram space is needed. Guessing 0.5X Ram? Suggestions anyone? Would 4 or 5 zram swaps be better than just one big one at 30 GB. (Thats 50% of ram devoted to swap, sounds excessive to me as I type this, is there a better way?)