On Wed, Apr 23, 2008 at 08:09:14AM -0700, Steven A. DuChene wrote: > Is there actually anyone ON this mailing list or is it dead???
I haven't seen traffic since mid April, but I had some *stuff* happen to my mailing list accounts and have just gotten that straightened out. :( BTW, Hey Steve! How are you? I used to work on OSCAR. > -----Original Message----- > >From: "Steven A. DuChene" <[EMAIL PROTECTED]> > >Sent: Apr 14, 2008 11:41 PM > >To: [email protected] > >Subject: [Discuss] power state control question > > > >On the old web site at: > > > >http://acpi.sourceforge.net/documentation/sleep.html > > > >it talks about for 2.6 kernel the system sleep state > >can be controlled via /sys/power/state but nowhere on > >the new lesswatts.org site does it say ANYTHING about > >how to actually controlling the system or how to put > >it into any of the available sleep states. Is this still > >a valid way to control this or is this a outmoded means of > >accomplishing anything or only available/implemented on > >laptops for instance? I have a Dell laptop with Intel Core2 > >Duo cpu and I see this /sys file on the system with a > >2.6.24.2 kernel but on a server I am experimenting with > >that has SLES10SP1 installed with a 2.6.16.46 kernel > >with Intel Xeon E5335 cpus I do not see this /sys file. > >I have checked the kernel boot line in grub menu.lst but > >there is nothing there turning off acpi. So, here's the deal, if you cat /sys/power/state You'll se a bunch of words. Those are the purportedly available states. I hedge this as some BIOS implementations, well, lie by advertising states (usually "mem") that don't actually work. At any rate, "standby" means S1, a.k.a., STOPGRANT; "mem" means S3; "disk" means S4. So, to enter one of these states, you need to echo _state_ > /sys/power/state where _state_ is one of the available words. GIYF, and will guide you to greater understanding. The usual issues in getting a system in to *and* out of S3 have to do with device drivers. Be very aware that some systems will go into S3, but never come (fully) out. In the general case, this is due to wonky drivers or various other needed massaging, like getting video to recover, so you may need to work at this. I have a *very* small kernel/uClibc/busybox-based stack that I personally use to test a system's S3 support--I only use a serial console on this thing, with no video support, no NICs, no disk, essentially nothing except a minimal kernel. IMHO, if this can't do S3, I don't think anything else can. So, now the punch line. AFAIK, most servers don't do S3. I suggest you try on a laptop first, to see how it all goes before attempting a server. -- David N. Lombard, Intel, Irvine, CA I do not speak for Intel Corporation; all comments are strictly my own. _______________________________________________ Discuss mailing list [email protected] http://mail.lesswatts.org/mailman/listinfo/discuss
