Hmmm...thousands of users and no one knows how to diagnose a USB keyboard issue.
Interesting.
Well, I made at least some possibility of progress. ehci_hcd (The USB controller driver)
seemed to want to use IRQ10, the same IRQ that libata and the NIC card were using.
So, not knowing how to resolve (possible?) IRQ conflicts in Linux, I just tried moving all
my PCI cards around to different slots. No difference. The keyboard could work
consistently, but I still couldn't get an IP address bound to the NIC card.
This leads me to some questions:
1. As I understand it, if you're using ACPI, then you can't force IRQs in the BIOS setup.
Can anyone confirm this?
2. Is there any way to force an onboard component, such as the NIC, to use a certain
IRQ or memory range, or is that fixed?
3. If I can't do either of the above, do I have to reinstall Linux to disable ACPI, or can I
just make a few changes?
Next I went hunting down BIOS information for my Abit NF7-S:
http://www.nforcershq.com/forum/viewtopic.php?t=22264
llists this changelog for BIOS update 2.4 for the ver 2.0 boards:
"Fixed the issue that PS/2 wheel mouse is no response under limited condition:
A. Use certain PS/2 wheel mouse and certain USB keyboard.
B. PS/2 wheel mouse works fine but lose response on 1st, 3rd, 5th.... restarting
windows. Nevertheless, it works fine on 2nd, 4th.... restarting windows. "
Now, this may be a slim chance, but I'm guessing this bios update might fix something
having to do with USB interrupts or similar?
Anyone care to hazard an opinion or more information? I'm getting pretty desperate
here....
Thanks
newmoon