From: Thomas Seifert <thomas-lists@mysnip.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a couple of powernow-k8 questions
Date: Fri, 2 Jul 2004 16:12:44 +0200 [thread overview]
Message-ID: <20040702161244.3a3099ed.thomas-lists@mysnip.de> (raw)
In-Reply-To: <20040702122652.GA15169@elf.ucw.cz>
Hi Pavel,
thanks and its solved already.
I got a brand new bios (July 1st ;-)) from my mainboard-manufacturer
which solved the problem.
My CPU is now running nicely at 32°C.
Regards,
Thomas
On Fri, 2 Jul 2004 14:26:52 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> > I'm running an athlon64 3000+ on an epox-mainboard.
> >
> > after some bios-upgrades through their support I'm getting at least a bit
> > of powernow-support ;)
> >
> > Through startup I'm getting these messages now:
> >
> > powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09b)
> > powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x2 (1500 mV)
> > powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
> > powernow-k8: 2 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
> > powernow-k8: cpu_init done, current fid 0xc, vid 0x2
> > ACPI: (supports S0 S1 S4 S5)
> >
> >
> > Just to confirm: does that mean only these modes are supported?
> > Wasn't there something down to 800 MHz for the athlon64-processors?
>
> I'd say bios problem. Only AMD people know for sure.
>
> > Is this a problem of the mainbord (aka still their bios ;)) or of
> > the driver?
> > Any way to workaround this?
>
> Look into archives for methods how to override.
>
> Pavel
> --
> People were complaining that M$ turns users into beta-testers...
> ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
prev parent reply other threads:[~2004-07-02 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 20:33 Thomas Seifert
2004-07-02 12:26 ` Pavel Machek
2004-07-02 14:12 ` Thomas Seifert [this message]
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=20040702161244.3a3099ed.thomas-lists@mysnip.de \
--to=thomas-lists@mysnip.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®