Onyx350 4x800/4g/v12 w/ teardown

A place to post hardware inventories.
Forum rules
Please post your 'hinv' in the following format:

Topic: Kind of machine (O2, Octane, Tezro, Onyx2, etc.), CPU (R10k 250MHz, R12k 300MHz, R16k 1GHz, etc.), RAM, graphics option (Example: Tezro V12 4xR16K 700MHz 4GB)

Body: output of hinv -v (hinv -vm if possible) and /usr/gfx/gfxinfo.

Please wrap the output in BBCode "code" blocks to improve legibility.
mopar5150
Posts: 548
Joined: Tue Apr 24, 2012 6:02 pm
Location: Palm Springs, CA
Contact:

Onyx350 4x800/4g/v12 w/ teardown

Unread postby mopar5150 » Sat Mar 19, 2016 4:40 pm

Hey Guys,
Here is an Onyx350 system I picked up that has the factory V12 install. I was amazed at how many parts are different from a standard Origin350.

Let me know if you guys want any other photos or info.

Code: Select all

002c12-L1>serial all

Data                            Location      Value
------------------------------  ------------  --------
Local System Serial Number      NVRAM         M2100762
Reference System Serial Number  NVRAM         M2100762
Local Brick Serial Number       EEPROM        NCC247
Reference Brick Serial Number   NVRAM         NCC247


EEPROM      Product Name    Serial         Part Number           Rev  T/W
----------  --------------  -------------  --------------------  ---  ------
INTERFACE   2U_INT_53       NCC247         030_1809_003          B    00
IO9         IO9             NDZ742         030_1771_005          A    00
ODYSSEY     ODY128B1_2      MVV600         030_1909_003          C    00
RISER       2U_RISER        NBD086         030_1808_005          A    00
NODE        IP53_4CPU       NBB714         030_1959_002          A    00
SNOWBALL    no hardware detected
PS 1        DPS-500EBE      XPD0339003397  060-0178-003          S3
PS 2        DPS-500EBE      XPD0339002947  060-0178-003          S3

EEPROM     JEDEC-SPD Info           Part Number        Rev Speed  SGI
---------- ------------------------ ------------------ ---- ------ --------
DIMM 0     CE000000000000000CECB100 M3 46L2820ET3-CA0   3E   10.0  N/A
DIMM 2     CE000000000000000CD8B100 M3 46L2820ET3-CA0   3E   10.0  N/A
DIMM 4     no hardware detected
DIMM 6     no hardware detected
DIMM 1     CE000000000000000CDBB100 M3 46L2820ET3-CA0   3E   10.0  N/A
DIMM 3     CE000000000000000CE4B100 M3 46L2820ET3-CA0   3E   10.0  N/A
DIMM 5     no hardware detected
DIMM 7     no hardware detected





System Maintenance Menu

1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor

Option? 5
Command Monitor.  Type "exit" to return to the menu.
>> hinv
System  SGI-IP35
4 800 MHz IP35 Processors
Main memory size: 4096 Mbytes
Graphics Controller
PCI IOC4: in slot 1, (adapter 0)
PCI Gigabit Ethernet (tigon3) Controller 1
Integral SCSI controller 2: Version IOC4 ATA
    CDROM: unit 0 on SCSI Controller 2, (cdrom(2,0,7))
Integral SCSI controller 0: Version Qlogic 12160
Integral SCSI controller 1: Version Qlogic 12160
>> hinv -v
IP35 Node Board, Module 002c12
    ASIC BEDROCK Rev 2, 200 MHz, (nasid 0)
    Processor A: 800 MHz R16000 Rev 2.2
          Secondary Cache 8MB 400MHz Tap 0xa , (cpu 0)
      R16010FPC Rev 2.2
    Processor B: 800 MHz R16000 Rev 2.2
          Secondary Cache 8MB 400MHz Tap 0xa , (cpu 1)
      R16010FPC Rev 2.2
    Processor C: 800 MHz R16000 Rev 2.2
          Secondary Cache 8MB 400MHz Tap 0xa , (cpu 2)
      R16010FPC Rev 2.2
    Processor D: 800 MHz R16000 Rev 2.2
          Secondary Cache 8MB 400MHz Tap 0xa , (cpu 3)
      R16010FPC Rev 2.2
    Memory on board, 4096 MBytes (Standard)
      Bank 0, 1024 MBytes (Premium)  <-- (Software Bank 0)
      Bank 1, 1024 MBytes (Premium)
      Bank 2, 1024 MBytes (Premium)
      Bank 2, 1024 MBytes (Premium)
IXBRICK Bridge, Module 002c12
    ASIC BRIDGE Rev 3, (widget 15)
    adapter IOC4 Rev 4f
          (pci id 1)
    adapter IOC4-ATA Rev 4f
          (pci id 1)
        peripheral CDROM, BUS 0, ID 0, MATSHITA DVD-ROM SR-8178
    adapter PCI (SCSI interface) Rev 6
          (pci id 3)
    adapter GigE Rev 15
          (pci id 4)
IXBRICK Bridge, Module 002c12
    ASIC BRIDGE Rev 3, (widget 15)
    adapter ID (Vendor 1412 Device 1724 class 4 subclass 4)
          (pci id 1)
ASIC XBOW Rev 3, on CBrick, Module 002c12
ODYSSEY Graphics Board, Module 002c12
>>

350_1.JPG
350_4.JPG
350_5.JPG
Rear of V12 cage. solid plate no vents
350_6.JPG
350_7.JPG
350_8.JPG
350_9.JPG
Top of V12 cage.
350_10.JPG
Bottom of V12 cage with small air duct put there for reference.
350_11.JPG
350_12.JPG
V12 heatsink retainer.
350_13.JPG
V12 out of cage showing heatsink.
350_14.JPG
Onyx350 fan on left Origin fan on right.
350_15.JPG
Onyx350 top, Origin bottom.
350_16.JPG
Onyx350 top, Origin bottom.
350_17 (2).JPG
Slot in Onyx350 fan lines up with side vent.
350_17.JPG
Onyx350 IP air dam on top, Origin bottom.
350_18.JPG
Small air duct mounted on rear panel.
If the thing isn't on fire it's a software problem.

:Tezro: :O3x0: :A350:

User avatar
foetz
Moderator
Moderator
Posts: 6542
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby foetz » Sat Mar 19, 2016 4:52 pm

that's great info. thanks for posting :-)

User avatar
vishnu
Donor
Donor
Posts: 3174
Joined: Sun Mar 18, 2007 3:25 pm
Location: Minneapolis, Minnesota USA

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby vishnu » Mon Mar 21, 2016 5:58 pm

Really great pics, beautiful to see! :mrgreen:
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...

:Tezro: :Octane2:

User avatar
GL1zdA
Donor
Donor
Posts: 414
Joined: Thu Dec 31, 2009 3:18 pm
Location: Warsaw, PL

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby GL1zdA » Tue Mar 22, 2016 4:01 am

Thanks for the photos. I have never enough SGI porn.
:PI: :Indigo: :Indigo: :Indigo: :Indy: :Indy: :Indigo2: :Indigo2IMP: :Octane: :Fuel: :540:

User avatar
ClassicHasClass
Donor
Donor
Posts: 2071
Joined: Wed Jul 25, 2012 7:12 pm
Location: Sunny So Cal
Contact:

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby ClassicHasClass » Tue Mar 22, 2016 11:53 am

Very interesting!
smit happens.

:Fuel: bigred, 900MHz R16K, 4GB RAM, V12 DCD, 6.5.30
:Indy: indy, 150MHz R4400SC, 256MB RAM, XL24, 6.5.10
:Indigo2IMP: purplehaze, 175MHz R10000, Solid IMPACT
probably posted from Image bruce, Quad 2.5GHz PowerPC 970MP, 16GB RAM, Mac OS X 10.4.11
plus IBM POWER6 p520 * Apple Network Server 500 * RDI PrecisionBook * BeBox * Solbourne S3000 * Commodore 128 * many more...

User avatar
spiroyster
Donor
Donor
Posts: 145
Joined: Thu May 03, 2012 8:24 am
Location: Somerset, UK

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby spiroyster » Wed Mar 23, 2016 3:52 am

You have some really nice systems mopar5150, thanks for sharing. Thank god we have people like you (and others here) to save this stuff :)

Forgive my ignorance here as I have no MIPS cluster experience with SGI (only workstations), but how does this differ from an Onyx4 with VPro? I appreciate both systems are scalable, but all essentially the same architecture underneath? In which case can an Onyx350 exist as a node in an Onyx4 system and vice versa as long as it uses VPro (if the node has graphics)?

mopar5150
Posts: 548
Joined: Tue Apr 24, 2012 6:02 pm
Location: Palm Springs, CA
Contact:

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby mopar5150 » Wed Mar 23, 2016 7:18 am

Thanks! If there is an SGI god then I will likely burn in hell for some of my failed hacks. :)

Other than the special V12 hardware these systems are all the same. With a router brick (and some serial number work) they could be connected together and be happy. They don't need the Vpro to be connected and I had one of the Onyx4 bricks connected to an Onyx2 G-brick.

The rack Tezro and Onyx350 use Vpro graphics however the Onyx4 used a separate 2U chassis with a special AGP riser with ATI cards.

I have some of the Onyx4 graphics bricks and will do a teardown and post the photos.
If the thing isn't on fire it's a software problem.

:Tezro: :O3x0: :A350:

User avatar
foetz
Moderator
Moderator
Posts: 6542
Joined: Mon Apr 14, 2003 4:34 am
Contact:

Re: Onyx350 4x800/4g/v12 w/ teardown

Unread postby foetz » Wed Mar 23, 2016 1:24 pm

spiroyster wrote:I have no MIPS cluster experience with SGI (only workstations)

that was one of the major advantages of these systems: no clusters. the big mips irons ran as one single system. just like a very big workstation.


Return to “SGI: hinv”

Who is online

Users browsing this forum: No registered users and 1 guest