Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 5905 - Mouse auto-detected by graphical installer, but it asks for mouse type anyway
Mouse auto-detected by graphical installer, but it asks for mouse type anyway
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-10-13 03:24 EDT by Johan Walles
Modified: 2015-01-07 18:38 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-10-21 13:57:27 EDT
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 Johan Walles 1999-10-13 03:24:06 EDT
The graphical install program starts by autodetecting my
mouse (successfully).  Then after having clicked about some
in the install program, it asks me what type of mouse I
have.  As I didn't really know whether I have a bus mouse or
a ps/2 mouse, of course I gave the wrong answer, and X
wouldn't start after installation.  I fixed this by moving
the /dev/mouse link to point to /dev/psaux, but as this may
not be a viable solution for beginners, maybe you should
look into mouse detection some more.

Comment 1 japj 1999-10-20 10:59:59 EDT
After graphical install with correct mousedetection (Microsoft 2.1A
serial mouse at com3) X does not get configured correctly

Also gpm is not started with -R (this is present in a FAQ of the
Redhat 6.0 paper documentation?).
Comment 2 Jay Turner 1999-10-21 13:57:59 EDT
Not selecting the correct mouse in mouseconfig is not a bug in the
installer.  The guess that the installer makes to start with is a
really basic guess, and there is a chance that the user would like to
customize that selection, which is why the second screen is given.
You can just select <next> in that screen, which will accept the
default that the installer found if you do not wish to customize.

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