linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Thu, 25 Sep 2003 18:59:55 -0500	[thread overview]
Message-ID: <200309251859.55887.rob@landley.net> (raw)
In-Reply-To: <20030923000647.A1128@pclin040.win.tue.nl>

On Monday 22 September 2003 17:06, Andries Brouwer wrote:

> > Any clues?  (This happens to me at least once an hour...)
>
> Some people have been reporting missing key releases (maybe also you),
> but these are all missing key presses. It is easiest to blame the
> keyboard, even though I could imagine ways to blame the kernel.

If the press is the first event, how does it know that it's missing?  Are you 
saying t got a key release that didn't match an active keypress?  This seems 
like a similar problem.  Are missing key releases flagged as errors and 
logged?  (Maybe the next time that key is pressed, if the system thinks it's 
already down?)

I'm certainly seeing missing releases.  Missing presses are just typos, I 
usually have enough gunk in the keyboard that it misses the occasional key 
anyway.  (This laptop lives in my backpack, with books and papers and Wendy's 
coupons and pens and...)  But "enter", "delete", or "cursor up" holding down 
for an extra second and change can be quite annoying.

> What about 2.4? Do you have to go back once an hour and add a symbol
> that was not transmitted correctly? Does 2.4 work perfectly for you?

Okay, over the past few days I've booted into 2.4.21 three times and done my 
standard text-intensive programming, email, and word processing.  I didn't 
notice any keys sticking.  (It's intermittent enough problem that this isn't 
difinitive, but it's the best I can do.)

On the other hand, the key repeat rate is a lot slower under 2.4.21, and I 
suspect it's using the hardware repeat instead of the software repeat.  The 
keyboard hardware definitely knows when a key gets released. :)

I.E. Under 2.4.21 I don't experience a problem.  (Maybe there is a technical 
problem with the hardware, but it doesn't manifest in a way that I ever 
notice.)  I'd be happy to live with the slower repeat rate if I could get 2.6 
to use 2.4's keyboard access method.

Rob

  parent reply	other threads:[~2003-09-26  0:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-20 20:33 Keyboard oddness Rob Landley
2003-09-20 22:18 ` Andries Brouwer
2003-09-21 18:51   ` Rob Landley
2003-09-21 10:04 ` Vojtech Pavlik
2003-09-21 20:20   ` Rob Landley
2003-09-22 20:06   ` Rob Landley
2003-09-22 22:06     ` Andries Brouwer
2003-09-23  0:23       ` Rob Landley
2003-09-23 10:51         ` Greg Louis
2003-09-25 23:59       ` Rob Landley [this message]
2003-09-26  1:27       ` Rob Landley
2003-09-26  8:15         ` Andries Brouwer
2003-09-26  8:43           ` Rob Landley
2003-09-26  8:46           ` Vojtech Pavlik
2003-09-26  9:43 Nicolas Mailhot
2003-09-26 10:24 ` Vojtech Pavlik
2003-09-26 10:41   ` Nicolas Mailhot
2003-09-26 10:51     ` Vojtech Pavlik
2003-09-26 12:48     ` jw schultz
2003-09-26 13:08     ` Nicolas Mailhot
2003-09-26 13:41       ` Vojtech Pavlik
2003-09-26 14:12         ` Nicolas Mailhot
2003-09-26 14:17           ` Vojtech Pavlik
2003-09-26 14:21             ` Nicolas Mailhot
2003-09-26 14:26               ` Vojtech Pavlik
2003-09-26 14:50                 ` Nicolas Mailhot
2003-09-26 15:06                   ` Vojtech Pavlik
2003-09-26 15:21                     ` Nicolas Mailhot
2003-09-26 15:24                       ` Vojtech Pavlik
2003-09-26 13:56       ` Helge Hafting
2003-09-26 14:01         ` Mike Dresser
2003-09-28 10:58           ` Helge Hafting
2003-10-02 12:40             ` Pavel Machek
2003-10-01 10:09   ` Pavel Machek
2003-10-01 13:06     ` Nicolas Mailhot

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=200309251859.55887.rob@landley.net \
    --to=rob@landley.net \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).