From: Bruno Ducrot <ducrot@poupinou.org>
To: Nebojsa Trpkovic <trx@inbox.ru>
Cc: cpufreq@www.linux.org.uk
Subject: Re: powernow-k8 manual voltage selection ?
Date: Mon, 20 Dec 2004 15:12:03 +0100 [thread overview]
Message-ID: <20041220141203.GO2140@poupinou.org> (raw)
In-Reply-To: <E1CfpfX-000ID6-00.trx-inbox-ru@f17.mail.ru>
Hi,
On Sun, Dec 19, 2004 at 04:15:31AM +0300, Nebojsa Trpkovic wrote:
> Hello.
>
> I just got my new box and I'm testing it all day long :)
> It's Socket754 AMD Athlon (Newcastle) 3000+. I've spotted that it can run stable (>=1h in prime95) at voltages much lover than it's by default. Default is:
> 1.500V @2.0GHz
> 1.100V @1.0GHz
> And my tests show something like this (I haven't tested all frequencies yet):
> 1.525V @2.5GHz
> 1.400V @2.4GHz
> 1.325V @2.3GHz
> 1.250V @2.2GHz
> 1.200V @2.1GHz
> 1.150V @2.0GHz <---
> 1.075V @1.9GHz
> ... and so on.
How you have done this? By powernow-k8 or via BIOS setting? If the
latter, I will not trust this input yet. You can verify this is OK via
cpufrequtils at
http://www.kernel.org/pub/linux/utils/kernel/cpufreq/cpufrequtils-0.1.tar.bz2
then go to cpufrequtils-0.1/debug/x86_64 and issue a make, then ./powernow-k8-decode
as root. You must have the msr kernel driver loaded to get it working.
> My question is:
> Is there some way (PATCH) to specify manualy voltages for every FID my CPU can run?
This has been discussed some times ago. You have to do it yourself (or
maybe ask someone to give you some advice or browse the cpufreq archive,
etc).
Such patch will never reach mainline (but may be posted to this list for
reference purpose only).
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-12-20 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 1:15 powernow-k8 manual voltage selection ? Nebojsa Trpkovic
2004-12-20 14:12 ` Bruno Ducrot [this message]
2004-12-20 15:48 ` Nebojsa Trpkovic
2004-12-20 16:45 ` Bruno Ducrot
2004-12-20 16:58 ` Bruno Ducrot
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=20041220141203.GO2140@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=trx@inbox.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.