Hi,
I am trying to bring up linux on a ATCA blade (Intel Xeon based Dual core processor) using initrd support with std. linux kernel -2.4.20-8.
The lilo.conf entry is:
image=/boot/vmlinuz
label=Std2.4
initrd=/boot/initrd.img
read-only
append="init=/sbin/init root=/dev/ram ramdisk=131072 rw "

The inittab file under /etc/ (within initrd):

id:3:initdefault:

# System initialization.
si::sysinit:/etc/init.d/rcS

10:0:wait:/etc/init.d/rc 0
11:1:wait:/etc/init.d/rc 1
12:2:wait:/etc/init.d/rc 2
13:3:wait:/etc/init.d/rc 3
14:4:wait:/etc/init.d/rc 4
15:5:wait:/etc/init.d/rc 5

# This line provides a nice out-of-box experience. For regular use, you
# should replace it with the proper getty lines below.
con:12345:respawn:/sbin/agetty console 115200

The kernel boots and shows up the login prompt asking for user name. As sooon as enter the user name (say root) and press enter, the login program does not prompt for password; instead shows the login prompt again asking for login name.
I have included the pam.d/ and passwd file under /etc/ (within initrd) needed by login.
The /sbin/agetty (used in the initrd image)binary when used on the same blade (which is booted with 2.6 kernel) will come up with the login name and then prompts for passwd as well. It passed the login when provided with correct credentials.

Any idea why this could happen?

Regards,
Kris