SGI: Hardware

I seen a pic of an Indy running at 500MHz. How can I do that?

Me too!
Mine needs a boost.

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?

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.

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

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.

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

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...

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.

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

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

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?