4 ms·

A while back before framework even existed I had a linux thinkpad. Support for things like wifi and screen resolution weren’t good on ubuntu. But in 2024 can s

by awongh 2y ago

A while back before framework even existed I had a linux thinkpad. Support for things like wifi and screen resolution weren’t good on ubuntu. But in 2024 can someone give me a rundown of why a custom hardware company like framework has trouble with sleep on their recommended distro? Where exactly on the stack is the issue and what exact software would need to be written to enable the laptop to go to sleep when you have ubuntu installed? Is it primarily a driver / closed source driver issue? Or is it an integration issue?

Fire-Dragon-DoL 2y ago
I'm curious about this too
soganess 2y ago
Impossible to be sure without logs, but the issue they are describing appears to be a problem with "modern standby" S0 vs good old-fashioned S3. Just guessing, some device is not correctly entering a deep sleep state (like an ssd not entering d3cold). So the machine isn't actually fully asleep. Honestly, I'm not sure of the technical benefits, but on the surface, modern standby sucks. I've seen reports of machines having sleep issues even under Windows, but Microsoft pushed it and here we are. Some machines, that support both, default to modern standby and can be changed to S3 with a kernel flag or bios setting. Some, less fortunate, have S3 fully disabled without a way of turning it on, save maybe recompiling your DSDT table.
theshrike79 2y ago
Even Windows machines have issues with the new low power states. It's called "Windows Modern Standby" and doesn't work on Windows =) LTT had a video about this two years ago and to my knowledge it hasn't improved much since: https://www.youtube.com/watch?v=OHKKcd3sx2c https://www.youtube.com/watch?v=OHKKcd3sx2c You can't even disable it easily, it used to be a menu item, then a CLI command and then a registry entry. They're all gone. IIRC the actual reason is a BIOS level issue, they can't support both S0 and S3 sleep properly.
- awongh 2y ago
  Interesting! This video seems to quickly mention that framework implements the correct BIOS firmware when set to s3 sleep....

by awongh 2y ago

Fire-Dragon-DoL 2y ago

I'm curious about this too

soganess 2y ago

Impossible to be sure without logs, but the issue they are describing appears to be a problem with "modern standby" S0 vs good old-fashioned S3. Just guessing, some device is not correctly entering a deep sleep state (like an ssd not entering d3cold). So the machine isn't actually fully asleep. Honestly, I'm not sure of the technical benefits, but on the surface, modern standby sucks. I've seen reports of machines having sleep issues even under Windows, but Microsoft pushed it and here we are. Some machines, that support both, default to modern standby and can be changed to S3 with a kernel flag or bios setting. Some, less fortunate, have S3 fully disabled without a way of turning it on, save maybe recompiling your DSDT table.

theshrike79 2y ago

Even Windows machines have issues with the new low power states. It's called "Windows Modern Standby" and doesn't work on Windows =) LTT had a video about this two years ago and to my knowledge it hasn't improved much since: https://www.youtube.com/watch?v=OHKKcd3sx2c https://www.youtube.com/watch?v=OHKKcd3sx2c You can't even disable it easily, it used to be a menu item, then a CLI command and then a registry entry. They're all gone. IIRC the actual reason is a BIOS level issue, they can't support both S0 and S3 sleep properly.

awongh 2y ago
Interesting! This video seems to quickly mention that framework implements the correct BIOS firmware when set to s3 sleep....