Hi Martin,
no, x86info is also reporting wrong estimate. However, examining more
the output of cpufreq-info, it may be that the estimate by x86info is
actually right:
I have 2.4GHz Core 2 Duo. When I set the frequency to 800 MHz by
"cpufreq-set -f 80", then the "cpufreq-info" reports
Hi Pavel!
* Pavel Reznicek [2010-01-05 11:00]:
> sorry I haven't checked the other bug reports before writting this one -
> looking at bugs #501280 and #253524, it seems like the frequency monitor
> may not work on some processors. As written in my previous report, I did
> not have a chance
Hi Martin,
sorry I haven't checked the other bug reports before writting this one -
looking at bugs #501280 and #253524, it seems like the frequency monitor
may not work on some processors. As written in my previous report, I did
not have a chance to compare the monitor on two identical pro
Hi Pavel!
* Pavel Reznicek [2010-01-04 18:42]:
> are you really sure the package works fine on amd64 ? When enabling it
> in gkrellm, I can see a fluctuating frequency, but when I switch my Intel
> Core2 Duo to 800 MHz (using cpufreq-set), there is no change in the
> frequency monitoriged b
Hello,
are you really sure the package works fine on amd64 ? When enabling it
in gkrellm, I can see a fluctuating frequency, but when I switch my Intel
Core2 Duo to 800 MHz (using cpufreq-set), there is no change in the
frequency monitoriged by gkrellm, although cpufreq-get command returns
ow...@bugs.debian.org (Debian Bug Tracking System) writes:
> This is an automatic notification regarding your Bug report
> which was filed against the gkrellm-x86info package:
>
> #562699: Add gkrellm-x86info to amd64 port
>
> It has been closed by Martin Wuertele .
>
> Their explanation is attach
6 matches
Mail list logo
