Problem on AMD64
yanefbsd at gmail.com
Mon Dec 22 13:15:52 PST 2008
On 12/22/08, David van Kuijk <dynasore at bigfoot.com> wrote:
> OK, thanks again. I didn't know those tools. est is not supported om
> AMD64, but I will start experimenting with powerd.
> The main thing I want to accomplish is to lower my energy bill after I
> found out my server is costing me 50 cents a day of electricity. So any
> other ideas (besides powering off ;-) are welcome...
> Kevin Oberman wrote:
>>> Date: Sun, 21 Dec 2008 22:31:04 +0100
>>> From: David van Kuijk <dynasore at bigfoot.com>
>>> Sender: owner-freebsd-acpi at freebsd.org
>>> Thanks for the responses so far.
>>> I would be happy with S3. I am however a little confused about the
>>> abilities of my server as reported by sysctl hw.acpi.
>>> As commented below this line suggests that no other states than S4/S5
>>> are supported:
>>> hw.acpi.supported_sleep_state: S4 S5
>>> But this is also listed:
>>> hw.acpi.standby_state: S1
>>> hw.acpi.suspend_state: S3
>>> Are these last two overridden by the first, meaning that S3 is not
>>> available from my BIOS???
>> Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because
>> almost all BIOSes support these states. Yours is the first BIOS I have
>> seen that does not do S1. That is really odd.
>> In any case, you have no available ways to cut power when your system is
>> really idle other than powering off. Of course, you may be able to do
>> some power saving with powerd and EST if your BIOS and CPU support those.
Look into the following sysctls:
Unfortunately [for you] est and PT4CC are completely Intel specific
power regulation interfaces.
AMD had something to offer on Linux, but I forget what that was...
More information about the freebsd-acpi