L-class console works in upper case

[Mihails Nikitins]

Hi,

Two of my L-classes perodically have problems with getty process (probably) on console.

Sometimes, the whole terminal screen shows everything in upper case, as well as converts any input to upper case.

Example.

LOGIN: ROOT
\PASSWORD:
\LOGIN INCORRECT

If you have an account with password where all characters are in lower case, you can log in. Everything will be treated as lower case in spite of displaying in upper case. You can type 'LOGOUT' and the line will reset to normal operation.

Example.


LOGIN: USER
\PASSWORD: *******
HOST>LOGOUT
LOGOUT USER
login:

Question: do you know how to prevent the bug?
Sometimes it may be critical if you can become root only on your console.

Thank you in advance!

BR,
Mihails

[K.Vijayaragavan.]

I Think you are using character bassed terminal console.

If that is the case, if any body tries to login with upper case on then it will happen.
that case i used to switch off the terminal and switch it on back to get the login screen and log in with lower case on.

check the /etc/gettydefs file
check the /etc/inittab file
check the terminal CMOS (firmware) setup.

-Vijay

[Pete Devlin · Accepted solution]

At the LOGIN prompt leave blank & type ctrl d, If I've understood correctly that should fixyour problem !

Cheers
Pete.

[Sanjay_6]

Hi Mihails,

In situations where you get the LOGIN prompt in uppercase on the console at the login prompt type "cntrl+d" and it should return with the lowercase login prompt.

Hope this helps.

Regds

[Mihails Nikitins]

Thanks a lot for Ctrl+D, it works!!! Could you please decscribe what happens when sending this sequence? Does it reset getty process?

BR,
Mihails

[Sanjay_6]

Hi Mihails,

I'm not so sure, but i believe cntrl+d will send a process kill sequence, something like a logout and this will in effect restart the getty process. To check this, do a ps -ef |grep console when the "LOGIN" prompt is displayed on console and note down the process no, Do a "cntrl+d" and then check the process id once again. I believe the process id should be different.

Hope this helps.

Regds