The existence of a BIOS option called "Linux-compatible sleep mode" is a dead giveaway that the default behavior is enshittified sleep that wakes up your system periodically so it can check your email, phone home to Microsoft, and maybe fail to go back to sleep.

Having such an obvious name like that is a gift, because otherwise you have to start decoding Intel Marketing names for their features to figure out which are actually anti-features.

Much as I might wish this were really the case, the truth is that it wasn't Windows' fault - IIRC from the explanation, Windows supports sleep modes that Linux doesn't, but it doesn't support them very well, and it's apparently not a rare issue. Something to do with S3 sleep mode IIRC.

The blame is shared between Microsoft and Intel. It's not really that Windows supports sleep modes that Linux doesn't, but that Microsoft and Intel conspired to get rid of S3 sleep mode entirely.

The intention was to replace S3 with fine-grained per-device sleep modes that would in aggregate lead to idle power that is almost as good as S3 while allowing for the "wake up and check email" kind of features. But to the surprise of approximately nobody, this complex multi-vendor strategy relying on high-quality drivers for every single peripheral in the machine did not work out as well as planned. The plan also did not in any way require that S3 sleep be eliminated from newer hardware platforms; that was just malicious behavior from the Wintel conspiracy.

Tbf forcing though a very complex buggy feature no one wanted did _require_ that you couldn't just use the better working existing solution.