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 13:18:01 +0100 [thread overview]
Message-ID: <20031127121801.GB9098@localhost> (raw)
In-Reply-To: <200311271139.07260.simon@highlyillogical.org>
On Thursday November 27th 2003 Simon wrote:
> I have a P4 2ghz (in a thinkpad), but it's not running at over about 1.2ghz
> now. If I `cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq` it
> tells me: "1198976". It should go faster than that. Similarly,
> scaling_available_frequencies says "149872 299744 449616 599488 749360 899232
> 1049104 1198976"
Don't know if this will help you, but I had the exact same problem on a
Compaq EVO N1050v (well 1.8 GHz instead of 2.0 GHz and it initially only
managed 1.2 GHz as mentioned in /proc/cpuinfo and from benchmarks).
It turned out to be an ACPI problem. Booting on 2.6 with "acpi=off" lead
to the correct 1.8GHz determination instead of only 1.2GHz, but no working
ACPI of course. On 2.4.21 booting either with of without ACPI made no
difference and lead on both occasions to 1.8GHz.
After upgrading the BIOS to the latest version I could finally run 2.6
with ACPI and at full capacity.
Incidentally a certain other OS which shall remain unnamed, reported the
maximum speed also as 1.2 GHz before the BIOS upgrade and as 1.8 GHz
after, but worked both times at 1.8 GHz, just as in Linux 2.4 ;-) After
this final hurdle had been straddled I regained control of /dev/hda1;
Anton does great work on NTFS, but I have work to do!
--
Marco Roeland
next prev parent reply other threads:[~2003-11-27 12:18 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 [this message]
2003-11-27 13:23 ` Simon
2003-11-27 13:42 ` Marco Roeland
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=20031127121801.GB9098@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).