From: Thomas Renninger <trenn@suse.de>
To: Erik Slagter <erik@slagter.name>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Pentium D 915 support
Date: Thu, 03 Aug 2006 13:44:53 +0200 [thread overview]
Message-ID: <1154605493.4302.494.camel@queen.suse.de> (raw)
In-Reply-To: <1154275129.21063.31.camel@skylla.slagter.name>
On Sun, 2006-07-30 at 17:58 +0200, Erik Slagter wrote:
> On zo, 2006-07-30 at 19:33 +0400, Alexey Starikovskiy wrote:
> modprobe acpi-cpufreq does work but output of cpufreq-info shows:
>
> > cpufrequtils 0.4: cpufreq-info (C) Dominik Brodowski 2004
> > Report errors and bugs to linux@brodo.de, please.
> > analyzing CPU 0:
> > driver: acpi-cpufreq
> > CPUs which need to switch frequency at the same time: 0
> > hardware limits: 2.40 GHz - 2.80 GHz
> > available frequency steps: 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.40 GHz available cpufreq governors: conservative, ondemand, powersave, userspace, performance
> > current policy: frequency should be within 2.40 GHz and 2.80 GHz.
> > The governor "performance" may decide which speed to use
> > within this range.
> > current CPU frequency is 2.80 GHz.
> > analyzing CPU 1:
> > driver: acpi-cpufreq
> > CPUs which need to switch frequency at the same time: 1
> > hardware limits: 2.40 GHz - 2.80 GHz
> > available frequency steps: 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.40 GHz available cpufreq governors: conservative, ondemand, powersave, userspace, performance
> > current policy: frequency should be within 2.40 GHz and 2.80 GHz.
> > The governor "performance" may decide which speed to use
> > within this range.
> > current CPU frequency is 2.80 GHz.
>
> Please note the amount of repeated same frequency.
>
I already saw something similar.
This is BIOS information, they probably want to take care that no
performance is lost and define 9 high and one low step.
> Also, it strikes me that /proc/acpi/../power only shows C1, is this normal?
>
On a Pentium D, I'd say yes.
> Last but not least: the loading or unloading of the module doesn't have
> any effect on the actual power consumption, even with powersave governor
> and both cores at 2.4 Ghz (both at 140 W).
Strange. 2.4 GHz is still a lot?
Have you already searched for a new BIOS, if not better do that first.
Thomas
next prev parent reply other threads:[~2006-08-03 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 13:12 Pentium D 915 support Erik Slagter
2006-07-30 15:33 ` Alexey Starikovskiy
2006-07-30 15:58 ` Erik Slagter
2006-08-03 11:44 ` Thomas Renninger [this message]
2006-08-03 11:48 ` Erik Slagter
2006-08-03 14:56 ` Thomas Renninger
2006-08-03 14:55 ` Erik Slagter
2006-08-03 15:29 ` Alexey Starikovskiy
2006-08-03 15:33 ` Erik Slagter
2006-08-03 15:51 ` Alexey Starikovskiy
2006-08-03 16:37 ` Thomas Renninger
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 15:57 Brown, Len
2006-08-03 16:29 ` Erik Slagter
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=1154605493.4302.494.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=erik@slagter.name \
/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