Getting Started, Documentation, Tips & Tricks

Indigo questions

I acquired a Indigo r4k sometime ago that was giving the TOD clock error, which I managed to fix with by replacing the battery only to discover there was a prom password. I managed to successfully clear the password by removing and reseating the eeprom chip. As expected the mac address reverted to ff:ff...... and I am unsure if the mac address can be reset on a r4k indigo or how to set the clock from the command monitor. IRIX is not bootable yet but I am working on that.

Any ideas on setting the mac address and clock?

Also hinv is showing IP20 R4000 at 75mhz but when I run diagnostics I am seeing IP20 R4400 at 150mhz. Not sure which is correct.
For a while computer companies specified the R4000 by its external clock speed, which is half of its internal speed. So 75 MHz clock on the board == 150 MHz R4000. The PROM version may be too old to recognize the PRid of the R4400, but I wouldn't expect any problems from that.

have you tried the PROM's date command?

_________________
:PI: :O2: :Indigo2IMP: :Indigo2IMP:
dyverize wrote:
I acquired a Indigo r4k sometime ago that was giving the TOD clock error, which I managed to fix with by replacing the battery only to discover there was a prom password. I managed to successfully clear the password by removing and reseating the eeprom chip. As expected the mac address reverted to ff:ff...... and I am unsure if the mac address can be reset on a r4k indigo or how to set the clock from the command monitor. IRIX is not bootable yet but I am working on that.

Well, no, this is not to be expected on an R4k Indigo - they don't lose their Ethernet address when the TOD clock battery dies.

However, quoting from G. Lenerz' site ( http://www.sgistuff.net/hardware/systems/indigo.html ) :

Quote:
Bad eaddr

Signs of failure: The system complains about a bad ethernet address (ff:ff:ff:ff:ff:ff).

In general this means that the EEPROM that contains the hardware ethernet address is dead or contains invalid data. It is an 8 pin MiniDIP serial EEPROM (93C56) which is socketed on the backplane.

In many cases the reason is, that in the Indigo different CPU boards (IP20, then IP12) were used. The location of the adress is different between the two boards and is properly relocated when a system is upgraded from IP12 to IP20. When the IP12 is placed back in the system the MAC address is erased.

A possible solution is to place the IP12 in the system and reset the mac adress from the PROM monitor using the eaddr command - the IP20 doesn't allow that. After that the system can be used with the IP12 board or upgraded to IP20 which will relocate the address once again.


I'd wager your Indigo had been used for a while with a R3000 Indigo CPU board. And apparently, you won't be able to restore the proper Ethernet address until you can put an R3000 CPU board in it.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
Of interest viewtopic.php?t=894
The Indigo had a prom password on it and the guy I got it from had never used it and didn't know what it was. So last resort I took a chance and pulled the eeprom and used the resetpw command to clear the password, it worked however as a side effect this clears the mac address. The address is on the chassis but I am unsure how to add it again, not that I will probably be needing it, but I am fairly new to IRIX and I do not know if this will cause issues installing or starting IRIX. It still has the original XZ4000 badges on the front so I think it was originally a IP20 but it has probably changed hands a lot over the years so who knows.

Any and all help is appreciated.
If you'd post where you are then someone with a HP1 R3000 board might be nearby.

_________________
Damn the torpedoes, full speed ahead!

Systems available for remote access on request.

:Indigo: :Octane: :Indigo2: :Indigo2IMP: :Indy: :PI: :O200: :ChallengeL: :O2000R: (single-CM)
That would be awesome but unfortunately I am on Prince Edward Island in Canada, and as far as I have been able to determine am the only one on the island who owns any or has any interest in Silicon Graphics computers.
Hmm - you might be right there.

Do you know any electronics types who would have a EPROM programmer?

_________________
Damn the torpedoes, full speed ahead!

Systems available for remote access on request.

:Indigo: :Octane: :Indigo2: :Indigo2IMP: :Indy: :PI: :O200: :ChallengeL: :O2000R: (single-CM)
Does anyone know what monitors can be used with an indigo? I know that Sgi systems need sync on green compliant monitors and I have one Silicon Graphics Crt which works fine with a 13w3 adapter but none of my other Crt's or Lcd monitors even produce a image, SOG or not. I also have several O2's which work on the non SOG monitors albeit a green tinted image. Is this normal behaviour or is something wrong?

Bad 13w3?
dyverize wrote:
Bad 13w3?
Maybe.

There isn't a standard 13W3 pinout, pretty much everybody who used one went their own way. If you'd like to see if your 13W3 adapter is compliant with (one of) the SGI 13W3 pinouts, there's a table of a few of the varieties in the nekowiki. http://www.nekochan.net/wiki/13W3

_________________
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
dyverize wrote:
I also have several O2's which work on the non SOG monitors albeit a green tinted image. Is this normal behaviour or is something wrong?

This is normal behaviour for non-SOG monitors: they don't recognize and filter the sync signal, which causes the image to be greenish.

_________________
:Indigo: R4000 :Indigo2: R4400 :Indigo2IMP: R4400 :Indigo2: R8000 :Indigo2IMP: R10000 :Indy: R4000PC :Indy: R4000SC :Indy: R5000SC :O2: R5000 :O2: RM7000 :Octane: 2xR10000 :Octane: R12000 :O200: - :O200: 2x2xR10000 :Fuel: R16000 :A350:
among more than 150 machines : Apollo, Be, Data General, Digital, HP, IBM, MIPS before SGI , Motorola, NeXT, SGI, Solbourne, Sun...
But what about for the indigo? The only monitor I have that works with it is a Silicon Graphics Crt. None of my Crts or LCD monitors (which work fine on my O2's and everything else) even produce an image with the indigo.
I am wondering if this is normal behavior for the indigo or maybe a bad 13w3 adapter.
dyverize wrote:
But what about for the indigo? The only monitor I have that works with it is a Silicon Graphics Crt. None of my Crts or LCD monitors (which work fine on my O2's and everything else) even produce an image with the indigo.
I am wondering if this is normal behavior for the indigo or maybe a bad 13w3 adapter.


Indy, Indigo2 and up provide a separate sync signal (as does LG1 Indigo), but I'm not sure if GR2 Indigo graphics do - earlier SGIs only provided sync-on-green.

_________________
Damn the torpedoes, full speed ahead!

Systems available for remote access on request.

:Indigo: :Octane: :Indigo2: :Indigo2IMP: :Indy: :PI: :O200: :ChallengeL: :O2000R: (single-CM)
SAQ wrote:
Indy, Indigo2 and up provide a separate sync signal (as does LG1 Indigo), but I'm not sure if GR2 Indigo graphics do -

I'm not sure about Indigo GR2 graphics either. Those pins were simply marked 'reserved' for a while. I know Reality Engine does *not* provide separate sync . Worse: it supplies +10V for stereo emitters on one of the pins. I think there are at least 3 or 4 different and sometime incompatible SGI 13W3 pinouts. The Indy &co used 'monitor id' pins, Octane, Onyx2 etc. used DDC. And then there's the Onyx Infinite Reality which leaves everything except RGB n/c.

Because the O2 has a commodity VGA plug, everyone has a cable which provides correct sync signals to a monitor and the monitor merely has to tolerate the SOG present in the RGB, but not necessarily be capable of using it.

The majority of 13W3-HD15 adapters out there is wired for SUN systems, which use yet another incompatible pinout. If such an adapter is used with an Indy, Indigo, Indigo2, ... it will not pass sync to the correct input pins of the monitor. If the monitor does not support SOG either, it will not sync at all.

Quote:
earlier SGIs only provided sync-on-green.

Nah, the old SGI's with GT(X) and VGX simply supplied SYNC on a separate BNC ;) I used that GT with a bog-standard iiyama LCD screen, btw.

_________________
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)