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.
Thanks,
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
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?
--
Dmitry
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 <[email protected]>
Candela Technologies Inc http://www.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