SUMMARY: Keyboard Problem

From: Slamet Fadilah <slamet.fadilah_at_gsm-siemens.co.ma>
Date: Wed Jun 27 2001 - 13:34:46 EDT
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0FF2F.7592B590
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> Subject: Keyboard Problem

PROBLEM :
> -----Original Message-----
> One of my SUN Ultra 10 always get a trouble with its keyboard.
> In the middle of an application, suddenly the keyboard hang,
> (the machine is alive, mouse working fine, but no input from =
keyboard)
> and to recover, it needs to logout and re-logon.
> It seems something wrong to do with login profile.

I got some suggestions as follow (I haven=B4t tested it yet, but I =
will),

-1. Eyal Edri > ...try to disable the NUM LOCK. some Xwindows on =
several sun
station got stuck , until we figured it was the num lock pressed .=20

-2. Mike Salehi > ...try kbd -r

-3. Richard J. Buchman > ...telnet back to the affected system, try a
keyboard reset to see if that breaks the lock.

-4. Dave Ballesteros > ...check the setting of hme0 port and compare it =
to
its server.
(his original message) : May not be your problem, but I recently ran =
into a
problem where the network
switch that was connected to the hme0 port on one of our servers was =
set to
autonegotiate 100/Full, and my hme0 port was set to 100/Full.  I was =
getting
periodic console messages (and the network engineer confirmed his logs =
were
getting messages as well) indicating my hme0 port link had gone down,
followed quickly by messages saying hme0 had been re-established.  When =
this
occurred, if I was in a session at the time, I could not key anything =
in
from the keyboard. I ended up having to close the xterm session, start
another session and login again.  We asked the network folks to lock =
the
switch at 100/full instead of using autonegotiate to resolve this =
problem.

-5. Farzad Hejazi > ...sometimes a combination of the CONTROL key and
another key can cause this situation.=20


Thanks a lot.

Slamet


Best Regards,
slamet FADILAH

TAC2OMCBSS, siemens mobile, casablanca
slamet.fadilah@gsm-siemens.co.ma

------_=_NextPart_001_01C0FF2F.7592B590
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>SUMMARY: Keyboard Problem</TITLE>
</HEAD>
<BODY>

<P><B><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; Subject:</FONT><FONT SIZE=3D2 =
FACE=3D"Tahoma"></FONT></B> <FONT SIZE=3D2 FACE=3D"Tahoma">Keyboard =
Problem</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">PROBLEM :</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; One of my SUN Ultra 10 always =
get a trouble with its keyboard.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; In the middle of an =
application, suddenly the keyboard hang,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; (the machine is alive, mouse =
working fine, but no input from keyboard)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; and to recover, it needs to =
logout and re-logon.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; It seems something wrong to do =
with login profile.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">I got some suggestions as follow (I =
haven=B4t tested it yet, but I will),</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">-1. Eyal Edri &gt; ...try to disable =
the NUM LOCK.</FONT><FONT FACE=3D"Tahoma"> </FONT><FONT SIZE=3D2 =
FACE=3D"Tahoma">some Xwindows on several sun station got stuck , until =
we figured it was the num lock pressed .</FONT><FONT FACE=3D"Tahoma"> =
</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">-2. Mike Salehi &gt; ...try kbd =
-r</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">-3. Richard J. Buchman &gt; ...telnet =
back to the affected system, try a keyboard reset to see if that breaks =
the lock.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">-4. Dave Ballesteros &gt; ...check =
the setting of hme0 port and compare it to its server.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">(his original message) : May not be =
your problem, but I recently ran into a problem where the =
network</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">switch that was connected to the =
hme0 port on one of our servers was set to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">autonegotiate 100/Full, and my hme0 =
port was set to 100/Full.&nbsp; I was getting</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">periodic console messages (and the =
network engineer confirmed his logs were</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">getting messages as well) indicating =
my hme0 port link had gone down,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">followed quickly by messages saying =
hme0 had been re-established.&nbsp; When this</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">occurred, if I was in a session at =
the time, I could not key anything in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">from the keyboard. I ended up having =
to close the xterm session, start</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">another session and login =
again.&nbsp; We asked the network folks to lock the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">switch at 100/full instead of using =
autonegotiate to resolve this problem.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">-5. Farzad Hejazi</FONT><FONT =
FACE=3D"Tahoma"> </FONT><FONT SIZE=3D2 FACE=3D"Tahoma">&gt; =
...sometimes a combination of the CONTROL key and another key can =
cause this situation.</FONT><FONT FACE=3D"Tahoma"> </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Thanks a lot.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Slamet</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Best Regards,</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Tahoma">slamet FADILAH</FONT></B>
</P>

<P><FONT SIZE=3D1 FACE=3D"Tahoma">TAC2OMCBSS, siemens </FONT><FONT =
COLOR=3D"#FF0000" SIZE=3D1 FACE=3D"Tahoma">m</FONT><FONT SIZE=3D1 =
FACE=3D"Tahoma">obile, casablanca</FONT>
<BR><FONT SIZE=3D1 =
FACE=3D"Tahoma">slamet.fadilah@gsm-siemens.co.ma</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0FF2F.7592B590--
Received on Wed Jun 27 18:34:46 2001

This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:24:58 EDT