public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Hal Duston <hald@sound.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input w/2.5.3-dj3
Date: Mon, 11 Feb 2002 21:55:18 +0100	[thread overview]
Message-ID: <20020211215518.A12817@suse.cz> (raw)
In-Reply-To: <Pine.GSO.4.10.10202111430440.12270-100000@sound.net>
In-Reply-To: <Pine.GSO.4.10.10202111430440.12270-100000@sound.net>; from hald@sound.net on Mon, Feb 11, 2002 at 02:39:47PM -0600

On Mon, Feb 11, 2002 at 02:39:47PM -0600, Hal Duston wrote:

> I've got CONFIG_INPUT_KEYBDEV=y in my .config so I am assuming yes.
> The keypresses don't generate the correct characters.  I.e. as far as
> I can tell, the 'm' key is Caps Lock, the '9' key is ScrLk, the '0'
> key is NumLk, the 'q' key is 'y', the 'w' key is Ctrl, the 'e' key is 
> 'j' the 'r' key is 'x'.  Etc.  I hope you don't need a complete list!

This is very interesting. Can you pass i8042_direct=1 to the kernel
command line if it fixes anything? Also atkbd_set=3 might help. Anyway,
please send me the log (dmesg) of the bootup in this case. Thanks.
 

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-02-11 20:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 20:39 Input w/2.5.3-dj3 Hal Duston
2002-02-11 20:55 ` Vojtech Pavlik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 19:24 Hal Duston
2002-02-15  0:22 ` Vojtech Pavlik
2002-02-12  1:00 Hal Duston
2002-02-12  9:00 ` Vojtech Pavlik
2002-02-11 17:56 Hal Duston
2002-02-11 17:58 ` Vojtech Pavlik
2002-02-08 19:12 Hal Duston
2002-02-09 17:00 ` Vojtech Pavlik
2002-02-07 17:55 Hal Duston
2002-02-08  7:17 ` Vojtech Pavlik
2002-02-07 16:43 Hal Duston
2002-02-07 16:51 ` Dave Jones

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=20020211215518.A12817@suse.cz \
    --to=vojtech@suse.cz \
    --cc=hald@sound.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