Hacker News new | ask | show | jobs
by MengerSponge 1187 days ago
And the fact that I have to shut down my windows laptop to have any reasonable expectation that it'll have a charge the next day. Or maybe even later that day.
1 comments

Disable S0 idle to get true S3 sleep or at least create a script to disable wifi and wakeup timers before entering sleep cf https://csdvrx.github.io/

My battery drops by more or less 0.5%/h so a 10h sleep = 5% drop.

Why does one have to do this on a Windows certified laptop?! Sounds like the tweaks I had to do when I ran Linux on my laptops from the 2000s.
I can't answer your question philosophically. You could decide not to, and accept the bugs as natural limitations of what's available to you.

But from a tech perspective, I see minor annoyances caused by complex systems with parts from many companies where 1 error in coordination can have very large bad consequences (ex: losing the Intel Serial IO on the Fold due to errors in the Intel drivers = no bluetooth, no touchscreen, so you will think it froze while it just needs the drivers reloaded, say by doing that from a USB keyboard or by RDP)

Our current hardware is great, and never has been simpler to use, but it has also even more complexity than before: this is increasing the risk of subtle issues that even most readers of HN would have no idea about if they hadn't read first about it here (like Dells catching fire due to ACPI S0 idle).

But nothing is set in stone! You did that in the 2000s? You can still do that if you want a great experience! You may already know about tweaking IO and IRQ addresses from before? That's not very applicable anymore, so update your knowledge to today's problems: learn about the the DSDT, the default APST settings per device, etc. It may take some time.

However, once it's done, 1) you have a much finer understanding of how your computer works allowing fixing the root cause, 2) so the problem rarely comes back but if it does you are ready 3) you're ready to tackle more challenges!

This year I'm moving to Linux on the Laptop using arch. Everything I learned on Windows is extremely helpful. The rest, I'm learhing it along!

https://www.youtube.com/watch?v=OHKKcd3sx2c

TL;DW: There's a bug in the implementation of windows modern standby that can cause it to activate energetically expensive operations while "asleep", and most PC manufacturers didn't bother to write drivers for the more effective, but less "feature rich" S3 sleep mode.

My laptop only supports S0, which is already extremely annoying.

My laptop is an Asus with a Ryzen 9. If I wanted to have to muddle around with wifi drivers and wakeup timers to have a barely functioning device I'd install Slackware on a 2010 Thinkpad.

So you don't want to "muddle around", and therefore the laptop you have, an "Asus with a Ryzen 9" is "extremely annoying". That's paying an lot of money to be annoyed by a top of the line CPU, but ok I guess?

Meanwhile, my foldable OLED thinkpad and my regular one, both with ridiculous Intel CPUs that are totally crushed by Ryzens are perfectly functional, both on Windows and Linux, and I enjoy them a lot!

Yet you call them "barely functioning" and insinuate they are as primitive as "Slackware on a 2010 Thinkpad"? Wow, if that isn't entitlement, I don't know what it is!

If you had been a little nicer, I would have offered some help to improve your S0idle experience.

I would suggest a little bit of self reflection, as I think your hardware is wasted on you due to your unwillingness of correctly configuring modern options.