EFI console gets to Shell> prompt and loops.

[Brian Schenkenberger]

Help. I shutdown my rx3600 to reboot and now when the EFI gets to the Shell> prompt, is loops ad infinitum. If I'm lucky, I can type CTRL-B and get back to the MP menu.

Who do I correct this???

[Antoniov.]

What does it means "loops ad infinitum"?
I guess you see continously Shell prompt like RETURN is pressed.

Antonio Vigliotti

[Brian Schenkenberger]

Exactly

[Antoniov.]

Brian,
sorry, but are you sure your keyboard is working fine?
How do you connect your rx3600 and console? Via PC and HyperTerm or esle with any VT terminal?
Which cable?

Antonio Vigliotti

[Brian Schenkenberger]

Same cabling/connection I've been using for months.
I can get to the MP menu and, for example, enter CM and at the CM> prompt enter command like PC -on/-off. It is only when I go to the COnsole that I have any issue. I can see everything startup as it normally does and then it drops to the Shell> and it's loop-de-loop. I can usually type a CTRL-B and get back to the MP menu. I can tell you that there is no problem with my keyboard. It works flawlessly in other DECterm window and when I connect to other hardware. ...and, FWIW, I don't have this problem with I connect (with the same mechanism) to the other rx2600.

Tomorrow, I'm taking the box out of the rack to see what may be avail inside to diddled to reset this thing.

[Antoniov.]

Mhm,
it's weird. It appear as autobaud feature. Enter is the ASCII code send to synchronize two serial devices.

Antonio Vigliotti

[Brian Schenkenberger]

ASCII code to sync? Can you please elaborate?

[Ted Buis]

Can you pause the boot process and enter the EFI shell, or go to boot maintenance?

[Antoniov.]

Brian,
autobaud, you know, is a feature used by serial devices to set the same speed.
Synchronizing is based on start bit and on recognition of CR.
You can try to disable autobaud on your terminal and set 9600,N,8,1.

Antonio Vigliotti

[Weatherman_1]

You weren't shutting down after a firmware upgrade, were you? Your problem sounds very similar to one I just had with a 4640. I ended up talking to HP support and they sent a tech out to replace the system board based on the log file info I sent them. This did correct the problem.