From: Matthew East <matthew.east@gmail.com>
To: Matthew East <matthew.east@gmail.com>,
cpufreq@www.linux.org.uk, linux@dominikbrodowski.de
Subject: Re: celeron *clutches at straws*
Date: Thu, 6 Jan 2005 17:16:34 +0000 [thread overview]
Message-ID: <3bd9116050106091631b1282d@mail.gmail.com> (raw)
In-Reply-To: <20050106161312.GC10011@dominikbrodowski.de>
Hi Dominik,
> > Whereever I look on the internet a Family 15 Model 2 is reported as a
> > Pentium 4!! I know that the chips are similar. So what is the truth?
> > Is my chip cpufreq capable or not?
>
> AFAIK no. Even though many parts of the CPU are similar so that they can be
> represented with the same CPUID, Celerons only do have one multiplier so
> SpeedStep is not supported on them.
>
> > If not, is there anything else I can do to save battery power?
>
> You can use throttling (/proc/acpi/processor/./throttling or the cpufreq -
> p4-clockmod driver) to avoid the CPU heating so much the fan has to be
> enabled / has to turn at a higher speed which causes an increase in energy
> consumption. It doesn't save any real CPU power, though, as the CPU most
> likely is put into a good idle power state already (check for C2 or higher
> in /proc/acpo/processor/./power )
>
> Dominik
>
That is seriously useful thanks very much. I haven't looked in
/proc/acpi/processor before! I have found that the C2 state is
supported.
mdke@kallisto mdke $ cat /proc/acpi/processor/CPU0/power
active state: C2
default state: C1
bus master activity: 00000000
states:
C1: promotion[C2] demotion[--] latency[000]
usage[07824590] *C2: promotion[--] demotion[C1]
latency[002] usage[134432919]
C3: <not supported>
mdke@kallisto mdke $ cat /proc/acpi/processor/CPU0/info
processor id: 0
acpi id: 0
bus mastering control: yes
power management: yes
throttling control: yes
limit interface: yes
Most useful of all will be your information on throttling, which i
will experiment with. The last time I tried using throttling (through
some kde gui on a mandrake live disk), it made some strange whining
noises ;) Is it wholly safe? Noises make me uneasy... but of course
cooling down the processor would be nice as my fan is on far too much!
I'd like a bit of reassurance before I start though, so I'll post this
reply back to the list. Any help is appreciated very much!
Thanks again,
Matt
next prev parent reply other threads:[~2005-01-06 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 0:19 celeron *clutches at straws* Matthew East
2005-01-06 16:13 ` Dominik Brodowski
2005-01-06 17:16 ` Matthew East [this message]
2005-01-06 22:12 ` Dominik Brodowski
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=3bd9116050106091631b1282d@mail.gmail.com \
--to=matthew.east@gmail.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@dominikbrodowski.de \
/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