Description of problem: We are having problems with USB mice (and keyboards) on RHEL 4 (U2) using HP dc7600C desktop computers: - when using an USB mouse and keyboard, only the mouse works in the installer. The keyboard does not work at all, even the leds for caps lock and scroll do not work. (both text and graphical install) - When using a PS/2 mouse instead (together with the USB keyboard), everything works ok (installation and running RHEL). - When I now reboot and change to the USB mouse again, the keyboard does not work (kudzu starts and detects the change, but I cannot confirm it as the keyboard does not work ...). I noted that there was a kernel error message when booting with the USB mouse: i8042.c: Can't read CTR while initializing i8042. I reproduced this with several HP dc7600C computers, mice and keyboards. I am having the same problem with FC4, but not with FC3.
20 against 1 bet it's BIOS. The proper course of action is to request a BIOS update from HP. Sometimes it helps to find and disable a "USB Legacy" seting, if BIOS setup provides it. The U3 may help with usb-handoff option. Please open a separate bug for FC4.
Ok, I tried the latest and gratest HP BIOS update from their website - same problem with this (should have tried this earlier ...). Then I downloaded the U3 beta. Without any options, the problem is still the same. However, the usb-handoff option works fine for both install and running. Thanks a lot! Hm, what should I do with this now: - ask HP for a fix? Never tried this before. Never had to do with their desktop hardware (and support) before, but I suspect this would be rather difficult. - open another bug for FC4? I suppose usb-handoff patch will be in FC5, too, right? - As this is a hardware problem, this bug can be closed, right?
FC5 not only has usb-handoff, but also has it on by default. FC4 with "yum update" should have the handoff code, and need the option to turn it on. Asking HP for a fix may be productive, but may be not. It's not undeard of to get a fix... Dell fixed such problems for us, for example (bug 165749). I cannot predict how responsive HP is going to be. The bug should be closed, yes.
Thanks a lot! I am closing the bug. I will try to ask HP to fix this bug.