Skip to contentSkip to conversation

cpufreq frequencies off for Core 2 Duo E6600 "Conroe"

DISCUSSION Matthias Hentges 2 participants 2 messages Oct 10, 2006 – Oct 26, 2006 ACPI

lore
Share & tools
lore
#0 lore raw

Hi all,

I'm the happy user of a shiny new C2D E6600 CPU. While cpufreq works, it only offers support for the lowest possible frequency (1596MHz)

(Linux mhcln01 2.6.19-rc1-git5-mh02 #3 SMP Tue Oct 10 01:35:05 CEST 2006 i686 GNU/Linux )

root@mhcln01:../system/cpu/cpu0/cpufreq >cat scaling_available_frequencies
2394000 2394000 2394000 2394000 2394000 2394000 2394000 2394000 2394000 1596000

As I understand it, the command above should list all possible "steps" for this CPU. The E6600 supports a multiplicator change between 6 and 9. For a default FSB of 266 this would mean the valid steps for the CPU are:

2394000 2128000 1862000 1596000

There is another thing bugging me with cpufreq:
+root@mhcln01:../system/cpu/cpu0/cpufreq >cat scaling_cur_freq 1596000
+root@mhcln01:../system/cpu/cpu0/cpufreq >cat cpuinfo_cur_freq 1596000

Since the machine is overclocked to FSB301 (2.7GHz), the output above is clearly wrong (should read 6 x 301 = 1806MHz). I wonder if it would be possible to replace the output with the real frequency, not some hard-wired frequency/vcore value?

Thanks for your time.

Signature · 3 lines
Matthias 'CoreDump' Hentges 

My OS: Debian SID. Geek by Nature, Linux by Choice
#1 lore raw

Hi,

Quoted 2 lines · Matthias Hentges

I'm the happy user of a shiny new C2D E6600 CPU. While cpufreq works, it only offers support for the lowest possible frequency (1596MHz)

That's probably because the BIOS only exposes the lowest and the highest frequency.

Quoted 10 lines

There is another thing bugging me with cpufreq:
+root@mhcln01:../system/cpu/cpu0/cpufreq >cat scaling_cur_freq 1596000
+root@mhcln01:../system/cpu/cpu0/cpufreq >cat cpuinfo_cur_freq 1596000

Since the machine is overclocked to FSB301 (2.7GHz), the output above is clearly wrong (should read 6 x 301 = 1806MHz). I wonder if it would be possible to replace the output with the real frequency, not some hard-wired frequency/vcore value?

Not easily.

Dominik