enigma_0Z wrote:
> Hmm.... lshw reports:
>
> Intel(R) Core(TM)2 Duo CPU
>
> Can you tell me if /sys/devices/system/cpu/cpu1/cpufreq is an
> independent file or a symlink on your system? As far as monitoring tools
> for the CPU Frequencies, /proc/cpuinfo is what I use, is there something
> better?
Hmmm, I don't think you have many other options. In fact, I just tried
it, and on my system it's a symlink as well. However, I know for sure
that they *did* work independently earlier, because at some point in the
7.04-7.10 area the second core got stuck at 2GHz after resuming from
suspend. For the record:
# uname -a
Linux bakbeest 2.6.24-3-generic #1 SMP Thu Jan 3 22:50:33 UTC 2008
x86_64 GNU/Linux
> My system is a Centrino laptop, but (as above) it has a Core 2 Duo CPU
> in it. Maybe something is set up wrong on my system? Is there some
> relevant config files for the CPU Frequencies? And what controls what
> goes into /sys/devices/system/cpu/*?
AFAIK it's the kernel, and nothing but the kernel. So this must be a
kernel problem.
enigma_0Z wrote: system/ cpu/cpu1/ cpufreq is an
> Hmm.... lshw reports:
>
> Intel(R) Core(TM)2 Duo CPU
>
> Can you tell me if /sys/devices/
> independent file or a symlink on your system? As far as monitoring tools
> for the CPU Frequencies, /proc/cpuinfo is what I use, is there something
> better?
Hmmm, I don't think you have many other options. In fact, I just tried
it, and on my system it's a symlink as well. However, I know for sure
that they *did* work independently earlier, because at some point in the
7.04-7.10 area the second core got stuck at 2GHz after resuming from
suspend. For the record:
# uname -a
Linux bakbeest 2.6.24-3-generic #1 SMP Thu Jan 3 22:50:33 UTC 2008
x86_64 GNU/Linux
> My system is a Centrino laptop, but (as above) it has a Core 2 Duo CPU system/ cpu/*?
> in it. Maybe something is set up wrong on my system? Is there some
> relevant config files for the CPU Frequencies? And what controls what
> goes into /sys/devices/
AFAIK it's the kernel, and nothing but the kernel. So this must be a
kernel problem.