USB camera - device not accepting address .., error -110
 

Hi,

I'm trying to get my USB camera to work with my RedHat Fedora Core 2 (kernel 2.6.5-1.358) box. According to the documentation, I should use spca5xx driver. I've installed and loaded the required drivers but when I plugged in my camera, here's what's happening:

May 13 14:35:45 linux kernel: Linux video capture interface: v1.00
May 13 14:35:45 linux kernel: usbcore: registered new driver spca5xx
May 13 14:35:45 linux kernel: /usr/local/spca5xx-20050501/drivers/usb/spca5xx.c: spca5xx driver 00.56.02 registered
May 13 14:36:29 linux kernel: usb 1-2: new full speed USB device using address 4
May 13 14:36:30 linux kernel: usb 1-2: device not accepting address 4, error -110
May 13 14:36:30 linux kernel: usb 1-2: new full speed USB device using address 5
May 13 14:36:30 linux kernel: usb 1-2: device not accepting address 5, error -110

Now, I've tested the device with another box (Windows XP Professional) and it works.

I've read a bit on Linux USB FAQ _http://www.linux-usb.org/FAQ.html

...

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.

... but that's not the case for me.

I'm lost now... Does anyone have any idea? Documentation I should read?

Thanks a lot!

Nathalie.

Good research!

One tact you might want to take is to go into BIOS and see if you can hand assign an IRQ to the USB host controller, look under PCI devices as the controller in and of itself is just another PCI device.

The other... upgrade the kernel. 2.6.5 is pretty stodgy, and a lot of mileage has been logged with ACPI and USB with 2.6 since that old puppy rolled off the line.

Also, you could just try and cheat, and add to grub.conf for your boot kernel the option: noacpi

Cheers,

Finegan

I've upgraded my kernel to 2.6.10. Here's the content of my system logs now:
...
May 22 11:21:09 muaddib kernel: usb 1-1: new full speed USB device using ohci_hcd and address 2
May 22 11:21:09 muaddib kernel: usb 1-1: device not accepting address 2, error -110
May 22 11:21:09 muaddib kernel: usb 1-1: new full speed USB device using ohci_hcd and address 3
May 22 11:21:09 muaddib kernel: usb 1-1: device not accepting address 3, error -110
May 22 11:21:09 muaddib kernel: usb 1-1: new full speed USB device using ohci_hcd and address 4
May 22 11:21:09 muaddib kernel: usb 1-1: device descriptor read/64, error -110
May 22 11:21:09 muaddib kernel: usb 1-1: device descriptor read/64, error -110
May 22 11:21:09 muaddib kernel: usb 1-1: new full speed USB device using ohci_hcd and address 5
May 22 11:21:09 muaddib kernel: usb 1-1: device descriptor read/64, error -110
May 22 11:21:09 muaddib kernel: usb 1-1: device descriptor read/64, error -110
...

What does pci=noacpi do?

Thanks,
Nathalie.

Another question...

Instead of manually do a modprobe videodev and modprobe spca5xx. How do I make the modules load at boot time?

Thanks again,
Nathalie.

Hi,

I finally decided to test my RH distro (kernel 2.6.10) on my other box that used to host Windows XP and everything works fine. I use the spca5xx driver and spcaview tool that I've downloaded from http://mxhaard.free.fr/download.html.

I was told that the important thing with that device (VA11A) is to load the module with the usbgrabber parameter set to 1 (modprobe spca5xx usbgrabber=1).

Thanks for all your help and advice.

Regards,
Nathalie.