Linux 版 (精华区)
发信人: netiscpu (说不如做), 信区: Unix
标 题: [转载] SGI hardware FAQ
发信站: 紫 丁 香 (Fri Jun 26 20:57:50 1998), 转信
【 以下文字转载自 cnunix 讨论区 】
【 原文由 Gamble_Tan@bbs.ustc.edu.cn 所发表 】
SGI hardware Frequently Asked Questions (FAQ)
This is one of the Silicon Graphics FAQ series, which consists of:
SGI admin FAQ - IRIX system administration
SGI apps FAQ - Applications and miscellaneous programming
SGI audio FAQ - Audio applications and programming
SGI diffs FAQ - Changes to the other FAQs since the last posting
SGI graphics FAQ - Graphics and user environment customization
SGI hardware FAQ - Hardware
SGI impressario FAQ - IRIS Impressario
SGI inventor FAQ - IRIS Inventor
SGI misc FAQ - Introduction & miscellaneous information
SGI movie FAQ - Movies
SGI performer FAQ - IRIS Performer
SGI pointer FAQ - Pointer to the other FAQs
SGI security FAQ - IRIX security
Read the misc FAQ for information about the FAQs themselves. Each FAQ is
posted to comp.sys.sgi.misc and to the news.answers and comp.answers
newsgroups (whose purpose is to store FAQs) twice per month. If you
can't find one of the FAQs with your news program, you can get it from
ftp://viz.tamu.edu/pub/sgi/faq/
ftp://rtfm.mit.edu/pub/usenet/news.answers/sgi/faq/
(rtfm.mit.edu is home to many other FAQs and informational documents,
and is a good place to look if you can't find an answer here.) The FAQs
are on the World Wide Web at
http://www-viz.tamu.edu/~sgi-faq/
If you can't use FTP or WWW, send mail to mail-server@rtfm.mit.edu with
the word 'help' on a line by itself in the text, and it will send you a
document describing how to get files from rtfm.mit.edu by mail. Send the
command 'send usenet/news.answers/sgi/faq/misc' to get the SGI misc FAQ,
and similarly for the other FAQs. Send the command 'send
usenet/news.answers/internet-services/access-via-email' to get the
"Accessing the Internet by E-Mail FAQ".
You may distribute the SGI FAQs freely and we encourage you to do so.
However, you must keep them intact, including headers and this notice,
and you must not charge for or profit from them. Contact us for other
arrangements. We can't be responsible for copies of the SGI FAQs at
sites which we do not control, and copies published on paper or CD-ROM
are certain to be out of date. The contents are accurate as far as we
know, but the usual disclaimers apply. Send additions and changes to
sgi-faq@viz.tamu.edu.
Topics covered in this FAQ:
---------------------------
-1- GENERAL INFORMATION
-2- Where can I get a copy of SGI's Periodic Table of the Irises?
-3- What third-party vendors sell thus-and-such for SGIs?
-4- Where can I get used SGI machines?
-5- What is my old SGI machine worth?
-6- What about my IRIS 2000 or 3000?
-7- Should I shut off my Iris at night?
-8- How fast is my R4000 or R4400 machine?
-9- What is the IP number of each SGI model?
-10- What graphics and audio options were/are available for each
model?
-11- What OS versions are supported on which platforms?
-12- MEMORY
-13- What type of memory does each SGI model use?
-14- Can I mix 1MB and 2MB SIMMS in my 4D/20 & 4D/25 Personal IRISes?
-15- Can I add 4MB SIMMS to my 4D/20 or 4D/25 PI?
-16- How many 4MB SIMMS can be put into an Indigo?
-17- How can I find a bad SIMM?
-18- Why does my system tell me I need a revision C Memory Controller
(MC) chip?
-19- Should I worry about a "recoverable memory parity error"?
-20- MONITORS AND VIDEO HARDWARE
-21- My monitor is maladjusted in some way. How to fix it?
-22- Can I have 2 graphics displays on my Indigo?
-23- What do I need to do stereo on an Onyx/RE2?
-24- Can I use my SGI monitor on my PC?
-25- Can I use my PC monitor on my SGI?
-26- What video formats, scan rate, etc. do SGI monitors support?
-27- How can I set my Indy to use 1280x1024 pixels on a third-party
monitor?
-28- What is the pinout for the Indy's 13W3 video connector?
-29- STORAGE DEVICES
-30- What do all these SCSI technical terms mean?
-31- How many SCSI devices can I have on an Indigo?
-32- How do I install external SCSI disks on my SGI?
-33- What kind of DAT drive does SGI sell for the Indigo?
-34- Can I use a 3rd-party cartridge tape drive on my Indigo?
-35- Which Exabyte drives work with SGI systems?
-36- How to connect my 3rd-party tape drive to my SGI?
-37- How should I set up my tape drive so tar's 'r' and 'u' options
work?
-38- What do I do when I can't read a tar tape made on another system?
-39- Why can't I write a tape on my DEC DAT drive and read it on my
SGI?
-40- Why does my SGI think my DAT has audio on it when it actually has
data?
-41- How can I recover a partially overwritten tar tape?
-42- When and how should I clean my tape drive?
-43- Why don't no-rewind tape devices always work in IRIX 5.3/6.0.1?
-44- What dump parameters should I use?
-45- How can I eject a jammed tape or CD?
-46- Can I use a non-SGI CD-ROM on my SGI?
-47- Can I use an SGI CD-ROM on a non-SGI?
-48- How can I write CD-ROMs on an SGI?
-49- Why can't Joe User eject his CD-ROM?
-50- How can Joe User mount and unmount his magneto-optical disk?
-51- Why do SGI SCSI controllers have host ID 0 instead of the usual
7?
-52- What about Syquest and Iomega (Zip, Jaz) removable media drives?
-53- EVERYTHING ELSE
-54- How long can my monitor/keyboard/mouse/Indycam cables be?
-55- How fast is the Indigo parallel port?
-56- What are the differences between the Indigo R4000 and Indigo2?
-57- What high speed interfaces are available for Onyx?
-58- Why doesn't my modem work?
-59- What about ISDN?
-60- What mice (or other pointing devices) can I use with my SGI?
-61- What about joysticks?
-62- What about uninterruptable power supplies?
-63- How can ordinary users control the multi-channel option (MCO)?
-64- What laptop or notebook SGIs are available?
----------------------------------------------------------------------
Subject: -1- GENERAL INFORMATION
Date: 09 Jan 1994 00:00:01 EST
The next few items discuss general questions about hardware.
------------------------------
Subject: -2- Where can I get a copy of SGI's Periodic Table of the
Irises?
Date: 10 Dec 1993 00:00:01 EST
SGI Direct (see the misc FAQ for phone numbers) and your friendly
neighborhood salesbeing are guaranteed to have the latest.
Nonetheless, the misc FAQ lists the locations of FTPable Postscript
versions under "What are some related network-accessible
documents?".
------------------------------
Subject: -3- What third-party vendors sell thus-and-such for SGIs?
Date: 12 May 1996 00:00:01 EST
See ftp://viz.tamu.edu/pub/sgi/hardware/3rd-party and
http://www.vigyan.com/~blbates/hardware/.
------------------------------
Subject: -4- Where can I get used SGI machines?
Date: 4 Jun 1997 00:00:01 CST
The SGI Systems Remarketing group makes used SGI machines available
to sales representatives. If you want to buy a used SGI machine, ask
your local sales rep or call SGI Direct (see the misc FAQ for phone
numbers).
wgbhres@world.std.com (Boris Levitin) and gcook@netcom.com
(Gary W. Cook) have supplied the following remarketer information:
Concorde Group
phone: 800-333-2786, 617-491-0400 fax: 617-491-7710
WWW: http://www.concorde.com/
Falcon Systems
phone: 800-326-1002, 916-344-1221 fax: 916-344-1292
WWW: http://www.falcons.com/
Great Eastern Technology <info@get.com>
phone: 617-937-0300
Inmartech <info@inmartech.com>
phone: 408-733-1480
Minicomputer Exchange, John McFarland
phone: 408-733-4400
WWW: http://www.mce.com/
R-Squared, Tony Sciacca <tonys@r2.com>
phone: 800-777-3478, 303-799-9292 fax: 303-799-9297
Recurrent Technologies <sales@recurrent.com>
phone: 408-727-1122
Reputable Systems, Greg Douglas <gdouglas@reputable.com>
phone: 303-444-2664
WWW: http://www.reputable.com/
Security Computer Sales
phone: 612-227-5683
Sun Valley Technical Repair, Joe Ferris
phone: 408-224-6261
X-Systems, Jon Nies <xsys@xsys.com>
phone: 800-886-5343 fax: 303-443-7440
XS International
phone: 404-874-1212
------------------------------
Subject: -5- What is my old SGI machine worth?
Date: 27 Jun 1996 00:00:01 EST
Thanks to Thomas Sippel-Dau <cmaae47@imperial.ac.uk> for this
summary:
Since computer technology has been improving so rapidly, this is
difficult to answer generally. But you can take the following
approches to get somewhere near a realistic estimate.
1. The Book Value.
This assumes the computer is an investment object which is written
down over a certain time. At the end of this time it is assumed that
the residual value will pay for scrapping the object, so you do not
have to pay someone to take it away. About 5 years seems reasonable
for computers.
Value the current value
Price the original price
n the age of the machine in months
p depreciation rate 1.6% (for 62.5 months useful life)
1.1 Linear method: Value = Price * ( 1 - n * p )
1.2 Degressive method: Value = Price * ( 1 - 2 * p ) ** n
In the first 4 years the degressive method will give lower values.
Once the degressive monthly depreciation is lower than the linear
one, you should sell the machine and buy a new one, otherwise you pay
more tax than you need to (talk to your accountants first, they
should know the exact depreciation rate and method).
2. Comparative method.
Get the new price of a similar current machine. Multiply the current
price by any usefulness multipliers. For example:
An Indigo R3000 server costs $8000 (N.B. NOT the real price)
An Iris 4D/25 is about half the speed of it
Then the current value of the 4D/25 cannot be more than $4000
regardless of what the book value says.
For this you must strip or enhance the machine to a current standard.
Say you take the price of an Indigo with 432 disk Mbyte and 16 Mbyte
memory to assess the residual value of a 4D/25 with eight Mbyte
memory and 330 Mbyte hard disk. You will arrive at the price after
you have upgraded the the 4D/25 to 16 Mbyte.
Since both machines are not very useful (stand alone) with so little
disk space, you can allow for the difference in disk space when you
calculate the price of the whole running system.
For this method the old system must be able to run current software
usefully. A system that does not run current software has no value,
but see below.
You should also take account of the maintenance cost for about three
years, which is when a system you buy now would be due for
replacement according to the book value method.
3. Components and options.
You can view the system as an assembly of useful parts, such as
monitor, keyboard, disk drives, system box, electronics module. If
you have extra memory or disks (over and above the currently useful
minimum), you can value them at about 80% of the price you currently
have to pay third party suppliers.
4. Residual use value.
If you can find a dedicated use for an old general purpose machine,
then this could give you a final number. However, you need to allow
for any work you have to put in to get to that state, and to keep the
system there. You will also find that only reasonably large
organisations have such dedicated uses.
Finally, a word about maintenance:
If you have one system only, and you cannot afford to lose it, you
need to take maintenance, regardless of how much it is. From about 5
systems you can save yourself maintenance if you can afford to lose
the odd system and load its uses onto the remaining ones. But
remember that rescheduling people often meets resistance, and keeping
people idle because of a system failure is extremely expensive.
See also David Dennis <david@amazing.com>'s "Buying Old SGI Systems
FAQ", cited in the misc FAQ.
------------------------------
Subject: -6- What about my IRIS 2000 or 3000?
Date: 20 Jul 1996 00:00:01 EST
See the IRIS 2000/3000 mailing list and FAQ (cited in the misc FAQ,
the latter under "What are some related network-accessible
documents?") and ftp://viz.tamu.edu/pub/sgi/hardware/4Dxx0.
------------------------------
Subject: -7- Should I shut off my Iris at night?
Date: 01 Jul 1994 00:00:01 EST
(Home users often ask this.) No, you should not. The hardware is
designed for continuous use, and IRIX schedules cleanup tasks for the
early morning. (See the cron(1M) and crontab(1) manpages and the
files in /usr/spool/cron.) Disks, tapes, CD-ROMs etc. consume little
power when idle and should NEVER be turned off or on (or connected or
disconnected) when the system is running.
However, turning off your *monitor* will save power and prolong its
life.
------------------------------
Subject: -8- How fast is my R4000 or R4400 machine?
Date: 27 Jan 1996 00:00:01 EST
Eric Williams <williams@agomoda.asd.sgi.com> reveals all:
It is confusing to spec the clock frequency for the R4000 and R4400
because they are so flexible. There are four interesting numbers:
- internal clock
- external clock
- secondary cache access cycle
- SYSINT frequency
Let's start by specifying the processor internal frequency. e.g. 150
MHz. All other frequencies are specified with respect to this one.
For programs that get good primary cache hit rates this number will
determine the performance.
The clock input to the R4400 (i.e. the crystal you buy) is always
half the internal frequency. In this case 75 MHz. This is generally
the number used by the chip manufacturers, to specify the speed of
the part. However from a system point of view, it is the least
visible to the user, and therefore IMHO the least interesting.
The secondary cache read and write access cycles are programmable in
terms the internal clock frequency (e.g. 150 MHz cycles). This
allows you to trade off the cost/speed of secondary cache rams with
system performance. When upgrading from 100 MHz to 150 MHz you can
either keep the same rams and increase the SCache access cycle or
install faster rams and keep the number of cycles constant. The
first option keeps the cost to a minimum while the second maximizes
performance.
Finally the interface that talks to the system (SYSINT) can run at a
programmable fraction (1/2, 1/3, ...) of the internal frequency. For
the example 150 MHz processor, this could be 75 MHz, 50 MHz, etc.
This puts an upper limit on the bandwidth to memory and affects some
latency parameters. Typically you would program the system interface
to run synchronously with the memory controller.
From what I've heard here about the Indy R4400 upgrade (I'm not
involved with it) I think you could say the following:
- the internal clock (primary cache, instruction execution, etc)
increases from 100 MHz to 150 MHz
- the clock crystal increases from 50 MHz to 75 MHz
- the secondary cache access times stays the same in absolute
terms (but increases in terms of internal clock cycles)
- the system interface to memory stays at 50 MHz (100 MHz div 2, vs.
150 MHz div 3)
BTW, the Indy upgrade example illustrates why IMHO the 75 MHz
external frequency of the R4400 is not an interesting number to
quote. Performance of real programs will be determined by the
internal 150 MHz clock, the secondary cache timing and the system
interface/memory speed, not the 75 MHz external clock.
The Jan/Feb 1996 Pipeline has a table of Indigo, Indy and Indigo^2
processor types and the versions of IRIX which support them.
------------------------------
Subject: -9- What is the IP number of each SGI model?
Date: 04 Jul 1996 00:00:01 EST
There are two different IP numbers, one referring to the hardware and
one to the software (kernel configuration). The latter is what you
see when you type 'hinv'. Here is a table of both numbers:
HW IP SW IP Model CPU Speed
----- ----- -------------------- ----- -----------
IP2 IP2 IRIS 3000 68020
IP4 IP4 4D/50, 4D/70 R2000 12.5MHz
IP4.5 IP4.5 4D/80, 4D/85 R2000 16MHz
4D/60 R2300
IP5 IP5 4D/1x0 R3000 16.7MHz
IP6 IP6 4D/20 R3000 12.5MHz
IP10 IP6 4D/25 R3000 20MHz
IP7 IP7 4D/2x0 R3000 25MHz
IP9 IP9 4D/210 R3000 25MHz
IP13 IP7 4D/3x0 R3000 33MHz
IP15 IP7 4D/4x0 R3000 40MHz
IP12 IP12 4D/30, 4D/35, Indigo R3000 30-36MHz
IP17 IP17 Crimson R4x00 50 or 75MHz
IP19 IP19 Onyx, Challenge R4x00 50 or 75MHz
IP20 IP20 Indigo R4000 R4x00 50 or 75MHz
IP22 IP22 Indigo2 R4x00 50 or 75MHz
IP24 IP22 Indy R4x00 50 or 75MHz
IP25 R10000 200 MHz
IP26 Challenge R8000 75 MHz
The missing numbers were used for machines that were not released.
R4x00 machines can be 50 MHz R4000s or 75Mhz R4400s. 'hinv' reports
twice that in recent versions of IRIX; see the previous question for
an explanation. We use the smaller number here for consistency.
------------------------------
Subject: -10- What graphics and audio options were/are available for
each model?
Date: 20 Apr 1996 00:00:01 EST
Walter Roberson <roberson@ibd.nrc.ca> writes: Here's a first draft.
Some of the fine details might be off a little, especially with respect
to older systems. CPU type is important in determining which graphics
options are supported.
Fields are
model: cpu@speed: audio notes
gfx code name (gfx market name ["gfxinfo board name: #bitplanes,
#Z planes, implementing hardware])
4D20: IP6@12: /dev/audio (8 bit u-law)
Da Vinci ([24, no Z]),
Eclipse (B ["VGR2"], G ["GR1": 24, 24 Z, RE1|RE2],
TG ["GR1": 24, 24 Z, RE1|RE2])
4D25: IP6@20: /dev/audio (8 bit u-law)
Da Vinci ([24, no Z]),
Eclipse (B ["VGR2"], G ["GR1": 24, 24 Z, RE1|RE2],
TG ["GR1": 24, 24 Z, RE1|RE2])
4D30: IP12@30: Indigo-type audio optional
Eclipse (B ["VGR2"], G ["GR1": 24, 24 Z, RE2], TG ["GR1": 24, 24 Z, RE2]),
Express (XS ["GR2", 8, no Z, 1 GE7, 1 RE3],
XS24 ["GR2": 24, no Z, 1 GE7, 1 RE3],
Elan ["GR2-Elan": 24, Z, 4 GE7, 1 RE3])
4D35: IP12@36: Indigo-type audio optional
Eclipse (B ["VGR2"], G ["GR1": 24, 24 Z, RE2], G ["GR1": 24, 24 Z, RE2]),
Express (XS ["GR2", 8, no Z, 1 GE7, 1 RE3],
XS24 ["GR2": 24, no Z, 1 GE7, 1 RE3],
Elan ["GR2-Elan": 24, Z, 4 GE7, 1 RE3])
4DRPC (R3000 Indigo): IP12@33: audio built in
Express (XS ["GR2", 8, no Z, 1 GE7, 1 RE3],
XS24 ["GR2": 24, no Z, 1 GE7, 1 RE3],
XSM ["GR2": 24, no Z, 4 GE7, 1 RE3],
Elan ["GR2-Elan": 24, Z, 4 GE7, 1 RE3]),
Starter/Light (Entry ["LG1": 8, soft Z, LG2, REX])
4D4RPC? (R4000 Indigo): IP20: audio built in
Express (XS ["GR2": 8, no Z, 1 GE7, 1 RE3],
XSM ["GR2": 24, no Z, 4 GE7, 1 RE3],
XZ ["GR2-XZ": 24, Z, 2 GE7, 1 RE3],
Elan ["GR2-Elan": 24, Z, 4 GE7, 1 RE3])
Starter/Light (Entry ["LG1MC": 8, soft Z, LG2, REX]),
4D50: IP4@12.5: no audio
Clover1 (B, G [optional Z])
4D60: IP4.5@16: no audio
Clover1 (B, G [optional Z])
4D70: IP4@12.5: no audio
Clover1 (B, G [optional Z]),
Clover2 (GT [Z], GTX [Z])
4D80: IP4.5@16: no audio
Clover2 (GT [Z], GTX [Z])
4D85: IP4.5@16: no audio
Clover2 (GT [Z], GTX [Z])
4D120: IP5@16.7: Vigra VME audio optional (not AL compatable)
Clover2 (GTX ["GTX": GM2, GE4, RM1, RV2]),
Stapuft (SKY, VGX ["VGX": IMP3]),
Venice (RealityEngine ["RE": 8 GE8, 2 RM4])
4D210: IP9@25: Vigra VME audio optional (not AL compatable)
Clover2 (GT ["GT": GM2, GE4, RM1, RV1], GTX ["GTX": GM2, GE4, RM1, RV2]),
Stapuft (VGX ["VGX": IMP3])
4D2[248]0: IP7@25: Vigra VME audio optional (not AL compatable)
Clover2 (GT ["GT": GM2, GE4, RM1, RV1], GTX ["GTX": GM2, GE4, RM1, RV2]),
Stapuft (VGX ["VGX": IMP3], VGXT/SKY ["VGX": IMP5])
4D310 (Crimson): IP17: Vigra VME audio optional (not AL compatable)
Clover2 (GTX ["GTX": GM2, GE4, RM1, RV2]),
Express (XS ["GR2": 8, no Z, 1 GE7, 1 RE3],
XS24 ["GR2": 24, no Z, 1 GE7, 1 RE3],
Elan ["GR2-Elan": 24, Z, 4 GE7, 1 RE]),
Light (Entry ["LG1"]),
Stapuft (VGX ["VGX": IMP3], VGXT/SKY ["VGX": IMP5])
Ultra (Extreme ["GU1-Extreme", 32 Z]),
Venice (RealityEngine ["REC": 8 GE8, 2 RM4]),
4D3[248]0: IP7@33: Vigra VME audio optional (not AL compatable)
Clover2 (GTX ["GTX": GM2, GE4, RM1, RV2]),
Stapuft (VGX ["VGX": IMP3], VGXT/SKY ["VGX": IMP5]),
Venice (RealityEngine ["RE"])
4D4x0: IP7@40: Vigra VME audio optional (not AL compatable)
Stapuft (VGX ["VGX": IMP3], VGXT ["VGX": IMP5]),
Venice (RealityEngine ["RE"])
Indy: IP22: audio built in
Express (XZ ["GR3-Elan": 24, Z, 4 GE7, 1 RE3.1]),
Newport (XL ["NG1": 8|24, soft Z, NG1, REX3])
Indigo2: IP22: audio built in
Express (XZ ["GR3-Elan": 24, Z, 4 GE7, 1 RE3.1]),
Newport (XL ["NG1": 8|24, soft Z, NG1, REX3]),
Newpress (Extreme+XL ["GU1-Extreme": 32 Z]),
Ultra (Extreme ["GU1-Extreme", 32 Z])
Onyx: IP19: ASO audio optional, Vigra VME audio optional (*is* AL
compatable!)
Venice (RealityEngine ["RE": 8 GE8, 2 RM4],
RealityEngine2/VTX ["REV": 12 GE10, 2 RM4 or RM5])
Notes:
See http://www.sgi.com/Archive/comp.sys.sgi/audio/1994/Aug/0082.html
for more details on audio on VME machines.
It is not certain that VGR2 graphics is {IP6,IP12} "B" series.
The 4D50 thru 4D85 have an audio channel, but there is no
documentation on it and there is no SGI or third party support for it.
SGI does not seem to have discussed it at all in the newsgroups.
XSM graphics seems to be quite rare. Elan without a Z buffer? The
newsgroups have mentioned it only once, but I have one so I'm sure it
exists.
The high-end graphics list is probably incomplete.
Slashes usually indicate points I'm not entirely clear on. For example
I'm unclear on whether Skywriter graphics is different than VGTX.
------------------------------
Subject: -11- What OS versions are supported on which platforms?
Date: 20 Dec 1996 00:00:01 EST
Walter Roberson <roberson@hamer.ibd.nrc.ca> contributes the following
list:
Here's a first draft of a table, based mostly on material that has
appeared in Pipeline. Details up to IRIX 3.3 are largely lost in the
mists of time, as are details about when various platforms went out
of service.
Note: Names with '+' should not be broken up into components. For
example, IRIX 3.3+3.3.2 is distinct from IRIX 3.3 and from IRIX
3.3.2, and indicates IRIX 3.3 with a maintenance release (what would
now be called a roll-up patch.)
Note: IRIX 4.0.1T, IRIX 4.0.4T, IRIX 4.0.5IPR, and IRIX 5.3+5.3 TIRIX
are Trusted IRIX releases, not general IRIX releases.
Note: IRIX 5.2 and 5.3 releases are sometimes very hardware
specific. The last release listed is not necessarily the last or
best release for all hardware.
IRIS 1000, 1200, 1400: Terminals, no user-accessible OS.
IRIS 2300, 2400, 2400T, 2500, 2500T, 3000, 3010, 3020, 3030, 3100,
3115, 3120, 3130, 3150: up to IRIX 3.2?? End of lifetime.
4D/20, 4D/25: IRIX 3.2? IRIX 3.3+3.3.1, IRIX 3.3+3.3.2, IRIX 3.3.2,
IRIX 3.3.2+3.3.3, IRIX 4.0.1, IRIX 4.0.1T, IRIX 4.0.2, IRIX 4.0.3,
IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T, IRIX 4.0.5, IRIX 4.0.5A, IRIX
4.0.5A+4.0.5C, IRIX 4.0.5IPR, IRIX 5.2, IRIX 5.3, IRIX 5.3+5.3 TIRIX
V/20, VIP10: 4.0.1+VIP10, IRIX 4.0.5A+V20_35. End of lifetime.
4D/30, 4D/35: IRIX 3.3+3.3.2+1.0 4D/35 (introduction), IRIX 3.3.2+1.0
4D/35 (introduction), IRIX 3.3+3.3.2+1.1 4D/35, IRIX 3.3.2+1.1 4D/35,
IRIX 3.3+3.3.2+3.3.3+1.1 4D/35, IRIX 3.3.2+3.3.3+1.1 4D/35, IRIX
4.0.1, IRIX 4.0.1T, IRIX 4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B,
IRIX 4.0.4T, IRIX 4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX
4.0.5IPR, IRIX 5.2, IRIX 5.3, IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX
V/30, V/35, VIP12: 4.0.1+VIP12, 4.0.2+V35, IRIX 4.0.5A+V20_35. End of
lifetime. [Might have supported one other release.]
4D/50: up to IRIX 3.2? IRIX 3.3+3.3.1, IRIX 3.3+3.3.2, IRIX 3.3.2,
IRIX 3.3.2+3.3.3, IRIX 3.3+3.3.2+3.3.3L, IRIX 3.3.2+3.3.3L, IRIX
3.3+3.3.2+3.3.3+3.3.3L, IRIX 3.3.2+3.3.3+3.3.3L, IRIX 4.0.1, IRIX
4.0.1T, IRIX 4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T,
IRIX 4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR. End of
lifetime, but IRIX 5.2 and IRIX 5.3 might work with GT graphics,
which are not officially supported in the 4D/50. IRIX 5.3 with XFS is
definitely not supported.
4D/60, 4D/60T: up to IRIX 3.2? IRIX 3.3+3.3.1, IRIX 3.3+3.3.2, IRIX
3.3.2, IRIX 3.3.2+3.3.3, IRIX 3.3+3.3.2+3.3.3L, IRIX 3.3.2+3.3.3L,
IRIX 3.3+3.3.2+3.3.3+3.3.3L, IRIX 3.3.2+3.3.3+3.3.3L, IRIX 4.0.1,
IRIX 4.0.1T, IRIX 4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX
4.0.4T, IRIX 4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR.
End of lifetime.
4D/70: up to IRIX 3.2? IRIX 3.3+3.3.1, IRIX 3.3+3.3.2, IRIX 3.3.2,
IRIX 3.3.2+3.3.3, IRIX 3.3+3.3.2+3.3.3L, IRIX 3.3.2+3.3.3L, IRIX
3.3+3.3.2+3.3.3+3.3.3L, IRIX 3.3.2+3.3.3+3.3.3L, IRIX 4.0.1, IRIX
4.0.1T, IRIX 4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T,
IRIX 4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR. End of
lifetime for 4D/70G and 4D/70 server. IRIX 5.2 (GT, GTX graphics
only), IRIX 5.3 (GT, GTX graphics only, not server), IRIX 5.3+5.3
TIRIX. End of lifetime. IRIX 5.3 with XFS is not supported.
4D/80, 4D/85: up to IRIX 3.2? IRIX 3.3+3.3.1, IRIX 3.3+3.3.2, IRIX
3.3.2, IRIX 3.3.2+3.3.3, IRIX 3.3+3.3.2+3.3.3L, IRIX 3.3.2+3.3.3L,
IRIX 3.3+3.3.2+3.3.3+3.3.3L, IRIX 3.3.2+3.3.3+3.3.3L, IRIX 4.0.1,
IRIX 4.0.1T, IRIX 4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX
4.0.4T, IRIX 4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR,
IRIX 5.2 (excluding G graphics), IRIX 5.3 (excluding G graphics),
IRIX 5.3+5.3 TIRIX. End of lifetime. IRIX 5.3 with XFS is not
supported.
4D/1[2,4,6,8]0, 4D/2[12468]0: up to IRIX 3.2? IRIX 3.3+3.3.1, IRIX
3.3+3.3.2, IRIX 3.3.2, IRIX 3.3.2+3.3.3, IRIX 4.0.1, IRIX 4.0.1T,
IRIX 4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T, IRIX
4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR, IRIX 5.2, IRIX
5.3, IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX. End of lifetime.
4D/310: IRIX 3.3 (introduction), IRIX 3.3+3.3.1, IRIX 3.3+3.3.2, IRIX
3.3.2, IRIX 3.3.2+3.3.3, IRIX 4.0, IRIX 4.0.1, IRIX 4.0.1T, IRIX
4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T, IRIX 4.0.5,
IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5D, IRIX 4.0.5E, IRIX
4.0.5F, IRIX 4.0.5G(rev B), IRIX 4.0.5G(rev D), IRIX 4.0.5H, IRIX
4.0.5 a360, IRIX 4.0.5H a360+MCO, IRIX 4.0.5IPR, IRIX 5.2, IRIX 5.3.
IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX. End of lifetime.
4D/3[2468]0: IRIX 3.3 (introduction), IRIX 3.3+3.3.1, IRIX 3.3+3.3.2,
IRIX 3.3.2, IRIX 3.3.2+3.3.3, IRIX 4.0, IRIX 4.0.1, IRIX 4.0.1T, IRIX
4.0.2, IRIX 4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T, IRIX 4.0.5,
IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR, IRIX 5.2, IRIX 5.3,
IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX. End of lifetime.
4D/4[2468]0: IRIX 3.3+3.3.2+3.3.3L (introduction), IRIX 3.3.2+3.3.3L
(introduction), IRIX 4.0, IRIX 4.0.1, IRIX 4.0.1T, IRIX 4.0.2, IRIX
4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T, IRIX 4.0.5, IRIX 4.0.5A,
IRIX 4.0.5A+4.0.5C, IRIX 4.0.5IPR, IRIX 5.2, IRIX 5.3, IRIX 5.3 with
XFS, IRIX 5.3+5.3 TIRIX. End of lifetime.
4D/510 (Crimson): 4.0.3 (introduction), IRIX 4.0.4, IRIX 4.0.4B, IRIX
4.0.4T, IRIX 4.0.5, IRIX 4.0.5A, IRIX 4.0.5A+4.0.5C, IRIX 4.0.5D,
IRIX 4.0.5E, IRIX 4.0.5F, IRIX 4.0.5G(rev B), IRIX 4.0.5G(rev D),
IRIX 4.0.5H, IRIX 4.0.5 a360, IRIX 4.0.5H a360+MCO, IRIX 4.0.5IPR,
IRIX 4.0.5J(rev A), IRIX 4.0.5J(rev B), IRIX 5.2, IRIX 5.3, IRIX 5.3
with XFS, IRIX 5.3+5.3 TIRIX, IRIX 6.2 (except GTX)
R3000 Indigo: IRIX 4.0, IRIX 4.0.1, IRIX 4.0.1T, IRIX 4.0.2, IRIX
4.0.3, IRIX 4.0.4, IRIX 4.0.4B, IRIX 4.0.4T, IRIX 4.0.5, IRIX 4.0.5A,
IRIX 4.0.5A+4.0.5C, 4.0.5MM, 4.0.5E, IRIX 4.0.5F, IRIX 4.0.5(IOP),
IRIX 4.0.5IPR, IRIX 5.1, IRIX 5.1.1, IRIX 5.1.1+5.1.1.1, IRIX
5.1.1+5.1.1.2, IRIX 5.1.1+5.1.1.3, IRIX 5.2, IRIX 5.3, IRIX 5.3 with
XFS, IRIX 5.3+5.3 TIRIX. End of lifetime.
R4000 Indigo: 4.0.5E (introduction), IRIX 4.0.5F, IRIX 4.0.5(IOP),
IRIX 4.0.5IPR, IRIX 5.2, IRIX 5.3, IRIX 5.3 with XFS, IRIX 5.3+5.3
TIRIX, IRIX 6.2.
Indy: Indy IRIX 5.1 (introduction), Indy IRIX 5.1+5.1.0.1, Indy IRIX
5.1.1, Indy IRIX 5.1.1+5.1.1.1, Indy IRIX 5.1.1+5.1.1.2, Indy Irix
5.1.1+5.1.1.3, IRIX 5.2, IRIX 5.2 for Indy R4600PC & Challenge S,
IRIX 5.2 for Indy R4600SC/XZ & Presenter, IRIX 5.3, IRIX 5.3 for
175MHz R4400 Indy, IRIX 5.3 for Indy R4000, R4400, R4600 100-200MHz,
IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX (except 175+ MHz), IRIX 5.3 for
R5000 Indy, IRIX 5.3 Indy R5000 with XFS, IRIX 6.2.
Indigo^2, Challenge M: IRIX 4.0.5H (introduction), IRIX 4.0.5 a360,
IRIX 4.0.5(IOP), IRIX 4.0.5IPR, IRIX 5.1, IRIX 5.1.1, IRIX
5.1.1+5.1.1.1, IRIX 5.1.1+5.1.1.2, IRIX 5.1.1+5.1.1.3, IRIX 5.2, IRIX
5.3, IRIX 5.3 for 175 MHz and 2MB cache, IRIX 5.3 for Indigo^2
Impact, IRIX 5.3 All Indigo^2 Impact, IRIX 5.3 with XFS, IRIX 5.3+5.3
TIRIX, IRIX 6.2.
Power Indigo^2, Power Challenge M: IRIX 6.0.1 (introduction), IRIX
6.0.1 with XFS (introduction), IRIX 6.0.1 for Power Indigo^2 with
Presenter, IRIX 6.1, IRIX 6.2
R10000 Indigo^2: IRIX 6.2 (introduction)
Challenge S: IRIX 5.2 for Indy R4600PC & Challenge S (introduction),
IRIX 5.2 for R4600SC/XZ & Presenter, IRIX 5.3, IRIX 5.3 for 175MHz
R4400 Indy, IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX (except 175+ MHz),
IRIX 6.2.
Challenge DM: IRIX 5.2 (introduction), IRIX 5.2 for Challenge/Onyx,
IRIX 5.3, IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX, IRIX 6.2
Challenge L, Challenge XL: IRIX 5.0 (introduction), IRIX 5.0.1, IRIX
5.1, IRIX 5.1.1, IRIX 5.1.1+5.1.1.1, IRIX 5.1.1+5.1.1.2, IRIX
5.1.1+5.1.1.3, IRIX 5.2, IRIX 5.2 for Challenge/Onyx, IRIX 5.3, IRIX
5.3 with XFS, IRIX 5.3+5.3 TIRIX, IRIX 6.2.
Onyx L, Onyx XL: IRIX 5.0 (introduction), IRIX 5.0.1, IRIX 5.1, IRIX
5.1.1, IRIX 5.1.1+5.1.1.1, IRIX 5.1.1+5.1.1.2, IRIX 5.1.1+5.1.1.3,
IRIX 5.2, IRIX 5.2 for Onyx Extreme, IRIX 5.2 for Challenge/Onyx, 5.2
TKO, IRIX 5.3, IRIX 5.3 with XFS, IRIX 5.3+5.3 TIRIX, IRIX 6.2.
Power Challenge L, Power Onyx L, Power Challenge XL, Power Onyx XL:
IRIX 6.0 (introduction), IRIX 6.0.1, IRIX 6.0.1 with XFS, IRIX 6.1,
IRIX 6.2
R10000 Challenge, R10000 Onyx, Power Challenge 10000, Power Onyx
10000: IRIX 6.2 (introduction)
------------------------------
Subject: -12- MEMORY
Date: 09 Jan 1994 00:00:01 EST
The next few items discuss adding memory.
------------------------------
Subject: -13- What type of memory does each SGI model use?
Date: 09 Mar 1996 00:00:01 EST
Walter Roberson <roberson@Ibd.nrc.ca> provided the following table.
'3rd' indicates the memory is
--
※ 来源: 中国科大BBS站 [bbs.ustc.edu.cn]
--
※ 转载:．紫 丁 香 bbs.hit.edu.cn．[FROM: mtlab.hit.edu.cn]
Powered by KBS BBS 2.0 (http://dev.kcn.cn)
页面执行时间：403.338毫秒