Red Hat Bugzilla – Bug 102830
mouse not detected on Proliant 1600 Rackmount Server
Last modified: 2014-03-16 22:38:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
Any mouse connected to PS/2 port or serial COM port is not detected by kudzu. No
mouse entry in the hwconf file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Use several mouse device connected to PS/2 and serial COM ports.
Actual Results: No new mouse device detected.
Expected Results: There should be a mouse detected.
Neither PS/2 nor serial mice are detected? Is the probe being run in 'safe' mode?
*** Bug 102910 has been marked as a duplicate of this bug. ***
I have the same problem and can't run the GUI from the server. Serial mouse
was not detected and various other mice. I don't know how to run the probe in
the safe mode but would try if someone tells me how.
Well, if it's failing in general, then the probe isn't being run in safe mode.
Will have to try and track down some of that hardware.
*** Bug 104598 has been marked as a duplicate of this bug. ***
You can run in safe mode or any other mode. The mouse is not recognized. I
would like to know if any fix is currently being worked on for this problem. I
purchased the new release of redhat 9.0 and haven't been able to run xwindows
because of the error in the operating system. I will work with technical
support or test whatever is needed to resolve this problem. Please respond on
the status of this bug so I can report it to my upper management.
(Note: bugzilla is not an official support mechanism; it's just a defect
At this point, it's not really being looked at much due to lack of the hardware
in question; this failure seems specific to that hardware.
I had the same problems but after I did a system erase using Compaq's
SmartStart 5.3 cd, and selected "Linux" as the os to be installed it
detected the PS2 mouse just fine.
Ignore last comment, the reason the mouse is now detected was because
i used "linux nousb" at the installation prompt.
"LINUX NOUSB" !!! Works great... Thanks
Closing out bugs on older, no longer supported, releases. Apologies for any lack
Please test this bug on a current release, such as Fedora Core 4. If it persists
there, please file a new bug.