this post was submitted on 20 Nov 2023
141 points (100.0% liked)

Technology

37720 readers
220 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] smeg@feddit.uk 22 points 1 year ago (2 children)

The important part, for the lazy:

For Modern Standby to work properly, the device Windows is running on needs to support it. That includes hardware like network interfaces and USB, but also support from system firmware and device drivers. But Microsoft doesn’t seem to have any sort of certification process or runtime hardware check for Modern Standby compatibility.

[–] albert180@feddit.de 4 points 1 year ago

Easy fix, it will be a requirement for Windows 12, unfortunately you all need to buy new computers ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

[–] rikonium@discuss.tchncs.de 2 points 1 year ago

Ugh, I had a Latitude 7210 2-in-1 and upgraded the 2230 SSD to a Western Digital SN530(?) one. Turns out after hours of troubleshooting Modern Standby, poring over Sleep Studies ("why is it draining 8% of battery an hour asleep?") that the specific drive I put in didn't "support" "Modern" Standby?

Anyways I have a ThinkPad with S3 sleep now and the fans actually turn off when I put it to sleep so that's a win.