Originally posted by OmniNegro
View Post
Power Management Bugs Hold Up Some Linux Laptops Due To Regulatory Requirements
Collapse
X
-
Originally posted by archkde View Post
I can certainly see s2idle being a great option, but I don't want it as an unconditional S3 substitute.
Comment
-
-
My older thinkpad just works, If i close the lid, it sleeps and goes multiple days without charging, wakes up just fine. But with newer laptops I've had (thinkpad and dell) so much troubles, Suspend basically wakes up automatically and even on hibernation battery is sometimes consumed in hours.
Comment
-
-
Amazing. I tend to disable all S power states in the BIOS except S3, as I actually tend to always shutdown my computer at the end of the day.
When going to lunch, I make a suspend to RAM, and that's it. All other power modes are disabled. Makes less wierd issues happening in general.Linuxer since the early beginnings...
Comment
-
-
Originally posted by Old Grouch View Post
Please don't use the BLINK attribute on your invisible sarcasm tags: it hurts my eyes.
Comment
-
-
Holy shit, I would not have expected this.
S3 issues, yes, all the way. On some boxes it works, other mess up rarely on entering, but some, sadly, mess up on resume.
But Soft-off, ATX-off or S5, whatever we call it?
I thought INIT makes all the programs shut down (correctly). Then it flushes all buffers/caches to the drives. Unmounts the drives (on can follow that during shutdown/reboot procedure) so everything is synced, and finally it remounts / read-only and sends the hardware the shutdown or reboot command.
So does the kernel have to prepare hardware?
I thought the last part is matter of CPU or SIO/EC and the SIO/EC (incl. clock) is the only thing to remain powered by the PSU (as one can see when you measure power consumption that there is something like 0.5 Watts being pulled). And the SIO listenes to possible magic key from the keyboard (so yeah, kbd controller will also be on then) or to magic packet arriving for WOL. And in some BIOS setups you can configure that, if the computer can be switched on in soft-off by keyboard or if you really have to shortcut the pins with the power-on key to signal the PSU to send power to the mainboard.
And then there is Microsoft with their privacy-invading shitty "connected standby" and the likes. You computer never really is off, it seems off, but there is full network stack and everything and it will talk to the net and send and fetch data.
But now people complain that Linux-driven devices would not fulfill all S5 criteria...
Stop TCPA, stupid software patents and corrupt politicians!
Comment
-
-
Originally posted by archkde View Post
No sarcasm intended at all. Complaints about S3 or s2idle not working properly are frequent. But before this article, I wasn't aware that the OS is even able to shut down the system improperly in the way described.
I went though a phase of being routinely unable to recover from suspend states (that was wireless network card related), but able to hibernate; and vice-versa.
I think that shutting down (and suspending) exercises rarely used code-paths, and rarely-used hardware facilities that are by no means bug-free. I don't think such problems are prioritised for resolution because it is 'always'* possible to 'just cut the power', which mostly has few after-effects,
*Not in phones that have unremovable batteries. Sometimes you have to wait for them to run flat. And not in remote devices, unless you have remotely-accessible power relays.
Comment
-
-
Originally posted by caligula View Post
In this case they actually improve the situation for customers by letting them buy higher quality systems with non-shit firmware.
Comment
-
-
Originally posted by Adarion View PostHoly shit, I would not have expected this.
S3 issues, yes, all the way. On some boxes it works, other mess up rarely on entering, but some, sadly, mess up on resume.
But Soft-off, ATX-off or S5, whatever we call it?
I thought INIT makes all the programs shut down (correctly). Then it flushes all buffers/caches to the drives. Unmounts the drives (on can follow that during shutdown/reboot procedure) so everything is synced, and finally it remounts / read-only and sends the hardware the shutdown or reboot command.
So does the kernel have to prepare hardware?
I thought the last part is matter of CPU or SIO/EC and the SIO/EC (incl. clock) is the only thing to remain powered by the PSU (as one can see when you measure power consumption that there is something like 0.5 Watts being pulled). And the SIO listenes to possible magic key from the keyboard (so yeah, kbd controller will also be on then) or to magic packet arriving for WOL. And in some BIOS setups you can configure that, if the computer can be switched on in soft-off by keyboard or if you really have to shortcut the pins with the power-on key to signal the PSU to send power to the mainboard.
And then there is Microsoft with their privacy-invading shitty "connected standby" and the likes. You computer never really is off, it seems off, but there is full network stack and everything and it will talk to the net and send and fetch data.
But now people complain that Linux-driven devices would not fulfill all S5 criteria...
Comment
-
Comment