public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Subject: Re: weird keyboard with 2.5.70
Date: Sun, 01 Jun 2003 15:52:42 +0200	[thread overview]
Message-ID: <3EDA052A.20807@g-house.de> (raw)
In-Reply-To: <20030601122903.GA18783@sexmachine.doom>

Konstantin Kletschke schrieb:
> * Christian Kujau <evil@g-house.de> [Sun, Jun 01, 2003 at 01:27:30AM +0200]:
> 
>>hm, i guessed this was an important thing "in the old days" (TM),
>>i never had problems when "hotplugging" ps/2. nevertheless - i _have_ to
>>unplug/replug the ps/2 keyboard to actually _use_ it. after this is done
>>the keyboard is working right (and the mainboard, too :-))
> 
> Today I realize it more signifikant here. Sometimes a pressed key hangs,
> the kernel realizes not, that it was a single click. Then the Key is
> repeyted until I press it once again.

no, here it's more than "a single klick will write 5-10 chars". it is 
_not_ repeated to the infinite. and no, both kbds are OK (2.4.20-rc3 works)

> Christian, do you get this error only in X or at console too?

on X and console.

> 
> Furthermore my ps2 kbd is usable without hotplugging it, though.
> 
> The strange thing happens very often using ssh.

no, i don't think it's appliation related. to actuallay _use_ my system 
i have to login. and to do that, i will write my username / password. 
and to do that, i have to unplug/replug my keyboard.

since i have other module issues right now i'm on 2.4.20rc3 again. what 
i have done yesterday in the evening was this:
- i compiled 2.5.70 again, input/usb support statically include but with 
a modular  CONFIG_USB_KBD (usbkbd) and a modular CONFIG_KEYBOARD_ATKBD 
(atkbd). then i rebooted, logged in via remote console where i was able 
to load "atkbd" and "usbkbd". then both kbds were up *in a sane way* !!

so this would be the workaround for me.
i wonder when the problem will diesappear as it did on linux/alpha :-)

Thanks for comments,
Christian.



  reply	other threads:[~2003-06-01 13:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 23:27 weird keyboard with 2.5.70 Christian Kujau
2003-05-31 23:55 ` Måns Rullgård
2003-06-01 13:59   ` Christian Kujau
2003-06-01 12:29 ` Konstantin Kletschke
2003-06-01 13:52   ` Christian Kujau [this message]
2003-06-01 17:03     ` Måns Rullgård
  -- strict thread matches above, loose matches on Subject: below --
2003-06-02  8:23 Konstantin Kletschke
2003-06-02 19:24 ` Konstantin Kletschke
2003-06-02 20:21   ` Christian Kujau
2003-05-31 16:44 Margit Schubert-While
2003-05-31 16:01 ` Alan Cox
2003-05-31 17:09   ` Måns Rullgård
2003-06-01 15:08   ` xombi
2003-06-01 17:50     ` root
2003-05-30 20:27 Christian Kujau
2003-05-31 15:16 ` Konstantin Kletschke
2003-06-02 16:11   ` Andy Pfiffer
2003-06-02 16:24     ` Wiktor Wodecki

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=3EDA052A.20807@g-house.de \
    --to=evil@g-house.de \
    --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