From: Thoralf Will <thoralf@cipsoft.com>
To: linux-kernel@vger.kernel.org
Subject: Re: pc_keyb: controller jammed (0xA7)
Date: Fri, 15 Jul 2005 19:19:34 +0200 [thread overview]
Message-ID: <42D7F026.90400@cipsoft.com> (raw)
In-Reply-To: <20050714182101.640137d8.zaitcev@redhat.com>
Pete Zaitcev wrote:
> On Thu, 14 Jul 2005 18:27:01 +0200, Thoralf Will <thoralf@cipsoft.com> wrote:
>
>
>>I didn't find any useful answer anywhere so far, hope it's ok to ask here.
>>I'm currently trying to get a 2.4.31 up and running on an IBM
>>BladeCenter HS20/8843. (base system is a stripped down RH9)
>>
>>When booting the kernel the console is spammmed with:
>> pc_keyb: controller jammed (0xA7)
>>But it seems there are no further consequences and the keyboard is
>>working.
>
>
> I saw a patch for it by Brian Maly, and yes, it was for 2.4.x.
> Maybe he can send you a rediff against current Marcelo's tree.
>
> However, is there a reason you're running 2.4.31 in Summer of 2005?
> Did you try 2.6, does that one do the same thing? It has a rather
> different infrastructure with the serio.
>
> -- Pete
>
Meanwhile I've found the source of the problem. A simple change in
drivers/char/pc_keyb.c
line 73 did the trick.
- #define kbd_controller_present() 1
+ #define kbd_controller_present() 0
The only backdraw I've noticed so far is the problem that the kernel
won't work on servers with a ps/2 keyboard controller anymore (of
course) properly. But that's a minor issue.
We are still running 2.4 kernels because our application is incompatible
with the new thread library. A migration is already planned but that
takes time, alot of. I don't expect a migration to take place before the
end of the year, maybe even later.
Thoralf
next prev parent reply other threads:[~2005-07-15 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1121358841.8002.linux-kernel2news@redhat.com>
2005-07-15 1:21 ` pc_keyb: controller jammed (0xA7) Pete Zaitcev
2005-07-15 17:19 ` Thoralf Will [this message]
2005-07-14 16:27 Thoralf Will
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=42D7F026.90400@cipsoft.com \
--to=thoralf@cipsoft.com \
--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