From: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Keyboard Scancode Problems
Date: Thu, 01 Feb 2001 01:37:03 +0100 [thread overview]
Message-ID: <3A78AFAF.82FCB4F2@Hell.WH8.TU-Dresden.De> (raw)
Hi all,
With all the latest kernels (at least since 2.4.0-test12)
I have had occasional problems with a PS/2 keyboard when
switching back and forth between X and text consoles.
In most cases the problem occurs when switching from X to
a text console, which renders the keyboard totally unusable.
Pressing any key results in ^W ^E and other garbage.
Sometimes pressing Ctrl fixes the problem, other times not
even SysRq works.
The kernel logs the following stuff:
keyboard: unrecognized scancode (70) - ignored
keyboard: unrecognized scancode (66) - ignored
keyboard: unknown scancode e0 71
keyboard: unknown scancode e0 70
and so forth. I cannot reliably reproduce it though.
Can someone enlighten me whether this is a keyboard problem,
X problem or something wrong with the kernel's console stuff?
-Udo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-01 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 0:37 Udo A. Steinberg [this message]
2001-02-01 0:42 ` Any reason why we can't auto-start LVM (vg's) in the kernel? List User
2001-02-01 1:14 ` Andreas Dilger
2001-02-01 18:55 ` Keyboard Scancode Problems Pierre Rousselet
2001-02-02 7:11 ` Stefan Frank
2006-10-26 18:03 keyboard scancode problems Joost Gevers
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=3A78AFAF.82FCB4F2@Hell.WH8.TU-Dresden.De \
--to=sorisor@hell.wh8.tu-dresden.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
all inboxes | Powered by JetHome®