Hi,
when I boot I get an E1DC error code. I've looked it up and it says that this error occurs during the firmware check. But the error is called "Dynamic Console Selection" .
1- Machine stopped at LCD led display = E1DC = CA00E1DC
E1DC Dynamic console selection. (maybe cable or keyboard)
Corrected hang at Firmware Checkpoint E1DC when processors numbered 0, 1, 2, 3, 4 and 5 are all deconfigured at the same time.
Quote:
E1DC Description: Dynamic console selection.
Action/Possibly Failing FRU
1. If a console is attached, but nothing is displayed on it, go to All display problems in
the Entry MAP.
2. If selection screens can be seen on the terminals and the appropriate key on the
input device is pressed within 60 seconds but there is no response to the keystroke:
a. If selecting the console with a keyboard attached to the system, replace the
keyboard, then replace the CEC backplane, Location: U0.1-P1.
b. If selecting the console with an ASCII terminal, suspect the terminal. Use the
problem determination procedures for the terminal.
Note: Terminal setting should be:
v 9600 baud
v no parity
v 8 data bits
v 1 stop bit
IBM Knowledge Center Error
CA00E1DC
Explanation
On a Linux or AIX system or partition, the partition firmware (the System Management Services, or SMS) is waiting for a firmware console to be selected. If the system is managed by a management console, open a VTERM and select it as the console. If the system is not managed by a management console, insure that a console is attached, then select that console when prompted.
Response
No repair action steps prior to working the failing item list.
Problem determination
No additional problem determination.
Look here for information about FWCONS symbolic FRU.
Perform the following.
If your server has an attached console, but the console display is not working, go to one of the following:
All display problems in AIX® server or AIX partition symptoms
All display problems in Linux® server or Linux partition symptoms
If you can see selection screens on the terminals, press the appropriate key on the input device within 60 seconds. If the console does not respond to the keystroke:
If you are selecting the console with a keyboard attached to the system, replace the keyboard, then replace the service processor (see Finding part locations).
If you are selecting the console with an ASCII terminal, suspect the terminal. Use the problem determination procedures for the terminal.
Note
The ASCII terminal settings should be: (**NOTE THE BELOW DID NOT WORK**)
19,200 baud
No parity
8 data bits
1 stop bit
----
After a period of time, the older machines will either display a series of icons
depicting keyboard, memory, network, SCSI, and speaker on the graphical
screen. As the speaker icon appears, if the machine has a speaker, it will emit a
beep. If you are using an ASCI console or graphical screen on newer PCI
machines, from IBM ^ pSeries 620 (7025 F80), instead of seeing
graphical icons, you will see the words keyboard, memory, network, SCSI, and
speaker. Throughout the rest of this redbook, this startup screen will be referred
to as the PCI icons screen.
For example, the IBM ^ pSeries 620 (7025 F80) boot sequence starts
with OK shown in the screen. Pressing the power on button causes the power
LED to flash; 20 seconds later, the fans start and the power LED comes on solid.
9xxx codes appear in the screen, these change to Exxx with location codes
appearing on the second LED row. When E1DC appears, the LFT display is
turned on. Very soon afterwards, E1F1 appears, and the PCI icons screen
appears on the display and the speaker sounds.
Before the speaker icon or word appears, a keyboard response must be received
if you want to do anything other than boot the machine in Normal mode.
Note: If you are using an LFT graphics display, you may miss the icons
screen while the display is warming up. You must press the required key
before the speaker icon or word appears or the machine will start a normal
boot and you will have to shutdown and start again.
|
Doing a google search:
[quote]
The solution to that (and perhaps your problem) is to remove the battery
from the F50 for at least 20 minutes, put it back again, and reboot the
F50. The NVRAM will clear, and get rebuilt on reboot.
--------
Once this problem occurs, the only way to correct the condition is to power
the system off, unplug the battery for approximately 10 minutes, plug in the
battery and power the system back on.
--------------
the E1DC step is the point where the display console is
determined, and the E1F1 step is where the prompts appear on the
display console. Since you see nothing on your graphics display at
this point, it would appear that the first serial port is set as your
display console (system console). There are two simple approaches you
can follow at this point:
(1) Hook up a serial terminal (or a PC emulating a serial terminal) to
the first serial port. A "LapLink" or "Serial Data Transfer" cable is
a good choice to make the connection, since each end of the cable has
both 9-pin and 25-pin connectors, and the "null modem" wiring
configuration is correct for the RS/6000. IBM 3151 emulation would be
ideal, but the more common VT52/VT100 emulation will work almost as
well -- it's more than adequate for the task at hand. Boot up the 43P
and when E1DC appears, start tapping on the "1" key of your "serial
terminal". When you get the menu, pick Utilities (3), then pick Select
Console (7). A prompt should appear on both the "serial terminal" and
your graphics display, hit the key that appears on the graphics display
on your PS/2 keyboard, and the system will restart. When you reach the
E1DC/E1F1 step this time around, press F1 on your PS/2 keyboard and
you'll be able to set up to boot from CD.
(2) With the power cord unplugged, remove the backup battery from it's
holder, and leave it removed for 15-20 minutes. Put everything back
and boot the 43P, at the E1DC step you should get the display prompt on
your graphics display, and you would proceed as I described in the
previous paragraph. *HOWEVER*, there have been reports of 43Ps going a
bit "crazy" when the backup battery has been removed, and sometimes it
is difficult to get the system back into an operational state once this
has been done. If you are someone who always seems to have "bad luck",
I'd recommend using the serial terminal approach -- it takes longer to
set up, but it's "safer".
----
then: goes to : 40670ea0 = 4067 0EA0
Quote:
0EA0 MOPS service processor code error. 1. Check for system firmware updates.
|
Solution:
1- Did a battery reset
2- Powered on the system
3- connected via Serial Null Modem Cable at port T1
v 9600 baud
v no parity
v 8 data bits
v 1 stop bit
4- When the machine is booting, you should see some garbled up text on the Putty Terminal
5- admin / admin
6- Clear all logs
7- power down and power up
8- should be working
