Big problem here is that Microsoft seems to have given up on sleep states, and just does S5 and then hibernates (which is horribly slow), so S3 on newer machines is often horribly broken in the firmware and can’t really be used. I’m not really interested in my system going to S5 - I want it in S3.
Blame modern standby (s0i3). S0i3 is a huge mess honestly, really hard to debug from what I’ve heard and so is full of bugs and unintuitive behaviour on both the hw manufacturers side and on windows side. However if it worked as advertised, it would be a strict improvement to s3.
Hibrrnate (S4) is still alive and well but they hide it in the ui, I don’t understand why because in my experience, it is by far the most stable.
I don’t get it. Why on earth are ASUS, MSI, Asrock etc paying AMI when they could literally get the FOSS community to write it for them with a little help?
Because software development in a corporate environment relies on milestones, deadlines and guarantees. Open source, which relies on volunteer work, doesn't do this well.
Out of curiosity, what’s preventing someone from making a regulatory db similar to tzdb other than the lack of maintainers?
This seems like the perfect use case for something like this: ship with a reasonable default, then load a specific profile after init to further tweak PM. If regulations change you can just update a package instead of having to update the entire kernel.
Add comment