From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Keyboard broken in 2.6.13.2
Date: Sat, 03 Dec 2005 10:16:28 +0000 [thread overview]
Message-ID: <1133604988.13652.2.camel@localhost> (raw)
In-Reply-To: <43909451.20105@candelatech.com>
On Gwe, 2005-12-02 at 10:37 -0800, Ben Greear wrote:
> I have a system with a super-micro P8SCI motherboard.
>
> The default FC2 kernel (2.6.10-1.771_FC2smp) works fine, but
> when I try to boot a 2.6.13.2 kernel, I see this error:
>
> i8042.c: Can't read CTR while initializing i8042
>
> If I hit the keyboard early in the boot, the system will just reboot.
>
> If I wait a bit, then it will boot to a prompt, but no keyboard input
> is accepted.
Fedora Core has a patch (which was rejected upstream) which
automatically fixes up problems with some BIOS USB emulation. On the
base kernel you need to specify "usb-handoff" on the command line at
boot. Another approach is to turn USB keyboard off in the BIOS.
Alan
prev parent reply other threads:[~2005-12-06 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 18:37 Keyboard broken in 2.6.13.2 Ben Greear
2005-12-02 21:15 ` Dmitry Torokhov
2005-12-02 22:11 ` Ben Greear
2005-12-03 10:16 ` Alan Cox [this message]
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=1133604988.13652.2.camel@localhost \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greearb@candelatech.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