linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Neil Jolly <jollyn@cadvision.com>
To: ian geiser <geiseri@msoe.edu>
Cc: "linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>,
	LinuxPPC List <linuxppc-user@lists.linuxppc.org>
Subject: Re: G3 Upgrade Questions....
Date: Tue, 27 Jul 1999 22:39:49 -0600	[thread overview]
Message-ID: <379E8995.31CA136B@cadvision.com> (raw)
In-Reply-To: 379E3513.738D0449@msoe.edu


ian geiser wrote:

> Hello,
>     I just installed a G3 upgrade card into my powercenter132
>     It is a 400Mhz with 1Meg at 200Mhz....
>     It registers under MacOS perfectly but i get the following under
>     proc/cpuinfo:
>     processor       : 0
>     cpu             : 750
>     temperature     : 0 C            <--Is this correct?!
>     clock           : 195MHz        <-- Is this correct?!
>     revision        : 130.1
>     bogomips        : 399.77
>     zero pages      : total 0 (0Kb) current: 0 (0Kb) hits: 0/1084 (0%)
>     machine         : Power Macintosh
>     motherboard     : AAPL,7300 MacRISC
>     memory          : 112MB
>
>     it only registers 195 Mhz and 0C for the temp... is the correct?
>     i am running Kernel 2.2.10

Here's a peek at my cpu info. A 233 G3 clocked to 292 with 83mhz bus, and
runs around 106 degrees F. Obviously the temp is not accurate, but clock
seems to be pretty close.

processor       : 0
cpu             : 750
temperature     : 0 C
clock           : 290MHz
revision        : 2.2
bogomips        : 581.63
zero pages      : total 0 (0Kb) current: 0 (0Kb) hits: 0/558 (0%)
machine         : Power Macintosh
motherboard     : AAPL,Gossamer MacRISC
L2 cache        : 512K unified pipelined-syncro-burst
memory          : 96MB


Neil


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  parent reply	other threads:[~1999-07-28  4:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-27 22:39 G3 Upgrade Questions ian geiser
1999-07-28  0:09 ` Paul Mackerras
1999-07-28 22:12   ` Jeremy Fitzhardinge
1999-07-29  0:47     ` I still cannot get L2cr to activate! ian reinhart geiser (ADMIN)
1999-07-29  4:46     ` G3 Upgrade Questions Takayuki Yamaizumi
1999-07-29  9:09       ` Adrian Cox
1999-07-30  1:38         ` Takayuki Yamaizumi
1999-07-30 11:38           ` Charles Lepple
     [not found]     ` <v04011707b3c5d8700e76@[199.174.198.69]>
     [not found]       ` <37A05228.3DFEDF87@msoe.edu>
1999-07-29 13:59         ` I still cannot get L2cr to activate! Jerry Quinn
1999-07-29 15:15           ` ian reinhart geiser (ADMIN)
1999-07-28  4:39 ` Neil Jolly [this message]
1999-07-28 12:53   ` G3 Upgrade Questions ian reinhart geiser (ADMIN)
     [not found] <87emhr7ocz.fsf@hades.nocrew.net>
1999-07-29 11:50 ` Geert Uytterhoeven
1999-07-29 12:12   ` Stefan Berndtsson
1999-07-29 12:32     ` Chris Ridd
1999-07-29 12:55     ` Gabriel Paubert
1999-07-29 13:30   ` Andreas Bogk
  -- strict thread matches above, loose matches on Subject: below --
1999-07-29 14:11 David DeHaven
1999-07-29 16:57 Ron Chmara

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=379E8995.31CA136B@cadvision.com \
    --to=jollyn@cadvision.com \
    --cc=geiseri@msoe.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@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).