From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 61E07C433DB for ; Sun, 28 Feb 2021 11:07:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2D46964DBD for ; Sun, 28 Feb 2021 11:07:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230107AbhB1LHa (ORCPT ); Sun, 28 Feb 2021 06:07:30 -0500 Received: from mail.kernel.org ([198.145.29.99]:44270 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230045AbhB1LH3 (ORCPT ); Sun, 28 Feb 2021 06:07:29 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 2E1B164E55; Sun, 28 Feb 2021 11:06:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1614510394; bh=pJvuY8jKQdW6P15mPmWczW82CeYsLR5C7TQDpXyLrl4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=avsyUXVmHGS73j6+VozNmL0RHLH08Q07hCTR7uL12uqjW0s6Cq9i+Iy5GlmvP8bxB VztYIlXQpaHLgJx3nhpsA6unV8r1hbOWod0xEZ758/NKLRT1e26p5UvpZdqgw6AWXL diukzi/DMjVNjHsbfk/C9xLAb+nkDuOlZgeA7Q7TT+CjaRSu/oASkYtmhqUOTXQkBU 3495iYB6Pf3XQmXKzqrApYhTPUs6BwvRwD+xJRVkchXza5g0XNMGwiORiN2bp0md3v nJl2InAbhMa9Tx9byUEwBu5w7YCiAKfFKswOECgJ8MgMWZb4pdakkrx2QjFM9y05wd jR0HUwtsKpFDg== Date: Sun, 28 Feb 2021 12:06:30 +0100 From: Mauro Carvalho Chehab To: Zhengyang Feng Cc: Andy Shevchenko , Laurent Pinchart , Linux Media Mailing List Subject: Re: An unsupported UVC device Message-ID: <20210228120630.75d98739@coco.lan> In-Reply-To: References: X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org Em Sun, 28 Feb 2021 11:38:32 +0200 Andy Shevchenko escreveu: > +Cc: maintainers / UVC maintainers > > > On Sat, Feb 27, 2021 at 12:04 PM Zhengyang Feng wrote: > > > > Dear maintainers, > > > > I'm resending this because the previous email was not clear and should > > be ignored. Sorry for the inconvenience caused. > > > > I was using HIK DS-U14 2K camera on Ubuntu 20.04 with built-in MIC > > (but it has only one USB cable) but it seems unsupported. It > > does not need a driver to be used on Windows (usable by just plugging > > in). > > I see no HIK devices on the support list > > (http://www.ideasonboard.org/uvc/), but when I run lsusb -d 2bdf:0281 > > -v | grep "14 Video" it does output several lines like these: > > > > bFunctionClass 14 Video > > bInterfaceClass 14 Video > > bInterfaceClass 14 Video > > bInterfaceClass 14 Video > > bInterfaceClass 14 Video > > > > It also says "Couldn't open device, some information will be missing". > > But it does not require a driver to work on Windows, so it should be a > > normal UVC device right? > > > > I observed that it is not supported as a camera, because although I > > see /dev/video0 and /dev/video1 (quite odd since it is only 1 camera), > > it fails by either OpenCV (cv2.VideoCapture(id)) or `cheese`, where it > > says "cannot open by index" (I tried both video0 and video1). > > Then I got the logs with `cheese`, in the zip file attached. I think since the > > device is quite new on the market, maybe you guys haven't tested it. > > > > BTW, I installed the latest from > > https://git.linuxtv.org/media_build.git before I generated the logs. > > The camera shows same behavior before and after I installed the latest > > version. And the USB connection works fine (I can use other cameras on > > this machine), also the camera itself is fine (tested on Windows machines). > > > > Feel free to tell me this is unrelated to the project/this mailing > > list, in that case I'll just > > get another camera. It sounds to me that there's something broken on this camera's descriptors, with the USB cable or with the USB stack. It sounds very weird to my eyes to see errors when getting the device descriptors like those: Bus 001 Device 007: ID 2bdf:0281 SN0002 HIK 2K USB CAMERA Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 bDeviceProtocol 1 Interface Association bMaxPacketSize0 64 idVendor 0x2bdf idProduct 0x0281 bcdDevice 11.00 iManufacturer 1 (error) iProduct 2 (error) iSerial 3 (error) The Kernel probe also has similar troubles: [ 31.553926] usb 1-1: Found UVC 1.00 device HIK 2K USB CAMERA (2bdf:0281) [ 32.065510] usb 1-1: Failed to query (GET_INFO) UVC control 11 on unit 1: -110 (exp. 1). [ 32.577665] usb 1-1: Failed to query (GET_INFO) UVC control 12 on unit 1: -110 (exp. 1). [ 33.089610] usb 1-1: Failed to query (GET_INFO) UVC control 2 on unit 2: -110 (exp. 1). [ 33.601620] usb 1-1: Failed to query (GET_INFO) UVC control 3 on unit 2: -110 (exp. 1). [ 34.113672] usb 1-1: Failed to query (GET_INFO) UVC control 7 on unit 2: -110 (exp. 1). [ 34.625635] usb 1-1: Failed to query (GET_INFO) UVC control 8 on unit 2: -110 (exp. 1). [ 35.137673] usb 1-1: Failed to query (GET_INFO) UVC control 10 on unit 2: -110 (exp. 1). [ 35.649581] usb 1-1: Failed to query (GET_INFO) UVC control 5 on unit 2: -110 (exp. 1). [ 36.161693] usb 1-1: Failed to query (GET_INFO) UVC control 11 on unit 2: -110 (exp. 1). [ 46.401833] usb 1-1: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. [ 51.460664] uvcvideo 1-1:1.1: Failed to query (129) UVC probe control : -110 (exp. 26). [ 51.460672] uvcvideo 1-1:1.1: Failed to initialize the device (-5). [ 61.656435] usb 1-1: 3:1: usb_set_interface failed (-110) [ 71.885237] usb 1-1: 3:1: usb_set_interface failed (-110) [ 77.003565] usb 1-1: 3:1: usb_set_interface failed (-110) ... [ 2022.115559] usb 1-1: 3:1: usb_set_interface failed (-110) Are you using any proprietary driver or had applied any patch/driver to the Kernel? Can you try testing it with vanilla Kernel 5.10? Thanks, Mauro