Prime 2550, part 2

The 2550 has been running fine since this group helped me revive it
last summer. Well, recently I left it running overnight and the next
day it was down. I traced the 2550's problem to the 15 amp slow-blow
fuse on the CPU power supply. I don't know what caused it to blow but
there was a fair amount of corrosion (no, not rust) on one end of the
fuse. Perhaps it has been building up over the years and caused a poor
and hot connection.

The system console I was using is also dead. Since both went down
overnight, maybe there was a common cause: a problem in the power
coming from the street or, since they were on the same circuit, one
caused the other to go down. Although probably only a remote
possiblility, maybe they co-incidentally went down overnight for
different reasons.

Anyway, for the moment, I don't really care. I still have a problem
with the 2550. Although the AMLC board is up and echoing characters
and logins typed at it, there is no response to the login command and
the login doesn't seem to occur. The system console does not respond
at all. The CP> mode prompt works fine: I can communicate with it,
switch between the CP> prompt and ST mode, stop the system and boot
the system using it. However, during boot, immediately after the
"DPM007: System booting, please wait." message, I get no response from
the console displaying PRIMOS.COMI output as I would normally expect.
However, I can hear the usual disk activity that I would expect and
the boot and the system seem to proceed just fine. It seems that there
is a communication problem between the CPU & the console/AMLC board.

When I first re-installed the PS, reconnected everything and attempted
to bring the 2550 back up, I had forgot to plug the system fan into
the power supply. The entire boot process completed, still without
PRIMOS.COMI output going to the console. Immediately after the boot,
there was a sensor error detected which caused a forced shutdown. I
reconnected the fan and again booted which proceeded as described
above.

Could I have disconnected something while removing and reinstalling
the power supply? I did dress cables some and there are some cables
inside the chasis that are disconnected but I think they had been
disconnected before these problems. Did something fail due to
overheating during the short time it was first up? What else could it
be?
.

Relevant Pages

  • Re: New HDD Installation
    ... Incidentally I think that the reason that the disc doesn't want to boot is because it doesn't have a proper Master Boot Record, it wasn't done by the cloning operation. ... If running the commands doesn't fix the problem then you can use the F10 option to install Windows and do an In-Place Upgrade, or what is more commonly called a "Repair Install". ... The results of our earlier test in the Disk Management console were not conclusive, was the option to do so there but simply unavailable or did you not see any option to do so at all? ...
    (microsoft.public.windowsxp.general)
  • Re: 6.2 Headless Installs Dont Seem to Work.
    ... instead of "boot -h". ... video console mode, completely ignoring the directive. ... Serial Console", which explains the -h and -D flags, the ... the serial port will become the console at the same time, ...
    (freebsd-questions)
  • Re: Yet more display troubles with 2.6.15-rc5-mm2
    ... >> If I boot with vga=normal, ... >> garbled graphics mode screeen with either what looks like just random ... >> then start it again (the garbled text mode console does work, ...
    (Linux-Kernel)
  • Re: [patch 2.6.28-rc2] atmel_serial: keep clock off when its not needed
    ... The other UARTs' clocks again behaved correctly during normal ... Not for the oddball case Haavard mentioned, no: the console port ... the early boot messages in any case. ... and worry about that issue later. ...
    (Linux-Kernel)
  • Re: I am sick of windows firewall
    ... Suppose I am offline overnight. ... I wake up in the ... morning, do my daily chores, and then boot the system and go on ...
    (comp.security.firewalls)