Bug 84424 - PS/2 mouse and keyboard don't work together
PS/2 mouse and keyboard don't work together
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Depends On:
  Show dependency treegraph
Reported: 2003-02-16 14:15 EST by Rick
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-19 17:34:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rick 2003-02-16 14:15:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
I installed Red Hat 8.0 from CD.  When the firstboot is run and the welcome 
screen is displayed, I have no mouse or keyboard.  They worked fine during 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Remove install CD
2.Turn on machine

Actual Results:  The welcome screen is displayed and I can go no further due 
to lack of input devices.

Expected Results:  The mouse and keyboard should function properly.

Additional info:

I noticed the USB mouse and USB keyboard options being started during boot up.
Comment 1 Rick 2003-02-16 16:24:37 EST
I plugged a USB mouse into the machine and booted.  The ps/2 keyboard and USB 
mouse work.  I unplugged the USB mouse, plugged the ps/2 mouse in and 
rebooted.  Neither the keyboard or mouse worked.  It appears that this is an 
XFREE issue.
Comment 2 Rick 2003-02-19 17:34:14 EST
This is actually a hardware problem.  I thought it was a software problem 
because the ps/2 mouse & keyboard worked together during setup, but not after 
setup was completed.  I have since learned that the ps/2 mouse plug has not 
worked correctly on the machine for quite some time.  

Note You need to log in before you can comment on or make changes to this bug.