From: Mikael Pettersson <mikpe@csd.uu.se>
To: vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org, ttsig@tuxyturvy.com
Subject: Re: Dell Latitude CPi keyboard problems since 2.5.42
Date: Mon, 27 Jan 2003 13:26:54 +0100 (MET) [thread overview]
Message-ID: <200301271226.NAA10528@harpo.it.uu.se> (raw)
On 26 Jan 2003 21:19:52 -0500, Tom Sightler wrote:
>> Hmm, interesting. Can you try disabling some of the probes for
>> extended keyboards in atkbd.c to see if some of them could confuse
>> your keyboard so that the BIOS doesn't like it after boot? Also you
>> may want to kill the keyboard reset on reboot ... (atkbd_cleanup) ...
>
>I've been following this because my Dell Latitude C810 has the
>"keyboard/mouse doesn't work after reboot" with all of the recent 2.5.x
>kernel that I have tried.
>
>When I saw the suggestion above to try removing the keyboard reset I
>thought that was just too easy to pass up giving it a try. Sure enough,
>removing just the one line that preforms the keyboard reset from
>atkbd_cleanup solves the problem for me.
I tried that too and it eliminated the keyboard error problem on my CPi.
(Strangely enough, when I tried the same hack with the 2.5.42 kernel
some time ago it did not help. Oh well.)
I added some logging to atkbd_command(), and found that GSCANSET
always returns 22 (decimal), but SSCANSET with 22 fails and
triggers the BIOS keyboard error. So what happens is that atkbd_set_3()
does GSCANSET and stores 22 in atkbd->oldset. Then it issues
SSCANSET with 2, checks the result with GSCANSET, gets 22, and
assumes 2 since 22 != 3. Just before reboot, atkbd_cleanup() does
SSCANSET with 22 (from atkb->oldset), which fails (though atkbd
doesn't check this) and later triggers the BIOS keyboard error.
Either removing the SSCANSET from atkbd_cleanup(), or changing
atkbd->oldset from 22 to 2, solves my CPi's keyboard problems.
/Mikael
next reply other threads:[~2003-01-27 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 12:26 Mikael Pettersson [this message]
2003-01-27 12:34 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2003-01-27 20:57 Mikael Pettersson
2003-01-27 21:52 ` Vojtech Pavlik
2003-01-28 1:56 ` Tom Sightler
2003-01-28 10:12 ` Vojtech Pavlik
2003-01-26 14:39 Mikael Pettersson
2003-01-26 20:55 ` Vojtech Pavlik
2003-01-24 20:49 NFS client locking hangs for period Christian Reis
2003-01-25 3:54 ` Neil Brown
2003-01-26 16:02 ` Christian Reis
2003-01-26 21:49 ` [NFS] " Trond Myklebust
2003-01-26 22:47 ` Christian Reis
2003-01-26 23:02 ` Trond Myklebust
2003-01-26 23:56 ` Christian Reis
2003-01-27 0:06 ` Trond Myklebust
2003-01-27 2:19 ` Dell Latitude CPi keyboard problems since 2.5.42 Tom Sightler
2003-01-15 10:22 Mikael Pettersson
2003-01-15 10:43 ` Andrew McGregor
2003-01-15 19:21 ` Valdis.Kletnieks
2003-01-16 2:50 ` Andrew McGregor
2003-01-16 13:33 ` Alessandro Suardi
2003-01-25 14:02 ` Vojtech Pavlik
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=200301271226.NAA10528@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.com \
--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 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®