Red Hat Bugzilla – Bug 118655
Logitech wireless mouse unresponsive after install of FC2T1
Last modified: 2015-01-04 17:05:00 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 Description of problem: Upon starting installtion of FC2 Test 1 my wireless keyboard and mouse stoped working when the cd booted. I checked bugzilla and found a similar bug report that said to update my bios. I did that, and my keyboard and mouse both worked great during the installation. After the installation completed my PC booted into X. My wireless keyboard now works just fine, but my wireless mouse is unresponsive. Both connect via a reciever to the PS/2 ports on my computer. I can plug a usb mouse into the computer and it is automatically detected and works just fine. I ran mouseconfig and tried everything that looked like a possible match, but I didn't have any luck. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Boot to runlevel 5 2. 3. Actual Results: Mouse does not work, I have seen no error messages. Additional info:
I have a bit of new information about this problem. It seems that the system ALWAYS boots with the wireless keyboard up, and the wireless mouse down. If I unplug the mouse side of the reciever, wait a few seconds, then plug it back in, the mouse begins to respond again. I thought maybe hotplug or kudzu might have changed something so I diff'd the output from lsmod before and after the mouse started working, but there were no changes. Could this be a problem with the ps/2 mouse driver and some sort of timeout?
If I unplug and plug the wireless receiver's mouse cord twice the wireless mouse pops on. After I did that I found this in the dmesg logs: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
Those error messages are kernel messages, not X server messages... reassigning to kernel...
any better with the current 2.6.9 update ?
Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you.