usb2 webcam only recognised as usb1.1 device

Bug #133266 reported by Robert Persson
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When I plug my logitech quickcam chat into an NEC pci usb 2.0 card, it is only recognised as a usb 1.1 device, even though it is in fact a usb 2.0 device. This leaves the camera fairly crippled because it is only possible to capture video at very low resolution.

By contrast, my scanner is correctly recognised as a usb 2.0 device. I have tried swapping the two devices about just in case it was a problem with one particular usb port, but this did not make a difference.

Here's what dmesg gave me:

robert@brian:~$ dmesg|grep USB
[ 48.211204] USB Universal Host Controller Interface driver v3.0
[ 48.254571] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[ 8.300000] uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
[ 8.304000] hub 1-0:1.0: USB hub found
[ 8.408000] uhci_hcd 0000:00:04.3: new USB bus registered, assigned bus number 2
[ 8.412000] hub 2-0:1.0: USB hub found
[ 8.516000] ohci_hcd 0000:00:0a.0: new USB bus registered, assigned bus number 3
[ 8.600000] hub 3-0:1.0: USB hub found
[ 8.704000] ohci_hcd 0000:00:0a.1: new USB bus registered, assigned bus number 4
[ 8.788000] hub 4-0:1.0: USB hub found
[ 8.892000] ehci_hcd 0000:00:0a.2: new USB bus registered, assigned bus number 5
[ 8.916000] ehci_hcd 0000:00:0a.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 8.916000] hub 5-0:1.0: USB hub found
[ 9.040000] usb 2-2: new full speed USB device using uhci_hcd and address 2
[ 9.212000] hub 2-2:1.0: USB hub found
[ 10.008000] usb 5-4: new high speed USB device using ehci_hcd and address 3
[ 10.456000] usb 3-2: new full speed USB device using ohci_hcd and address 2
[ 43.048000] ubuntu/media/gspcav1/gspca_core.c: USB SPCA5XX camera found.(SPCA561A)
[ 1903.504000] usb 3-2: USB disconnect, address 2
[ 1916.308000] usb 4-1: new full speed USB device using ohci_hcd and address 2
[ 1916.524000] ubuntu/media/gspcav1/gspca_core.c: USB SPCA5XX camera found.(SPCA561A)
[ 1959.452000] usb 4-1: USB disconnect, address 2
[ 1961.340000] usb 5-4: USB disconnect, address 3
[ 1965.624000] usb 4-2: new full speed USB device using ohci_hcd and address 3
[ 1965.840000] ubuntu/media/gspcav1/gspca_core.c: USB SPCA5XX camera found.(SPCA561A)

Here's what I got from lspci:

00:0a.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI])
        Subsystem: NEC Corporation Hama USB 2.0 CardBus
        Flags: bus master, medium devsel, latency 32, IRQ 11
        Memory at df800000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

00:0a.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10 [OHCI])
        Subsystem: NEC Corporation Hama USB 2.0 CardBus
        Flags: bus master, medium devsel, latency 32, IRQ 9
        Memory at df000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

00:0a.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20 [EHCI])
        Subsystem: Unknown device 0ee4:3383
        Flags: bus master, medium devsel, latency 32, IRQ 11
        Memory at de800000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2

In Kinfocenter's listings of usb devices, the scanner is listed as being subject to an EHCI host controller, whereas the camera appears to be under an OHCI controller.

This is what Kinfocenter tells me about the scanner:

EPSON Scanner

Manufacturer: EPSON

Class
255
Subclass
0
Protocol
0
USB Version
2.00

Vendor ID
0x4b8
Product ID
0x11e
Revision
1.00

Speed
480 Mbit/s
Channels
0
Max. Packet Size
0

And this is what it tells me about the camera:

Camera

Manufacturer:

Class
255
Subclass
0
Protocol
0
USB Version
1.10

Vendor ID
0x46d
Product ID
0x92e
Revision
0.00

Speed
12 Mbit/s
Channels
0
Max. Packet Size
0

Revision history for this message
Gerald Murray (gmurray) wrote :

The bug report should be changed to "need driver for quickcam pro".

The camera is being reported as usb 1.1 because the camera is using vendor-specific protocol.
Using usb 1.1 to communicate with the device is the default behaviour. When a driver
is found for the camera, it will claim the device and use high speed.
This is not a bug with USB.

Revision history for this message
Robert Persson (ireneshusband) wrote :

The camera uses the gspca driver. The driver definitely gets loaded because I can watch the video stream it produces in ekiga etc. The problem is that I can only get the stream at low resolution because of the narrow bandwidth of usb 1.1.

Revision history for this message
Robert Persson (ireneshusband) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Robert Persson (ireneshusband) wrote :

I am currently using Hardy and I am still getting the same problem unfortunately.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Please include the following additional information, (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
* Please include the output of the command "uname -a" in your next response.
* Please run the command "dmesg > dmesg.log" after a fresh boot (with the cam plugged in) and attach the resulting file "dmesg.log" to this bug report.
* Please run the command "sudo lspci -vvnn > lspci-vvnn.log" (with the cam plugged in) and attach the resulting file "lspci-vvnn.log" to this bug report.
* Please run the command "sudo lsusb -v > lsusb-v.log" (with the cam plugged in) and attach the resulting file "lsusb-v.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies

Thanks in advance!

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.