Hacker News Reader

Comment by VWWHFSfQ | Hacker News Reader

> Obviously Linux can sleep easily since decades ago.

Yeah right. Suspend and resume is still buggy as hell. Power management in general in Linux is still awful after all these years.

View on HN

Low-level power savings (s3 sleep) and magic packet (Wake-on-LAN) have been a standard since the late 90s. Getting a Linux OS that actually delivers these standardized power features is now a 20+ year old bug. I can only imagine the amount of energy that would have been saved if this bug was properly fixed 25 years ago. With solid-state tech becoming cheaper every day, I now expect nobody will make an "it just works" OS that has both sleep and wake working on-demand. Globally, the HDDs will simply continue to spin until there are none.

Who pays for Linux development? Either companies for servers or embedded Linux. Servers don't sleep. Embedded might sleep, but it's not PC hardware, so it needs completely different power management features.

Nobody is paying for Linux on average PC hardware, that's why 20 year old bugs are not fixed.

I Confirm this.

For years I use suspend on my laptop with latest Debian, and it's very difficult to have an uptime higher than 15 days.

Every now and then, the logging in freezes to death on wake-up and requires hard power off.

This sounds like an isolated and highly specific experience being generalized to an entire operating system.

I have no idea how it looks on the dev/setup side, but suspend and resume is definitely a solved problem, seeing that I've never had any problems with it on my Steam Deck

It's very likely designed for that use case so not very relevant.

Most PC are delivered with Windows, and even though Linux works on them, it's unlikely the PC were designed with suspend stability as criteria.

If that's the case, who's to fault here? Linux or buggy ACPI states implemented in the motherboards?

Reply on news.ycombinator.com