SGI: hinv

Octane2: 2x400MHz | V12 | DCD | DM2 | DM10 | PCI Cage | GigE

recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Sept. 23, 2011, 6:38 p.m...
Thanks to another nekochan member I've acquired a very clean Octane2 (the incandescent portion of the lightbar even works).

The graphics carrier originally included one of the SGI XIO dual-channel FC boards, until its services are needed I pulled it to prevent the automatic fastfan mode that occurs if XIO slot 'C' is populated (the V12 uses slot(s) A/B, and the DM2 slot 'D'). The 2GB of memory is comprised of eight 256MB DIMMs (edit: now six 512MB and two 256MB DIMMs), and until I rearrange monitors the display is currently connected to the 13W3 port on the V12.
Code:
hinv -vm
Location: /hw/node
PM20400MHZ Board: barcode LKE894     part 030-1476-002 rev  B
Location: /hw/node/xtalk/15
IP30 Board: barcode KTV280     part 030-1467-001 rev  D
Location: /hw/node/xtalk/15/pci/2
FP1 Board: barcode KVJ895     part 030-0891-003 rev  G
PWR.SPPLY.ER Board: barcode AAE0210721 part 060-0035-002 rev  A
Location: /hw/node/xtalk/13
XTALKPCI Board: barcode MDS825     part 030-0952-005 rev  E
Location: /hw/node/xtalk/11
ODY128VERSIONB Board: barcode MDF834     part 030-1611-001 rev  C
Location: /hw/node/xtalk/10
XT-DIGVID Board: barcode MJX248     part 030-1653-002 rev  H
2 400 MHZ IP30 Processors
Heart ASIC: Revision F
CPU: MIPS R12000 Processor Chip Revision: 3.5
FPU: MIPS R12010 Floating Point Chip Revision: 0.0
Main memory size: 3584 Mbytes
Xbow ASIC: Revision 1.4
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes
Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Disk drive: unit 2 on SCSI controller 0 (unit 2)
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
Integral SCSI controller 7: Version IEEE1394 SBP2
IEEE1394 Disk: node d0160100001dc0 port 0 lun 0 on SCSI controller 7 (unit 2)
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: V12
Integral Fast Ethernet: ef0, version 1, pci 2
Iris Audio Processor: version RAD revision 12.0, number 1
Iris Audio Processor: version RAD revision 13.0, number 2
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0005) PCI slot 3
PCI Adapter ID (vendor 0x10a9, device 0x0005) PCI slot 1
PCI Adapter ID (vendor 0x104c, device 0x8024) PCI slot 3
IIDC Video Camera: unit 0, revision 1.30, connected to DM10, unit 0
XT-DIGVID Multi-standard Digital Video: controller 1, unit 1, version 0x0
Dual Channel Display
DMediaPro DM10 FW option: unit 0, revision 1.1.0
Code:
/usr/gfx/gfxinfo -vv
Graphics board 0 is "ODYSSEY" graphics.
Managed (":0.0") 3200x1200
BUZZ version B.1
PB&J version 1
128MB memory
Banks: 4, CAS latency: 3
Monitor 0 type: Unknown
Dual Channel Display option
Monitor 1 type: VSC 4892        Monitor 2 type: VSC 4892
Input Sync: Voltage - Video Level; Source - Internal; Genlocked - False
Channel 0:
Origin = (0,0)
Video Output: 1600 pixels, 1200 lines, 60.00Hz (2@1600x1200_60_ds)
Video Format Flags:  (none)
Sync Disabled
Using Gamma Map 0
Monitor Type:  VSC-4892
Gain (all color components) - 0.000000 ; range [1,10]
Channel 1:
Origin = (1600,0)
Video Output: 1600 pixels, 1200 lines, 60.00Hz (2@1600x1200_60_ds)
Video Format Flags:  (none)
Sync Disabled
Using Gamma Map 0
Monitor Type:  VSC-4892
Gain (all color components) - 0.000000 ; range [1,10]
Code:
scsicontrol -i /dev/scsi/*
ANSI vers 3, ISO ver: 0, ECMA ver: 0; supports:  16bit synch linkedcmds cmdqueing
Device is  ready
/dev/scsi/sc0d2l0:  Disk          FUJITSU MAN3184MC       5507
ANSI vers 3, ISO ver: 0, ECMA ver: 0; supports:  16bit synch linkedcmds cmdqueing
Device is  ready

scsicontrol -i /dev/scsi/1394/d0160100001dc0/lun0/c7p0
/dev/scsi/1394/d0160100001dc0/lun0/c6p0:  Disk          SCM     CAMERAMATE-CF   1394
ANSI vers 4, ISO ver: 0, ECMA ver: 0; supports:
Device is  ready
Code:
configmon -h
SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
0              NA            NA                  NA            NA        NA
1             FP1            NA              KVJ895  030-0891-003         G
2            IP30            NA              KTV280  030-1467-001         D
3      PM20400MHZ            NA              LKE894  030-1476-002         B
4  ODY128VERSIONB            NA              MDF834  030-1611-001         C
5       XT-DIGVID            NA              MJX248  030-1653-002         H
6    PWR.SPPLY.ER            NA          AAE0210721  060-0035-002         A
7        XTALKPCI            NA              MDS825  030-0952-005         E
8     SCSI_CTLR_0            NA                  NA            NA        NA
9         DRIVE_1            NA  3CE14L63    Copyrigh    SX173404LC      BD13
10         DRIVE_2            NA        UFL3P1901VYE     MAN3184MC      5507
11     SCSI_CTLR_1            NA                  NA            NA        NA
12     SCSI_CTLR_7            NA                  NA            NA        NA
===============================================================================
Code:
uname -aR
IRIX64 octane 6.5 6.5.30m 07202013 IP30
Code:
xtdigvid_hinv
/hw/node/xtalk/10
XT-DIGVID (part number 030-1653-002 H), serial number MJX248
IRIX number 1
ML Device Index 1
Code:
xtdigvid_confidence
Unzipping ml reference frames...
done
Uncompressing xtdigvid reference frames...
done

*********************************************************************
*********************************************************************
****                                                             ****
***        XTDIGVID_CONFIDENCE ===== XTDIGVID_CONFIDENCE          ***
***        XTDIGVID_CONFIDENCE ===== XTDIGVID_CONFIDENCE          ***
****                                                             ****
*********************************************************************
*********************************************************************


System type is: OCTANE2
System has 2 CPUs and 2048MB of memory
Found 1 XTDIGVID board(s)


Found 1 XTDIGVID board(s)

Starting xtdigvid_confidence script ......


Total XTDIGVID boards in the system is 1 board(s).
Test will run for 1 loop(s).


Board(s) information:

XT-DIGVID plugged in /hw/node/xtalk/10
(Part number is 030-1653-002, Rev H), Serial number MJX248


>>>>> PLEASE NOTE ABOUT PART NUMBERS <<<<<
>>>>> Each part number above corresponds to an XTDIGVID board.


==> Please verify that each board information is correct.

==> Verify that the total board reporting number matches
==> the number of boards installed.  Are they matched ? (y/n): y
Continuing with the xtdigvid_confidence......




Running standard XTDIGVIDTST tests.

INSTRUCTION:
1) Connect a LVDS cable from the xtdigvid connector labelled P1
to the VBOB connector labelled P1.

2) Connect a LVDS cable from the xtdigvid connector labelled P2
to the VBOB connector labelled P2.

3) On the VBOB, connect a coax from 'HD out 1' to 'HD in 1'.
connect a coax from 'HD out 2' to 'HD in 2'.

4) On the VBOB, connect a coax from 'SD out 1' to 'SD in 1'.
connect a coax from 'SD out 2' to 'SD in 2'.

Is everything ready <y/n>?: n
....Further DM2 testing will have to wait until I acquire a VBOB and a pair of LVDS cables)

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Sept. 25, 2011, 7:04 a.m...
Added a couple of photos....

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
nekonoko avatar
nekonoko
Site Admin
Who joined Jan. 23, 2003, 1:31 a.m.
and authored 7947 notes
Wrote the following at Sept. 26, 2011, 1:30 p.m...
Looks fantastic :)

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Sept. 26, 2011, 8:19 p.m...
nekonoko wrote:
Looks fantastic :)
Thanks! ;)

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
smj avatar
smj
Who joined Nov. 12, 2007, 7:54 p.m.
and authored 935 notes
Wrote the following at Sept. 27, 2011, 2:57 p.m...
That is entirely unacceptable. If I ever visit, I'm putting an Avery label on it. ;)

_________________
Then? :IRIS3130: ... Now? :O3x02L: :1600SW: +MLA :Fuel: :Octane2: :Octane: :Indigo2IMP: ... Other: DEC :BA213: :BA123: Sun , DG AViiON , NeXT :Cube:
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Sept. 27, 2011, 5:49 p.m...
smj wrote:
That is entirely unacceptable. If I ever visit, I'm putting an Avery label on it. ;)
It did have one, but I got a little overzealous while appling low-gloss armorall.

BTW - don't you also have an V12-DCD-DM2-DM5-FC equipped Octane2 to immortalize in an hinv post? Preferably with a few photos so we can see just how pathological the Avery label fixation has become. :D

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
smj avatar
smj
Who joined Nov. 12, 2007, 7:54 p.m.
and authored 935 notes
Wrote the following at Sept. 29, 2011, 11:27 a.m...
recondas wrote:
BTW - don't you also have an V12-DCD-DM2-DM5-FC equipped Octane2 to immortalize in an hinv post? Preferably with a few photos so we can see just how pathological the Avery label fixation has become. :D

Yeah, and I'd love to remove the FC board and re-arrange things to avoid fast-fan.

I have to complete a culling of the Octanes, and figure out what I'm keeping - probably just one built around the V12, another around the MXE+PVO. The sticking point is testing the components I've collected and building up the other three chassis so they can find new homes.

In theory that will be a trigger for an update of the remaining Octane' hinv posts.

_________________
Then? :IRIS3130: ... Now? :O3x02L: :1600SW: +MLA :Fuel: :Octane2: :Octane: :Indigo2IMP: ... Other: DEC :BA213: :BA123: Sun , DG AViiON , NeXT :Cube:
fu avatar
fu
Who joined Sept. 29, 2005, 8:39 a.m.
and authored 983 notes
Wrote the following at Oct. 1, 2011, 9:53 a.m...
mint indeed

reminds me a of a new old stock octane you got during the warehouse clearance, congrats rec :)
m20003293
Who joined Aug. 23, 2011, 10:05 p.m.
and authored 27 notes
Wrote the following at Oct. 7, 2011, 12:46 a.m...
Very nice....

Wow those DVI connectors are great :) Wish I could find them for my V10 card

_________________
Image Image Image Image Image Image
jan-jaap avatar
jan-jaap
Who joined June 17, 2004, 10:35 a.m.
and authored 3603 notes
Wrote the following at Oct. 7, 2011, 1:17 a.m...
That is a very nice looking Octane!
recondas wrote:
Code:
xtdigvid_confidence

[...]
Running standard XTDIGVIDTST tests.

INSTRUCTION:
1) Connect a LVDS cable from the xtdigvid connector labelled P1
to the VBOB connector labelled P1.

2) Connect a LVDS cable from the xtdigvid connector labelled P2
to the VBOB connector labelled P2.

3) On the VBOB, connect a coax from 'HD out 1' to 'HD in 1'.
connect a coax from 'HD out 2' to 'HD in 2'.

4) On the VBOB, connect a coax from 'SD out 1' to 'SD in 1'.
connect a coax from 'SD out 2' to 'SD in 2'.

Is everything ready <y/n>?: n
....Further DM2 testing will have to wait until I acquire a VBOB and a pair of LVDS cables)


Good find. I will have to try this myself. I have the VBOB & cables, but all coax cables I have are survivors from the time I lived in a student house where we ran a 10base2 network :shock: They are buried so deep I may as well order some new ones :oops:

_________________
Now this is a deep dark secret, so everybody keep it quiet :)
It turns out that when reset, the WD33C93 defaults to a SCSI ID of 0, and it was simpler to leave it that way... -- Dave Olson, in comp.sys.sgi
Currently in commercial service: Image :Onyx2: (2x) :O3x02L:
In the museum : almost every MIPS/IRIX system.
Wanted : GM1 board for Professional Series GT graphics (030-0076-003, 030-0076-004)
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Oct. 7, 2011, 4:24 a.m...
m20003293 wrote:
Very nice.... Wow those DVI connectors are great :) Wish I could find them for my V10 card
Thank you. The DVI ports are on a Dual Channel Display option board commonly called a DCD. DCDs do make semi-rare appearances on eBay. Two nekochan members have recently had some listed on eBay, so you could also try a post in the wanted forum.

jan-jaap wrote:
That is a very nice looking Octane!
Thank you as well. The nice appearance is courtesy of the care taken by the previous owner - it's nice not have have to deal with the 'it came from surplus where it was pushed across the floor on its plastic parts because it was too heavy to lift" appearance of so much of what appears on eBay these days.

jan-jaap wrote:
Good find. I will have to try this myself.
If you happen to have a DIVO in one of your Onyx2s ( which also work in an Octane ), there are similar tools (divohinv and divotest) there too.

BTW, when you run the xtdigvid_confidence tests, please post some details.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Oct. 14, 2011, 4:23 p.m...
Added a gig and a half of RAM and updated the hinv.......

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Oct. 16, 2011, 11:54 a.m...
...... and a pseudo DM10. This one is the Adaptec AFW-4300B with the red PCB mentioned in the Octane Hardware Aggregator (and elsewhere in the forums). It successfully reads and writes Compact Flash media using a MicroTech FWCameraMate.

I did discover if the 32-bit PCI Adaptec AFW-4300B was installed in a numerically lower PCI slot (in the PCI card cage) than the 64-bit PCI-X GigE board I'd get PCI Bridge errors during boot and neither would function reliably after boot. Installing the PCI-X board in PCI slot 1 and the 32-bit board in slot 3 resolved the issue.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Sept. 20, 2012, 1:47 p.m...
Added a dual 400Mhz processor module and updated the original hinv post.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8449 notes
Wrote the following at Sept. 25, 2012, 9:29 p.m...
recondas wrote:
...... and a pseudo DM10.

I did discover if the 32-bit PCI Adaptec AFW-4300B was installed in a numerically lower PCI slot (in the PCI card cage) than the 64-bit PCI-X GigE board I'd get PCI Bridge errors during boot and neither would function reliably after boot. Installing the PCI-X board in PCI slot 1 and the 32-bit board in slot 3 resolved the issue.

I wonder if neko's lockups with the Adaptec Duoconnect in the Tezro were due to a similar peculiarity ?
recondas avatar
recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes
Wrote the following at Sept. 26, 2012, 4:59 a.m...
hamei wrote:
I wonder if neko's lockups with the Adaptec Duoconnect in the Tezro were due to a similar peculiarity ?
Interesting thought. Could you try the Duoconnect in your tezro-similar O350?

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8449 notes
Wrote the following at Sept. 26, 2012, 9:29 a.m...
recondas wrote:
Could you try the Duoconnect in your tezro-similar O350?

The Duoconnect left the building or I'd be happy to give it a try :(