Please refer to the below Q & A from the USB FAQ. One of our customers
is seeing this behaviour right now. The weird bit is that the setup has
worked in the past, and as far as I know, the hardware or BIOS (or OS
installation) haven't changed at all. Any ideas what might cause this
problem to start occurring all of a sudden?
Mainboard: Abit KD7
OS: Red Hat Linux 7.3
Kernel: 2.4.18-17.7.x
--
Q: Why doesn't USB work at all? I get "device not accepting address"
A: You may have some problem with your PCI setup that's preventing your
USB host controller from getting hardware interrupts. When Linux submits
a request, but never hears back from the controller, this is the
diagnostic you'll see. To see if this is the problem, look at
/proc/interrupts to see if the interrupt count for your host controller
driver ever goes up. If it doesn't, this is the problem: either your
BIOS isn't telling the truth to Linux (ACPI sometimes confuses these
things, or setting the expected OS to windows in your BIOS), or Linux
doesn't understand what it's saying.
Sometimes a BIOS fix will be available for your motherboard, and in
other cases a more recent kernel will have a Linux fix. You may be able
to work around this by passing the noapic boot option to your kernel, or
(when you're using an add-in PCI card) moving the USB adapter to some
other PCI slot. If you're using a current kernel and BIOS, report this
problem to the Linux-kernel mailing list, with details about your
motherboard and BIOS.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list