public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Meelis Roos <mroos@linux.ee>
Subject: Re: 2.6.9+ keyboard LED problem
Date: Wed, 5 Jan 2005 13:28:37 -0500	[thread overview]
Message-ID: <200501051328.37849.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0501051856090.9146@math.ut.ee>

On Wednesday 05 January 2005 12:04 pm, Meelis Roos wrote:
> 
> The input changes in 2.6.9 made keyboard LED setting unreliable. 2.6.8 
> is OK, 2.6.9, 2.6.10 and todays BK are buggy.
> 
> The problem is that setting the LEDs now interferes with keyboard and 
> ps/2 mouse input and makes the kernel lose key press and key release 
> events.
> 
> Short demonstation:
> #!/bin/sh
> while :; do xset led 3; xset -led 3; sleep 0.01; done
> 
> This script works from X but the same effect can be seen on the console 
> using setleds. The problem was found with ledcontrol package but is 
> easyly reproduced with the script above.
> 
> Key press and release events are lost, mouse movement is lost or 
> movement is converted into clicks or mouse loses sync (by dmesg info). 
> There are also messages like
> atkbd.c: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
> in dmesg.
> 
> Don't try the script without the sleep command unless you have a network 
> connection to log in and kill the script ;)
> 

Seems to work fine here. The led is blinking rapidly but I can type just
fine and touchpad works as well.

What kind of box do you have? UP/SMP, Preempt?

-- 
Dmitry

  reply	other threads:[~2005-01-05 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 17:04 2.6.9+ keyboard LED problem Meelis Roos
2005-01-05 18:28 ` Dmitry Torokhov [this message]
2005-01-05 18:38   ` Meelis Roos
2005-01-05 18:54     ` Dmitry Torokhov
2005-01-06  0:12       ` Ville Hallik
2005-01-06  6:43         ` Dmitry Torokhov
2005-01-06  8:30           ` Meelis Roos
2005-01-06 14:50           ` Ville Hallik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501051328.37849.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox