On Sat, 22 Aug 2009, Joe Snikeris wrote:
> On Fri, Aug 21, 2009 at 11:53 PM, Ian Smith<smi...@nimnet.asn.au> wrote:
> > On Fri, 21 Aug 2009, Joe Snikeris wrote:
> > > On Thu, Aug 20, 2009 at 10:58 PM, Ian Smith<smi...@nimnet.asn.au> wrote:
> > > At any rate, I gave up on ACPI. I've got suspend-to-ram and
> > > suspend-to-disk (hibernation) working perfectly using APM.
> > >
> > > Does anyone know if there are any disadvantages related to
> > > power-saving features when using APM over ACPI? Is powerd able to do
> > > its job just as well?
> > The answer to that (at 5.5-STABLE) used to be 'no', but there is some
> > APM code in powerd.c, related to how it determines the AC line state,
> > though it's not clear to me if it would require compiling APM in kernel.
> > Certainly /etc/rc.d/power_profile can't set CPU CX states without ACPI.
> Ok. Just did a search to find out what CPU CX states were. For a
> good explanation of the CX states:
Good hunting; a good overview of current load/power handling on FreeBSD,
also posted to -mobile and/or -acpi as I recall.
> > Switching speeds relies on the dev.cpu.0.freq and dev.cpu.0.freq_levels
> > sysctls - are these available when you're running on APM? If so, try
> > running powerd(8) in verbose foreground mode (-v) and see what happens.
> Yes they are. And powerd in verbose foreground mode shows that it is
> lowering the frequency all the way down to 75 MHz depending on the
> load. Cool.
At 75MHz, it should be :)
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"