linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Nicolas Mailhot <Nicolas.Mailhot@laposte.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Fri, 26 Sep 2003 17:24:51 +0200	[thread overview]
Message-ID: <20030926152451.GA10799@ucw.cz> (raw)
In-Reply-To: <1064589686.23200.24.camel@ulysse.olympe.o2t>

On Fri, Sep 26, 2003 at 05:21:26PM +0200, Nicolas Mailhot wrote:
> Le ven 26/09/2003 ? 17:06, Vojtech Pavlik a écrit :
> > On Fri, Sep 26, 2003 at 04:50:25PM +0200, Nicolas Mailhot wrote:
> > > Le ven 26/09/2003 ? 16:26, Vojtech Pavlik a écrit :
> > > > On Fri, Sep 26, 2003 at 04:21:57PM +0200, Nicolas Mailhot wrote:
> > > > > Le ven 26/09/2003 ? 16:17, Vojtech Pavlik a écrit :
> 
> > > > > > If that doesn't work, you have a more severe problem than a stuck key,
> > > > > > that wouldn't be solved by stopping the repeat.
> > > > > 
> > > > > It stops the repeat all right.
> > > > > The problem is the keyboard is dead afterwards:(
> > > > 
> > > > That's very interesting. Can you enable DEBUG in i8042.c and post a log?
> > > 
> > > Will it be of any use for an USB keyboard ? (just asking)
> > 
> > No. For an USB keyboard I'd suggest unplugging it, then re-plugging and
> > then it should work. Then look at what 'dmesg' says.
> 
> Ok. I think I've already tried this and the outcome was not satisfying,
> and I sort of remember dmesg was empty. I'll try this with usb debug
> enabled this evening or next monday. (I just hope something comes out of
> this - 2.6 is great till the keyboard goes mad).

You can also enable DEBUG in hid-core.c.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-09-26 15:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26  9:43 Keyboard oddness 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-09-20 20:33 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
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

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=20030926152451.GA10799@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Nicolas.Mailhot@laposte.net \
    --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 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).