From: Ben Greear <greearb@candelatech.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Keyboard broken in 2.6.13.2
Date: Fri, 02 Dec 2005 14:11:15 -0800 [thread overview]
Message-ID: <4390C683.2030507@candelatech.com> (raw)
In-Reply-To: <200512021615.16247.dtor_core@ameritech.net>
Dmitry Torokhov wrote:
> On Friday 02 December 2005 13:37, 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.
>>
>
>
> Does booting with "usb-handoff" boot option help any?
Not sure, but acpi=no works.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-12-02 22:11 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 [this message]
2005-12-03 10:16 ` Alan Cox
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=4390C683.2030507@candelatech.com \
--to=greearb@candelatech.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.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