Bug 4760 - Problem with keyboard/mouse lock-up & Promise Ultra 66
Problem with keyboard/mouse lock-up & Promise Ultra 66
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-27 20:09 EDT by dushaw
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dushaw 1999-08-27 20:09:42 EDT
We have had a very peculiar problem associated with
gpm.  First, we have the following system:

ASUS P2B-F motherboard
20 GB Western Digital HD
Promise Ultra 66 card
RedHat 6.0
Linux 2.2.10, with a patch for the Ultra 66 card
(I don't think the patch has a bearing on the problem,
but I think the Ultra 66 card does.)

  With gpm automatically started up during reboot, the mouse
and keyboard apparently have an address conflict so that the
keyboard and mouse lock up.  Sometimes killing gpm (by
logging in remotely) will free the keyboard, sometimes not.
Sometimes after killing gpm, starting and stopping X
windows will free up the keyboard.


  Presently, we are able to get everything to work by:
1) disabling gpm automatic startup
2) unplugging the mouse
3) rebooting
4) logging in as root
5) plugging in the mouse
6) starting "gpm -t ps/2" manually

Leaving the mouse plugged in upon reboot, and manually
starting "gpm -t ps/2" does not work.  Perhaps this is
not a gpm problem but a kernel problem; but it is gpm
related!

I know of at least one other person (Brion Vibber:
brion@pobox.com) with a similar system who has this
problem.

Thanks,
B.D.

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