From: Matthias Hentges <oe@hentges.net>
To: linux-acpi@vger.kernel.org
Subject: cpufreq frequencies off for Core 2 Duo E6600 "Conroe"
Date: Tue, 10 Oct 2006 02:41:03 +0200 [thread overview]
Message-ID: <1160440863.4575.69.camel@mhcln03> (raw)
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
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.
--
Matthias 'CoreDump' Hentges
My OS: Debian SID. Geek by Nature, Linux by Choice
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-10 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 0:41 Matthias Hentges [this message]
2006-10-26 2:49 ` cpufreq frequencies off for Core 2 Duo E6600 "Conroe" Dominik Brodowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1160440863.4575.69.camel@mhcln03 \
--to=oe@hentges.net \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox