most of the we are facing when we trun ON the system. no beap sound and
fan runs forever....no display
Help on this issue
Thankyou
Has anything been changed/added to these systems? For example,
I have (on Sun Blade 2000 systems) seen such behavior when:
1) A second (or replacement) CPU module has been installed, and it
is not torqued to the proper specs, so it is not making reliable
connections on that long multi-pin connector.
2) Memory DIMMs have been added or replaced, and one is either bad,
not fast enough, or not properly seated in the connectors.
3) No keyboard connected, even though there is a monitor connected,
so the error messages go to /dev/ttya, and there is no terminal
connected to monitor that. Then you could have a bad boot drive
-- or the eeprom settings for "boot-device" have been corrupted,
or something like that.
> Help on this issue
No direct experience with a Sun Blade 2500, but if it behaves
similarly to the SB-2000, these could be the problem.
I hope that the above suggestions help you to find the problem.
Good Luck,
DoN.
--
Email: <dnic...@d-and-d.com> | Voice (all times): (703) 938-4564
(too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
--- Black Holes are where God is dividing by zero ---
we didn't change any thing. but i am very interseted about keyborad,
you mean if keyborad is not connected and might be NVRAM.
Yes -- if there is no keyboard connected, it will default to
communicating via the TTYA serial port (at 9600 baud, by default.)
And you *might* be getting error messages on the TTYA port which
could tell you what is wrong.