News for hackers. Stuff that matters.
Re:Open-Sourcing our Firmware by alufers on Friday January 21, 2022 @04:09PM (#30030038)
Sorry for changing the topic but does anybody know the reason Intel has removed the seep states?

It drives me absolutely nuts when I open my bag and feel the heat coming out of it, and my laptop is left with 20% charge.

Re:Open-Sourcing our Firmware by ohazi on Friday January 21, 2022 @04:21PM (#30030160)
I believe the push came from Microsoft.

Apple has been able to do "clever" things while asleep, like waking up the wifi chipset periodically to check for email / messages / notifications / updates, so that when you wake up, everything magically feels ready to go instead of feeling like you just woke up from 1984 and have reams of crap to download.

But this only works well because Apple does their own firmware for most of the machine, and seems to do a reasonably good job, despite a few issues. They're careful about only doing things that aren't going to obliterate the battery in a way that would be surprising.

Microsoft is jealous of this functionality and knows they want something like that for Windows. They also know they need to cater to the lowest common denominator with system builders, so they asked Intel to put this kind of capability into their platforms, and to explicitly disable the old modes, so that system builders wouldn't be able to drag their feet. The result is that they've all switched, but the outcomes are generally poor and high variance. Sometimes they're passably okay within Windows, but not always. It'll probably get better, but for now things are crap, especially on Linux.

Re:Open-Sourcing our Firmware by FredFS456 on Friday January 21, 2022 @10:45PM (#30033237)
I believe it's configurable in firmware, as my ThinkPad e14 gen 2 has a BIOS option to set the sleep state behaviour. The options are labelled "Windows" and "Linux".
Re:Open-Sourcing our Firmware by Already__Taken on Saturday January 22, 2022 @01:04PM (#30039151)
Why is this hard? Like I know it's all hard. But is it just new? or is it not documented at all, or some structural issue with how distros expect states to work?
Re:Open-Sourcing our Firmware by sevenlake on Friday January 21, 2022 @10:54PM (#30033308)
Have they? As far as I'm aware, sleep states are "supported" in hardware well enough, but doesn't prevent software/settings from not using them correctly.

Not that I blame them, there are many different sleep states from core/package level [0] that map onto system/platform level sleep states [1]. Fucking confusing, and I'm sure something is waking it up. Have you checked Windows Task Scheduler? My college laptop had a Norton Antivirus scan wakeup at 5am every day and would be re-enabled every Windows Update, similar pain to you

[0] https://www.intel.com/content/www/us/en/support/articles/000... [1] https://www.tenforums.com/tutorials/63346-sleep-states-avail...

Re:Open-Sourcing our Firmware by danuker on Friday January 21, 2022 @09:43PM (#30032766)
The correct course of action is to return the "defective" product.
Re:Open-Sourcing our Firmware by alufers on Saturday January 22, 2022 @02:02PM (#30039728)
Unfortunately it's my work laptop.
Re:Open-Sourcing our Firmware by baybal2 on Friday January 21, 2022 @11:18PM (#30033485)
Maybe they made a hardware bug in suspend circuit, and decided to simply fuse it out?