From: Marco Roeland <marco.roeland@xs4all.nl>
To: Simon <simon@highlyillogical.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
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:42:45 +0100 [thread overview]
Message-ID: <20031127134245.GA9404@localhost> (raw)
In-Reply-To: <200311271323.37123.simon@highlyillogical.org>
At Thursday November 27th 2003 Simon wrote:
> Is there anything I can do about this apart from go back to 2.4 (I've grown to
> like CONFIG_PREEMPT too much for that!) or run with the battery in all the
> time? - I've a string of past laptops where the batteries only last 5 minutes
> because of running with battery + ac power all the time, so I've been in the
> habit of always removing it these days... - I've never had a problem running
> it at max speed with 2.4.
Well running without battery might cause problems, why disable a fine
UPC when it's there. ;-)
> 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.
--
Marco Roeland
next prev parent reply other threads:[~2003-11-27 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 11:39 [2.6.0-test10] cpufreq: 2G P4M won't go above 1.2G - cpuinfo_max_freq too low Simon
2003-11-27 12:18 ` Marco Roeland
2003-11-27 13:23 ` Simon
2003-11-27 13:42 ` Marco Roeland [this message]
2003-11-27 14:57 ` Simon
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:
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=20031127134245.GA9404@localhost \
--to=marco.roeland@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@highlyillogical.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).