Red Hat Bugzilla – Bug 143813
Mouse not working after install
Last modified: 2015-01-04 17:14:32 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Description of problem: I installed Fedora Core 3 using noprobe, because it wouldn't work any other way. While booting up, it freezes at "finding new hardware", so I have to enter interactive mode and disable starting kudzu so that the system will start. When I do boot into the system, I find that my USB mouse (Microsoft Explorer Optical) doesn't work. I can't move the pointer at all. This was an upgrade from Fedora Core 2, and the xorg.conf file I used successfully in FC2 remained unchanged. Version-Release number of selected component (if applicable): kudzu-1.1.95-1 How reproducible: Always Steps to Reproduce: 1. Install Fedora Core 3 2. Boot 3. Actual Results: Cannot use mouse to move pointer Expected Results: Should be able to use mouse Additional info:
Created attachment 109153 [details] my xorg.conf file
Created attachment 109154 [details] output from dmesg
The kernel version I'm using is 2.6.9-1.681_FC3
I got the same results with 2.6.9-1.667
Same problem was here when installing Fedora Core 3 (fc3) from scratch (so no update). After installation, in the first boot, the system went to kudzu (?) and wanted the finalize the installation, asking date+time, monitor type and such. The system was very difficult to handle then, because there was no working mouse and some windows didn't have any keyboard shortcuts to go futher or the shortcuts didn't somehow work. For example in a stage, "Please select resolution" nothing worked. Finally I remembered Ctrl+Shift+NumLock trick to enable keyboard's numpad's mouse emulation in X. I believe it expected to find PS/2 mouse, as there is such a port in the machine, but there is no PS2-mouse though. The machine has/had 3-button serial MouseSystems mouse and also Bluetooth HID mouse and Bluetooth dongle. But those mouses were not recognized although they both worked well in fc1 and fc2 and also in fc3 the HID Bluetooth mouse was "easily" configured manually later when the first boot was complete. So, I think there should be some mouse test in the start of Kudzu before anytyhing else, and also note that if mouse doesn't work, one can use Ctrl+Shift+Numlock trick to emulate mouse. For me this problem was easy to go around, but I'd think many who are installing Linux distribution for the first time couldn't have gone through the first boot in any other way but disabling kudzu with 'I'nteractive mode, which then again is not suitable for novices. (btw, I don't think this is a Platform dependent bug, so changing i686 to All would be right.)
Kernel 2.6.10-1.741_FC3 seems to fix this.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
This seems to have only been a problem with kernel 2.6.9. When I updated to kernel 2.6.10, the problem disappeared. Fedora Core 4 does not seem to have this problem. As far as I'm concerned, this bug is fixed.