From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Description of problem: System with PS/2 keyboard and mouse. Model: GE HO97986 PS/2 Optical Mouse with Scrollwheel. During install mouse does not work in graphical mode. Anaconda identifies it as "Generic 3 button mouse". X starts, pointer icon is visible but not moved by the mouse. At some point, not always the same, the light turns off. It does not turn back on unless PS/2 is unplugged and replugged in. Hence, I have installed FC4 in text mode. The mouse does not work either in Fedora desktop. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install FC4 in graphic mode, or 2. run FC4 GUI 3. Actual Results: The mouse above does not work Expected Results: The mouse should work. Additional info: Hardware Browser reports this device as "ImEx PS/2 Generic Explorer Mouse" Manfacturer: Unknown Driver: generic3ps/2 Device: /dev/input/mice Attached: /root/install.log.syslog /etc/sysconfig/mouse /etc/X11/xorg.conf /var/log/Xorg.0.log /var/log/dmsg /var/log/anaconda.log /var/log/anaconda.syslog No problem while using this mouse in Windows XP Pro SP2 (dual boot). It identifies it as "Microsoft PS/2 Mouse". Similar problem arises with Knoppix live CD when it scans for USB devices.
Created attachment 123550 [details] /root/install.log.syslog
Created attachment 123551 [details] /etc/sysconfig/mouse
Created attachment 123552 [details] /etc/X11/xorg.conf
Created attachment 123553 [details] /var/log/Xorg.0.log
Created attachment 123554 [details] /var/log/dmsg
Created attachment 123555 [details] /var/log/anaconda.log
Created attachment 123556 [details] /var/log/anaconda.syslog
If you edit your xorg.conf and set Protocol to ExplorerPS/2 does it work?
No. Ie I have replaced in xorg.conf the line: Option "Protocol" "IMPS/2" with the line Option "Protocol" "ExplorerPS/2" Then shut down, connected the mouse (so that light were on), booted FC4 and it went off as soon as the kernel started. Hence, the mouse does not work. And the Hardware Explorer entry is the same as before: "ImEx PS/2 Generic Explorer Mouse"
This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you.
This problem has not been solved by the kernel update 2.6.15-1.1830_FC4. The light stays on along boot as long as no reflecting surface is close. When approached, the light turns off, hence this mouse does not work. Besides, I start in runlevel 3. This new kernel disrupts the NVidia X settings, so that X does not start.
[This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
Using FC5 latest version (as of 14/3/07 2:28 EST) and my mouse is still not working. I am using MS Virtual Machine 2004. My mouse was working earlier today when I installed, but as soon as I upgraded my packages, my mouse stopped working. The pointer is displayed but does not move.
(this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug.