From: regmad@gsusgi2.gsu.edu (Michael de Kraker)
Subject: Re: HELP 3b2 dead
Keywords: 3b2 boot
Organization: Georgia State University
Date: Fri, 4 Sep 1992 16:22:23 GMT

dcb@kopachuk.uucp (David Breneman) writes:

>In article <regmad.715453158@gsusgi1.gsu.edu> regmad@gsusgi2.gsu.edu (Michael de Kraker) writes:
>>Help Help Help:
>>
>>	Currently it just sits there both power and diag lights
>>	light but no flashing and no firmware prompt.
>>
>>	Heres what happened:
>>
>>	Hit big red switch to on
>>	Wait Wait Wait ( get impatient )
>>	Hit big red switch to Standby
>>	Console prompt flashes on screen init level 0 begins
>>        System shuts down by self.
>>	Hit big red switch and does not come up power and diag led light.
>>

Perhaps I should be clearer her the system was acting normally when I
hit the switch to standby.... The system has not come up since.

>Did you try pushing the reset button several times when the Diagnostics
>light comes on?  That sould get it into firmware mode.  

Yep an nothing no garbage or anything.
The power and diag lights come on no flashing hard disk spins up and then
NOTHING!!!!! no firmware no UNIX.

>It's a little
>vague what you mean by "Console prompt flashes on screen init level 0
>begins".  Do you mean that you get the message "INIT: new run level 0"
>(not sure of exect wording - but you know it if you see it) or do you
>merely get a flickering of the cursor?  If you just get a flickering
>of the cursor, the console port baud rate may have been changed. 

Yes I got the message once just before the system shutdown as a result
of the my impatience and hitting the switch to standby.
The word Flashes was meant to portray the fact that after I hit the 
big red switch to standby, the system came up and right back down.

>Cycle your terminal
>through all its baud rates and see if you can get something intelligible
>to some up.  The best way to do this is to change the speed on the
>terminal, press the reset button a couple times and see if anything
>comes up on the screen.  If not, try it at another speed.  If you
>eventually get a repsonse at a speed other than 9600, then you know that
>that is the problem.  With the machine in firmware mode, when it asks
>program to run enter "baud".  It will them prompt you for the correct
>speed.  Enter it (9600), change your terminal back to 9600 and reboot
>the machine.
>> 
>>	The only result was I felt that the main board runs hot
>>	which may be normal. One coincidene is that the ATT 610
>>	terminal appears to have died along with the 3b it will
>>	rcv but not xmit. It was not used as the console during 
>>	death of the 3b2 but was used subsequently. May be a clue.
>>
>Well, make sure you're using a working terminal!
>*Necessary* settings for a 610 used as the console are:
>	SPEED		9600
>	SEND PARITY	NONE
>	LOCAL ECHO	OFF

Again I tried several terminals at all settings and have always been aware
of the port requirements. The death of the 610 terminal may have been 
a clue. Possibly the console circuitry is fried on the 3b2 end killing my
terminal or vice versa.

>>	Again any advice or sources for parts and service at a reasonable
>>	rate would be greatly appreciated.

>Worst case scenario is it's the mother board.  You can get these used
>for a couple hundred bucks.  It sounds, however, like a failure to
>communicate :-) .  Probably console set up wrong, bad cable, or wrong
>baud rate on the console port.

I suspected this but wholesale replacement of the mother board is not fixing,
it is replacing. I have no source for a mother board either. Where can I get
one. Maybe it is the power supply what are the voltages and test points????

Again thanks for the response to everyone but need suggestions for clues
as to the system with solid power and diag led's.