From: CaT <cat@zip.com.au>
To: cpufreq@www.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.64 - cpu freq not turned on
Date: Fri, 7 Mar 2003 02:26:16 +1100 [thread overview]
Message-ID: <20030306152616.GB432@zip.com.au> (raw)
There was a 2.5.x kernel that allowed me to use cpufreq with it but the
recent ones just give me this message:
cpufreq: Intel(R) SpeedStep(TM) for this chipset not (yet) available.
Now I know it worked before cos I noticed it and played about with the 8
speed steps I had available to me (and I thought I only had 2).
What information is needed about my chipset to make the code detect it
properly?
(not on cpufreq ml btw)
--
"Other countries of course, bear the same risk. But there's no doubt his
hatred is mainly directed at us. After all this is the guy who tried to
kill my dad."
- George W. Bush Jr, 'President' of the United States
September 26, 2002 (from a political fundraiser in Huston, Texas)
next reply other threads:[~2003-03-06 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 15:26 CaT [this message]
2003-03-06 23:32 ` 2.5.64 - cpu freq not turned on Dominik Brodowski
2003-03-07 0:17 ` CaT
2003-03-07 11:22 ` Ducrot Bruno
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=20030306152616.GB432@zip.com.au \
--to=cat@zip.com.au \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).