From: Logan Johnson <logan@slackware.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: USB Keyboard and 2.2.18pre
Date: Sun, 26 Nov 2000 13:40:20 -0800 [thread overview]
Message-ID: <20001126134020.A15022@slackware.com> (raw)
Hello all! I've run into an interesting problem with the newer stable kernels.
I have an iMac DV SE (400MHz, the first DV SE.. with the stubby keyboard).
2.2.18pre21 and pre22 and pmac_stable all seem to have the same problem, which
is that the keyboard is non-functional at the console.
The keyboard is detected and is bound to input0. I can ssh in,
'cat /dev/input/event0', and watch my terminal fill with garbage as I mash
keys on the keyboard. But I can't get any characters to show up on the
console.
The USB mouse also works fine, as I can gpm all over my boot messages. (I
tried copying and pasting a root login for fun, but realized after the 't'
that it was really hard to copy and paste a carriage return. ;)
It doesn't seem to be a keymap issue, as both mac-us-std and us fail to
produce any characters onscreen from any keys.
The 2.2.15 that shipped with linuxppc 2000 seems to have a perfectly functional
keyboard, so my suspicion is that the problem lies in the new input layer I've
read so much (and yet so little) about.
Has anyone else seen this issue? Alternatively, can anyone else with my
hardware duplicate (or fail to duplicate) the problem? I can post my kernel
config(s) if needed.
Also, I'm perfectly happy to serve as a guinea pig if someone has an idea on
this but not the hardware to test it with.
--Logan
--
Logan Johnson | logan@slackware.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-11-26 21:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001126134020.A15022@slackware.com \
--to=logan@slackware.com \
--cc=linuxppc-dev@lists.linuxppc.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).