From: Tom Bruno <crweb@vwords.com>
To: cpufreq@www.linux.org.uk
Subject: Re: cpu won't stay in powersave mode
Date: Mon, 15 Dec 2003 15:18:04 +0000 [thread overview]
Message-ID: <1071501484.21334.1.camel@localhost> (raw)
Sorry, accendtly hit reply instead of send to list.
On Mon, 2003-12-15 at 14:14, Thomas Renninger wrote:
> Tom Bruno wrote:
>
> >Like i said above if I change it via hand using echo, /proc/cpuinfo
is
> >correct, and the cputest reports the correct speed constantly.
> >
> >performance mode: 2.4ghz
> >powersave mode: 1.2ghz
> >Intel P4-M 2.4ghz
> >Dell Inspiron 8500 - Bios A05
> >kernel-2.6.0-test11
> >
> >
> /proc/cpu_info didn't work for me, too.
> However it seems to work now(after I changed the governors to be
> compiled as modules(or the way around?)).
>
I've now tried both as modules, and compiled in, /proc/cpuinfo works
niether report correctly.
> If you want to detemine the current real speed of your machine use the
> procspeed prog I posted some days ago(04.12, 09.12).
yes, that is the program i spoke of. However, like i said, when
/proc/cpuinfo is reporting wrong, my system works it's way back to full
speed even though powersave is in the /sys scaling_governor.
It will report the changed speed (clockdown to 1.2ghz) for about 10
seconds, and then will start to report again at 2.4ghz even though the
setting haddn't changed.
--
Vwords.com Technology Services
PC and Network Services for Southern Illinois
Phone: 618-713-6896
--
Vwords.com Technology Services
PC and Network Services for Southern Illinois
Phone: 618-713-6896
next reply other threads:[~2003-12-15 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 15:18 Tom Bruno [this message]
2003-12-19 16:15 ` cpu won't stay in powersave mode Dominik Brodowski
2003-12-20 17:21 ` Tom Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-12-15 1:17 Tom Bruno
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=1071501484.21334.1.camel@localhost \
--to=crweb@vwords.com \
--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