Re: Invalid detection CPU frequency ?

On Wednesday 28 September 2005 08:57, Vladimir Grebenschikov wrote:
> В вт, 27/09/2005 в 15:27 +0900, Hajimu UMEMOTO пишет:
>
> > I met this, too.  Putting cpufreq_load="YES" into your
> > /boot/loader.conf should solve your problem.
>
> Thank you, it really helps, now after boot I always get valid 1.7Ghz
> as high possible CPU speed.
>
> but sysctl picture changed:
> now I have:
> % sysctl dev.cpufreq dev.cpu dev.p4tcc dev.acpi_throttle
> dev.cpufreq.0.%driver: cpufreq
> dev.cpufreq.0.%parent: cpu0
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 1487
> dev.cpu.0.freq_levels: 1700/-1 1487/-1 1400/-1 1225/-1 1200/-1
> 1050/-1 1000/-1 875/-1 800/-1 700/-1 600/-1 525/-1 450/-1 375/-1
> 300/-1 225/-1 150/-1 75/-1 dev.p4tcc.0.%desc: CPU Frequency Thermal
> Control
> dev.p4tcc.0.%driver: p4tcc
> dev.p4tcc.0.%parent: cpu0
> dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1
> 3750/-1 2500/-1 1250/-1 sysctl: unknown oid 'dev.acpi_throttle'
> %
>
> so I've lost dev.acpi_throttle and got dev.p4tcc. Is it right ?

Yes, and it looks like you also gained dev.est.