From: Dave Jones <davej@suse.de>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: rudmer@legolas.dynup.net, linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Linux 2.5.10-dj1
Date: Sun, 28 Apr 2002 22:38:42 +0200 [thread overview]
Message-ID: <20020428223842.J14743@suse.de> (raw)
In-Reply-To: <20020427030823.GA21608@suse.de> <200204271313.g3RDD4024060@smtp1.wanadoo.nl> <20020427155116.I14743@suse.de> <200204281145.g3SBjJJ20178@smtp2.wanadoo.nl> <m3lmb7zjkp.fsf@lapper.ihatent.com>
> On 2.5.10-dj1 it works like this: keyboard led is responsive to
> hitting caps lock, but when LED is off I get upper case letter typed,
> and when LED is off I get lower case letters. However, the strange bit
> is that lets say I type in my username and password so that they
> appear in lowercase on the screen, I still don't get in. And just fir
> having tried, typing with the caps lock LED off, thus getting upper
> case text, doesn't help either.
>
> Any pointer to where I go off to track this down?
Add a #define ATKBD_DEBUG to drivers/input/keyboard/atkbd.c
and a #define I8042_DEBUG_IO to drivers/input/serio/i8042.c, and maybe
Vojtech can figure out whats going wrong from the output?
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-04-28 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 3:08 Linux 2.5.10-dj1 Dave Jones
2002-04-27 5:32 ` A Guy Called Tyketto
2002-04-27 12:51 ` Rudmer van Dijk
2002-04-27 13:51 ` Dave Jones
2002-04-28 11:45 ` Rudmer van Dijk
2002-04-28 19:53 ` Alexander Hoogerhuis
2002-04-28 20:38 ` Dave Jones [this message]
2002-04-28 22:47 ` Vojtech Pavlik
2002-04-28 20:49 ` Rudmer van Dijk
2002-04-28 23:51 ` ext2 free blocks count corrupted (was Re: Linux 2.5.10-dj1) Petr Vandrovec
2002-04-29 1:26 ` Linux 2.5.10-dj1 Chris Wright
2002-04-27 18:34 ` Adrian Bunk
2002-04-27 18:46 ` Dave Jones
2002-04-29 9:14 ` Adrian Bunk
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=20020428223842.J14743@suse.de \
--to=davej@suse.de \
--cc=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rudmer@legolas.dynup.net \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.