SGI: Hardware

The O2 Hardware Aggregator - Page 1

The following list will include only non sgi-made, confirmed working hardware...


• SCSI HardDisks :

    Any 1' SCA-2 HD [Take a look @ FAQ #1 & #6 down the list]

    Suggestions for low-noise 15K HDs:
    - Fujitsu MAS3367NC
    - 146GB Maxtor 15K II


• SCSI PCI Cards :

    01. Adaptec AHA-2940UW
    02. Adaptec AHA-2944UW HVD [via this hack ]
    03. Adaptec AHA-3940UW [via this hack ]

• Fibre Channel Cards :

    01. QLogic QLA2200: 1Gb Fibre Channel Adapter Copper/HSSDC Interface
    02. QLogic QLA2200/66: 1Gb Fibre Channel Adapter Copper/HSSDC Interface
    03. QLogic QLA2200F/66 1Gb Fibre Channel Adapter Optical LC connector, confirmed by magellan
    04. QLogic QLA2212: 2 x 1Gb FC-AL Interfaces [Everyone thank Dr.Dave for his guide/tests/efforts ]
    05. QLogic QLA2342: dual-port 2GB optical FC, confirmed by mapesdhs

• FireWire (IEEE-1394) Cards :


• Network Cards :

    01. FORE PCA-200E ATM Adapter Card
    02. Phobos P1000 Gigabit PCI card, confirmed by Ian Mapleson but "the SGI OEM'd "tg" and "eg" gigabit cards will *not* work in the O2"


• CD-ROM Drives :

    01. DEC RRD46 12X, confirmed by Ian Mapleson .
    02. NEC 1910A 32X, confirmed by mapesdhs
    03. NEC 3010A (40x)
    04. Plextor PX-12CSe 12X
    05. Plextor PX-20TSe 20X
    06. Plextor PX-32TSi, confirmed by twix . Eject button does not align with the o2's plastics.
    07. Plextor PX-40TS 1.12, Firmware info: 1 , 2
    08. TEAC 532S (32x)
    09. Toshiba XM-3801B, confirmed by Arabski
    10. Toshiba XM-4101B
    11. Toshiba XM-5401TA
    12. Toshiba XM-6201B 32X, confirmed by mapesdhs
    13. Toshiba XM-6401B

• CD-RW Drives :

    01. HP 9600 SCSI CDRW , confirmed by Ian Mapleson .
    02. Pioneer DR-466 (12x SCSI), confirmed by gaku but "...the plastics won't align with the O2 case"
    03. Plextor CD-R PX-R412C 1.04
    04. Teac CD-R 56 S4 1.0F
    05. Yamaha CRW4416SXZ [8x4x24]
    06. Yamaha [8x8x24], confirmed by Ian Mapleson
    07. Yamaha CRW2100SZ [16x10x40]

• DVD-ROM Drives :

    01. Toshiba SD-M1401 [more info on using it internally here or externally here and there ]
    02. Toshiba SD-M1711, confirmed by hamei [ Note: There have been both positive and negative reports on the use of non-SGI variants of the Toshiba SD-M1711 with an O2. The issue is possibly firmware related, if you attach an SD-M1711 to an O2 please post if you were successful or not, the firmware revision of the SD-M1711, and the PROM/IRIX revison of the O2. ]

• DVD-R/RW :

    01. Pioneer DVR-S303 [Professional model, released only in Japan ]

• DVD-RAM Drives :

    01. Matshita/Panasonic LF-201
    02. Matshita/Panasonic LF-291
Details on firmware updates and software to allow use of non-cartridge disks is in this thread .

• DAT/DDS :


• 3.5" Floppy Drives :
    01. Teac FD-235 HS

• Removable Drives :
    01. Imation LS-120 [SCSI]
    02. Iomega Jazz [SCSI]
    03. Iomega Zip 100 [SCSI]
    04. Iomega Zip 100 Plus [SCSI/Parallel]

• Magneto-Optical (MO) Drives :
    01. Fujitsu MCM3064SS
    02. Fujitsu MCM3130SS
    03. Fujitsu MCJ3230SS

A detailed bilingual guide by Diego A. De Giorgio [ Generatrix ] can be found here: The MOD/M.O.D. (Magneto Optical Drive) IRIX FAQ

• Scanners / Printers :

    01. Hewlett Packard ScanJet 5P
    02. Epson Perfection 636 [SCSI]
    03. Umax Astra 1220S Flatbed Scanner [with the proper cabling to get to a DB25 SCSI connector]
    04. Zebra/Eltron P310C PVC card printer, confirmed by zahal

• Tablets/Mice/Spaceballs :

    01. WACOM ArtPad II [Model KT-0405-R]
    02. WACOM Intuos [Serial]
    03. WACOM Intuos 2 [Serial]
    04. Spaceball 4000FLX, confirmed by zahal " MD 1.8.6 works on my O2 (it uses libsball) "

• PCMCIA Card readers :


• Monitors

- SoG tolerant:

    - Acer AL1916W LCD (1440x900), confirmed by Dr. Dave

    - CMV CT-720D 17" LCD, confirmed by strandedinnz

    - Compaq P1220 22", Confirmed by Ian Mapleson

    - Cornea MP704 , (17" 1280x1024 VGA only LCD), confirmed by tillin9

    - Dell 1800FP 18.1" SXGA LCD (S-IPS true 24-bit), confirmed by MisterDNA

    - Dell 1901FP, confrimred by ramq

    - Dell 1908FPc, confirmed by theodric , but: "When I factory-reset the monitor, I got fuzzing @ 60Hz-- then I picked 72Hz and all was clear. Also works well @ 50Hz "

    - Dell 1908WFP, confirmed by theodric at [email protected] using his custom vfo.

    - Dell 2001FP 20.1" UXGA LCD (S-IPS true 24-bit), confirmed by MisterDNA

    - Dell 2005FPW, confirmed by lewis

    - Dell 2405FPW, confirmed by dangermouse

    - Dell 2407wfp, (24" 1920x1200 DVI/VGA), confirmed by tillin9

    - Dell U2414M, confirmed by Ian Mapleson

    - Dell P1130 21", confirmed by Ian Mapleson

    - Eizo FlexScan S1910, confirmed by Arabski

    - Elements EN-LM500/ Envision EN5100e 15" TFT, confirmed by tillin9 but: "(same panel marketed under at least those two names), only supports 1024x768 max resolution VGA" .

    - Fujitsu Siemens X140f (@1024x768), confirmed by ramq

    - Fujitsu Siemens SCALEOVIEW L22W-3 (@1440x900 - native res is 1680x1050) confirmed by [[C|-|E]]

    - Gateway VX900 18" CRT, confirmed by akimmet

    - Hanns-G HW191A 19" 1440x900 LCD, confirmed by theodric

    - HP 2035, confirmed by Arabski . " native 1600x1200. Nice feature is "Custom Scaling" which allows to map pixels 1:1, so any resolution looks good (black frame around image) ."

    - HP F1703 17" SXGA LCD (dithered 18-bit) (several versions made), confirmed by MisterDNA

    - HP L2335, confirmed by tikiroa but "good [email protected], [email protected], [email protected], at 32 bit large black boxes in the lower part of the screen; standard resolutions good"

    - HP P1130 21", confirmed by Ian Mapleson

    - HP P1230 21", confirmed by Ian Mapleson

    - HP LP2475W, confirmed by Ian Mapleson

    - IBM P70 17" CRT

    - IC Power 17' & 19' LCDs, confirmed by zizban .

    - Iiyama Vision Master Pro 17 17" CRT (both on HD15 and BNC inputs)

    - LaCie 19'' & 22'' ElectronBlue IV, confirmed by fu . (LaCie CRTs are re-badged Mitsubishi Diamondtrons).

    - LG Flatron L1732TQ, confirmed by bidD.

    - LG Flatron L1952H, confirmed by cicero

    - Mitsubishi Diamondtron RDF225WG 22", (same as LaCie's ElectronBlue CRTs, specs )

    - Mitsubishi Diamond Pro 2070SB, confirmed by Ian Mapleson

    - NEC MultiSync FP1370 (22'' CRT), confirmed by gaku

    - NEC MultiSync FP1375X 22", confirmed by Ian Mapleson

    - NEC Multisync LCD 1830, confirmed by loonvf

    - NEC 1860NX (18" TFT) - 1280x1024, DVI/VGA, confirmed by tillin9

    - Philips 150S4, (15" 1024x768 VGA only LCD), confirmed by tillin9

    - Philips 150S6FG/00 (15" TFT), confirmed by xc8

    - Samsung 153T 15" LCD (dithered 18-bit), confirmed by MisterDNA

    - Samsung 172x, confirmed by phrosty-boi

    - Samsung SyncMaster 226BW, confirmed by Glock

    - Samsung SyncMaster 710V, confirmed by Indyboy

    - Samsung 740N, confirmed by hamei

    - Samsung 913N Syncmaster, confirmed by Skysearcher

    - Samsung 940BW and Samsung 940BF, confirmed by tesla.

    - Samsung 950p, confirmed by zafunk, -->needs SOG activation

    - Sony G530, confirmed by Ian Mapleson

    - Sony G550, confirmed by Ian Mapleson

    - Sony GDM-400PS 19", confirmed by gborce

    - Sony W700 24" CRT, confirmed by dion_b

    - ViewSonic G810, confirmed by Ian Mapleson

    - ViewSonic P220F, confirmed by Ian Mapleson

- Non SoG capable but hackable (YMMV):

    - Eizo FlexScan L567, hacked by cicero : "...Colors are okay, some vertical regions of the displayed image are a little blurred. You probably notice this effect when working in the shell."

    - NEC Multisync LCD 1770 NX, hacked by cicero : "...you have to use a customized VGA cable (pin 11 - 15 removed) in order to force the display to use the SOG signal" .

    - Nokia Multigraph 449M (15'' CRT), hacked by gaku : "..."almost" looking normal with an gamma-patch" applied as suggested by -> hindu <- "
I seen a pic of an Indy running at 500MHz. How can I do that?

_________________
Dell 8400 P4HT 3.4GHz / HP DV2047CL / Compaq P3 733MHz
SGI 02 175MHz / Indy 150MHz / Indy 150MHz
iMac G3 SE 700MHz
Me too!
Mine needs a boost.

_________________
*****************************
The difficult can be done.
The impossible takes a little longer.
*****************************
Been talked about- the 500MHz Indy is the result of a bug in the PROM, and isn't really running that fast.

The R5k/180 -> R5k/200 upgrade seems to work pretty well, though, based on reports I've heard, and you might be able to boost up a 175 or 200MHz R4k CPU module to something faster (the 100 and 150MHz R4000/4400 modules are 5v CPUs, the 175 and 200MHz modules are 3.3V CPUs. The 250MHz R4400 as used in the PM5 for Indigo2 is also a 3.3V part). The main question, apart from voltages, is how the CPU clock is made. On Indigo2, 100, 150, 200 and 250MHz modules use a straight .5x the internal frequency can oscillator. Not sure what the Indy R4k modules used. Also unsure about the PROM capabilities.
Does anyone have the eprom image or burned eproms that would be necessary to overclock a R5k 150 to 200MHz? What's the minimum cache speed required for this to work?
canavan wrote:
Does anyone have the eprom image or burned eproms that would be necessary to overclock a R5k 150 to 200MHz? What's the minimum cache speed required for this to work?


PROMS are the standard R5k PROMS, cache is (AFAIK) the same (the modification is changing the external oscillator from 45MHz to 50MHz, and the 150MHz processor module is also a 50MHz external clock. R5k doesn't have the backside cache bus, so cache access is at the system bus speed (45 or 50 MHz)- it's very likely that the 150SC and 180 modules have the same cache RAMs.
I wrote this up a bit on a thread:

viewtopic.php?f=3&t=9772

I'm still looking for a image of the small serial eeprom on the indy r5k module board (any speed) to finish testing. I tried writing a serial eprom binary from scratch a few different ways but couldn't get it to boot so I need an original read to modify.

_________________
TriOx
A reference point for people worried about heat - just swapped a 10k rpm IBM DDYS drive out for a 15k rpm Maxtor Atlas (not even Atlas II) and the newer faster drive runs cooler than the older slower one.
I'm having a serious problem booting an SGI Fuel. I believe it is running IRIX 6.5 and the PROM is version 6.144.

The system was working but no one knew the root password. Of course I tried getting into single user mode by typing 'single' at the PROM console which started a boot then the screen went blank and the system became nonresponsive. I tried using 2 different overlay installation CD's (can't find original OS) to boot but both appear to lock up the graphics after copying files to the harddrive (before any menus even come up).

I've tried connecting a null-modem cable to COM1 from an XP PC running hyperterminal (9600 8-N-1) but have never been able to get any output to the terminal. I've tried with and without the keyboard and mouse plugged into the Fuel. In an attempt to get this working I was playing with environment variable in the PROM and may have changed something that's caused my current situation. I set the following:
console=d
AutoBoot=No

When the Fuel is turned on, the 3 lights on the keyboard flash as normal; the LED on the case flashed white for a bit then goes solid white (normal I think); but the monitor never turns on! Usually the monitor would come on maybe 10 seconds after the flashing keyboard lights, just in time to see the graphical display prompting to enter Maintenance Mode.

If I press the power button on the Fuel at this point it shuts down immediately.

The last thing I did in the PROM console was run 'init' which froze the screen. After a hard reset I haven't been able to get the monitor to come on at all.

Will removing the PROM battery reset all PROM variables or only reset the password?

Any help would be much appreciated.

Matt
Connect with a terminal to the L1 controller to find out if there is system activity left. The connector is ON the systemboard, so you have to open the case (left panel). You can find the DB9 pin port 5cm right from the middle.

About the terminal settings.... you tried it with 9600baud but i thing you need 19200 or 38600. My other 3xxx devices use 38600/8/1/n. So check the manual or try an error.

regards
Joerg

_________________
http://www.irixworld.net
Hi - for the console at the rear of the Fuel I use 9600,n,8,1 connected to the serial #1 port and use a null modem cable.
Joerg is right that the other O3xxx family members use 38400 baud.
The keyboard/mouse removed should get you to a console menu

_________________
Origin 3400 32 x 400 MHz / 32 GB
Origin 3200 8 x 500 MHz / 8GB
Origin 2000 8 x 300 MHz + 24 x 250 MHz / 48 GB
Fuel V12 600 MHz + 2GB
In-build Onyx2 rack system / IR2 / 4 x RM7 ..........watch this space
maxsleg wrote:
Hi - for the console at the rear of the Fuel I use 9600,n,8,1 connected to the serial #1 port and use a null modem cable.
Joerg is right that the other O3xxx family members use 38400 baud.
The keyboard/mouse removed should get you to a console menu


Those are the same settings I've used but I've never seen a single character display on the console! I've tried all 3 ports (2 on the back and 1 on mainboard) with 2 different serial cables (1 straight through and 1 with pins 2 & 3 crossed over). I've also tried with and without the kb/mouse plugged in.

Is it possible that the problem is on my PC end of the connection. I'm running HyperTerminal on WinXP.
joerg wrote:
Connect with a terminal to the L1 controller to find out if there is system activity left. The connector is ON the systemboard, so you have to open the case (left panel). You can find the DB9 pin port 5cm right from the middle.

About the terminal settings.... you tried it with 9600baud but i thing you need 19200 or 38600. My other 3xxx devices use 38600/8/1/n. So check the manual or try an error.


Thanks Joerg. I tried your suggestion and still nothing on the serial console!
matt2079 wrote:
joerg wrote:
Connect with a terminal to the L1 controller to find out if there is system activity left. The connector is ON the systemboard, so you have to open the case (left panel). You can find the DB9 pin port 5cm right from the middle.

About the terminal settings.... you tried it with 9600baud but i thing you need 19200 or 38600. My other 3xxx devices use 38600/8/1/n. So check the manual or try an error.


Thanks Joerg. I tried your suggestion and still nothing on the serial console!


I dont mean the console.... i'm talking about the l1 controller. I cant verifed the settings because my fuel is at $home, but i dont believe that it used the old 9600 baud settings. After search 10min on techpubs i cant find the info.... grrrr. :(

Whats the status of the Front LED?
My Fuel needs more than 30sec befor the screen get a signal. I know it depends on the amount of memory how long it takes :)


regards
Joerg

_________________
http://www.irixworld.net
Hi - you say the light bar flashes red a bit then goes solid white - I would just double check all is OK with your PCee terminal - have you got the terminal 'ONLINE' and in the right serial port at the back of the PCee?
It is a null modem cable and 9600,n,8,1 you need for the serial port 1 connection..I think I agree with Joerg that the L1 is 38400...

_________________
Origin 3400 32 x 400 MHz / 32 GB
Origin 3200 8 x 500 MHz / 8GB
Origin 2000 8 x 300 MHz + 24 x 250 MHz / 48 GB
Fuel V12 600 MHz + 2GB
In-build Onyx2 rack system / IR2 / 4 x RM7 ..........watch this space
joerg wrote:
I dont mean the console.... i'm talking about the l1 controller. I cant verifed the settings because my fuel is at $home, but i dont believe that it used the old 9600 baud settings. After search 10min on techpubs i cant find the info.... grrrr. :(

Whats the status of the Front LED?
My Fuel needs more than 30sec befor the screen get a signal. I know it depends on the amount of memory how long it takes :)

regards
Joerg


I understand. I tried the L1 controller as well - no results.

The front LED turns red for about 2 seconds immediately after the power button is pressed. Then it flashes white 18-20 times over about 1 minute. Then it is solid white.
maxsleg wrote:
Hi - you say the light bar flashes red a bit then goes solid white - I would just double check all is OK with your PCee terminal - have you got the terminal 'ONLINE' and in the right serial port at the back of the PCee?
It is a null modem cable and 9600,n,8,1 you need for the serial port 1 connection..I think I agree with Joerg that the L1 is 38400...


Everything seems fine on the PC end. It only has one serial port (COM1) which is the only DB-9 port on the PC. I've tried 2 cables:
DB-9M to DB-9F marked 'null-modem' on the connectors with a DB-9F to DB-9F adapter - pins 2 & 3 are crossed
DB-9M to DB-9F with same DB-9F to DB-9F adapter - pins 2 & 3 are 'straight-thru'

I'm using HyperTerminal on WinXP. Is it possible that's where the problem is? Should I try a different terminal emulator?

Thanks,

Matt
matt2079 wrote:
joerg wrote:
I dont mean the console.... i'm talking about the l1 controller. I cant verifed the settings because my fuel is at $home, but i dont believe that it used the old 9600 baud settings. After search 10min on techpubs i cant find the info.... grrrr. :(

Whats the status of the Front LED?
My Fuel needs more than 30sec befor the screen get a signal. I know it depends on the amount of memory how long it takes :)

regards
Joerg


I understand. I tried the L1 controller as well - no results.

The front LED turns red for about 2 seconds immediately after the power button is pressed. Then it flashes white 18-20 times over about 1 minute. Then it is solid white.


Are you sure that you use the right cable? For the l1 controller you have to send "crtl+t"<enter>.

Can you hear if the disk is working and starting the OS? If so, try to ping the machine over the network. After a few minutes use telnet or ssh to login.

Why do you set "console d"? Thats no wounder why you cant see anything on the screen :) Get a working cable and set it back to "console g". The docs says that on some some systems the password jumper can be removed to set the value back to "g". But the docs doesnt say on which machines exactly. I also dont know if the FUEL have a password jumper.

regards
Joerg

_________________
http://www.irixworld.net
matt2079 wrote:
I'm using HyperTerminal on WinXP. Is it possible that's where the problem is? Should I try a different terminal emulator?


Hyperterm works fine for me and i use it since years. But if you have another system around test it.

regards
Joerg

_________________
http://www.irixworld.net
joerg wrote:
matt2079 wrote:
I'm using HyperTerminal on WinXP. Is it possible that's where the problem is? Should I try a different terminal emulator?


Hyperterm works fine for me and i use it since years. But if you have another system around test it.

regards
Joerg


I managed to get a connection to the L1 controller!

Now what do I need to check?