Will do.

On Wed, 10 Jul 2002, Brad Hards wrote:

> On Wed, 10 Jul 2002 07:27, Graham TerMarsch wrote:
> > Short version of the problem is the "classic" bulk transfer timeout problem
> > or problems with the devices not accepting their USB ID numbers when given
> > one from usb-uhci.  Our machine that experienced the problems here was an
> > Athlon 1GHz running on an AOpen AK73Pro motherboard, which uses the
> > VIA-686A chipset, all running RH-7.3.  FYI, we also had the same problems
> > on this machine with RH7.1, RH7.2, MDK8.0, and MDK8.1 (SuSE-7.1 worked,
> > but was more than a bit out of date for some of the other things we
> > wanted).
> >
> > After much fighting, pulling of hair, and many long hours spent going
> > through testing out various debug builds, kernel revisions, etc., I
> > finally found a single item that made a total world of difference.....
> >
> >   In the BIOS, take the "Assign IRQ for USB" option and turn it off.
> 
> We have almost this issue in the FAQ. 
> 
> <quote>
> 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. 
> </quote>
> 
> Stephen - can we add something like this BIOS setting issue to the second 
> para? Just to make it a bit more explicit.
> 
> 

-- 
 /------------------------------------+-------------------------\
|Stephen J. Gowdy                     | SLAC, MailStop 34,       |
|http://www.slac.stanford.edu/~gowdy/ | 2575 Sand Hill Road,     |
|http://calendar.yahoo.com/gowdy      | Menlo Park CA 94025, USA |
|EMail: [EMAIL PROTECTED]       | Tel: +1 650 926 3144     |
 \------------------------------------+-------------------------/



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Stuff, things, and much much more.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to