Red Hat Bugzilla – Bug 126168
keyboard not found in last 2 kernel updates
Last modified: 2015-01-04 17:07:09 EST
Description of problem:
System: Intel P4, 2.8GHz with Hyperthreading, 512 MB RAM, bog standard
PS/2 UK keyboard.
My keyboard is not recognized when booting the smp kernel in the last
2 releases (2.6.6-1.427 and 2.6.6-1.435). Worked fine under
2.6.6-1.358. The single-processor kernels work fine.
Version-Release number of selected component (if applicable):
2.6.6-1.427smp and 2.6.6-1.435smp
Steps to Reproduce:
1. Boot into latest upgrade smp kernel
Keyboard isn't recognized. kudzu runs, presumably to say that a
component has been removed (i.e. the keyboard) but as it only has a
keyboard interface that doesn't help much!)
I'd expect the keyboard to work. The release notes to the 427 kernel
mentioned improvements to the keyboard subsystem - I haven't looked
into it more deeply than that.
System: Intel P4, 2.8 GHz Hyperthreaded, Chaintech 9PJL3 motherboard
When logged in via ssh and running Kudzu, it indeed wants to remove
the AT keyboard. In /proc/bus/input/devices there is no AT keyboard,
just the mouse (PS/2 Logitech Mouse).
To get the mouse working, it has to be unplugged/plugged in again.
The following kernels don't have this problem: 2.6.6-1.435,
2.6.5-1.358 and 2.6.5-1.358smp
Problem also still exists for me in kernel-2.6.6-1.435.2.1smp
I also still have the same problem with kernel-smp-2.6.6-1.435.2.1
Problem still here with kernel-smp-2.6.6-1.435.2.3
System: Intel P4, 3.0GHz with Hyperthreading, 1024 MB RAM, standard
ps/2 swedish keyboard.
Im having the same problem, if im booting with smp then the keyboard
won't work and kudzu tries to remove it, if i boot with single cpu or
with ACPI off, then if works. I have this problem with
kernel-smp-2.6.6-1.435.2.3, the kernels 2.6.5-1.358 and 2.6.5-1.358smp
didnt have this problem.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.