Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

E250 - Monitor not working - lights just flashing

18 views
Skip to first unread message

bertieb...@gmail.com

unread,
Aug 14, 2012, 12:17:04 PM8/14/12
to
Cant actually see this because its remote from me - this is what the
people on site are reporting.

What I think has happened is that the server has been powered on and
THEN the monitor has been connected.

I seem to vaguely remember with these that the monitor has be
connected before powering on? Unfortunately, its not a simple case of
powering off/on because of the app the servers are running (needs to
be done properly)

Michael

unread,
Aug 14, 2012, 4:25:29 PM8/14/12
to
Hi,

On 08/14/12 06:17 PM, BertieB...@gmail.com wrote:
> Cant actually see this because its remote from me - this is what the
> people on site are reporting.
>
> What I think has happened is that the server has been powered on and
> THEN the monitor has been connected.
Don't know if I understand you correctly but the monitor should always
work regardless if it was connected or not.
Is there a keyboard attached to the E250?

>
> I seem to vaguely remember with these that the monitor has be
> connected before powering on? Unfortunately, its not a simple case of
> powering off/on because of the app the servers are running (needs to
> be done properly)
What lights are flashing? the running LED or service LED?

/michael

bertieb...@gmail.com

unread,
Aug 15, 2012, 4:36:24 AM8/15/12
to
On Aug 14, 9:25 pm, Michael <michael_laaja...@yahoo.com> wrote:
> Hi,
>
> On 08/14/12 06:17 PM, BertieBigBol...@gmail.com wrote:> Cant actually see this because its remote from me - this is what the
Hi Michael,

As you know the E250 is pretty old and I'm sure, years ago, I
remembered that if the system didnt detect the monitor at boot time
then it was no use plugging in a monitor subsequently because it just
wouldnt work. In fact, I vaguely remember that plugging in a monitor
later sometimes crashed the system.

Lights I refer to are on the monitor. Yes there is keyboard attached.

Doug McIntyre

unread,
Aug 15, 2012, 9:02:06 AM8/15/12
to
"BertieB...@gmail.com" <bertieb...@gmail.com> writes:
>As you know the E250 is pretty old and I'm sure, years ago, I
>remembered that if the system didnt detect the monitor at boot time
>then it was no use plugging in a monitor subsequently because it just
>wouldnt work. In fact, I vaguely remember that plugging in a monitor
>later sometimes crashed the system.
>Lights I refer to are on the monitor. Yes there is keyboard attached.

There isn't anything in a Sun that detects if a *monitor* is attached or
not for directing output to a frame-buffer.

There is a detection in OBP for the *keyboard* is attached during boot
to use a frame-buffer vs. sending console output to /dev/ttya. If a
keyboard isn't detected, it could be that the frame-buffer won't get
any output.

So, double check your keyboard. See if it works on another system,
make sure it has a good connection, reconnect it. etc.

Otherwise, get a remote serial port from another Sun system,
(ie. hookup ttyb on that to ttya on this one), tip out (or whatever
serial comm program you like using), and watch what is going across
ttya as the system boot, if you see anything.

(I can't imagine with the noise an E250 puts out, even having a
frame-buffer in it and anybody doing any interaction with the beasts
in front of the actual thing. They always were far far away in the
data center running headless for me).

bertieb...@gmail.com

unread,
Aug 15, 2012, 12:41:12 PM8/15/12
to
On Aug 15, 2:02 pm, Doug McIntyre <mer...@geeks.org> wrote:
OK, interesting. Maybe Im getting confused - its been a while :-)

Im sure there were issues in the past with disconnecting/connecting
causing a reboot - maybe its the keyboard?
Better check I guess that there is keyboard attached.

Yes, they usually do sit in the data centre and usually telnet to. For
some reason my customer is having an issue because the monitor is not
working even though its just stuck in a cabinet in a computer room....

Doug McIntyre

unread,
Aug 15, 2012, 3:05:42 PM8/15/12
to
"BertieB...@gmail.com" <bertieb...@gmail.com> writes:
>On Aug 15, 2:02=A0pm, Doug McIntyre <mer...@geeks.org> wrote:
>> "BertieBigBol...@gmail.com" <bertiebigbol...@gmail.com> writes:
>> >As you know the E250 is pretty old and I'm sure, years ago, I
>> >remembered that if the system didnt detect the monitor at boot time
>> >then it was no use plugging in a monitor subsequently because it just
>> >wouldnt work. In fact, I vaguely remember that plugging in a monitor
>> >later sometimes crashed the system.
>> >Lights I refer to are on the monitor. Yes there is keyboard attached.
>>
>> There isn't anything in a Sun that detects if a *monitor* is attached or
>> not for directing output to a frame-buffer.
>>
>> There is a detection in OBP for the *keyboard* is attached during boot
>> to use a frame-buffer vs. sending console output to /dev/ttya. If a
>> keyboard isn't detected, it could be that the frame-buffer won't get
>> any output.

>Im sure there were issues in the past with disconnecting/connecting
>causing a reboot - maybe its the keyboard?
>Better check I guess that there is keyboard attached.

It is the keyboard. Traditionally, it is the STOP-A sequence that can
halt the Sun machines. This sequence can be sometimes triggered as
well sometimes just by unplugging the keyboard. On the serial console,
the equivilent is sending a serial break, which is really just an all-zeros
condition across the serial bus..


Michael

unread,
Aug 16, 2012, 5:51:03 AM8/16/12
to
Hi,
On 08/15/12 10:36 AM, BertieB...@gmail.com wrote:
> On Aug 14, 9:25 pm, Michael<michael_laaja...@yahoo.com> wrote:
>> Hi,
>>
>> On 08/14/12 06:17 PM, BertieBigBol...@gmail.com wrote:> Cant actually see this because its remote from me - this is what the
>>> people on site are reporting.
>>
>>> What I think has happened is that the server has been powered on and
>>> THEN the monitor has been connected.
>>
>> Don't know if I understand you correctly but the monitor should always
>> work regardless if it was connected or not.
>> Is there a keyboard attached to the E250?
>>
>>
>>
>>> I seem to vaguely remember with these that the monitor has be
>>> connected before powering on? Unfortunately, its not a simple case of
>>> powering off/on because of the app the servers are running (needs to
>>> be done properly)
>>
>> What lights are flashing? the running LED or service LED?
>>
>> /michael
>
> Hi Michael,
>
> As you know the E250 is pretty old and I'm sure, years ago, I
So are we, but we still do our jobs :)
> remembered that if the system didnt detect the monitor at boot time
> then it was no use plugging in a monitor subsequently because it just
> wouldnt work. In fact, I vaguely remember that plugging in a monitor
> later sometimes crashed the system.
>
> Lights I refer to are on the monitor. Yes there is keyboard attached.
Hmm, as other has written the keyboard is not hot plug and can crash and
even more a system. To be hotplug and not cause permanent damage a
device must first connect GND then power so the connection lines must be
with different lengt(GND longest)

If the monitor flashes and no readable text on the screen, I would think
of either monitor or the graphic adaper has gone south.

Can they test the monitor on a different system, what graphic adapter is
it? thinking of connector type the normal for a E250 is standard 15 pin
dsub.

Important is that the E250 and monitor is connected on the same AC
phase/connector otherwise they must not be hot connectec/disconnected
due to earth may be floating at a different level on different AC phases!!!

I once recieved a PDP11 that did not have any GND on the RS232 cable
that worked for the customer but in our side so we toasted the serial
board and this was one of my first projects (:


ChrisQ

unread,
Aug 20, 2012, 7:27:42 AM8/20/12
to
Not sure about the monitor, but typically, the keyboard must be plugged
in and detected at power up by obp, for the monitor to be used as the
output device.

The answer is to power down, check cables to keybaord and monitor, but also
that the obp eeprom settings are set to (check syntax)
output-device=screen and
input-device=keyboard. They occasionally get corrupted and on an old machine
like that, the eeprom battery, which maintains the eeprom settings, may be
dead or on it's last legs...

Regards,

Chris

bertieb...@gmail.com

unread,
Aug 21, 2012, 7:19:04 AM8/21/12
to
On Aug 16, 10:51 am, Michael <michael_laaja...@yahoo.com> wrote:
> Hi,
Sure connector type is standard? I always thought it was the 'Sun'
type?

I have asked them to test monitor on another system in the interim.
Got a guy going to site on saturday so I'll be speaking him then to
see whats what.



bertieb...@gmail.com

unread,
Aug 21, 2012, 8:58:36 AM8/21/12
to

> The answer is to power down, check cables to keybaord and monitor, but also
> that the obp eeprom settings are set to (check syntax)
> output-device=screen and
> input-device=keyboard. They occasionally get corrupted and on an old machine
> like that, the eeprom battery, which maintains the eeprom settings, may be
> dead or on it's last legs...
>
> Regards,
>
> Chris

thanks. Of course, if it is the eeprom settings, then the only way to
access these I guess is via console port?
Still waiting to hear back if its 2 machines or just 1 affected like
this.

If its 2 then my money is on user-stupidity by not having keyboard
connected because its too much of a coincidence for both machines to
go faulty at the same time.


ChrisQ

unread,
Aug 21, 2012, 9:10:22 AM8/21/12
to
On 08/21/12 12:58, BertieB...@gmail.com wrote:
>

>
> thanks. Of course, if it is the eeprom settings, then the only way to
> access these I guess is via console port?

If the system is up and you can run a shell, or telnet into the machine,
there's always the 'eeprom' command, which allows you to view and change
settings, much as you can from the obp prompt.

Iirc, this causes an immediate change and doesn't need a reboot, so you
need to change the screen first, then the keyboard, to avoid locking
yourself out of the machine with half the mode changes done :-)...

Regards,

Chris

bertieb...@gmail.com

unread,
Aug 21, 2012, 10:23:32 AM8/21/12
to
On Aug 21, 2:10 pm, ChrisQ <m...@devnull.com> wrote:
Chris - good point about the eeprom command. thanks. I can check this
remotely.

Michael

unread,
Aug 21, 2012, 12:58:26 PM8/21/12
to
Hi,
Depends, most E250 and all I have ever come across was headless or used
the very low end PGX32 or I think it even was one cheaper one.
The come PGX64.
PKG32 on out E450(2xE250) below from prtdiag -v

SYS PCI 33 10 TSI,gfxp GFXP


> I have asked them to test monitor on another system in the interim.
> Got a guy going to site on saturday so I'll be speaking him then to
> see whats what.
>
>
>
If the monitor is toasted then there is 13W3->15DSUB convertes and then
just get a standard LCD monitor.
http://www.amazon.com/Sun-13W3-M-HD15-F-Video-Adapter/dp/B001I27X5Y

it might be wise to get a new EEPROM soon because the E250 is never
going to die unless the battery gets bad or some disk dies :)

The issue with battery is that in only will be detected after a poweroff!

/michael
0 new messages