I got very quick and vast solution. thank everyone .
Almost all response point to the command :
$ /usr/openwin/bin/kbd_mode -a
or
$ /usr/openwin/bin/kbd_mode -a > /dev/console
this will put the console back into ASCII mode.
and another solution is remote login to this mechine , load openwin, and
quit. this
will reset the keyboard.
other suggestion:
Try to run the following command as root:
/usr/lib/saf/ttymon -g -h -p "`uname -n` console login: " -T sun
-d /dev/console -l console -m ldterm,ttcompat
[likun] I have tried this solution , but failed.
THE cause:
[Umesh Chandra Singhal ] this typically happens due to X process killing.
[Casper Dik ] This only happens when openwin crashes, so perhaps you need to
update your patches )Or run CDE and it will never happen)
[Tim Pointing ] The problem with your keyboard producing strange characters
was, as you mentioned caused by your server exiting improperly. The keyword
device driver was left in a state whereby it produces X Window events for
key
presses, rather than ASCII characters.
[Russ Poffenberger] When the X server starts, it changes the mode of the
keyboard from outputting ASCII characters, to outputting keycodes. The
server
uses keycodes so it has more flexibility in customizing the layout. If the
server
crashes, it is possible that the keyboard is not reset.
[Eugene Kramer] Looks like your Openwin did not reset keyboard back to its
normal
condition. You can try to use /usr/openwin/bin/kbd_mode -a (telnet to
the host first)
[Mark Cain] The most likely thing is that the keyboard translation mode is
left set for
openwindows rather than having been reset to ascii by a normal exit from
Xsun.
The other possibility (although as I recall, in this case you don't get
anything echoed) is for a process to leave the terminal in "raw" mode.
In this case, try sending a "new line" using ^U^J to clear out any input,
then
type blindly (since it won't be echoing) "stty sane^J" to get back to
a usable stty mode.
[Jos¨¦ Gregorio Escalada] the problem is openwindows not ending
properly, leaving the keyboard mode incorrect.
[lan] This is caused by an application run from the desktop hanging
[<usivha01] It may be due to termination of X-server. So the server thinks
that the mode is now in X-mode.
the origial question belowed
====================
several days ago , one of my server quit from openwin suddenly, back to the
>console
>login prompt , and whatever character i enter , it print a lots garbage
,
>like
>"@@@@@@@@@", or something similar, ^C or ^D could do nothing good.
>what i can do is to reboot this mechine.
>
>Is there anyone know why I got these garbage , such as which daemon
>malfunction ,
>and what could i do to prevent from rebooting the mechine ?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=
my->name = "likun";
my->email[0] = "likun@bjaimail.asiainfo.com";
my->email[1] = "likun@bjai.asiainfo.com";
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:48 CDT