On Sun, Jan 28, 2007 at 07:26:00PM +0100, Lars Stokholm wrote: > > Damnit, I seem to be making one mistake after another, with no end to > it. I'm truely sorry for wasting your time.
Been there, done that. A lot of times when I had a problem with the base
system (from 5.3-RELEASE uptil now) it turned out to be "pilot error".
> Let's step back to where I
> started; dev.cpu.0.cx_supported *does* exist:
>
> # sysctl dev.cpu.0.cx_supported
> dev.cpu.0.cx_supported: C1/0
>
> And here's the problem; this is what I get when I fire up FreeBSD:
>
> ...
> Starting ums0 moused:.
> hw.acpi.cpu.cx_lowest: C1
> sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
> Mounting NFS file systems:.
> ...
>
> Taking the power_profile into account, I guess it comes something
> similar to:
>
> # sysctl hw.acpi.cpu.cx_lowest=C1/0
I'm not sure that this is what is being called. The '/0' is removed by awk:
$ sysctl -n hw.acpi.cpu.cx_supported
C1/0
$ sysctl -n hw.acpi.cpu.cx_supported |awk '{ print "C" split($0, a) }' -
2>/dev/null
C1
> hw.acpi.cpu.cx_lowest: C1
> sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
Works fine here:
# sysctl hw.acpi.cpu.cx_lowest=C1/0
hw.acpi.cpu.cx_lowest: C1 -> C1
> So, finally, the question now is why I get the "invalid argument".
The only thing I can think of is that you've defined
performance_cx_lowest or economy_cx_lowest to some bogus value in rc.conf.
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpg0hSDD2GZF.pgp
Description: PGP signature
