Fresh 4.3.3 Install Hangs After rpc.lockd subsystem

[zookcruiser]

I'm an AIX newbie trying to do a fresh install of 4.3.3 onto a model 7025-F40. The install process completes without error, but the system hangs during the boot process immediately after the rpc.lockd subsystem starts. I'm using a PC running Procomm attached to the first serial port as the system console. There are no graphics adapters installed. I also tried version 4.3.2 and got the same result. Any help would be greatly appreciated.

 

[nick2004]

Have you set the speed to 9600?

 

[MoshiachNow]

What do you mean exactly by "system hangs" ?
Any number on the LCD display ? "Long live king Moshiach !"
h

http://www.noahide.com/movement.htm

 

[zookcruiser]

Yes, I have the speed set to 9600. The console seems to communicate just fine. I get all the normal messages during the boot process about all the services and subsystems that are starting up along with their process id's. The last message displayed is about starting the rpc.lockd subsystem.

What I mean by "hangs" is there is no further activity and I'm not able to do anything. It's at the point where I would expect a login prompt to appear. There is no code displayed on the LCD.

I thought about trying to login through the network via telnet, but since I've never successfully booted up, I don't have an IP address assigned. Can I do that in service mode?

 

[MoshiachNow]

I think that your problem is in the networking area,but not with the missing IP assignment.

I would try to replace the network adapter first. "Long live king Moshiach !"
h

http://www.noahide.com/movement.htm

 

[GFitzG]

I would replace the cable. Experience has shown that AIX console messages etc. work ok if you have an incorrectly configured cable (e.g. with just Tx, Rx and Gnd). Although this may be good enough to get your through the install - it may not be adequate for "getty" - i.e. as soon as it tries to launch the RS232 console login it realises that not all the correct RS232 signals are present - and nothing else is displayed...

I plump for trying a pucker cable before tinkering with adapters or internal hardware.

 

[zookcruiser]

levw, I considered replacing the network adapter, but since it's integrated into the planar, that's not a possibility.

GFitzG gets the gold star. I lugged a "known working" 3153 terminal into my office, connected it to the F40 and it boots up just fine. I had the PC connected using a laplink cable. I assumed that since the terminal worked during the install process that everything was ok. Thanks for your help. This site is terrific.