Issue #4 new

new WDM device not registred

Anonymous created an issue

Hi i have compiled the loader without problem. - Loaded the uvcvideo kernel module - loaded the firmware to the webcam with ./loader I have no /dev/video* device appaering

  • Reloading the uvcvideo module (modprobe -rv uvcvideo && modprobe -v uvcvideo):

rmmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/uvc/uvcvideo.ko rmmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/compat_ioctl32.ko rmmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/videodev.ko rmmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/v4l1-compat.ko alxgomz@gandalf:~/downloads/drivers/r5u870/uvc/r5u87x$ alxgomz@gandalf:~/downloads/drivers/r5u870/uvc/r5u87x$ alxgomz@gandalf:~/downloads/drivers/r5u870/uvc/r5u87x$ sudo modprobe -v uvcvideo insmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/v4l1-compat.ko insmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/videodev.ko insmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/compat_ioctl32.ko insmod /lib/modules/2.6.27-rc7-vagner/kernel/drivers/media/video/uvc/uvcvideo.ko

giving dmesg: Linux video capture interface: v2.00 usbcore: registered new interface driver uvcvideo USB Video Class driver (v0.1.0) usbcore: deregistering interface driver uvcvideo Linux video capture interface: v2.00 usbcore: registered new interface driver uvcvideo USB Video Class driver (v0.1.0)

but still no /dev/video* and so applications cannot use the webcam.

Comments (14)

  1. Alex Hixon repo owner

    So, the following doesn't work?

    $ hg pull
    # ./loader --force-clear
    # modprobe -r uvcvideo
    # modprobe uvcvideo
    # dmesg | tail
    $ stat /dev/video0
    

    and loader reports positive microcode state?

  2. Anonymous

    No alex, it doesn't work.

    Here is the usb ID of my webcam: 05ca:1834

    and its verbose lsusb.... if it helps:

    Bus 002 Device 003: ID 05ca:1834 Ricoh Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05ca Ricoh Co., Ltd idProduct 0x1834 bcdDevice 1.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 78 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 6 Imaging bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 6 Imaging bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0c00 2x 1024 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 6 Imaging bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x1400 3x 1024 bytes bInterval 1 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered)

  3. Alex Hixon repo owner

    Ah, you're running a WDM model. That would explain why uvcvideo isn't picking it up.

    I've talked to Hans de Goede about writing a kernel module that does the video processing for WDM-based devices and merging that into the mainline kernel.

    At the moment, there's no real solution for this. If you're running an older kernel, you can stick with r5u870, otherwise there's not much that can be done.

    Also, interestingly, you said that loader *successfully* uploaded microcode to the camera? This is interesting, since my understanding (judging from other bug reports) was that they failed if it was a WDM device. Obviously this hasn't occured to you?

  4. Anonymous

    To be honnest I don't really know how to check if the firmware is (correctly) uploaded to the cam. But as you can see below ./loader report no problem:

    $ sudo ./loader Searching for device... Found camera : 05ca:1834 Firmware : ucode/r5u87x-05ca-1834.fw

    Camera reports negative microcode state. Sending microcode to camera... Enabled microcode. Camera reports microcode version 0x0111.

    The r5u870 kernel module works correctly up to version 0.10 (which cannot be compiled against kernel version newer than 2.6.23.17) version 0.11 and 0.11.1 doesn't compil correctly on my system (0.11) or compils and loads but doesn't work properly as all i can see in differents apps is a greenish blury image.

    I hope it can help.

    Thanks for thoose clear explanation of why and how! Successfully uploaded firmware to device 05ca:1834!

  5. Anonymous

    I don't know how useful it can be but i think i have the same issue with a 05ca:1870 (0x0112) cam. i had to uncomment the line in loader.h to let it be discovered because of the dupe issue and microcode succesfully loads, but i have no /dev/video0.. i don't know what a WDM device is ( :-) ) and i don't know if mine is one of them, but maybe this can be somehow useful for you. FYI I've been able to use my webcam with r5u870 up to 2.6.25.x

    thank you for your work ;)

  6. Anonymous

    hi! [root@laptop r5u87x]# uname -r 2.6.26.5-45.fc9.i686 [root@laptop r5u87x]# ./loader Searching for device... Found camera : 05ca:1830 Firmware : ucode/r5u87x-05ca-1830.fw

    Camera reports positive microcode state. Camera reports microcode version 0x0100. Not doing anything - camera already setup. ----- no /dev/video0 device :( maybe this can be useful ...

  7. Anonymous

    Same proplem here but maybe a little bit different. I have tried:

    1. ./loader
    2. modprobe -r uvcvideo
    3. modprobe uvcvideo The firmware is successfully loaded and the uvcvideo module is reloaded but I still didn't have any /dev/video* device.

    When I tried to re-upload the firmware with # ./loader --force-clear I get this: Searching for device... Found camera : 05ca:1830 Firmware : ucode/r5u87x-05ca-1830.fw

    Camera reports positive microcode state. Warning: Failed to reset microcode.

    Error: Failed to upload firmware to device: Broken pipe (code -32).

    I haven't understood what a WDM device is and how can we know if the camera is a WDM device.

  8. Anonymous

    I've got the same results: no video device node.

    This is my console output:

    $ sudo ./loader --force-clear Searching for device... Found camera : 05ca:1870 Firmware : ucode/r5u87x-05ca-1870.fw

    Camera reports negative microcode state. Warning: Not force-clearing because the device has no ucode. Sending microcode to camera... Enabled microcode. Camera reports microcode version 0x0112.

    Successfully uploaded firmware to device 05ca:1870! $ sudo ./loader Searching for device... Found camera : 05ca:1870 Firmware : ucode/r5u87x-05ca-1870.fw

    Camera reports positive microcode state. Camera reports microcode version 0x0112. Not doing anything - camera already setup.

    Successfully uploaded firmware to device 05ca:1870! $ sudo modprobe -r uvcvideo $ sudo modprobe uvcvideo $ dmesg | tail [ 163.728527] Linux video capture interface: v2.00 [ 163.776254] usbcore: registered new interface driver uvcvideo [ 163.777730] USB Video Class driver (v0.1.0) $ stat /dev/video0 stat: cannot stat `/dev/video0': No such file or directory

  9. Anonymous

    The loader script started working for me as soon as I sudoed it (no big deal). However, I had both positive state and "not doing anything" responses, and force-clear still breaks -- basically the same thing going on here. Not sure how important all the individual numbers are, but mine's a little different so I figured I'd put it up for comparison. Basically it gives positive and microcode 0x0100, reloads fine, breaks on force-clear, and then immediately works fine on reload again.

    charidan@Linuxeratops:~/r5u87x$ sudo ./loader
    r5u87x firmware loader v0.2
    
    Searching for device...
    Found camera: 05ca:1833
    Camera reports positive microcode state.
    Camera reports microcode version 0x0100.
    Not doing anything - camera already setup.
    
    Successfully uploaded firmware to device 05ca:1833!
    
    charidan@Linuxeratops:~/r5u87x$ sudo ./loader --reload
    r5u87x firmware loader v0.2
    
    Searching for device...
    Found camera: 05ca:1833
    Camera reports positive microcode state.
    Camera reports microcode version 0x0100.
    Not doing anything - camera already setup.
    
    Successfully uploaded firmware to device 05ca:1833!
    Reloading uvcvideo module...
    Finished.
    
    charidan@Linuxeratops:~/r5u87x$ sudo ./loader --force-clear
    r5u87x firmware loader v0.2
    
    Searching for device...
    Found camera: 05ca:1833
    Camera reports positive microcode state.
    Warning: Failed to reset microcode.
    
    Error: Failed to upload firmware to device: Broken pipe (code -32).
    
    charidan@Linuxeratops:~/r5u87x$ sudo ./loader --reload
    r5u87x firmware loader v0.2
    
    Searching for device...
    Found camera: 05ca:1833
    Camera reports positive microcode state.
    Camera reports microcode version 0x0100.
    Not doing anything - camera already setup.
    
    Successfully uploaded firmware to device 05ca:1833!
    Reloading uvcvideo module...
    Finished.
    
  10. gilesknap

    Hi,

    I am getting exactly the same issues as above in reponse #13.

    I am running Natty Narwhal and my machine is a sony SX2XP with the camera is reported as: 05ca:1830 Ricoh Co., Ltd Visual Communication Camera VGP-VCC2 [R5U870] Which is listed as one of the supported cameras (and hence I assume is not a WDM model - but not sure how to confirm this)

    I see no /dev/video* folder and also get the same error when performing --force-clear.

    removing and restoring uvcvideo with modprobe gives the following output:- [ 1715.804223] USB Video Class driver (v1.0.0) [ 2124.400148] usbcore: deregistering interface driver uvcvideo [ 2132.189553] Linux video capture interface: v2.00 [ 2132.200220] usbcore: registered new interface driver uvcvideo [ 2132.200227] USB Video Class driver (v1.0.0)

    Any pointers appreciated. gilesknap

  11. Log in to comment