From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Zhengyang Feng <zyfeng97@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: An unsupported UVC device
Date: Sun, 28 Feb 2021 12:06:30 +0100 [thread overview]
Message-ID: <20210228120630.75d98739@coco.lan> (raw)
In-Reply-To: <CAHp75VftsNoroK3-fKaR5VGsbh-2dahPEM650+Sw880jPFD9dQ@mail.gmail.com>
Em Sun, 28 Feb 2021 11:38:32 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> escreveu:
> +Cc: maintainers / UVC maintainers
>
>
> On Sat, Feb 27, 2021 at 12:04 PM Zhengyang Feng <zyfeng97@gmail.com> 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
next prev parent reply other threads:[~2021-02-28 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 10:02 An unsupported UVC device Zhengyang Feng
2021-02-28 9:38 ` Andy Shevchenko
2021-02-28 11:06 ` Mauro Carvalho Chehab [this message]
2021-02-28 13:25 ` Laurent Pinchart
2021-03-01 2:46 ` Zhengyang Feng
2021-03-01 2:58 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210228120630.75d98739@coco.lan \
--to=mchehab@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=zyfeng97@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox