public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Christopher Meredith <theophile@saintmail.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PowerNow!, cpufreq, and swsusp
Date: Wed, 12 Mar 2003 17:40:01 -0100	[thread overview]
Message-ID: <20030312183954.GA13653@suse.de> (raw)
In-Reply-To: <3e6f6919.1546.10699@saintmail.net>

On Wed, Mar 12, 2003 at 12:06:33PM -0500, Christopher Meredith wrote:

 > Also, cpufreq doesn't seem to do anything. Should it be
 > working automatically?

no.

 > Even when the machine sits unattended
 > for over 8 hours, the fan never turns off and the cpu
 > temperature is consustently 69-70 degrees C.

The kernel doesn't define policy, but exposes the necessary
interface to userspace.  There are a few folks working on
tools / scripts to adjust the speed dynamically.
look through the cpufreq mailing list archives to find them
(or google)

 > What must I do here?

Read Documentation/cpu-freq/user-guide.txt

short: mount sysfs, and ..

(root@evo:cpufreq)# cd /sys/class/cpu/cpufreq/cpu0/cpufreq
(root@evo:cpufreq)# cat /proc/cpuinfo | grep MHz
cpu MHz		: 1390.536
(root@evo:cpufreq)# echo powersave >scaling_governor
(root@evo:cpufreq)# cat /proc/cpuinfo | grep MHz
cpu MHz		: 529.728
(root@evo:cpufreq)# echo performance >scaling_governor

		Dave


  reply	other threads:[~2003-03-12 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 17:06 PowerNow!, cpufreq, and swsusp Christopher Meredith
2003-03-12 18:40 ` Dave Jones [this message]
2003-03-15 12:56   ` Christopher Meredith
2003-03-13  1:31 ` Nigel Cunningham
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 23:37 Christopher Meredith
2003-03-12 23:41 ` Greg KH

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=20030312183954.GA13653@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=theophile@saintmail.net \
    /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