From: Ducrot Bruno <ducrot@poupinou.org>
To: Wouter Verhelst <wouter@grep.be>
Cc: cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Sat, 10 Jan 2004 19:53:08 +0100 [thread overview]
Message-ID: <20040110185308.GZ14031@poupinou.org> (raw)
In-Reply-To: <20040110163212.GD10531@grep.be>
On Sat, Jan 10, 2004 at 05:32:12PM +0100, Wouter Verhelst wrote:
> On Sat, Jan 10, 2004 at 04:41:10PM +0100, Dominik Brodowski wrote:
> > On Sat, Jan 10, 2004 at 04:21:45PM +0100, Wouter Verhelst wrote:
> > > On Sat, Jan 10, 2004 at 02:18:24PM +0100, Dominik Brodowski wrote:
> > > > On Sat, Jan 10, 2004 at 12:08:00PM +0100, Wouter Verhelst wrote:
> > > > > Vanilla 2.6.1, but I had the same problem with 2.6.0 (didn't try
> > > > > p4-clockmod on any kernel before that).
> > > >
> > > > You shouldn't need to use p4-clockmod at all... speedstep-ich is a better
> > > > choice for your system...
> > >
> > > This doesn't seem to work, it says 'No such device'. I have a VIA 82C686
> > > south bridge, not an Intel one, so I guess that's the reason.
> >
> > Unfortunately, you're right. VIA doesn't publish their spec sheets as Intel
> > does, so there's no speedstep-via driver (yet). Maybe acpi.ko works?
>
> It does, but when my CPU is throttled, it makes an uncomfortable sound
> at high frequency, so I try to avoid that.
>
Do you mean the processor is at high speed (performance), and throttling
is enabled?
So it should not be even surprising.
The P4 is able to throttle itself, so I guess the throttling
things done externally by the south bridge would have not even
been tested by the platform designer...
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-10 18:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 18:18 p4-clockmod doesn't seem to allow the highest possible speed Wouter Verhelst
2004-01-10 10:15 ` Dominik Brodowski
2004-01-10 11:08 ` Wouter Verhelst
2004-01-10 13:18 ` Dominik Brodowski
2004-01-10 15:02 ` Wouter Verhelst
2004-01-10 15:38 ` Dominik Brodowski
2004-01-10 16:30 ` Wouter Verhelst
2004-01-10 15:21 ` Wouter Verhelst
2004-01-10 15:41 ` Dominik Brodowski
2004-01-10 16:32 ` Wouter Verhelst
2004-01-10 18:53 ` Ducrot Bruno [this message]
2004-01-10 19:35 ` Wouter Verhelst
2004-01-11 15:48 ` Ducrot Bruno
2004-01-11 17:30 ` Dominik Brodowski
2004-01-11 18:05 ` Ducrot Bruno
2004-01-11 17:35 ` Dominik Brodowski
2004-01-11 19:56 ` Wouter Verhelst
2004-01-11 20:06 ` Dominik Brodowski
2004-01-11 20:24 ` Wouter Verhelst
2004-01-12 12:26 ` Ducrot 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=20040110185308.GZ14031@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=wouter@grep.be \
/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.