After installing Gentoo Linux version 2.6.21 and rebooting the system, User cannot login to system using a USB keyboard on a Pentium 3 700 computer. The keyboard input is read twice for each character. For example, if the word "root" is typed, the result on the screen is "rroooott." Reproducible: Always Steps to Reproduce: 1.Start the computer using the 2007.0 LiveCD 2.emerge gentoo-sources (actually tested against 2.6.20 3.from outside the chroot environment execute the command zcat /proc/config.gz > /mnt/gentoo/usr/src/linux/.config 4.from within the chroot environment execute make && make modules_install 5.copy bzImage into boot directory and update grub.conf to use the new image. 6.reboot the computer 7.when prompted to login attempt to login by typing "root" Actual Results: on step 6. the result is "rroooott" from where the keyboard's keys are being read in twice. This includes backspace. Ctrl+Alt+Delete still behaved correctly so it is possible to shutdown the kernel using that key combination. Expected Results: that when "root" is typed in "root" is displayed and that the system itself actually interprets key input as "root." Test System Components: Pentium 3 700 MHz 256 MB of Memory Tyan Trinity 400 Mainboard (chipset: Apollo pro 133:VT82C694X+VT82C596B ) Belkin ClassicKeyboard (part number: F8F001-BLK-USB) reran this on gentoo-sources-2.6.19-r5 using the config.gz file from the 2007.0 LiveCD and the kernel behaved as expected (the keyboard's input was read only once per key).
Are you able to test 2.6.20, to figure if this is a 2.6.20 or 2.6.21 regression? It would also be very useful if you could test the latest development kernel, currently 2.6.22-rc4
(In reply to comment #1) > Are you able to test 2.6.20, to figure if this is a 2.6.20 or 2.6.21 > regression? > It would also be very useful if you could test the latest development kernel, > currently 2.6.22-rc4 > rechecked against build 2.6.22-rc4-git6 and the problem did not occur, looks like it was fixed in this build.
OK. It seems like you are the only person affected by this bug at the moment. If you are interested in diagnosing it further, we could attempt to find the fix and backport it. Testing 2.6.20 would be a good start. If you don't have time or interest, that's fine. This bug will be closed when 2.6.22 goes into portage. Thanks for the testing.
gentoo-sources-2.6.22 is now in portage
