All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mohammad <moin@librem.one>
Cc: Ricardo Ribalda <ribalda@chromium.org>, linux-media@vger.kernel.org
Subject: Re: Get j5 WebCam JVCU100 supported by Linux UVC driver
Date: Thu, 3 Feb 2022 02:31:49 +0200	[thread overview]
Message-ID: <YfsidYtBQhhlP4Ab@pendragon.ideasonboard.com> (raw)
In-Reply-To: <6cc718e4-87ee-cc91-1208-6f48419bad31@librem.one>

Hi Mohammad,

On Sun, Jan 30, 2022 at 09:18:32PM -0600, Mohammad wrote:
> Hi Laurent,
> 
> As it happens, I have two Windows machines; one with Windows 7 and
> another with Windows 10.  Which version of Windows should I test it on,
> and how do I capture a USB trace in Windows?  I appreciate the help!

I don't think the version matters too much. If you can test it on both
(just plugging it in and checking if it works), it's even better.

When it comes to capturing USB traces, I haven't tried that for probably
at least 15 years, so I'm afraid I can't help.

> On 1/30/22 6:00 PM, Laurent Pinchart wrote:
> > On Sun, Jan 30, 2022 at 12:12:53PM -0600, Mohammad wrote:
> >> Is there a way around this problem?  Would I have to reach out to the
> >> device manufacturer?
> >
> > If you have access to a Windows machine, it could be useful to check if
> > it works there. If it doesn't, the device is likely faulty. If it does,
> > then a debugging session would be required, which could involve
> > capturing a USB trace when using the camera under Windows, to figure out
> > what is different between Windows and Linux.
> >
> >> On 1/28/22 4:47 AM, Laurent Pinchart wrote:
> >>> On Fri, Jan 28, 2022 at 09:31:43AM +0100, Ricardo Ribalda wrote:
> >>>> I received out of list the dmesg output from Mohammad
> >>>>
> >>>> It looks like a hardware error to me:
> >>>>
> >>>> [   48.729618] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
> >>>> [   48.749361] uvcvideo: Found UVC 1.00 device j5 WebCam JVCU100 (0711:3108)
> >>>> [   48.751876] uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
> >>>
> >>> A GET_CUR failure on the video probe control is indeed fairly bad. If I
> >>> had to guess, I would suspect either an issue at the USB level, or a
> >>> firmware bug in the webcam.
> >>>
> >>>> [   48.751879] uvcvideo: Failed to initialize the device (-5).
> >>>> [   48.751930] usbcore: registered new interface driver uvcvideo
> >>>>
> >>>> On Wed, 26 Jan 2022 at 17:23, Ricardo Ribalda wrote:
> >>>>> Hi Mohammad
> >>>>>
> >>>>> Could you share the output of dmesg when you connect the device?
> >>>>>
> >>>>> And also lsusb -vvvv -d 0711:3108
> >>>>>
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> On Wed, 26 Jan 2022 at 17:20, Mohammad wrote:
> >>>>>> Greetings,
> >>>>>>
> >>>>>> I have been trying to use the j5 WebCam JVCU100 on Linux and it doesn't
> >>>>>> function properly.  Cheese cannot seem to find it, and I did not see it
> >>>>>> listed on your list of supported devices, so I thought I would bring it
> >>>>>> to your attention.  Here is what I see from running lsusb:
> >>>>>>
> >>>>>> Bus 001 Device 006: ID 0711:3108 Magic Control Technology Corp. j5
> >>>>>> WebCam JVCU100
> >>>>>>
> >>>>>> Also, running lsusb -d 0711:3108 -v | grep "14 Video" returns
> >>>>>>
> >>>>>> Couldn't open device, some information will be missing
> >>>>>>       bFunctionClass         14 Video
> >>>>>>       bInterfaceClass        14 Video
> >>>>>>       bInterfaceClass        14 Video
> >>>>>>       bInterfaceClass        14 Video
> >>>>>>       bInterfaceClass        14 Video
> >>>>>>
> >>>>>> So, looks like the Linux UVC driver at least recognizes the webcam.
> >>>>>> Please let me know if you can help with this, thanks!

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2022-02-03  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  2:47 Get j5 WebCam JVCU100 supported by Linux UVC driver Mohammad
2022-01-26 16:23 ` Ricardo Ribalda
2022-01-28  8:31   ` Ricardo Ribalda
2022-01-28 10:47     ` Laurent Pinchart
2022-01-30 18:12       ` Mohammad
2022-01-31  0:00         ` Laurent Pinchart
2022-01-31  3:18           ` Mohammad
2022-02-03  0:31             ` Laurent Pinchart [this message]

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=YfsidYtBQhhlP4Ab@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=moin@librem.one \
    --cc=ribalda@chromium.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.