[uunix]

Attempting net install from Octane onto Onyx2.

The Onyx2 does not have the eaddr set in the env / nvram. Now it must have because lmhostid showed up b0:02:01:81


I can add it with setenv -f eaddr b0:02:01:81, but this does not last a restart and I suspect does not last going through the install process.

The eaddr does seem a bit short I must admit.

I can run the fx.64 as the first step no problem using boot -f bootp()blah blah blah.. etc


When it comes to installing from the remote server though, it errors with

Code:

cannot invoke addr 0

I am wondering therefore if the lack of the eaddr is causing this?

Thoughts?

[Edit] I have amended 08:00 to the server settings and to the prom entry to no avail. So maybe it's not that.

[jan-jaap]

For the 'big iron', the mac address is not the system ID! The system ID derives from the backplane or system controller.

For the Onyx2, the system ID is in the form Bnnnnn (Onyx1 was Annnnnn), but the IO6 has a MAC address of the form 08:00:69:xx:xx:xx like every other SGI

[uunix]

Does the Onyx2 (IP27) support 6.5.30 ?

[dexter1]

Yes. All systems from ip27 onwards will run 6.5.30, with the exception of ip28 (indigo2 R10000)

[kikems]

<QUOTE author="uunix" post_id="2640" time="1534708927" user_id="51">

Attempting net install from Octane onto Onyx2.

The Onyx2 does not have the eaddr set in the env / nvram. Now it must have because lmhostid showed up b0:02:01:81


I can add it with setenv -f eaddr b0:02:01:81, but this does not last a restart and I suspect does not last going through the install process.

The eaddr does seem a bit short I must admit.

I can run the fx.64 as the first step no problem using boot -f bootp()blah blah blah.. etc


When it comes to installing from the remote server though, it errors with

Code:

cannot invoke addr 0

I am wondering therefore if the lack of the eaddr is causing this?

Thoughts?

[Edit] I have amended 08:00 to the server settings and to the prom entry to no avail. So maybe it's not that.

Add this enviroments, asuming that your IRIX machine have IP 192.168.0.150 and your server from install have IP 192.168.0.100 :

setenv netaddr 192.168.0.150
setenv srvaddr 192.168.0.100

[uunix]

Well that was a PITA!!

Booted to CD and set source to network, which worked in as much as nothing.. so had to do a disk install.

Ah well, all done, still have speckles on the screen, so suspect some hardware issue.

Boot up is clean apart from...

Code:

<i>
</i>IR0: ARM: Error executing stored video command 8 @0x0406cea4
IR0: ARM: flashprom combo image failed to load, loading EBF...

Installing patches now.

[jan-jaap]

<QUOTE author="uunix" post_id="2673" time="1534765518" user_id="51">

Ah well, all done, still have speckles on the screen, so suspect some hardware issue.

Log in over the network or serial console, run /usr/gfx/stopgfx. Then run IR diagnostics: /usr/diags/IR/bin/irsaudit

That'll tell you what's going on. When you're done, /usr/gfx/startgfx will restart the graphics pipe.

Otherwise, the GE eeprom can sometimes get scrambled, Recondas @ Nekochan used to know everything about that one. I think the command is 'ireeprom', and one of the options will clear / initialize it.

[uunix]

<QUOTE author="jan-jaap" post_id="2675" time="1534768825" user_id="183">

<QUOTE author="uunix" post_id="2673" time="1534765518" user_id="51">

Ah well, all done, still have speckles on the screen, so suspect some hardware issue.

Log in over the network or serial console, run /usr/gfx/stopgfx. Then run IR diagnostics: /usr/diags/IR/bin/irsaudit

That'll tell you what's going on. When you're done, /usr/gfx/startgfx will restart the graphics pipe.

Otherwise, the GE eeprom can sometimes get scrambled, Recondas @ Nekochan used to know everything about that one. I think the command is 'ireeprom', and one of the options will clear / initialize it.

Cheers Jan.. I just did that a few mins ago.. but didn't stop gfx.. ran again.. bit long this output.. but shows two fails

Code:

<i>
</i>RSLT fpconn         FAIL

Code:

<i>
</i>META                fpconn            0              1

I will check out ireeprom, cheers

Full results.

Code:

<i>
</i>ONYX01 6# /usr/diags/IR/bin/irsaudit
REV                 Rev:3.3.2 Thu Jul 20 18:13:09 PDT 2006 sherwood on splat
CMDL                /usr/diags/IR/bin/irsaudit
TEST reset          Reset
RSLT reset          PASS
TEST xgid           Report XG ID and test MAP RAM config
INFO                Revision: 00, Part No.: c102, Manufacturer No.: 2aa
INFO                MAP RAM Config = 128Kx32 bits, SSRAM type used = 32K*36
INFO                  bits
RSLT xgid           PASS
TEST xgregs         Test the XG registers
RSLT xgregs         PASS
TEST xgram          Test the XG MAP RAM
INFO                Found XG MAP RAM to have 128K entries
TRCE                Doing XG MAP RAM data path test
TRCE                Doing XG MAP RAM address path test
TRCE                Doing XG MAP RAM cell test.
RSLT xgram          PASS
TEST xgerr          Test the XG Error Behavior
INFO                Running Bad Map RAM Parity Tests
INFO                    Enabling parity checking...
INFO                Running Bad Map RAM Parity Tests
INFO                    Disabling parity checking...
INFO                Running XT Configuration Tests
RSLT xgerr          PASS
TEST hh_reg         HIP Host Registers
RSLT hh_reg         PASS
TEST ha_reg         HIP ARM Registers
RSLT ha_reg         PASS
TEST jtaginit       JTAG Master
RSLT jtaginit       PASS
TEST mbox           ARM-Host Mailbox
RSLT mbox           PASS
TEST sysprobe       JTAG System Probe
TRCE                GE board has 4 GE ASICs.
INFO                GE board is a GE16.
TRCE                BEF has 4MB of memory.
TRCE                RM #0 is an RM/TM combination.
INFO                RM #0 is an RM10
TRCE                TM #0 has 256MB (4Mx8 parts) of texture memory.
TRCE                RM #1 is an RM/TM combination.
INFO                RM #1 is an RM10
TRCE                TM #1 has 256MB (4Mx8 parts) of texture memory.
TRCE                RM/TM #2 not detected via JTAG.
TRCE                RM/TM #3 not detected via JTAG.
TRCE                DG has 2 VOC configuration.
TRCE                No option present in DG option slot.
TRCE                DG has 32K colormap RAMs.
TRCE                DG has no external gamma/deep colormap RAM.
RSLT sysprobe       PASS
TEST nicprobe       NIC Board Probe
TRCE                Checking XG NICs
TRCE                Reading ARM ucode from: /usr/diags/IR/ucode/arm1_nic.u
TRCE                GE NIC #: 0000.003c.148b (family: 0b)
TRCE                    Serial #: JKY190
TRCE                    Part #: 030-1398-001
TRCE                    rev_code: E
TRCE                    name: GE16-4
NIC#                PNGE-030-1398-001 SN-JKY190 (0000.003c.148b)
TRCE                RM0 NIC #: 0000.003e.fd7f (family: 0b)
TRCE                    Serial #: KBT313
TRCE                    Part #: 030-1402-001
TRCE                    rev_code: E
TRCE                    name: RM9
NIC#                PNRM-030-1402-001 SN-KBT313 (0000.003e.fd7f)
TRCE                TM0 NIC #: 0000.003e.b2f0 (family: 0b)
TRCE                    Serial #: KKX430
TRCE                    Part #: 030-1588-001
TRCE                    rev_code: D
TRCE                    name: TM8-256
NIC#                PNTM-030-1588-001 SN-KKX430 (0000.003e.b2f0)
TRCE                RM1 NIC #: 0000.0058.df17 (family: 0b)
TRCE                    Serial #: MHZ607
TRCE                    Part #: 030-1402-002
TRCE                    rev_code: B
TRCE                    name: RM9
NIC#                PNRM-030-1402-002 SN-MHZ607 (0000.0058.df17)
TRCE                TM1 NIC #: 0000.0058.e820 (family: 0b)
TRCE                    Serial #: MJT321
TRCE                    Part #: 030-1588-002
TRCE                    rev_code: A
TRCE                    name: TM8-256
NIC#                PNTM-030-1588-002 SN-MJT321 (0000.0058.e820)
TRCE                DG NIC #: 0000.0039.19f7 (family: 0b)
TRCE                    Serial #: HLL883
TRCE                    Part #: 030-1055-001
TRCE                    rev_code: P
TRCE                    name: DG5-2
NIC#                PNDG-030-1055-001 SN-HLL883 (0000.0039.19f7)
RSLT nicprobe       PASS
TEST intr           HIP Interrupts
TRCE                Expecting ARM interrupt...
TRCE                Expecting a FIFO_HI interrupt...
TRCE                Expecting a FIFO_LO interrupt...
RSLT intr           PASS
TEST icu_mem        ICU Memory
RSLT icu_mem        PASS
TEST fmreg          FM Registers
RSLT fmreg          PASS
TEST fmvcbus        VC Bus Test (using FM)
RSLT fmvcbus        PASS
TEST fmdid          FM Normal DID Table
RSLT fmdid          PASS
TEST fmovdid        FM Overlay/Underlay DID Table
RSLT fmovdid        PASS
TEST encreg         Encoder Registers
RSLT encreg         PASS
TEST vocreg         VOC Registers
RSLT vocreg         PASS
TEST vocdblbuf      VOC Double-buffered Registers
RSLT vocdblbuf      PASS
TEST vocspreg       VOC Special Register Operations
RSLT vocspreg       PASS
TEST voccpbuf       VOC Copy-buffered Register Mechanisms
RSLT voccpbuf       PASS
TEST dacreg         Video DAC Registers
RSLT dacreg         PASS
TEST xmapreg        XMAP Registers
RSLT xmapreg        PASS
TEST xmapdid        XMAP Normal DID Table
RSLT xmapdid        PASS
TEST xmapovdid      XMAP Overlay/Underlay DID Table
RSLT xmapovdid      PASS
TEST xmapchid       XMAP Channel Id Table
RSLT xmapchid       PASS
TEST vcbus          VC Bus Test (using XMAP)
RSLT vcbus          PASS
TEST xmapmem        XMAP mem test
TRCE                Doing XMAP CLUT data path test.
TRCE                Doing XMAP CLUT address path test.
TRCE                Doing XMAP CLUT cell test.
RSLT xmapmem        PASS
TEST ge_intbist     GE Board Internal BIST
RSLT ge_intbist     PASS
TEST ge_extbist     GE Board External BIST
RSLT ge_extbist     PASS
TEST dg_intbist     DG Board Internal BIST
RSLT dg_intbist     PASS
TEST dgconn         DG4 Boundary Scan
TRCE                Testing for stucks (DACs in SAMPLE).
TRCE                Testing for shorts (DACs in SAMPLE).
TRCE                Testing for stucks (DACs in EXTEST).
TRCE                Testing for shorts (DACs in EXTEST).
RSLT dgconn         PASS
TEST rmconn         RM boundary scan
TRCE                Testing RM #0 for stucks.
TRCE                Testing RM #0 for shorts.
TRCE                Testing RM #1 for stucks.
TRCE                Testing RM #1 for shorts.
RSLT rmconn         PASS
TEST fpconn         DG-RM Frontplane Boundary Scan
TRCE                Testing for stucks on RM #0.
TRCE                Testing for shorts on RM #0.
INFO                Short ?: pixin[3] @ C12 on xmap0 (2 short 0's, 2 short 1's
INFO                  of 26 tests).  NET=rm0.impp1_v[6],fp[3]
INFO                Short ?: pixin[7] @ A14 on xmap0 (5 short 0's, 5 short 1's
INFO                  of 26 tests).  NET=rm0.impp3_v[6],fp[7]
INFO                Stuck 0: pixin[11] @ C14 on xmap0 (all 13 fails).
INFO                  NET=rm0.impq0_v[6],fp[11]
INFO                Short 0: pixin[19] @ B17 on xmap0 (3 fails of 13 tests).
INFO                  NET=rm0.impq4_v[6],fp[19]
INFO                Stuck 1: pixin[23] @ C17 on xmap0 (all 13 fails).
INFO                  NET=rm0.impr1_v[6],fp[23]
DIAG                Fix suggestions:  1) checking connection of frontplane to
DIAG                  RM 0; 2) checking connection of frontplane to DG; 3)
DIAG                  replace RM 0 (rework looking for chip or connectivity
DIAG                  fault); 4) replace DG (rework looking for chip or
DIAG                  connectivity fault).
TRCE                Testing for stucks on RM #1.
TRCE                Testing for shorts on RM #1.
INFO                43 errors detected
CODE fpconn         BF  Y PNTM-030-1588-001:SN-KKX430(0000.003e.b2f0)
CODE fpconn         BF  Y PNRM-030-1402-001:SN-KBT313(0000.003e.fd7f)
CODE fpconn         BF  Y PNDG-030-1055-001:SN-HLL883(0000.0039.19f7)
RSLT fpconn         FAIL
INFO                Maximum error count (1) reached
META                ITERATION=1       PASSES         NON-PASSES
META                reset             1              0
META                xgid              1              0
META                xgregs            1              0
META                xgram             1              0
META                xgerr             1              0
META                hh_reg            1              0
META                ha_reg            1              0
META                jtaginit          1              0
META                mbox              1              0
META                sysprobe          1              0
META                nicprobe          1              0
META                intr              1              0
META                icu_mem           1              0
META                fmreg             1              0
META                fmvcbus           1              0
META                fmdid             1              0
META                fmovdid           1              0
META                encreg            1              0
META                vocreg            1              0
META                vocdblbuf         1              0
META                vocspreg          1              0
META                voccpbuf          1              0
META                dacreg            1              0
META                xmapreg           1              0
META                xmapdid           1              0
META                xmapovdid         1              0
META                xmapchid          1              0
META                vcbus             1              0
META                xmapmem           1              0
META                ge_intbist        1              0
META                ge_extbist        1              0
META                dg_intbist        1              0
META                dgconn            1              0
META                rmconn            1              0
META                fpconn            0              1
META                TOTAL             34             1
CODE                SUM  Hardware error
CODE                BSUM   0R   0Y  15G PNGE-030-1398-001:SN-JKY190 (0000.003c.148b)
CODE                BSUM   0R   1Y   3G PNTM-030-1588-001:SN-KKX430 (0000.003e.b2f0)
CODE                BSUM   0R   1Y   3G PNRM-030-1402-001:SN-KBT313 (0000.003e.fd7f)
CODE                BSUM   0R   0Y   4G PNTM-030-1588-002:SN-MJT321 (0000.0058.e820)
CODE                BSUM   0R   0Y   4G PNRM-030-1402-002:SN-MHZ607 (0000.0058.df17)
CODE                BSUM   0R   1Y  20G PNDG-030-1055-001:SN-HLL883 (0000.0039.19f7)
TRCE                Sending crashlog to availmon... (Use +nolog to avoid this.)

[Irinikus]

Have you tried testing the system with each RM10 independently to rule out possible problems there? (Only one RM10 inserted.)


TRCE Testing for stucks on RM #0.
TRCE Testing for shorts on RM #0.
INFO Short ?: pixin[3] @ C12 on xmap0 (2 short 0's, 2 short 1's
INFO of 26 tests). NET=rm0.impp1_v[6],fp[3]
INFO Short ?: pixin[7] @ A14 on xmap0 (5 short 0's, 5 short 1's
INFO of 26 tests). NET=rm0.impp3_v[6],fp[7]
INFO Stuck 0: pixin[11] @ C14 on xmap0 (all 13 fails).
INFO NET=rm0.impq0_v[6],fp[11]
INFO Short 0: pixin[19] @ B17 on xmap0 (3 fails of 13 tests).
INFO NET=rm0.impq4_v[6],fp[19]
INFO Stuck 1: pixin[23] @ C17 on xmap0 (all 13 fails).
INFO NET=rm0.impr1_v[6],fp[23]
<COLOR color="#FF0000"> DIAG Fix suggestions: 1) checking connection of frontplane to
DIAG RM 0; 2) checking connection of frontplane to DG; 3)
DIAG replace RM 0 (rework looking for chip or connectivity
DIAG fault); 4) replace DG (rework looking for chip or
DIAG connectivity fault).</COLOR>
TRCE Testing for stucks on RM #1.
TRCE Testing for shorts on RM #1.
<COLOR color="#FF0000"> INFO 43 errors detected</COLOR>
CODE fpconn BF Y PNTM-030-1588-001:SN-KKX430(0000.003e.b2f0)
CODE fpconn BF Y PNRM-030-1402-001:SN-KBT313(0000.003e.fd7f)
CODE fpconn BF Y PNDG-030-1055-001:SN-HLL883(0000.0039.19f7)
<COLOR color="#FF0000">RSLT fpconn FAIL</COLOR>


fpconn FAIL, indicates that there may be connection problem on the frontplane (Check all of the pins on the frontplane and the connectors of the various modules.)

<B><U>EDIT:</U></B>

I see from your other post that the problem existed before you exchanged the raster managers, so it could very well be the DG5 module.

The DIAG output refers to it twice as possibly being a problem, however, check the pins on the frontplane, where the two raster managers and the DG5 plug in.