Red Hat Bugzilla – Bug 119474
serial mouse not working during installation
Last modified: 2007-11-30 17:10:39 EST
Fresh installation of Fedora Core 2 Test 2.
Installer reports mouse as "Generic - 2 Button Mouse (serial)", but
mouse doesn't work during installation. After installation, there's no
/etc/sysconfig/mouse, not valid InputDevice entry in
/etc/X11/XF86Config and no system-config-mouse tool installed.
It should have found and configured the mouse at /dev/ttyS1
Probably kudzu's fault.
Comps bug, actually. Will hopefully be fixed in newer builds.
Reopening, we should probably do something during installation.
Possibly related to this, the installer detected my 3-button PS/2
mouse but it is not working in X or in gpm.
No, that's a different issue... that should Just Work.
At the end of a fresh installation, I find this in install.log.syslog:
<13>Apr 4 18:08:22 kudzu: linked /dev/mouse to /dev/ttyS1
<13>Apr 4 18:08:22 kudzu: ran mouseconfig for ttyS1
So, at that point, kudzu is correct about my mouse
(system-config-mouse was missing, though, different bug).
*** Bug 119259 has been marked as a duplicate of this bug. ***
I can confirm that serail mice don't work in the installer as of
04/16/2004 rawhide tree.
Same for FC2t3. Even after manual selection (ms compatible +/- 3 btn
emu or generic 3 button) the mouse is not recognized.
Michael has confirmed that serial mice remain inoperative in the
FC2-e0507.0 release candidate.
Funny thing is that by starting gpm the serial mouse gets recognized
by X. It's still functional after stopping gpm.
Leonard, that was a different bug. [Serial mouse after (!)
installation in X works fine here with the release candidate. In
Test3, one of the side-effects of "service gpm start" is that kernel
module "sermouse" is loaded. But that alone doesn't enable the mouse
What is the /etc/sysconfig/mouse in the non-functional case?
I need to try that (no sooner than tomorrow) with a fresh install. In
Test2, /etc/sysconfig/mouse did not exist. With Fedora Core 2, the
file was most likely created by me after installation (not just to
enable the third button). /root/install.log.syslog contains:
<13>May 15 18:42:30 kudzu: ran mouseconfig for ttyS0
FC2, after fresh install with non-working mouse, /etc/sysconfig/mouse
FULLNAME="Generic - 2 Button Mouse (serial)"
The device /dev/ttyS0 is correct.
Side-note: In reply to comment 10 (Leonard), _after_ installation
mouse stops working in X as soon as I "chkconfig gpm stop ; reboot".
Correct, the gpm init script starts the input layer redirector (for
lack of a better place ATM.)
The same bug is reported by me in No 124275
[just tracking: bug persists in FC3 Test1]
*** This bug has been marked as a duplicate of 115513 ***
With a Logitech C7 mouse, bug persists after installation, and does
not work *at all*.
Still there in Core 3 test1.
Logitech Cordless Navigator Duo mouse does not work if I use the ps/2
adapter to plug both connectors to PS/2 instead of one PS/2, one USB.
However, when the boot process completed, whatever I change the ps/2
connector(which is used for mouse) to USB or PS/2, the mouse still
continue to work.
I installed FC4 which did not recognize my mouse. I have a Microsoft Serial
mouse. Tried it as serial and with a PS2 adapter and the install cannot see
either one. Any suggestions on how to get it to work is appreciated.
Here is what I do to fix for FC4 (both x86-32 and x86-64) for serial mice:
1. Log into console or text mode as root.
2. Run mouseconfig - set up for serial mouse, ignore any error messages.
3. Use your favourite editor to open /etc/sysconfig/mouse
4. The last line should contain /dev/mice - change this to /dev/ttyS? where the
question mark refers to the port your mouse is plugged into.
5. Save /etc/sysconfig/mouse
6. Run service gpm start and when you go back to X (Gnome / KDE) the mouse
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.