Weird bug. My webcam is listed twice dmesg [ 3.264159] uvcvideo: Found UVC 1.00 device USB 2.0 UVC VGA WebCam (13d3:5710) [ 3.270673] input: USB 2.0 UVC VGA WebCam: USB2.0 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input20 ls -ltrh /dev/video* crw-rw----+ 1 root video 81, 1 24.03.2018 15:03 /dev/video1 crw-rw----+ 1 root video 81, 0 24.03.2018 15:03 /dev/video0 v4l2-ctl --list-devices USB 2.0 UVC VGA WebCam: USB2.0 (usb-0000:00:1a.0-1.3): /dev/video0 /dev/video1 [fademind@manjaro ~]$ xinput [[ cuted ]] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ USB 2.0 UVC VGA WebCam: USB2.0 id=14 [slave keyboard (3)] lsmod [fademind@manjaro ~]$ lsmod |grep uvc uvcvideo 106496 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_v4l2 28672 1 uvcvideo videobuf2_common 49152 2 uvcvideo,videobuf2_v4l2 videodev 208896 3 uvcvideo,videobuf2_common,videobuf2_v4l2 media 45056 2 uvcvideo,videodev usbcore 290816 6 uvcvideo,usbhid,ehci_hcd,xhci_pci,xhci_hcd,ehci_pci lsusb details Bus 001 Device 003: ID 13d3:5710 IMC Networks UVC VGA Webcam Xorg log [fademind@manjaro ~]$ cat /var/log/Xorg.0.log|grep VGA [ 3.769] (II) intel(0): Output VGA1 has no monitor section [ 3.769] (II) intel(0): Enabled output VGA1 [ 4.225] (II) config/udev: Adding input device USB 2.0 UVC VGA WebCam: USB2.0 (/dev/input/event12) [ 4.225] (**) USB 2.0 UVC VGA WebCam: USB2.0 : Applying InputClass "evdev keyboard catchall" [ 4.225] (**) USB 2.0 UVC VGA WebCam: USB2.0 : Applying InputClass "libinput keyboard catchall" [ 4.225] (**) USB 2.0 UVC VGA WebCam: USB2.0 : Applying InputClass "system-keyboard" [ 4.226] (**) USB 2.0 UVC VGA WebCam: USB2.0 : Applying InputClass "Keyboard Defaults" [ 4.226] (II) Using input driver 'libinput' for 'USB 2.0 UVC VGA WebCam: USB2.0 ' [ 4.226] (**) USB 2.0 UVC VGA WebCam: USB2.0 : always reports core events [ 4.226] (II) event12 - USB 2.0 UVC VGA WebCam: USB2.0 : is tagged by udev as: Keyboard [ 4.226] (II) event12 - USB 2.0 UVC VGA WebCam: USB2.0 : device is a keyboard [ 4.226] (II) event12 - USB 2.0 UVC VGA WebCam: USB2.0 : device removed [ 4.251] (II) XINPUT: Adding extended input device "USB 2.0 UVC VGA WebCam: USB2.0 " (type: KEYBOARD, id 14) [ 4.252] (II) event12 - USB 2.0 UVC VGA WebCam: USB2.0 : is tagged by udev as: Keyboard [ 4.252] (II) event12 - USB 2.0 UVC VGA WebCam: USB2.0 : device is a keyboard [fademind@manjaro ~]$ Only device as video0 works. Any ideas whats goin on here?? Thanks
On Sat, Mar 24, 2018 at 02:34:28PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=199193 > > Bug ID: 199193 > Summary: UVC VGA WebCam: USB2.0 is listed as two video devices > Product: Drivers > Version: 2.5 > Kernel Version: linux416 4.16.r180324.g99fec39-1 All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release.
Thanks for feedback. E-Mail was sent. Regards
Hi, I found the thread on http://www.spinics.net/lists/linux-usb/msg167290.html. But I don't now how to sent an e-mail for that particular thread on linux-usb@vger.kernel.org. This is just to report that i have the same bug on all laptop i have access (Asus UX31A, UX305FA, UX330UA). The bug started on kernel 4.16 and is not present on the previous kernel. So it should be easily reproducible on every laptop with an integrated webcam. Thanks, Tasev
Apparently this is a 'feature' introduced by commit that went in kernel 4.16: 088ead25524583e2200aa99111bea2f66a86545a. media: uvcvideo: Add a metadata device node Some UVC video cameras contain metadata in their payload headers. This patch extracts that data, adding more clock synchronisation information, on both bulk and isochronous endpoints and makes it available to the user space on a separate video node, using the V4L2_CAP_META_CAPTURE capability and the V4L2_BUF_TYPE_META_CAPTURE buffer queue type. By default, only the V4L2_META_FMT_UVC pixel format is available from those nodes. However, cameras can be added to the device ID table to additionally specify their own metadata format, in which case that format will also become available from the metadata node.