From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020712 Description of problem: The ps/2 mouse is not detected during installation when using a USB keyboard. Switching to a ps/2 keyboard (and restaring installer) resolves the issue. Tried different mice, one Genius, one Logitech and one MS ps/2 mouse. The mouse works fine with a USB keyboard after installation. Version-Release number of selected component (if applicable): limbo beta 2, limbo2 How reproducible: Always Steps to Reproduce: 1.Plug in ps/2 mouse and USB keyboard 2.Boot limbo2 CD 3.anaconda detects no mouse at all Additional info: May be a vendor specific problem. I only tried this on an A/Open motherboard.
Will investigate.
This is kernel or hw related - on my hw if I leave the PS/2 keyboard plugged in until just before the kernel finishes booting and /sbin/linuxrc starts, the mouse will show up.
msf: *USB* keyboard
I cannot get the PS/2 mouse to be detected at all unless I have the PS/2 keyboard also plugged long enough for the kernel to see it. This is with the hw I have available easily. Whether or not the USB keyboard is plugged in is not relevant. Apparently some hw, or the kernel, or some combination of factors, does not register a PS/2 mouse unless the PS/2 keyboard is also present.
Dr. Mike, please try 2.4.18-11 when it finishes build. <zaitcev> Why does it happen in BOOT kernel only? <arjan> in the ps2-mouse-only case, the broken code would fail the very first open of /dev/psaux <arjan> but succeed all later <arjan> guess what, anaconda is the first <arjan> while kudzu's probing opens it a few times <arjan> so you only effectively see it during install
Seems to work now thanks.
I'm still seeing a failure with kernel-2.4.18-12.5. If I have the PS/2 mouse and the USB keyboard, then the installer doesn't see the mouse. If I plug back in the PS/2 keyboard (still leaving the USB keyboard attached) and rerun the installer, then both keyboards and the mouse work.
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/