Red Hat Bugzilla – Bug 7725
keyboard timeout
Last modified: 2008-05-01 11:37:53 EDT
I am installing Redhat 6.1 on an ALR Revolution SMP pro (dual p-pro). The system contains a DPT SCSI RAID ctlr (PCI), an Adaptec 2940 scsi ctlr (PCI), 2 intel etherexpress pro10 ctlrs (PCI), 512 MB memory, SVGA video card, 2 serial ports. I've downloaded the most current BIOS update from gateway's web site & flashed it.... The install works without flaw. On the ensuing reboot I get the message "keyboard timeout [2]" and the console is unusable. The system will be alive after re-booting and can be telnet-ed to, yet the console is unusable. Despite all my attempts fooling around with BIOS settings I cannot get over this. Are there any others out there with the same problem? Is there any alternate keyboard driver that I could use? Any other ideas? Thanx
On installing of either 6.0 or 6.1 on a system with a ASUS 44BX mother board I had a similar sounding problem: but I only got the keyboard tinmeout[2] message once, usually the keyboard just stopped working. The problem occured after booting when gpm was run (from rc.d) for console, or when X started knowing the mouse was a ps/2. I worked around this by using a serial mouse instead.
assigned to kernel
*** Bug 8009 has been marked as a duplicate of this bug. ***
I've tried to re-install using a serial mouse rather than a bus mouse and get the same error messages and the console remains unusable due to the keyboard timeout. Any further thoughts?
I have a similar problem. I'm running RHL 6.0 on a Pentium II 400MHz, FIC VB 601 Mother board (also uses an Intel 440 BX chipset). Keyboard & mouse are PS-2, both from Genius. Kernel is a custom-compiled 2.2.10. Approximately every second boot, the login console appears (login:) but keyboard appears frozen. I tried a custom-compiled 2.2.14 kernel, but I get the same problem. I don't get any related messages in /var/log/messages, however. Both kernels have support for Unix89 PTY's. Is there any way I can diagnose this further to find out what is going on? Thanks.
Anyone still have this problem in 6.1 or 6.2 ?