HP-UX console troubles....

[Jerad Clark]

Just an FYI -- the normal admins for this box are on vacation - hence my ignorance.... sorry.

We have the HP monitor console with HP keyboard hooked to our HP 9000 L class box.

My problem is that on the console screen I don't have a normal prompt, or output.

I only see exactly what I type, and no command I can think of causes it to display anything else.

I don't know why, or how to get things back to normal.

The machine was rebooted, yesterday by one of the admins before he went on vacation - but that didn't fix my issue.

anyone?
thanks.

[Michael Elleby III_1]

Jerad-

Try typing in 'stty sane' and press ENTER. Then press Ctrl-J

Another thing to try is to turn off the monitor, hold down the left shift key and turn the Console back on. This should reset the console back to normal.

Mike-

[Jerad Clark]

Mike -

I tired both solutions you offered. Nothing changed.

thanks though.

[Brian Bergstrand]

First, make sure the console is actually plugged in to the correct box and that the connection is solid on both ends (the server and the monitor). Is this a dumb terminal or an actual graphics monitor?

[Denver Osborn · Accepted solution]

Can you turn off the console, hold down the 'D' key when you power it back on. Release the 'D' key after about 5-10secs. It may say 'default configs used, press return to clear' -> press enter.

Do you have the console login now?

-denver

[Helen French]

I don't remember exactly, but in some of the old HP terminals there was a setting for repeating whatever you type on the KBD. Check for anything like "auto repeat" or "repeat" parameter in the terminal settings menu. If it's set to Yes, then put it back to No.

Also, some terminals will repeat the keyboard if you short input PINs 2 and 3. Make sure your cable is proper.

[Jerad Clark]

Brian - plugged in and good go - looks like a terminal screen.

Denver - This worked. I was able to log in and can now browse around the disk. Thanks for the info.

Does anyone know "where" I was, in case it happens again somehow?

[Michael Elleby III_1]

I'm glad you got it fixed, though I slapped myself upside my head when I read Denver's answer, because he was right on point.. Couldn't remember that one..

Mike-

[Bill Hassell]

HP terminals such as the 700/9x series have a number of settings and one of the settings is REMOTE MODE. Most likely the terminal was left with the function displaying REMOTE MODE on f4 and someone pressed it. This turns off the asterisk in REMOTE MODE and now the terminal just echos what you type--nothing is sent to the computer.

Holding the D key down when you power up the terminal will indeed get that setting back to normal but it does change a number of other settings to match MPE systems (the HP 3000). It is always a good idea to change the settings to be compatible with HP-UX (and other Unix flavors). Here's a quick reference on what to change to turn off the HP3000-specific features:

Press the USER/SYSTEM key between f4 and f5.
Press f5 MODES and make sure there is only ONE asterisk in all the function labels and that is: REMOTE MODE*
(for troubleshooting, the f7 DISPLAY FUNCTNS asterisk will show all characters oncluding LF CR, etc)
Press the USER/SYSTEM key again and then press f8, the CONFIG KEYS.
Press f5 TERMINAL CONFIG, then tab to the InhHndShk(G) field in the middle of the page. Change it to YES, using f2 NEXT CHOICE then tab to Inh DC2(H) and also change it to YES. Tab to the last field on the page TermMode. Here you can leave it as HP or change it to EM220 (best results) EM100 (less useful) or EM52 (least useful). The EM settings refer to vt220, vt100 and vt52 emulation modes. The choice depends on whether you have a new HP9000 with a GSP and the GSP has been set to vt100 or HP.

[Jerad Clark]

Mike - I hope you didn't slap too hard, you obviously know more than I do about this :)

Bill - Good info / explanation. Thanks.

[Jerad Clark]

Bill - Just an FYI. You have a small typo, at least for my machine.

For me I press F4 to get to MODES, not F5.

Everything else was fine, I set it to all your recommended settings.

Thanks again.

[Bill Hassell]

Sorry about the typo...I was doing it from memory. You probably know that sysadmin memory is highly volatile and needs continuous refreshing. ;-)