From: "Timothy A. Seufert" <tas@mindspring.com>
To: Dan Bethe <dan_bethe@yahoo.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: powerbook doubles as a frying pan
Date: Sat, 3 Feb 2001 15:24:45 -0800 [thread overview]
Message-ID: <v04220800b6a23b70189a@[10.0.0.42]> (raw)
In-Reply-To: <20010203030351.28012.qmail@web1003.mail.yahoo.com>
At 7:03 PM -0800 2/2/01, Dan Bethe wrote:
>> However, from what I've heard the G4 sensor is essentially useless.
>> On my own dual processor 500, a MacOS temperature readout utility
>> consistently tells me that one processor is 24 degC (or more) cooler
>> than the other. Both CPUs are the same die revision of course.
>
> Maybe one is being used more than the other. :) That would often be
>the case.
The construction of the heatsink used in the dual processor G4s
guarantees that the two processors should always be about the same
temperature. They're thermally coupled by a very thick chunk of
aluminum.
Besides, the difference between the readings remains the same whether
the machine is doing nothing or crunching RC5 full blast (the MacOS
RC5 client does use both CPUs).
> One is that the Wallstreet II series had a revision that had a
>motherboard bus somewhere around 83 MHz and was way hotter than the
>rest, which were often at 66 MHz. I'm pretty sure the cpu speed was
>292 MHz on that faster motherboard. They had to lower the motherboard
>bus for subsequent models because it was too hot.
That was the original Wall Street series, not Wall Street II (which
was actually codenamed "PDQ" by the way). The 233 MHz WS had a 66
MHz bus but the 250 and 292 MHz WS models had 83 MHz busses.
But the bus wasn't the reason they got so hot. That was caused by
the use of first generation 0.29 micron Motorola G3 processors (all
that was available), and inadequate cooling. Later versions of the
G3 were process shrunk and use a lower core voltage, resulting in
less than half the power consumption at the same clock. And later
versions of the PowerBook G3 got better cooling technology.
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-03 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 0:27 powerbook doubles as a frying pan Brad Midgley
2001-01-29 11:01 ` Benjamin Herrenschmidt
2001-01-29 15:15 ` Michael Schmitz
2001-01-29 15:30 ` Chas Williams
2001-01-29 21:54 ` Troy Benjegerdes
2001-02-03 3:15 ` Dan Bethe
2001-01-31 5:36 ` Timothy A. Seufert
2001-02-03 3:03 ` Dan Bethe
2001-02-03 23:24 ` Timothy A. Seufert [this message]
2001-02-05 12:46 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 1:09 Iain Sandoe
2001-01-29 15:27 Iain Sandoe
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='v04220800b6a23b70189a@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=dan_bethe@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).