S3 Standby State Done Right 216
For Earth Day, Cameron Butterfield has written in with a pointer to his article on how to get your Windows PC into S3 sleep, and why you want to. It covers the question of how to take advantage of this extremely low-power mode even when your machine is an "always on" file server, remote desktop, or VNC server.
And Linux? (Score:5, Insightful)
network broadcast traffic (Score:3, Insightful)
Will it not wake up whenever any workgroup broadcasts are sent to it?
Re:want a "file transfer" powerdown mode. (Score:3, Insightful)
Thanks to AMD's CnQ, and Intel later following suit, any CPU made in at least the past year (and more for AMD64 CPUs), will idle down to low power states automatically.
Also easy. You can hit the power button on the monitor, you can wait for it to automatically shut off after 15-20 minutes, or with X11, you can run xset and tell the video card o shut-off the monitor.
That one is not done, and is not really reasonably possible to do, nor helpful (on desktops) if it was done.
You need to write to the disk every few seconds, to maintain a consistent state, with or without a journaling file system. Your (desktop) HDD can't be spun-down in such a case, as spinning it up, over and over, would use more power than leaving it on, not to mention wear and tear... And since it's still spinning, even if you cached 1GB to RAM, flushing that to disk would use just as much power as writing it to the disk directly, a byte at a time.
Par for the couse. M$ booby trap. (Score:2, Insightful)
Windows XP will often times not give s3 suspend as an option even when turned on in BIOS. But with Microsofts dumppo.exe utility you can
How typical, a DOS only power tool to manipulate your hardware and everyone else is out of luck. Yeah, that stinks. [edge-op.org] Thanks, Bill.
Re:want a "file transfer" powerdown mode. (Score:3, Insightful)
Hate to tell you, but that's exactly what happens. You can't guaranty file system consistency when doing out-of-order writes. That's among the main reasons Ext3 does a full "fsync" every 6 seconds. It's a serious limitation of Ext2 in it's default mode. You're simply playing Russian Roulette with your data, and eventually you'll lose.
You certainly don't have to take my word for it. It's a well known issue, and there are several write-ups of it.
Re:Calculations are a bit off (Score:3, Insightful)
Some good options now are Seasonic S12, Antec NeoHE, Silverstone ST30NF, Nexus NX-80x0 series.
Re:Encore (Score:3, Insightful)