LKML Archive on
help / color / mirror / Atom feed
From: Simon <>
To: Marco Roeland <>
Cc: Linux Kernel Development <>
Subject: Re: [2.6.0-test10] cpufreq: 2G P4M won't go above 1.2G - cpuinfo_max_freq too low
Date: Thu, 27 Nov 2003 14:57:48 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20031127134245.GA9404@localhost>

On Thursday 27 November 2003 1:42 pm, Marco Roeland wrote:

> > Seems that this is a fault of a better implementation of something... But
> > "better" to me shouldn't take away choice of cpu speed from the user? ;)
> One last straw you might try, is building all the different cpufreq
> drivers as modules, and trying if modprobeing one of them might work.
> They seem to all behave slightly differently with respect to what they
> assume to be true from the ACPI reported values, and what they try on
> their own.

You're a star, thankyou. It was loading p4-clockmod by default. I had all the 
pentium-related modules compiled in, and it was behaving like that... dmesg 
said it was loading p4-clockmod.

I modprobe'd speedstep-ich instead, and foom! Straight up to 2ghz.


  reply	other threads:[~2003-11-27 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 11:39 Simon
2003-11-27 12:18 ` Marco Roeland
2003-11-27 13:23   ` Simon
2003-11-27 13:42     ` Marco Roeland
2003-11-27 14:57       ` Simon [this message]
2003-11-27 15:23         ` Marco Roeland

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [2.6.0-test10] cpufreq: 2G P4M won'\''t go above 1.2G - cpuinfo_max_freq too low' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).