Bug 7725
Summary: | keyboard timeout | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | rsnapp |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-14 01:50:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
rsnapp
1999-12-10 12:56:31 UTC
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 ? |