All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-bk way too fast
Date: Mon, 21 Jun 2004 13:02:14 +0200	[thread overview]
Message-ID: <20040621110214.GA1721@ucw.cz> (raw)
In-Reply-To: <1087813570.1691.7.camel@teapot.felipe-alfaro.com>

On Mon, Jun 21, 2004 at 12:26:10PM +0200, Felipe Alfaro Solana wrote:

> > > Something is definitely screwy with the latest -bk.  I updated from a 
> > > kernel ~1 week ago, and all timer-related stuff is moving at a vastly 
> > > increased rate.  My guess is twice as fast.  Most annoying is the system 
> > > clock advances at twice normal rate, and keyboard repeat is so sensitive 
> > > I am spending quite a bit of time typing this message, what with having 
> > > to delettte (<== example) extra characters.  Double-clicking is also 
> > > broken :(
> > 
> > Q: Are you using the atkbd.softrepeat=1 parameter? Or an USB keyboard?
> >    If not, you shouldn't be getting faster repeats even if the timer
> >    were off, because the repat shoul be generated by the keyboard
> >    itself.
> 
> I'm using a PS/2 Microsoft Natural Keyboard Elite and I see the faster
> typing rates only while in X. However, keyboard rate is normal while in
> a text console.

It's possible that X does it's own autorepeat, though that'd rather
surprise me.

Can you check with showkey -s, and xev in X?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-06-21 11:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  2:54 2.6.7-bk way too fast Jeff Garzik
2004-06-21  3:29 ` Ricky Beam
2004-06-21  7:20   ` Felipe Alfaro Solana
2004-06-21  8:23   ` Vojtech Pavlik
2004-07-02  7:53     ` David Woodhouse
2004-07-02 12:56       ` Vojtech Pavlik
2004-06-21  3:36 ` Jeff Garzik
2004-06-21  3:49   ` Matt H.
2004-06-21 11:53     ` Marcel Holtmann
2004-06-21  3:52   ` Zwane Mwaikambo
2004-06-21  3:55     ` Zwane Mwaikambo
2004-06-21  4:02   ` Andrew Morton
2004-06-21  5:00     ` Norberto Bensa
2004-06-21  5:39       ` Norberto Bensa
2004-06-21  6:16         ` Linus Torvalds
2004-06-21  7:05           ` Clemens Schwaighofer
2004-06-21  7:18             ` Matt H.
2004-06-21  7:16               ` Andrew Morton
2004-06-21  8:15                 ` Matt H.
2004-06-21  8:20                   ` Clemens Schwaighofer
2004-06-21  9:25                     ` Clemens Schwaighofer
2004-06-21 10:24                     ` Felipe Alfaro Solana
2004-06-21  7:37             ` Linus Torvalds
2004-06-21  9:52               ` Jeff Sipek
2004-06-21 16:41                 ` Jeff Sipek
2004-06-21  7:19           ` Jeff Sipek
2004-06-21  5:11     ` Jeff Garzik
2004-06-21  5:08 ` Aubin LaBrosse
2004-06-21  8:22 ` Vojtech Pavlik
2004-06-21 10:26   ` Felipe Alfaro Solana
2004-06-21 11:02     ` Vojtech Pavlik [this message]
2004-06-21  8:48 ` Andrew Morton
2004-06-21  9:17   ` Matt H.
2004-06-21  9:56   ` Jeff Sipek
2004-06-21 10:47   ` Felipe Alfaro Solana
2004-06-21 16:55     ` Norberto Bensa
  -- strict thread matches above, loose matches on Subject: below --
2004-06-21 13:20 Sau Dan Lee
2004-06-21 15:17 ` Vojtech Pavlik
2004-06-21 15:25   ` Sau Dan Lee

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=20040621110214.GA1721@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.