Linux

15143 readers

238 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

152

Why does Linux have such a terrible sleep? (programming.dev)

submitted 2 days ago by onlinepersona@programming.dev to c/linux@programming.dev

126 comments fedilink hide all child comments

In 8 hours it uses 20% of the battery. When Windows or Mac are put to sleep, the damn things can sleep for a week! This is the case with Linux on multiple laptops.

Is there some kind of manipulation going by ring -1 that detects Linux is running? Is Linux not respecting some procedure and kissing a step?

you are viewing a single comment's thread
view the rest of the comments

[–] Lehmuusa@nord.pub 23 points 1 day ago (1 children)

On my Linux computer I just close the laptop's lid and it goes to sleep, consuming almost no battery power. I can open it hours later and have basically the same amount of battery left as before.

But some laptop manufacturers have proprietary systems in place for the sleep mode that are not supported in Linux because it would be a gargantuan effort when the laptop manufacturer refuses to coöperate.

[–] GalacticGrapefruit@lemmy.world 13 points 1 day ago (1 children)

This is the answer.

Proprietary firmware. Fuck Intel.

[–] stormeuh@lemmy.world 3 points 1 day ago

Laptops with AMD chips are not necessarily better in this regard.

From my anecdotal experience with an HP laptop (from work), with an AMD 7840HS, the blame is often also with the system integrator. That one has a bug in the power management system, where if you plug the charger in during sleep, the power state gets locked to some very low power sleep mode, until you either reboot, or plug the charger in while it's not asleep.

HP doesn't want to look at this because they don't support Linux, meanwhile AMD kernel devs claim that this is probably a BMC bug so they can't fix it. Whatever the real culprit is in my case, the BMC can do so much these days that it wouldn't surprise me if a lot of sleep issues are due to bad firmware.

Either way, system integrators like HP refusing to support Linux is in part what allows Intel and AMD to ignore a lot of Linux-specific bugs. SIs have a lot of manpower to help diagnose and fix them, and they have leverage when reporting bugs to CPU manufacturers.