Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 119474 - serial mouse not working during installation
Summary: serial mouse not working during installation
Keywords:
Status: CLOSED DUPLICATE of bug 115513
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
: 119259 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-30 20:02 UTC by Michael Schwendt
Modified: 2007-11-30 22:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:02:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Michael Schwendt 2004-03-30 20:02:19 UTC 
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.

How reproducible:
Didn't try
Comment 1 Bill Nottingham 2004-03-30 22:01:34 UTC 
Comps bug, actually. Will hopefully be fixed in newer builds.
Comment 2 Bill Nottingham 2004-03-30 22:51:56 UTC 
Reopening, we should probably do something during installation.
Comment 3 adam.huffman 2004-04-03 23:56:01 UTC 
Possibly related to this, the installer detected my 3-button PS/2
mouse but it is not working in X or in gpm.
Comment 4 Bill Nottingham 2004-04-05 19:18:05 UTC 
No, that's a different issue... that should Just Work.
Comment 5 Michael Schwendt 2004-04-05 19:28:56 UTC 
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).
Comment 6 Brent Fox 2004-04-16 18:49:16 UTC 
*** Bug 119259 has been marked as a duplicate of this bug. ***
Comment 7 Brent Fox 2004-04-16 20:16:59 UTC 
I can confirm that serail mice don't work in the installer as of
04/16/2004 rawhide tree.
Comment 8 Leonard den Ottolander 2004-05-04 12:28:34 UTC 
Same for FC2t3. Even after manual selection (ms compatible +/- 3 btn
emu or generic 3 button) the mouse is not recognized.
Comment 9 Warren Togami 2004-05-08 19:50:43 UTC 
Michael has confirmed that serial mice remain inoperative in the
FC2-e0507.0 release candidate.
Comment 10 Leonard den Ottolander 2004-05-08 19:53:28 UTC 
Funny thing is that by starting gpm the serial mouse gets recognized
by X. It's still functional after stopping gpm.
Comment 11 Michael Schwendt 2004-05-08 20:43:51 UTC 
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
in X.]
Comment 12 Bill Nottingham 2004-05-19 21:45:07 UTC 
What is the /etc/sysconfig/mouse in the non-functional case?
Comment 13 Michael Schwendt 2004-05-19 23:09:58 UTC 
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
Comment 14 Michael Schwendt 2004-06-04 01:53:06 UTC 
FC2, after fresh install with non-working mouse, /etc/sysconfig/mouse
contains:

FULLNAME="Generic - 2 Button Mouse (serial)"
MOUSETYPE="Microsoft"
XEMU3="yes"
XMOUSETYPE="Microsoft"
IMOUSETYPE="bare"
DEVICE=/dev/ttyS0

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".
Comment 15 Bill Nottingham 2004-06-04 01:56:06 UTC 
Correct, the gpm init script starts the input layer redirector (for
lack of a better place ATM.)
Comment 16 Janos Lichtenberger 2004-06-09 12:43:55 UTC 
The same bug is reported by me in No 124275
Comment 17 Michael Schwendt 2004-07-14 21:25:01 UTC 
[just tracking: bug persists in FC3 Test1]
Comment 18 Michael Schwendt 2004-08-24 07:19:36 UTC 

*** This bug has been marked as a duplicate of 115513 ***
Comment 19 Rob Porter 2004-08-26 21:04:04 UTC 
With a Logitech C7 mouse, bug persists after installation, and does
not work *at all*.

Still there in Core 3 test1.
Comment 20 NHUT THAI LE 2004-09-11 13:28:02 UTC 
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.
Comment 21 Bob Smith 2005-10-04 22:14:13 UTC 
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.
Comment 22 Chris Peet 2005-10-11 12:39:58 UTC 
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
should work.
Comment 23 Red Hat Bugzilla 2006-02-21 19:02:16 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.