IBM AIX console pseries

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.

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

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

------------------------------------------

After rebooting the machine, system always goes to
SERVICE PROCESSOR FIRMWARE menu

select option #3 System Information Menu
#3 Read Service Processor Error Logs
press C to clear all error log

shutdown the system from the menu
remove the power cable -- wait 2 minutes -- plug in the power cable
start the system, should be working

I have few questions:

1- Do I need to have the console connected during the boot process ?

2- The console previously was graphics card LFT0 and now changed to TTY0


/>lscfg
  Model Architecture: chrp
  Model Implementation: Multiple Processor, PCI bus


+ lai1             U0.1-P1-I1/G1                                   GXT135P Graphics Adapter
* siokma0          U0.1-P1-X1/K1                                   Keyboard/Mouse Adapter
+ sioka0           U0.1-P1-X1/K1                                   Keyboard Adapter
+ kbd0             U0.1-P1-X1/K1-K1                                PS/2 keyboard
+ sioma0           U0.1-P1-X1/K1                                   Mouse Adapter
+ mouse1           U0.1-P1-X1/O1-O1                                2 button mouse
+ sa0              U0.1-P1-X1/S1                                   Standard I/O Serial Port
+ tty0             U0.1-P1-X1/S1-L0                                Asynchronous Terminal
+ sa1              U0.1-P1-X1/S2                                   Standard I/O Serial Port
+ tty1             U0.1-P1-X1/S2-L0                                Asynchronous Terminal
+ sa2              U0.1-P1-X1/S3                                   Standard I/O Serial Port
+ tty2             U0.1-P1-X1/S3-L0                                Asynchronous Terminal
+ mem0                                                             Memory
+ proc0            U0.1-P1                                         Processor
+ proc1            U0.1-P1                                         Processor


----------

/>lscons -b
/dev/tty0

/>lscons -d
/dev/tty0

/>lscons
/dev/tty0



Type or select values in entry fields.
Press Enter AFTER making all desired changes.

                                                        [Entry Fields]
  PATHNAME of console                                [/dev/lft0]                                                                 +
  Enable for LOGIN                                    yes                                                                        +
  PATHNAME of console LOG FILE                       [/var/adm/ras/conslog]                                                      +
  SIZE of console LOG FILE                           [32768]                                                                     +
  Console log VERBOSITY                              [1]                                                                         +#
  Console tag VERBOSITY                              [0]      
 COMMAND STATUS

Command: failed        stdout: yes           stderr: no

Before command completion, additional instructions may appear below.

0514-418 chcons: Console login cannot be enabled because the console device
                 is not an available lft or tty.

----
/>lsdev -C

gxme0      Defined                 Graphics Data Transfer Assist Subsystem


lai0       Defined   1a-00         GXT135P Graphics Adapter
lai1       Defined   1a-08         GXT135P Graphics Adapter
lft0       Defined                 Low Function Terminal Subsystem

lvdd       Available               LVM Device Driver

pty0       Available               Asynchronous Pseudo-Terminal
tty0       Available 01-S1-00-00   Asynchronous Terminal
tty1       Available 01-S2-00-00   Asynchronous Terminal
tty2       Available 01-S3-00-00   Asynchronous Terminal

---
/>cfgmgr
Method error (/usr/lib/methods/cfg_lai -l lai1 ):
        0514-040 Error initializing a device into the kernel.
Method error (/etc/methods/cfglft -l lft0 ):
        0514-032 Cannot perform the requested function because the
                 specified device is dependent on another device which does
                 not exist.


3- Looks like the graphic card is not working or undefined ?

/> errpt
---------------------------------------------------------------------------
LABEL:		GRAPHICS_ADAPTER_ER
IDENTIFIER:	2CCF66F7

Date/Time:     
Sequence Number: 171441
Machine Id:      0059C87D4C00
Node Id:         ora
Class:           H
Type:            TEMP
Resource Name:   lanaidd         
Resource Class:  NONE
Resource Type:   NONE
Location:        

Description
DEVICE ERROR

Probable Causes
ADAPTER

Failure Causes
ADAPTER
SOFTWARE DEVICE DRIVER

	Recommended Actions
	VERIFY ADAPTER IS INSTALLED PROPERLY
	RUN DIAGNOSTICS AGAINST THE FAILING DEVICE
	IF PROBLEM PERSISTS THEN DO THE FOLLOWING
	REPLACE CARD

Detail Data
DETECTED   FAILED    RC   ERROR
       lanai_init    -1    01    0 0 0
LABEL:		SRC_TRYX
IDENTIFIER:	1BA7DF4E

Date/Time:        
Sequence Number: 171434
Machine Id:      0059C87D4C00
Node Id:         oradb
Class:           S
Type:            PERM
Resource Name:   SRC             

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

	Recommended Actions
	DETERMINE WHY SUBSYSTEM CANNOT RESTART

Detail Data
SYMPTOM CODE
         256
SOFTWARE ERROR CODE
       -9020
ERROR CODE
           0
DETECTING MODULE
'srchevn.c'@line:'343'
FAILING MODULE
clsmuxpdES
---------------------------------------------------------------------------
LABEL:		SRC_RSTRT
IDENTIFIER:	BA431EB7

Date/Time:        
Sequence Number: 171433
Machine Id:      0059C87D4C00
Node Id:         oradb
Class:           S
Type:            PERM
Resource Name:   SRC             

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

	Recommended Actions
	VERIFY SUBSYSTEM RESTARTED AUTOMATICALLY

Detail Data
SYMPTOM CODE
         256
SOFTWARE ERROR CODE
       -9035
ERROR CODE
           0
DETECTING MODULE
'srchevn.c'@line:'217'
FAILING MODULE
clsmuxpdES
---------------------------------------------------------------------------
LABEL:		SRC_RSTRT
IDENTIFIER:	BA431EB7

Date/Time:        
Sequence Number: 171432
Machine Id:      0059C87D4C00
Node Id:         oradb
Class:           S
Type:            PERM
Resource Name:   SRC             

Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

	Recommended Actions
	VERIFY SUBSYSTEM RESTARTED AUTOMATICALLY

Detail Data
SYMPTOM CODE
         256
SOFTWARE ERROR CODE
       -9035
ERROR CODE
           0
DETECTING MODULE
'srchevn.c'@line:'217'
FAILING MODULE
clsmuxpdES
---------------------------------------------------------------------------
LABEL:		GS_START_ST
IDENTIFIER:	AFA89905

Date/Time:        
Sequence Number: 171431
Machine Id:      0059C87D4C00
Node Id:         ora
Class:           O
Type:            INFO
Resource Name:   grpsvcs         

Description
Group Services daemon started

Probable Causes
Daemon started during system startup
Daemon re-started automatically by SRC
Daemon started during installation
Daemon started manually by user

User Causes
Daemon started manually by user

	Recommended Actions
	Check that Group Services daemon is running

Detail Data
DETECTING MODULE
RSCT,pgsd.C,1.54,554                          
ERROR ID 
63Y7ej0LEbVQ/Xr/.C2E.8....................
REFERENCE CODE
                                          
DIAGNOSTIC EXPLANATION
HAGS daemon started by SRC. Log file is /var/ha/log/grpsvcs_2_148.aix.
---------------------------------------------------------------------------
LABEL:		TS_START_ST
IDENTIFIER:	97419D60

Date/Time:       
Sequence Number: 171430
Machine Id:      0059C87D4C00
Node Id:         ora
Class:           O
Type:            INFO
Resource Name:   topsvcs         

Description
Topology Services daemon started

Probable Causes
Daemon started during system start-up
Daemon re-started automatically by SRC
Daemon started during installation
Daemon started manually by user

User Causes
Daemon started manually by user

	Recommended Actions
	Confirm that this is desirable

Detail Data
DETECTING MODULE
rsct,bootstrp.C,1.184,4129                    
ERROR ID 
6UpNEL0IEbVQ/EH01C2E.8....................
REFERENCE CODE
                                          
Topology Services daemon started by:
SRC
Topology Services daemon log file location
/var/ha/log/topsvcs.11.174332.aix.ar_AA
Topology Services daemon run directory
/var/ha/run/topsvcs.aix/
---------------------------------------------------------------------------
LABEL:		RMCD_INFO_0_ST
IDENTIFIER:	A6DF45AA

Date/Time:        
Sequence Number: 171429
Machine Id:      0059C87D4C00
Node Id:         ora
Class:           O
Type:            INFO
Resource Name:   RMCdaemon       

Description
The daemon is started.

Probable Causes
The Resource Monitoring and Control daemon has been started.

User Causes
The startsrc -s ctrmc command has been executed or
the rmcctrl -s command has been executed.

	Recommended Actions
	Confirm that the daemon should be started.

Detail Data
DETECTING MODULE
RSCT,rmcd.c,1.46,209                          
ERROR ID 
6eKora0J0bVQ/QFE/C2E.8....................
REFERENCE CODE
                                          
LABEL:		SCANOUT
IDENTIFIER:	CF8CADB6

Date/Time:       
Sequence Number: 171427
Machine Id:      0059C87D4C00
Node Id:         localhost
Class:           H
Type:            PERM
Resource Name:   sysplanar0      
Resource Class:  planar
Resource Type:   sysplanar_rspc
Location:        

Description
SYSTEM FAILURE WITH SCAN DATA

Probable Causes
SYSTEM HARDWARE
SOFTWARE ERROR

Failure Causes
SYSTEM HARDWARE
SOFTWARE SUBSYSTEM

	Recommended Actions
	PERFORM PROBLEM DETERMINATION PROCEDURES
	IF PROBLEM CONTINUES TO OCCUR REPEATEDLY THEN DO THE FOLLOWING
	CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
ERROR COUNT
           1
SCAN DATA PATHNAME
/var/adm/ras/platform/scanoutlog.0059C87D4C00.B


Any clues how to know to know if the problem is with

  • Graphics Card LFT0
  • how to reset the graphics card ?

May be something to do with the graphics card

Machine Serial Number: 659C87D
Processor Type: PowerPC_POWER4
Number Of Processors: 2
Processor Clock Speed: 1200 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 NULL
Memory Size: 16384 MB
Good Memory Size: 16384 MB
Firmware Version: IBM,RG040325_d75e04_s
Console Login: enable
Auto Restart: true
Full Core: false


Name:  display
    Node:  display@1
    Physical Location: U0.1-P1-I1/G1

      GXT135P A/D 2D Graphics Adapter:
        EC Level....................H13284
        FRU Number..................00P5758
        Manufacture ID..............MATROX
        Part Number.................80P4527
        System Info Specific.(YL)...U0.1-P1-I1/G1




A PROBLEM WAS DETECTED ON  �-'�-'�-'�-'�-'�-'�-' 25 �-'�-'�-'�-' 22:41:25 2019                                                                                     801014

The Service Request Number(s)/Probable Cause(s)
(causes are listed in descending order of probability):

  802-67E: A resource was not detected that was previously installed.
    lai0             FRU: 00P5758              U0.1-P1-I1/G1
                     GXT135P Graphics Adapter
    pci7             FRU: n/a                  U0.1-P1-I1
                     PCI Bus

  803-67E: A software error was encountered while running the Diagnostic
           Application on lai1.

Use Enter to continue.


root@oradb:/backup>lscfg -vp | grep Graphics
  lai1             U0.1-P1-I1/G1                                   GXT135P Graphics Adapter
      GXT135P A/D 2D Graphics Adapter:



 lai0             U0.1-P1-I1/G1        GXT135P Graphics Adapter
  lai1             U0.1-P1-I1/G1        GXT135P Graphics Adapter


root@oradb:/backup>lsdev -Cs pci
ent0      Available 1L-08 10/100 Mbps Ethernet PCI Adapter II (1410ff01)
ent1      Available 1j-08 10/100/1000 Base-TX PCI-X Adapter (14106902)
fcs0      Available 1H-08 FC Adapter
fcs1      Available 1n-08 FC Adapter
ide0      Available 1G-19 ATA/IDE Controller Device
isa0      Available 1G-18 ISA Bus
lai0      Defined   1a-00 GXT135P Graphics Adapter
lai1      Defined   1a-08 GXT135P Graphics Adapter
pci2      Available 1G-10 PCI Bus
pci3      Available 1G-12 PCI Bus
pci4      Available 1G-14 PCI Bus
pci5      Available 1G-16 PCI Bus
pci6      Available 1Y-10 PCI Bus
pci7      Available 1Z-08 PCI Bus
pci8      Available 1Y-12 PCI Bus
pci9      Available 1Y-13 PCI Bus
pci10     Available 1Y-14 PCI Bus
pci11     Available 1Y-16 PCI Bus
sisscsia0 Available 1S-08 PCI-X Dual Channel Ultra320 SCSI Adapter
sisscsia1 Available 1V-08 PCI-X Dual Channel Ultra320 SCSI Adapter

No. A "console" in UNIX speech is just a terminal, save for that it is attached directly (no network in between) to the system. One common security feature is to allow root to directly login only through the console, so that logging in directly as root needs a physical access to the system in question. So, the console is like the "main" terminal, but in every other regard it is just like any other terminal.

Well, look here:

The graphics adapters that were there once are simply not there any more. Either they are both broken and the system cannot configure them even so much that they are recognized (one might have become dysfunctional that way but two at the same time is improbable) or they have been removed from the system. Delete these devices ( rmdev ) and run cfgmgr and i suppose they will not resurface. "Defined" means the defiitions for the adapter are still in the ODM but the device isn't there any more. It it would be then it would be "available".

This seems to be a rather old hardware (i remember having two GXT135P adapters in a R/6000 Model 43P-140), so it should have a serial connector. Attach a serial console to it and start with that. Note that at some point (i don't remember exactly when) the serial characteristics went from 9600, 8,1,N to 19200, 8,1,N, so if you have no luck with 9600 baud try 19200.

I hope this helps.

bakunin