From: Francesco Poli <frx@firenze.linux.it>
To: CpuFreq <cpufreq@www.linux.org.uk>
Subject: Re: longhaul gives /proc/sys/cpu/0/speed-m{in,max} = 0
Date: Thu, 1 Jan 2004 18:55:56 +0100 [thread overview]
Message-ID: <20040101185556.3354db6e.frx@firenze.linux.it> (raw)
In-Reply-To: <87n09aa0j2.fsf@emit.demon.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
On Tue, 30 Dec 2003 13:38:25 +0000 Ian McConnell wrote:
> Is this right? speed-min and speed-max are both zero so I can't use
> any of the userspace speed throttling programs such as cpuspeed-1.1.
With 2.4.x kernels, I think you must set the `userspace' governor in
order to have the CPU clock frequency (and voltage) assigned by a
userspace process: issue the following command (as root)
# echo -n "0%0%100%userspace" > /proc/cpufreq
and then you should be able to enjoy cpuspeed or whatever...
> Also if /proc/sys/cpu/0/speed = 0, how do I tell what speed my machine
> is running at?
The following command
$ cat /proc/cpuinfo
should show the actual CPU clock frequency (among the other things).
--
| GnuPG Key ID = DD6DFCF4 | You're compiling a program
Francesco | Key fingerprint = | and, all of a sudden, boom!
Poli | C979 F34B 27CE 5CD8 DC12 | -- from APT HOWTO,
| 31B5 78F4 279B DD6D FCF4 | version 1.8.0
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2004-01-01 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 13:38 longhaul gives /proc/sys/cpu/0/speed-m{in,max} = 0 Ian McConnell
2004-01-01 17:55 ` Francesco Poli [this message]
2004-01-02 16:33 ` Ian McConnell
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=20040101185556.3354db6e.frx@firenze.linux.it \
--to=frx@firenze.linux.it \
--cc=cpufreq@www.linux.org.uk \
/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