Description of problem: On dell i8100 (and dell i8200) fedora core test 3 is installed using only the touch pad. After plugging in a logitech usb wheel mouse some time after install kudzu wants to add a Generic Mouse (PS/2) at each subsequent reboot until told to ignore. Both 'mice', the touch pad and the usb mouse, work OK Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Is it consistent - if you re-run kudzu after unplugging the USB mouse, the PS/2 mouse appears to go away?
Is this what you intended: 1. boot laptop 2. unplug usb mouse 3. reboot laptop I have done this 3 times and the kudzu message did not reappear. I also did the following 3 times: 1) boot laptop 2) unplug usb mouse 3) reboot laptop 4) plug in usb mouse 5) reboot laptop Again the Generic Mouse(PS/2) message did not reappear. I also ran kudzu -p a couple of times in a console, again nothing. After I had seen this kudzu message a couple of times (before bugzillaing it) I told kudzu to 'ignore' it. Does this 'ignore' leave a persistent 'checkmark' somewhere? PS /etc/sysconfig/hwconf has an entry: 'usbprod: USB-PS/2 Optical Mouse'.
Yes, 'ignore' leaves a permanent 'don't worry about this device' entry. What does your /etc/sysconfig/hwconf look like?
It is very possible this kudzu message is NOT related to the usb mouse. Yesterday I installed test3 on a dell inspiron 8200 without the usb mouse plugged in. (the i8200 has an Alps GlidePoint/Stickpointer/Touchpad). After install the stickpointer/touchpad worked perfectly and 'XF86Config' and 'hwconf' had the correct entries. Without plugging in the usb mouse I rebooted the laptop. Kudzu promptly came up with the same message that it wants to add a Generic PS/2 mouse. I have neither configured the mouse from the kudzu prompt nor 'ignored' it. I have also not plugged in the usb mouse yet. If you want me to test anything just ask.
This should be fixed when kudzu-1.1.35-1 is used in an install environment. *** This bug has been marked as a duplicate of 107679 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.