From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Matthias Hentges <oe@hentges.net>
Cc: linux-acpi@vger.kernel.org
Subject: Re: cpufreq frequencies off for Core 2 Duo E6600 "Conroe"
Date: Wed, 25 Oct 2006 22:49:21 -0400 [thread overview]
Message-ID: <20061026024921.GA18459@dominikbrodowski.de> (raw)
In-Reply-To: <1160440863.4575.69.camel@mhcln03>
Hi,
On Tue, Oct 10, 2006 at 02:41:03AM +0200, Matthias Hentges wrote:
> 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.
> 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
prev parent reply other threads:[~2006-10-26 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 0:41 cpufreq frequencies off for Core 2 Duo E6600 "Conroe" Matthias Hentges
2006-10-26 2:49 ` Dominik Brodowski [this message]
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=20061026024921.GA18459@dominikbrodowski.de \
--to=linux@dominikbrodowski.net \
--cc=linux-acpi@vger.kernel.org \
--cc=oe@hentges.net \
/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