Webcam Logitech C310 detected but not working on Buster

Getting your soundcard to work, using Debian on non-i386 hardware, etc

Webcam Logitech C310 detected but not working on Buster

Postby jlinkels » 2020-06-05 00:52

This is a completely fresh installation of Debian 10.4.0-amd64
Kernel 4.19.0.9-amd64

The webcam is detected, driver is loaded but it cannot be accessed for recording video. Device is recognized, node is created correctly, permissions are right. v4l sees the camera. Only getting a picture from the camera fails.

I get the strong suspicion that this is a kernel/driver issue. I have found not bug reports (yet?). Webcam used to work on Stretch. Still works on Jessie.

For what it matters, during debugging I have applied ugo+rwx permissions to both /dev/bus/usb/002/006 and /dev/video. No difference.

Code: Select all
lsusb:
Bus 002 Device 006: ID 046d:081b Logitech, Inc. Webcam C310


Code: Select all
ll /dev/bus/usb/002/006
crw-rw-r--  1 root root 189, 133 Jun  5 01:04 /dev/bus/usb/002/006


Code: Select all
jlinkels@donald-pc:~$ ll /dev/video*
crw-rw----+ 1 root video 81, 0 Jun  5 01:04 /dev/video0
crw-rw----+ 1 root video 81, 1 Jun  5 01:04 /dev/video1
jlinkels@donald-pc:~$ getfacl /dev/video*
getfacl: Removing leading '/' from absolute path names
# file: dev/video0
# owner: root
# group: video
user::rw-
user:jlinkels:rw-
group::rw-
group:video:rw-
mask::rw-
other::---

# file: dev/video1
# owner: root
# group: video
user::rw-
user:jlinkels:rw-
group::rw-
group:video:rw-
mask::rw-
other::---


This is the part in dmesg where the camera is not installed:
Code: Select all
[   12.419494] uvcvideo: Found UVC 1.00 device <unnamed> (046d:081b)
[   12.447588] usbcore: registered new interface driver snd-usb-audio
[   12.457165] uvcvideo 2-1.3.1:1.0: Entity type for entity Extension 4 was not initialized!
[   12.457169] uvcvideo 2-1.3.1:1.0: Entity type for entity Extension 6 was not initialized!
[   12.457172] uvcvideo 2-1.3.1:1.0: Entity type for entity Extension 7 was not initialized!
[   12.457174] uvcvideo 2-1.3.1:1.0: Entity type for entity Processing 2 was not initialized!
[   12.457176] uvcvideo 2-1.3.1:1.0: Entity type for entity Extension 3 was not initialized!
[   12.457179] uvcvideo 2-1.3.1:1.0: Entity type for entity Camera 1 was not initialized!
[   12.457321] input: UVC Camera (046d:081b) as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3.1/2-1.3.1:1.0/input/input19
[   12.457447] usbcore: registered new interface driver uvcvideo
[   12.457449] USB Video Class driver (1.1.1)


Googling told me that
Code: Select all
Entity type for entity Camera 1 was not initialized!
is not necessarily a fatal error.

Code: Select all
jlinkels@donald-pc:/usr/lib/udev/rules.d$ lsmod | grep uvc
uvcvideo              118784  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_v4l2         28672  1 uvcvideo
videobuf2_common       53248  2 videobuf2_v4l2,uvcvideo
videodev              212992  3 videobuf2_v4l2,uvcvideo,videobuf2_common
media                  45056  2 videodev,uvcvideo
usbcore               294912  8 ehci_pci,snd_usb_audio,usbhid,snd_usbmidi_lib,usb_storage,uvcvideo,ehci_hcd,uas


Code: Select all
jlinkels@donald-pc:/usr/lib/udev/rules.d$ v4l2-ctl --list-devices
UVC Camera (046d:081b) (usb-0000:00:1d.0-1.3.1):
        /dev/video0
        /dev/video1




This is what I see when I play the camera in mplayer:
Code: Select all
mplayer tv://

Code: Select all
Playing tv://.
TV file format detected.
Selected driver: v4l2
 name: Video 4 Linux 2 input
 author: Martin Olschewski <olschewski@zpr.uni-koeln.de>
 comment: first try, more to come ;-)
v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.
Selected device: UVC Camera (046d:081b)
 Capabilities:  video capture  streaming
 supported norms:
 inputs: 0 = Camera 1;
 Current input: 0
 Current format: YUYV
tv.c: norm_from_string(pal): Bogus norm parameter, setting default.
v4l2: ioctl enum norm failed: Inappropriate ioctl for device
Error: Cannot set norm!
Selected input hasn't got a tuner!
v4l2: ioctl set mute failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
[vdpau] Error when calling vdp_device_create_x11: 1
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 58.35.100 (external)
Mismatching header version 58.18.100
Selected video codec: [ffmjpeg] vfm: ffmpeg (FFmpeg MJPEG)
==========================================================================
v4l2: ioctl streamon failed: No space left on device
Audio: no sound
Starting playback...


MPlayer interrupted by signal 2 in module: video_read_frame
[mjpeg @ 0x7fe34752e820]No JPEG data found in image
Error while decoding frame!


And this happens when I open Cheese:
Code: Select all
(cheese:3834): cheese-WARNING **: 01:34:24.143: Failed to allocate required memory.: gstv4l2src.c(658): gst_v4l2src_decide_allocation (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin28/GstV4l2Src:v4l2src1:
Buffer pool activation failed
jlinkels
 
Posts: 40
Joined: 2008-07-12 14:34

Re: Webcam Logitech C310 detected but not working on Buster

Postby andre@home » 2020-06-05 06:07

I found this topic on similar problems, if you click via it you find possible pathways for a given solution.

https://www.raspberrypi.org/forums/view ... p?t=252590
https://www.raspberrypi.org/forums/view ... &p=1515246
Ultimately you get to this:
https://unix.stackexchange.com/a/539573
More on the UVC drivers here: https://www.ideasonboard.org/uvc/
Where you also see that your Logitech should be supported by it:
046d:081d Logitech Webcam C310 Logitech V
andre@home
 
Posts: 386
Joined: 2011-10-02 08:00

Re: Webcam Logitech C310 detected but not working on Buster

Postby jlinkels » 2020-06-05 15:15

Thank you.

Yes, I had seen all those pages before I posted here. It is correct that I see 2 devices. /dev/video0 and /dev/video1.

I assume 1 device is for metadata and the other device for the actual stream. So running v4l2-ctls gives:

Code: Select all
jlinkels@donald-pc:~$ v4l2-ctl --list-formats -d /dev/video0
ioctl: VIDIOC_ENUM_FMT
        Type: Video Capture

        [0]: 'YUYV' (YUYV 4:2:2)
        [1]: 'MJPG' (Motion-JPEG, compressed)


and

Code: Select all
jlinkels@donald-pc:~$ v4l2-ctl --list-formats -d /dev/video1
ioctl: VIDIOC_ENUM_FMT
        Type: Video Capture



In mplayer I can select either of the two devices:

Code: Select all
jlinkels@donald-pc:~$ mplayer tv:// -tv device=/dev/video0
MPlayer 1.3.0 (Debian), built with gcc-8 (C) 2000-2016 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing tv://.
TV file format detected.
Selected driver: v4l2
 name: Video 4 Linux 2 input
 author: Martin Olschewski <olschewski@zpr.uni-koeln.de>
 comment: first try, more to come ;-)
v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.
Selected device: UVC Camera (046d:081b)
 Capabilities:  video capture  streaming
 supported norms:
 inputs: 0 = Camera 1;
 Current input: 0
 Current format: YUYV
tv.c: norm_from_string(pal): Bogus norm parameter, setting default.
v4l2: ioctl enum norm failed: Inappropriate ioctl for device
Error: Cannot set norm!
Selected input hasn't got a tuner!
v4l2: ioctl set mute failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
[vdpau] Error when calling vdp_device_create_x11: 1
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 58.35.100 (external)
Mismatching header version 58.18.100
Selected video codec: [ffmjpeg] vfm: ffmpeg (FFmpeg MJPEG)
==========================================================================
v4l2: ioctl streamon failed: No space left on device
Audio: no sound
Starting playback...
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
V:   0.0   9/  9 ??% ??% ??,?% 0 0
[mjpeg @ 0x7f65a1064820]No JPEG data found in image
Error while decoding frame!
V:   0.0  10/ 10 ??% ??% ??,?% 0 0
[mjpeg @ 0x7f65a1064820]No JPEG data found in image


Code: Select all
jlinkels@donald-pc:~$ mplayer tv:// -tv device=/dev/video1
MPlayer 1.3.0 (Debian), built with gcc-8 (C) 2000-2016 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing tv://.
TV file format detected.
Selected driver: v4l2
 name: Video 4 Linux 2 input
 author: Martin Olschewski <olschewski@zpr.uni-koeln.de>
 comment: first try, more to come ;-)
v4l2: ioctl get format failed: Invalid argument
v4l2: ioctl set mute failed: Inappropriate ioctl for device
v4l2: 0 frames successfully processed, 0 frames dropped.

Exiting... (End of file)


In Cheese I can also select a device. But neither of the 2 devices generate a video stream. It should be clear that I have successfully tested displaying the webcam in Mplayer on a different PC with an older Debian version. On that laptop I do have 2 webcams and I can select the device I want.

Although it is an extra complication that 2 devices are created, I don't see why at least one of them should not play video.

The tip on StackExchange to create an additional device does not seem to be useful. Unless there is a limitation in the recording or playback application which limits the selecting of a certain device.

Having a device recording video cannot be THAT complicated, even if 2 devices are created when plugged in.

jlinkels
jlinkels
 
Posts: 40
Joined: 2008-07-12 14:34

SOLVED Webcam Logitech C310 detected but not working on Bust

Postby jlinkels » 2020-06-05 18:10

OK, I plugged the webcam directly into an USB 3.0 port on the computer instead of the hub and it worked right away.

It had been working for years like that in the hub. :?:

jlinkels
jlinkels
 
Posts: 40
Joined: 2008-07-12 14:34

Re: Webcam Logitech C310 detected but not working on Buster

Postby andre@home » 2020-06-05 19:57

Great... good you tried. :mrgreen:

Of course I did not/never realized you were using a hub. They can be faulty, also for some external hard disks....
Direct connection of such hardware is mostly preferred, the combi of simple things like a mouse+ keyboard often has a wider tolerance.
It is clear that distance does not help, it would not be one of the first questions I'v asked, and maybe would never have asked it...to be honest.. :roll:
Good luck continuing your Debian's !
andre@home
 
Posts: 386
Joined: 2011-10-02 08:00

Re: Webcam Logitech C310 detected but not working on Buster

Postby eriefisher » 2020-06-05 20:49

I have found with USB hubs it will matter whether they are powered or not. Some devices don't like powered hubs, others require it to work properly.
____________________________________________
There's a manual?
Siduction
Debian Sid
Xfce4 4.14
User avatar
eriefisher
 
Posts: 114
Joined: 2008-06-04 03:49
Location: Ontario's South Coast

Re: Webcam Logitech C310 detected but not working on Buster

Postby jlinkels » 2020-06-05 20:55

This is a powered one. But like I wrote before, it has worked like this for years.
jlinkels
 
Posts: 40
Joined: 2008-07-12 14:34

Re: Webcam Logitech C310 detected but not working on Buster

Postby andre@home » 2020-06-06 06:29

This are sometimes very difficult things to trace back.

What did change in the system trough updates that may have influences?

Or what does the time do with the power supply of the USB-hub? As such power supplies are nowadays mostly a high frequency switching type.... what if alteration leads to some disturbing harmonic or a spurious signal... on the USB cable that cause EMC-like complete disfunctioning of the camera? Cause: a capacitor that fails to do his work anymore to suppress such signal? Who knows...
You may try another power supply with the right specs?

EMC: https://en.wikipedia.org/wiki/Electroma ... patibility
andre@home
 
Posts: 386
Joined: 2011-10-02 08:00


Return to Hardware

Who is online

Users browsing this forum: No registered users and 12 guests

fashionable