On Tue, 19 Jun 2007, David wrote:

> All,
> 
> I have an Asus A8N-SLI motherboard that seems to be having trouble with USB.  
> I was under the impression that it "used to work", but I have only recently 
> started using USB heavily so I do not know if this was my imagination.
> 
> The problem is addressed by question 6 of Troubleshooting in the FAQ, I get 
> repeated "usb 1-5: device not accepting address 9, error -110" errors and 
> devices do not work.  The problems happen to devices plugged into the 
> internal motherboard headers and any external port (using a cable or not), so 
> I assume that this is not the problem.
> 
> I have examined interrupts and there does not seem to be a problem.  When 
> inserting or removing a device the interrupt count increases.  I have toggled 
> the "Plug and Play OS" option in the BIOS which will assign an IRQ to the USB 
> controllers if it is set to off.  Changing this setting only changes the IRQ 
> that is eventually assigned and makes no difference to the errors.  I have 
> also played with various combinations of noapic, noacpi and pci=routeirq (as 
> suggested by dmesg output).
> 
> I have tried with ohci and ehci compiled into the kernel and compiled 
> separately as modules.  With ehci unloaded the error messages seem to be:
> 
> usb 1-4: device descriptor read/64, error -62
> usb 1-4: new full speed USB device using ohci_hcd and address 4
> usb 1-4: device not accepting address 4, error -62
> 
> I am using the latest BIOS for my motherboard, though there is a beta 
> version: 
> A8N-SLI Beta BIOS 1604.  The kernel is 2.6.20 on AMD64 (with Gentoo patches). 
>  
> However, when searching I have found people with similar problems on other 
> distributions.  I compiled 2.6.16 to test and the same problem occurs.
> 
> The output from dmesg and an example /proc/interrupts are below (attaching 
> failed).  If there is any other debugging I can do (recompiling a kernel with 
> debugging etc) then I am happy to do this if somebody can give me a few 
> pointers.

These errors indicate that your computer is completely unable to 
communicate with the USB device.  It could be a problem with the device 
or a problem with the computer.

Do you know that your devices work in a different computer?  Have you 
found any devices that work in your computer?  Can you get hold of a 
USB keyboard and see if it works with the BIOS during setup or 
pre-boot?

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to