Nekonomicon - recondas

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Tezro: 4x800MHz | 8GB | V12 | DCD | DM10 | SAS | USB at Nov. 7, 2011, 6:11 p.m...

hamei wrote: Huh ? Is this a twoie desktop with the dcd ?

Exactly.

I didn't quote the entire gfxinfo section that was updated (since the entire update is included in the original post) - it's two ViewSonic VP2039b LCD panels in an Ergotron mount .

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of Octane Digital Video Option at Nov. 15, 2011, 11:21 a.m...

Have you installed the necessary software? There's some additional info in this thread: viewtopic.php?f=16&t=16720059

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of Octane Digital Video Option at Nov. 15, 2011, 12:58 p.m...

nitrat wrote:

it's working, installing software to get VideoDeamon running was quite a pain, but it seems to run ;-)

Glad you found the thread helpful. I see your Octane still uses the default 'IRIS' host name. If personalizing the Octane is on your to-do list, you might find the following wiki article another source of useful info: http://www.nekochan.net/wiki/ ... tomization

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4835 notes

Wrote on the subject of Origin 350: 4x800MHz 8MB Cache | 4GB | 2UPX PCI Module at Nov. 18, 2011, 3:59 a.m...

Origin 350 with the less often seen 2UPX PCI Expansion Module (a standard 2U O350 chassis with four PCI-X and one XIO-2 slot, but without processor, memory or bedrock). The O350 and the 2UPX are linked via a NUMAlink cable connected to the external XIO ports.

Currently the O350 (001c01) has an IO9 and a QL2342 dual-channel 2GB FC board, the 2UPX (001e03) holds a QL12160 dual-channel U160 controller and an SGI-branded PXG2RB-SGI-RHoS dual-port Gigabit board.

Code:

hinv -vm

Location: /hw/module/001c01/node

IP53_4CPU Board: barcode NGA768     part 030-1959-002 rev -B

Location: /hw/module/001c01/PXbrick/xtalk/10

2U_INT_53 Board: barcode NDL537     part 030-1809-004 rev -A

Location: /hw/module/001c01/IXbrick/xtalk/15

2U_INT_53 Board: barcode NXR118     part 030-1809-006 rev -C

Location: /hw/module/001c01/IXbrick/xtalk/15/pci-x/0/1/ioc4

IO9 Board: barcode NYL142     part 030-1771-006 rev -A

4 800 MHZ IP35 Processors

CPU: MIPS R16000 Processor Chip Revision: 2.2

FPU: MIPS R16010 Floating Point Chip Revision: 2.2

CPU 0 at Module 001c01/Slot 0/Slice A: 800 Mhz MIPS R16000 Processor Chip (enabled)

Processor revision: 2.2. Scache: Size 8 MB Speed 400 Mhz  Tap 0xa

CPU 1 at Module 001c01/Slot 0/Slice B: 800 Mhz MIPS R16000 Processor Chip (enabled)

Processor revision: 2.2. Scache: Size 8 MB Speed 400 Mhz  Tap 0xa

CPU 2 at Module 001c01/Slot 0/Slice C: 800 Mhz MIPS R16000 Processor Chip (enabled)

Processor revision: 2.2. Scache: Size 8 MB Speed 400 Mhz  Tap 0xa

CPU 3 at Module 001c01/Slot 0/Slice D: 800 Mhz MIPS R16000 Processor Chip (enabled)

Processor revision: 2.2. Scache: Size 8 MB Speed 400 Mhz  Tap 0xa

Main memory size: 4096 Mbytes

Instruction cache size: 32 Kbytes

Data cache size: 32 Kbytes

Secondary unified instruction/data cache size: 8 Mbytes

Memory at Module 001c01/Slot 0: 4096 MB (enabled)

Bank 0 contains 512 MB (Standard) DIMMS (enabled)

Bank 1 contains 512 MB (Standard) DIMMS (enabled)

Bank 2 contains 512 MB (Standard) DIMMS (enabled)

Bank 3 contains 512 MB (Standard) DIMMS (enabled)

Bank 4 contains 512 MB (Standard) DIMMS (enabled)

Bank 5 contains 512 MB (Standard) DIMMS (enabled)

Bank 6 contains 512 MB (Standard) DIMMS (enabled)

Bank 7 contains 512 MB (Standard) DIMMS (enabled)

Integral SCSI controller 9: Version QL12160, low voltage differential

Integral SCSI controller 10: Version QL12160, low voltage differential

Integral SCSI controller 2: Version IDE (ATA/ATAPI) IOC4

Integral SCSI controller 0: Version QL12160, low voltage differential

Disk drive: unit 1 on SCSI controller 0 (unit 1)

Integral SCSI controller 1: Version QL12160, low voltage differential

Integral SCSI controller 11: Version Fibre Channel QL2342 Port 1, 100 MHz PCI-X

Integral SCSI controller 12: Version Fibre Channel QL2342 Port 2, 100 MHz PCI-X

IOC3/IOC4 serial port: tty7

IOC3/IOC4 serial port: tty8

IOC3/IOC4 serial port: tty9

IOC3/IOC4 serial port: tty10

Gigabit Ethernet: tg5, module 001c01, PCI bus 1 slot 1 port 0

Gigabit Ethernet: tg6, module 001c01, PCI bus 1 slot 1 port 1

Integral Gigabit Ethernet: tg0, module 001c01, PCI bus 1 slot 4

PCI Adapter ID (vendor 0x14e4, device 0x1648) PCI slot 1

PCI Adapter ID (vendor 0x14e4, device 0x1648) PCI slot 1

PCI Adapter ID (vendor 0x1077, device 0x1216) PCI slot 1

PCI Adapter ID (vendor 0x10a9, device 0x100a) PCI slot 1

PCI Adapter ID (vendor 0x1077, device 0x1216) PCI slot 3

PCI Adapter ID (vendor 0x14e4, device 0x1645) PCI slot 4

PCI Adapter ID (vendor 0x1077, device 0x2312) PCI slot 1

PCI Adapter ID (vendor 0x1077, device 0x2312) PCI slot 1

IOC4 firmware revision 83

IOC3/IOC4 external interrupts: 1

HUB in Module 001c01/Slot 0: Revision 2 Speed 200.00 Mhz (enabled)

IP35prom in Module 001c01/Slot n0: Revision 6.210

Code:

>env

001c01

Environmental monitoring is enabled and running.

Description    State       Warning Limits     Fault Limits       Current

-------------- ----------  -----------------  -----------------  -------

1.8V    Enabled  10%   1.62/  1.98  20%   1.44/  2.16    1.777

12V <not present>

12V #2    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.063

3.3V    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.320

12V IO    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.063

5V AUX    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.044

3.3V AUX    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.285

PCI 5V AUX    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.070

PCI 3.3V    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.302

PCI 2.5V    Enabled  10%   2.25/  2.75  20%   2.00/  3.00    2.509

PCI 5V    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    4.966

XIO 12V BIAS <not present>

XIO 5V <not present>

XIO 2.5V <not present>

XIO 3.3V AUX <not present>

IP53 3.3V AUX    Enabled  10%   2.97/  3.63  20%   2.64/  3.96    3.302

IP53 5V AUX    Enabled  10%   4.50/  5.50  20%   4.00/  6.00    5.070

IP53 12V    Enabled  10%  10.80/ 13.20  20%   9.60/ 14.40   12.000

IP53 VCPU    Enabled  10%   1.13/  1.38  20%   1.00/  1.50    1.241

IP53 SRAM    Enabled  10%   2.25/  2.75  20%   2.00/  3.00    2.483

IP53 1.5V    Enabled  10%   1.35/  1.65  20%   1.20/  1.80    1.495

Description     State       Warning RPM  Current RPM

--------------- ----------  -----------  -----------

FAN  0  EXHST 1    Enabled         1980         2235

FAN  1  EXHST 2    Enabled         1980         2220

FAN  2       PS    Enabled         3200         4891

FAN  3    PCI 1    Enabled         1980         2960

FAN  4    PCI 2    Enabled         1980         2678

Advisory   Critical   Fault      Current

Description       State       Temp       Temp       Temp       Temp

----------------- ----------  ---------  ---------  ---------  ---------

0 INTERFACE 0       Enabled   31C/ 87F   48C/118F   55C/131F   17C/ 62F

1 INTERFACE 1       Enabled   31C/ 87F   48C/118F   55C/131F   19C/ 66F

2 INTERFACE 2       Enabled   31C/ 87F   48C/118F   55C/131F   21C/ 69F

3 PCI RISER         Enabled   31C/ 87F   48C/118F   55C/131F   19C/ 66F

4 ODYSSEY        <not present>

5 NODE              Enabled   31C/ 87F   48C/118F   55C/131F   18C/ 64F

6 BEDROCK           Enabled   31C/ 87F   48C/118F   55C/131F   18C/ 64F

001e03

Environmental monitoring is enabled and running.

Description    State       Warning Limits     Fault Limits       Current

-------------- ----------  -----------------  -----------------  -------

1.8V   Wait Pwr  10%   1.62/  1.98  20%   1.44/  2.16    0.028

12V <not present>

12V #2   Wait Pwr  10%  10.80/ 13.20  20%   9.60/ 14.40    0.188

3.3V   Wait Pwr  10%   2.97/  3.63  20%   2.64/  3.96    0.138

12V IO   Wait Pwr  10%  10.80/ 13.20  20%   9.60/ 14.40    0.188

5V AUX   Wait Pwr  10%   4.50/  5.50  20%   4.00/  6.00    5.018

3.3V AUX   Wait Pwr  10%   2.97/  3.63  20%   2.64/  3.96    3.285

PCI 5V AUX   Wait Pwr  10%   4.50/  5.50  20%   4.00/  6.00    5.044

PCI 3.3V   Wait Pwr  10%   2.97/  3.63  20%   2.64/  3.96    0.138

PCI 2.5V   Wait Pwr  10%   2.25/  2.75  20%   2.00/  3.00    0.013

PCI 5V   Wait Pwr  10%   4.50/  5.50  20%   4.00/  6.00    0.000

XIO 12V BIAS <not present>

XIO 5V <not present>

XIO 2.5V <not present>

XIO 3.3V AUX <not present>

IP53 3.3V AUX <not present>

IP53 5V AUX <not present>

IP53 12V <not present>

IP53 VCPU <not present>

IP53 SRAM <not present>

IP53 1.5V <not present>

Description     State       Warning RPM  Current RPM

--------------- ----------  -----------  -----------

FAN  0  EXHST 1   Wait Pwr         1980            0

FAN  1  EXHST 2   Wait Pwr         1980            0

FAN  2       PS   Wait Pwr         3200            0

FAN  3    PCI 1   Wait Pwr         1980            0

FAN  4    PCI 2   Wait Pwr         1980            0

Advisory   Critical   Fault      Current

Description       State       Temp       Temp       Temp       Temp

----------------- ----------  ---------  ---------  ---------  ---------

0 INTERFACE 0      Wait Pwr   50C/122F   54C/129F   58C/136F   24C/ 75F

1 INTERFACE 1      Wait Pwr   50C/122F   54C/129F   58C/136F   24C/ 75F

2 INTERFACE 2      Wait Pwr   50C/122F   54C/129F   58C/136F   24C/ 75F

3 PCI RISER        Wait Pwr   50C/122F   54C/129F   58C/136F   24C/ 75F

4 ODYSSEY        <not present>

5 NODE           <not present>

6 BEDROCK        <not present>

Code:

001c01-L1>serial all

001c01

Data                            Location      Value

------------------------------  ------------  --------

Local System Serial Number      NVRAM         M2005xxx

Reference System Serial Number  Attached I/O  M2005xxx

Local Brick Serial Number       EEPROM        NXRxxx

Reference Brick Serial Number   NVRAM         NXRxxx

EEPROM      Product Name    Serial         Part Number           Rev  T/W

----------  --------------  -------------  --------------------  ---  ------

INTERFACE   2U_INT_53       NXRxxx         030_1809_006          C    00

IO9         IO9             NYLxxx         030_1771_006          A    00

ODYSSEY     no hardware detected

RISER       2U_RISER        NWExxx         030_1808_006          C    00

NODE        IP53_4CPU       NGAxxx         030_1959_002          B    00

SNOWBALL    no hardware detected

PS 1        no hardware detected

PS 2        DPS-500EBE      XPD0601000375  060-0178-003          S4

EEPROM     JEDEC-SPD Info           Part Number        Rev  Speed  SGI

---------- ------------------------ ------------------ ---- ------ --------

DIMM 0     CE000000000000000C9B1200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 2     CE000000000000000C9A1200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 4     CE000000000000000CA21200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 6     CE000000000000000C9E1200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 1     CE000000000000000CCE1200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 3     CE000000000000000CCC1200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 5     CE000000000000000CCA1200 M3 47L6423DT2-CA0   2D   10.0  N/A

DIMM 7     CE000000000000000CD61200 M3 47L6423DT2-CA0   2D   10.0  N/A

001e03

Data                            Location      Value

------------------------------  ------------  --------

Local System Serial Number      NVRAM         M2005xxx

Reference System Serial Number  NVRAM         M2005xxx

Local Brick Serial Number       EEPROM        NDLxxx

Reference Brick Serial Number   NVRAM         NDLxxx

EEPROM      Product Name    Serial         Part Number           Rev  T/W

----------  --------------  -------------  --------------------  ---  ------

INTERFACE   2U_INT_53       NDLxxx         030_1809_004          A    00

IO9         no hardware detected

ODYSSEY     no hardware detected

RISER       2U_RISER        NBJxxx         030_1808_005          A    00

NODE        no hardware detected

SNOWBALL    no hardware detected

PS 1        no hardware detected

PS 2        DPS-500EBE      XPD0342003505  060-0178-003          S3

EEPROM     JEDEC-SPD Info           Part Number        Rev  Speed  SGI

---------- ------------------------ ------------------ ---- ------ --------

DIMM 0     no hardware detected

DIMM 2     no hardware detected

DIMM 4     no hardware detected

DIMM 6     no hardware detected

DIMM 1     no hardware detected

DIMM 3     no hardware detected

DIMM 5     no hardware detected

DIMM 7     no hardware detected

Code:

001c01-L1>version

L1 1.48.1 (Image B), Built 01/22/2007 11:34:34    [MIPS 2MB image]

Code:

001c01-L1>cfg

:0  - 001c01

:1  - 001e03

001c01-L1>link v

port 'EXT II' appears okay (7)

port 'PIC B' appears okay (7)

port 'NODE NI' appears okay (1)

port 'NODE II' appears okay (7)

Code:

001e03-L1>version

L1 1.38.10 (Image B), Built 08/03/2005 12:54:59    [MIPS 2MB image]

Firmware Image B: Rev. 1.38.10, Built 08/03/2005 12:54:592:54:59

Code:

001e03-L1>brick

rack: 001, slot: 03, partition: none, type: 2UPX [2MB flash], serial:NDLxxx, source: EEPROM

Code:

001e03-L1>pci

Bus Slot Stat    Power Mode/Speed

--- ---- ------- ----- -----------

1    1 0x00 0c  7.5W PCIX 100MHz

1    2 0x00 0f  none PCIX 100MHz

2    1 0x00 01   15W PCI   33MHz

2    2 0x00 0f  none PCI   33MHz

Code:

001e03-L1>link v

port 'EXT II' appears okay (1)

port 'PIC B' appears okay (1)

port 'NODE NI' <not present>

port 'NODE II' <not present>

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4835 notes

Wrote on the subject of Origin 350: 4x800MHz 8MB Cache | 4GB | 2UPX PCI Module at Nov. 18, 2011, 7:37 a.m...

PymbleSoftware wrote:

Congratulations.

jan-jaap wrote:

Nice!

Thanks on both counts.

jan-jaap wrote:

So a 2UPX module is really an expansion compute module without the (IP53_4CPU) node board, right?

Sure looks like it to me:

Attachment:

2UPX-1.jpg [ 132.26 KiB | Viewed 579 times ]

Attachment:

2UPX-2.jpg [ 122.76 KiB | Viewed 579 times ]

Attachment:

2UPX-3.jpg [ 183.37 KiB | Viewed 579 times ]

Attachment:

2UPX-4.jpg [ 222.6 KiB | Viewed 579 times ]

jan-jaap wrote:

Do these things grow on trees where you live ? :mrgreen:

I wish - none of those that you've linked originated from a local source. This one actually came from Canada.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Irix Install Problems at Nov. 21, 2011, 1:08 p.m...

Which IRIX CD are you attempting to load, and tell us more about the external CD drive (and anything that might also be connected to your external SCSI bus). Make/model of the drive, SCSI ID, cabling, any adapters involved, and how termination is supplied.

And hope you have a very happy birthday!

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Warning:Origin 350 PSU may fail during sustained powered-on! at Nov. 22, 2011, 5:25 a.m...

That's some very useful info. Thanks for posting the follow up!

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes

Wrote on the subject of What's the fair price for V12 ? at Nov. 22, 2011, 10:14 a.m...

kubatyszko wrote:

That would make sense, and 151EUR is not as ridiculous as some sellers ask (even $500).

That one was an Octane V12, which is currently in less demand commercially than the Fuel version.

There still seems to be some commercial demand for the Fuel V12. This "WTB Fuel V12 gfx cards or machines with V12" recently appeared in the Hardware Wanted forum:

gopackgo66 wrote:

I'm looking for about 15 V12 grx cards. V12 gfx or V12 only part number 013-3416-007 (030-1726-006)

I've had some got-lucky-on-eBay experiences too, but for the time being you'd probably better expect some competition on that front.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of What's the fair price for V12 ? at Nov. 23, 2011, 4:02 a.m...

hamei wrote: Dr D had a different theory (Recondas can dredge it up in about thirty seconds, I bet).

hamei is probably referring to one of these Dr. Dave posts, though if you haven't already seen it, the entire thread is worth reading.
viewtopic.php?f=3&t=16720976&start=30#p7300469
viewtopic.php?f=3&t=16720976&start=45#p7300506

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Fuel V10 EEPROM 'disassembly' at Nov. 23, 2011, 6:55 a.m...

Thanks j-j!

If some one wants to compare the differences, here's the eeprom dump for the each of the Fuel V12s in my 'graphics-added' O350:
#1

Code: Select all


Product name: ASTODY


Serial        MLV203


Part Number   030_1726_003


Rev           E


T/W           00

Code: Select all


ODYSSEY (CH)


00 20 00 01 00 00 00 df


ODYSSEY (CIA), no data available (1)


ODYSSEY (BIA)


00 09 00 9b 57 33 c9 53 4f 4c 45 43 54 52 4f 4e


c6 41 53 54 4f 44 59 c6 4d 4c 56 32 30 33 cc 30


33 30 5f 31 37 32 36 5f 30 30 33 00 c2 5f 45 01


02 c2 30 30 04 ff ff ff ff 04 ff ff ff ff 04 ff


ff ff ff c1 00 00 00 a0


ODYSSEY (PIA), no data available (1)


ODYSSEY (IUA)


00 01 33 01 01 01 01 04 01 06 03 00 09 02 0f 01


13 01 16 01 19 01 24 00 00 00 00 00 00 04 03 01


01 20 07 01 05 ff 00 ff 04 42 01 01 00 20 03 00


01 02 01 4f 00 01 4f f4

#2

Code: Select all


Product name: ASTODY


Serial        MYA424


Part Number   030_1726_005


Rev           A


T/W           0

Code: Select all


ODYSSEY (CH)


00 20 00 01 00 00 00 df


ODYSSEY (CIA), no data available (1)


ODYSSEY (BIA)


00 09 00 62 53 40 c9 53 4f 4c 45 43 54 52 4f 4e


c6 41 53 54 4f 44 59 c6 4d 59 41 34 32 34 cc 30


33 30 5f 31 37 32 36 5f 30 30 35 00 c2 5f 41 01


02 c2 30 30 04 ff ff ff ff 04 ff ff ff ff 04 ff


ff ff ff c1 00 00 00 d5


ODYSSEY (PIA), no data available (1)


ODYSSEY (IUA)


00 02 33 01 01 01 01 04 01 06 03 00 09 02 0f 01


13 01 16 01 19 01 24 00 00 00 00 00 00 04 03 01


01 20 07 01 05 ff 00 ff 04 42 01 01 00 20 03 00


01 02 01 4f 00 01 4f f3

#1 de-hexed in a similar fashion to what jan-jaap did with the V10 data in his post:

Code: Select all


cc 30 33 30 5f 31 37 32 36 5f 30 30 33 = 030_1726_003 (part number)


c9 53 4f 4c 45 43 54 52 4f 4e = SOLECTRON (manufacturer)


c6 41 53 54 4f 44 59 = ASTODY (product name)


c6 4d 4c 56 32 30 33 = MLV203 (bar code)


c2 30 30  =  00 (T/W)


c2 5f 45  =  _E (revision code)

jan-jaap wrote: There's another EEPROM on the card, identified as "XIO (IUA)". Who knows what's to be found there.

The "CH" and "IUA" segments appear to be identical between your V10 and and the first V12, but there are differences between the IUA segments of the two V12s.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of What's the fair price for V12 ? at Nov. 23, 2011, 7:27 p.m...

PymbleSoftware wrote: But I think there is a difference between V10 and V12 ... Look at the first table in http://www.nekochan.net/wiki/VPro#Features

The Fuel used V10s with two different part numbers.

The first V10, those with part number 030-1725-00x, had 32MB of memory soldered to the PCB.

Later in production SGI began using V10s with part number 030-1826-00x. It was discovered during the thread linked above that these V10s actually had 128MB of memory - the PCB and components are identical to the 030-1726-00x V12 used in the Fuel.

Since both have 128MB of memory, hamei was trying to point out that if you can determine how the Fuel defines one as a V10 and the other as a V12, Fuel V12s might not be so rare/expensive. That was also why jan-jaap started the thread that contained the contents of the 030-1826-00x V10 eeprom: viewtopic.php?f=3&t=16725883 - so that perhaps someone here can decipher how one is identified with only 32MB and the other with 128MB.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Irix Install Problems at Nov. 25, 2011, 6:56 p.m...

cybercow wrote: I had the exact same issue on exactly same machine, only my Octane2 is V6. Like SAQ says you are using too old installation tools. Cant't remember now but i think i failed with 6.5.15?, later i obtained 6.5.26 and 6.5.30 and that was a go with no problems.

Support for the V6 and V8 first appeared in IRIX 6.5.8.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of DMediaPro VBOB 013-2746-006 vs. 013-3646-006 ? at Dec. 19, 2011, 6:34 p.m...

Here's a few shots of the inside of the TOI/TMDS equipped 013-2746-007 Rev A VBoB.

If someone with an 013-3636-00x VBoB would like to compare to see what might be different inside the 013-3646-00x and 013-2746-00x VBobs, the main board is labeled with part number 030-1515-008 Rev A (and the TOI/TMDS option board is 030-1537-002 Rev C):

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Installing & booting IRIX from Compact Flash (CF-IDE-SCSI) at Dec. 20, 2011, 3:03 p.m...

silicium wrote: Can mediad mount them automatically ?

I use Compact Flash media for the same purpose, but connect via Firewire. Compact Flash cards connected to a Firewire controller aren't auto-mounted by mediad.

With IRIX 6.5(.30) I use:

Code: Select all


# mount -t dos -o partition=1 /hw/path-to-your-controller-and CFmedia /your/chosen/mountpoint

to mount the CF card.

As long as there aren't any other DOS file systems mounted, you can use

Code: Select all


# umount -t dos

to unmount and extract your CF card.

BTW - DOS/FAT partitions are limited to a max size of 2GB under IRIX.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Fuel PSU problems at Dec. 27, 2011, 12:27 p.m...

Pontus wrote: Checking the pinout on the 24 pin P1 connector it doesn't match the color coding of neither ATX or WTX specs, but the _alternate_ pinout here http://pinouts.ru/Power/wtxmain_pinout.shtml matches except for one pin. That page also states that there is a 6-pin header used with the alternate pinout for CPU power, which the Fuel uses (well, it's a 8 pin connector but 2 are not connected).

As a follow up to Pontus' excellent description of the differences between the pinout of the 24-pin connector used in alternative WTX and Fuel HiPro HP-W460GC33 power supplies, I took a few minutes and created a table that helps to illustrate the differences and similarities of the (alternative) WTX, the Fuel Sparkle FSP460-60PFN, a generic Sparkle ATX2.2 FSP460-460PFN and ATX2.2 power supply pinouts side-by-side.

The WTX pinout was taken from the pinouts.ru page linked by Pontus, the Fuel PS pinout was derived from photographs posted by 87Porsche of the 24-pin connector on his Fuel's Sparkle FSP460-60PFN 460W power supply , and the list of wire colors/voltages printed on the Fuel/Sparkle power supply label .

I obtained a non-SGI/ATX2.2 version of the Sparkle power supply that uses the same FSP460-60PFN part number as the SGI version , but with an ATX 2.2 pinout. The non-SGI Sparkle FSP460-60PFN uses the same Nidec D08T-12PU cooling fan as the SGI version, which may eliminate the fan issues Pontus experienced.

The pinout of the non-SGI/ATX2.2 power supply is included in the table for comparison, as is the standard ATX 2.2 pinout (which also provides additional clues as to the electrical values of wire colors not listed on either Sparkle label). Hopefully a side-by-side of the four color-coded pinouts will serve as sort of a Fuel Power Supply Rosetta Stone.

Obvious differences between the WTX and Fuel Power Supply pinouts:

Pin 3 in the WTX pinout is an orange wire listed as "3.3VDC Sense", the values for the brown wire connected to pin 3 of the SGI/Sparkle aren't listed on the label, but the ATX/EPS version of the Sparkle power supply (with the same FSP460-60PFN part number) piggybacks the brown wire into the motherboard connector with one of the orange +3.3VDC wires (ATX pinouts from other sources list the brown wire as 3.3V Aux)
Pin7 is listed in the WTX pinout as "+5VDC (Aux)", the purple wire connected to pin 7 of the SGI/Sparkle is listed as "+5Vsb" (sb = standby).
Pins 11 (PC), 12 (FAN C), 23 (PSON) and 24 (FAN M) aren't assigned specific wire colors or values in the WTX pinout, the colors and values used in the SGI/Sparkle connector most likely provide environmental monitoring of the power supply to the Fuel L1.

Note that the WTX and SGI pinouts for the eight-pin connector used to supply CPU power (labeled "P2" in the Sparkle power supply wiring bundle) are different . The available photos of the SGI version of the Sparkle PS don't provide a clear view of that connector, so it hasn't been included yet. I'll update the post as soon as I have an opportunity to open one of the Fuels.

Please double check the values given in the table *and* the unlisted CPU power connector *before* attempting any to use an alternative power supply in your Fuel!!

The chart visible in this post is a jpeg, if the text proves hard to read in that format, the pdf version attached should be easier to read.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of IRIX compatible PCI Cards - A Visual Aggregation at Jan. 1, 2012, 11:25 a.m...

SGI Dual-Port Copper Gigibit Ethernet. SGI marketing designation PCIX-GIGENET-C-2P, SGI part number 030-2126-001.

Broadcom BCM5704-based chipset, OEM'd by Silicom (the Silicom model designation is PXG2RB-SGI-RoHS, Revision 1.0). Appears in an hinv with vendor ID 0x14e4, device ID 0x1648, which the PCI Database shows as a Broadcom NetXtreme Dual Gigabit Adapter . 133Mhz when used in a PCI-X slot, also slotted for use in either 3.3 or 5V PCI slots at their native speeds.

Supported under IRIX 6.5.20 or 6.5.21 with patch 5513, 6.5.22 or higher unpatched.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4915 notes

Wrote on the subject of For download: IRIX netboot appliance at Jan. 6, 2012, 12:47 p.m...

Adrenaline wrote:

Is there way to wipe the drive from prom? I'm guessing it doesn't like the non-irix partitions?

See Clearing Old Data Prior to Installation.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of For download: IRIX netboot appliance at Jan. 6, 2012, 1:05 p.m...

Adrenaline wrote:

Thanks! But how would that work doing a netboot? I don't have a cd-rom drive to boot fx from my IRIX CDs unfortunately.

Never tried it with a networked install, but if you're able to get into the installation menu you might be able drop into the Admin menu (#13) and run run fx from the admin chrooted shell.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of For download: IRIX netboot appliance at Jan. 6, 2012, 1:49 p.m...

Adrenaline wrote:

Code:

dks0d1s0: volume header not valid

swap partition (0) is not a valid swap area.

Hard to tell from only two lines out of the netboot process where things are going south. Can you invoke fx using this method? http://www.nekochan.net/wiki/IRIX_Netwo ... figuration

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of For download: IRIX netboot appliance at Jan. 6, 2012, 2:10 p.m...

Adrenaline wrote:

That worked! Doing an "auto" on it now.

Just to eliminate the potential for additional headaches I'd suggest following that guide's directions to explicitly partition it as a root option (ro) drive - but use a block size of 4096 .

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Fuel PSU problems at Jan. 11, 2012, 2:05 p.m...

Had an opportunity to extract the Sparkle FSP460-60PFN power supply from one of the Fuels and open it side-by-side with the PC-ATX version (that carries the same Sparkle part number).

First a comparison of the the labeling (the SGI version is on top). Not seen in this view, but the non-SGI/PC-ATX version is labeled "For Intel", so to minimize confusion I'll refer to them as the Intel or SGI verions.

The layout of the interior of the two power supplies is almost identical. The most notable difference between the two is a small circuit board, which is present in the SGI version but absent in the Intel version.

It would appear the extra circuit board is there to provide the SGI version environmental/fan monitoring and control, the fan cable in the SGI version is routed to the extra circuit board.

Both the Intel and SGI versions have a Nidec BetaSL model D08T-12U fan - the SGI version has three wires, the one used in the Intel version two.

In the Intel version the fan is connected to the main power supply PCB:

The fan header location used in the Intel version is marked on the main PCB in the SGI version, but no connection header was soldered in during assembly:

My guess is that the Fuel's L1 environmental monitoring won't work as intended without the additional circuit board (though it may be possible to wire the fan using the same method as pontus illustrated earlier in this thread).

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Fuel PSU problems at Jan. 12, 2012, 2:31 p.m...

guardian452 wrote: @recondas, if you are willing to do a bit more disassembly, could you take an extra pic of that SGI specific board?

That was my original intention, but even with the attachment screw removed there's too little play in the wiring to turn the board far enough to get a shot of the surface components - didn't want to risk breaking a solder connection and fubar a working PS.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of A little clip showing my OctaneII in action at Jan. 22, 2012, 2:19 p.m...

jeremy123 wrote: Thats my highly personalized OctaneII

I don't have access to uTube at the moment, but guessing from the comments in your post you have one of the classic MIPS Octanes. Were you aware that the new Rackable/SGI re-released the Octane using a Roman numeral model designator ? (if you do have one of the Rackable Octanes just ignore this post)

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4967 notes

Wrote on the subject of nekoware cleanup project at Feb. 1, 2012, 4:33 a.m...

hamei wrote:

Black Cardinal wrote:

I'm not sure what would be the best way to track votes. I'd be afraid that a thread could get pretty big and spread the data out too much to easily figure out the tally.

I think you're right. On the other hand, the situation isn't going to get better by itself .... got any idears ?

How about a thread for each beta app. Have the thread include the full name of the app to be tested, something like Beta Test: neko_newapp-0.1.13.tardist

I'd suggest that the person who packaged/submitted the app should start the thread - that initial post could include basic details on the app like dependencies or anything else noteworthy.

That naming-convention/single-thread methodology would make it fairly easy to find the thread, and see if anyone had tested the app, if any issues had been discovered, how many yea or nay votes had been cast. And the thread would remain, so if a year down the road someone has just gotten around to loading the app (even if it's been moved to /current), they can see what, if any, issues others might have had - something that might be helpful in tracking down potential problems or as yet unforeseen dependency issues.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4967 notes

Wrote on the subject of nekoware cleanup project at Feb. 1, 2012, 5:44 a.m...

hamei wrote:

That sounds pretty good - except for the part about the person who creeated the tardist creating the thread. I think most of them are dead :shock:

OK - fair enough. Until beta is cleaned up, if anyone who decides to test an app without an existing Beta Test thread would create the test thread (so that'd be any app that doesn't already have an originator-created thread).

It probably wouldn't be a bad idea if the person who created the test thread amended/edited the thread title once the testing had received enough votes. Something like Beta Test: neko_newapp-0.1.13.tardist - COMPLETED (or YEA or NAY or whatever). It would leave the thread open if further or future discussion was needed, but would serve as an easy visual clue that the initial testing had been completed.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of My new computer room at Feb. 4, 2012, 11:17 a.m...

There's a legend, deep in the jungle, about a new clearing where everything but the old O350's go......

Very Nice!

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of O2 dmrecord error at Feb. 7, 2012, 12:58 p.m...

rooprob wrote:

Observation. It's ok with 256MB ram, seems to record reliably all the time. Doesn't matter whether it's 2x 128 or 4x64. So discounting the slots or the sticks. Put in 384 (256 +128) and it's records and fails to record in even amounts. When it fails to record, it often only does twice

Early on there was an issue with O2s that had more than 256MB of memory installed , but afaik *only* IRIX 6.3 was affected.

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of DM3 / DM5 LVDS cable pinout at March 7, 2012, 7:41 a.m...

fockion wrote: have anyone eventually measured the pin-out of the LVDS cable?

If they did they haven't posted anything about it here.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of DM3 / DM5 LVDS cable pinout at March 7, 2012, 8:22 a.m...

mapesdhs wrote: I guess the key question is, can one use a 'standard' LVDS cable in place of the original SGI-branded
cables for DM2/VBOB/etc.?

Right. Hence the request for a pin out of an original SGI cable.........

canavan wrote: Is it straight through MDR26 <> MDR26 (or half pitch Centronics, whatever it is called)?

Don't know if it's straight through - you can see the pinout of a couple of the MDR26 LDVS cables 3M uses in this PDF , and the Camera Link MDR26 cable in this PDF - neither are pin-to-pin straight through.

Possibly a different application and/or pinout, but if anyone wants a couple of 'donor' MDR26 connectors there's currently "more than 10" male-to-male MDR26-to-MDR26 cables with the correct latch-type retention hardware on eBay for seven bucks a pop. http://www.ebay.com/itm/8-MDR26-Male-to ... 563e43cb12 Not a bad price for donor parts, considering "new" connectors and shells would run you $6.81 and $9.18 respectively at Mouser (and you'd need two connectors/shells for each cable).

Mouser will also sell a complete one-meter version of a 3M MDR26 cable for 58 bucks (slightly less if more than five are purchased): http://www.mouser.com/ProductDetail/3M/ ... cHiw%3d%3d - but you'd still need to make sure the pinout is DM2/3 compatible.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4968 notes

Wrote on the subject of Pixie for IRIX at March 8, 2012, 6 p.m...

sgienthu wrote:

Yes, I've installed neko_libpng-1.2.47 from /beta. No problems by the moment with Pixie.

Beta versions of nekoware are promoted to current/stable status after three members recommend the package.

neko_libpng-1.2.47 currently has two recommendations, would you be so kind as to consider adding your recommendation to that thread? You can find it here: viewtopic.php?f=15&t=16726272

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Fuel PSU problems at March 10, 2012, 3:28 p.m...

kubatyszko wrote: So I decided to pursue the ATX->Fuel conversion as well, with priceless of Pontus' and Recondas' research and diagrams, I can report success.

Nicely done.

kubatyszko wrote: It does complain about some I2C not present - I haven't figured that out yet.

The SGI supplied Sparkle power supply I opened was almost identical to the Sparkle ATX 2.2 version (with the same part number as the SGI OEM unit) - the major difference being a small circuit board in the SGI Sparkle. I suspect that additional circuit board might provide the I2C signal your Fuel mentions as missing. As long as its absence doesn't generate an auto-shutdown, the warning message is likely to be only a minor annoyance to someone who would other be without a working power supply.

kubatyszko wrote: Now - real-world test, I plugged the contraption to my Fuel - and voila, full success.

That's the part that would diminish the magnitude of the I2C warning.

Thanks for taking the time to share your findings. Keep us posted on your success with the PS fan speed monitoring workaround.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Fuel PSU problems at March 19, 2012, 5:27 a.m...

Probably not close enough to ramq to make shipping practical, but if anyone is looking for an ATX PS to mod for use with a Fuel, I still have the generic Sparkle ATX2.2 FSP460-460PFN power supply mentioned earlier in this thread. The generic ATX 2.2 Sparkle carries the same Sparkle part number (FSP460-460PFN) and 460w power rating as the Fuel WTX Sparkle, but would require kubatyszko's adaptation for use in a Fuel.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of Getting a Phobos P1000 Gbit NIC to work in O2... at April 18, 2012, 9:58 a.m...

Not sure how helpful they might be, but the manual ftp://ftp.sonicwall.com/pub/software/NI ... dified.pdf and the IRIX 6.5 driver ftp://ftp.sonicwall.com/pub/software/NI ... 0-v6.5.zip for the P1000 are available via ftp.

Of all people I'm sure you've been there, downloaded that, (I didn't see them on your web site, but I also didn't spend too much time looking), but on the slim chance you haven't I went ahead and posted the links.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of o300 quieter fan question at April 19, 2012, 4:12 a.m...

You can get a pretty good idea of which fans you can use by running the L1 command "env" and looking at the fan "Warning RPM":

Code: Select all


Description    State       Warning RPM


-------------- ----------  -----------


FAN 0     LEFT    Enabled         2160


FAN 1   CENTER    Enabled         2160


FAN 2    RIGHT    Enabled         2160


FAN 3       PS    Enabled         2160


FAN 4      PS'    Enabled         2160

You can use that to select low noise fans with that have a minimum speed above that number.

BTW, some 'temperature controlled' fans won't start until a minimum preset temperature is reached, the O300's environmental monitoring will likely read that as a fan failure and as a result auto-shutdown the machine. Had similar issues with an O350 I added VPro graphics to for another nekochan member . I used Vantec TF6025 Thermoflow fans with that set up and had to switch one of those to a non-thermostatic fan to avoid L1 fan warning messages.

The fans Adrenaline used look sound like they'd work well. Those are are rated at 2400rpm - comfortably above the 2160 rpm level that would generate a fan failure message in the O300.

Since he's already done proof testing, you could probably go ahead and graft the new fans onto the original O300 connectors (and not have to worry about un-doing the splice job if the fans didn't work out). If you do wire the new fans into the original connectors, you might consider taking a few photos - I'm sure anyone else who finds themselves in a your shoes would really appreciate it.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
Who joined June 6, 2004, 4:55 p.m.
and authored 4835 notes

Wrote on the subject of A few Sun questions at April 20, 2012, 3:44 p.m...

No firmware downloads, but if you can find readily available documentation for the system, SunShack has an on-line Sun System Handbook that includes the Sun Blade 2500 (Silver): http://www.sunshack.org/data/sh/2.1.8/i ... 2500S.html

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of o300 quieter fan question at April 21, 2012, 3:14 a.m...

You have experience with SGI hardware and wonder why it's non-standard?

The header for the 3-pin fans used in the O350 also don't comply with the common standard. The SGI pinout for other IP35 stuff (the Fuel and the O350) is Pin 1 - 12VDC; Pin 2 - Tach; Pin 3 - Ground. If you want to double check that the O300 fan wiring is (or isn't) the same, use a DMM to check the pinout of the original fans before you pull them. Once you're satisfied you've got the correct sequence, then re-wire the connectors (and new fans) to match.

Since the O350 uses a standard 3-pin connector, I used a dental pick to release the the wires from the connector and reinserted them to match the SGI pinout.

If you're lucky the terminals on whatever fan you select will fit into that less common connector used in the O300. If they don't, you might be able to use the info in smj's molex link to find solder or crimp wiring terminals that will fit.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of LTO anyone at May 5, 2012, 4:22 p.m...

As a follow up note, I just added an IBM LTO2/Ultrium-TD2 tape drive

Code: Select all


# mt status


Controller: SCSI


Device: IBM: ULTRIUM-TD2     4770


Status: 0x20262


Drive type: DAT


Media : READY, writable, at BOT

that works with the following definition file:

Code: Select all


/* IBM LTO-2 / Ultrium-TD2 */


{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD2", 0, 0, {0},


MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|


MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|


MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,


40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,


tpsc_default_dens_count, tpsc_default_hwg_dens_names,


tpsc_default_alias_dens_names,


{0}, 0, 0, 0,


0, (u_char *)0 },

That IBM LTO-2 drive completed a 12.4GB full system backup (using the IRIX gui for cpio) in a hair over 10 minutes.

There's a How-To post in the neko_wiki that describes where to place the definition file and how to configure your system to use it (and the tape drive): http://www.nekochan.net/wiki/Tape_Drive ... r_IRIX_6.5

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of ATTENTION!! Members who have Macintosh Signature Icons.... at May 5, 2012, 5:40 p.m...

Would anyone who linked the G4 Cube , MacPro , G5 PowerMac or NextStation Turbo w/Duckfoot Monitor icons in their Profile signature please remove those links. Those off-site icon images are missing and/or won't open.

The signature icons in question were originally provided by ZoonF in this forum post.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of ATTENTION!! Members who have Macintosh Signature Icons.... at May 5, 2012, 6:57 p.m...

smj wrote: Noticed this earlier, started to remove them, forgot, now complete. Were the dead links doing anything heinous to the board?

Probably more of an issue on the user end - your browser sits there trying to load the non-existent icon images until it times out. And unfortunately that's true for *everyone* who tries to load a page that includes a post by someone with one of the dead signature icons - none of the IRIX browsers need any slow-down enhancers.

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

recondas
Moderator
From NC - USA
Who joined June 6, 2004, 5:55 p.m.

Wrote on the subject of 10 StereoGraphics CE-3 on ebay, not mine, US only at May 6, 2012, 8:12 a.m...

Here's a couple of photos of an StereoGraphics CrystalEyes emitter (though not the ESGI model):

: Nine-Pin serial connection on this model - the pinout is available on the nekowiki or TechPubs.

There's a PDF version of the StereoGraphics Developer's Handbook that includes some interesting background info http://www.cs.unc.edu/Research/stc/FAQs ... ndbook.pdf

StereoGraphics wrote: SGI’s high-end machines, the Onyx® and Crimson® lines, may be
configured to run square-pixel windowed stereo with separate
addressable buffers for left and right eye views, at 960x680 pixels per eye
(108 fields per second). This does not require any more pixel memory
than already exists to support the planar 1280x1024. Some SGI highend
computers have additional display RAM available, and they can
support other square-pixel windowed stereo resolutions, though higher
resolutions come at the expense of field rate. For example, such high-end
high-display-memory SGI systems support 1024x768 pixels per eye but
only at 96 fields per second, which is high enough to have a flicker free
effect for all but very bright images.

As well as a data sheet for the CrystalEyes 3 glasses that are the focus of this thread: http://old.mfb-geo.com/pic/pdf/brochure ... l_eyes.pdf

***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

The collected works of recondas - Page 15