[linux-uvc-devel] Fwd: Fwd: Larmtek camera issue

[Paul J. <pa...@te...>]

Sorry - I am now feeling a little foolish. I decided to check with a 
different program in case zoom is the problem. Using vlc media player I 
am getting a picture, so the problem is zoom, not anything you have 
developed. I'm off to debug that now - please accept my apologies for 
the noise on the list.

Rgds.,
Paul

-------- Forwarded Message --------
Subject: Fwd: Larmtek camera issue
Date: Thu, 4 Nov 2021 10:16:01 +0000
From: Paul Jewell <pa...@te...>
To: lin...@li... 
<lin...@li...>

Further to my last message: I have a gentoo based laptop which is 
running 5.13.8 still. When I plug the camera into it, I get the same 
error message about "Failed to query...", but there is a picture in the 
zoom client from the camera. This suggests the issue is related to 
something else other than the uvccamera code, and the error message is 
not an indication of this problem. I would still welcome any suggestions 
you may have!

Thanks,
Paul

-------- Forwarded Message --------
Subject: Larmtek camera issue
Date: Thu, 4 Nov 2021 10:02:43 +0000
From: Paul Jewell <pa...@te...>
To: lin...@li...

Good morning!

First of all, I should point out that I have searched across the 
internet for others with this issue, but to no avail.

I have a LarmTek camera USB Webcam 1080P - this is the link: 
www.amazon.co.uk/gp/product/B07VTPQ9NQ

It worked under both Linux and Windows 10 (dual-booted - I need the 
latter for work from home) from the time I bought it until recently. It 
is permanently plugged into my desktop computer.

I started the zoom client yesterday, and was greeted by a blank screen. 
The camera active light comes on, but no picture is available in the client.

If I reboot the computer, then plug the camera in I get the following:

---------------------8<--------------------------

Nov  4 09:42:38 tristan kernel: usb 1-1: new high-speed USB device 
number 5 using xhci_hcd
Nov  4 09:42:38 tristan kernel: usb 1-1: New USB device found, 
idVendor=0525, idProduct=a4a2, bcdDevice=30.00
Nov  4 09:42:38 tristan kernel: usb 1-1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Nov  4 09:42:38 tristan kernel: usb 1-1: Product: HiEthernet
Nov  4 09:42:38 tristan kernel: usb 1-1: Manufacturer: Huawei
Nov  4 09:42:38 tristan kernel: usb 1-1: SerialNumber: 1234567891
Nov  4 09:42:42 tristan kernel: usb 1-1: USB disconnect, device number 5
Nov  4 09:42:43 tristan kernel: usb 1-1: new high-speed USB device 
number 6 using xhci_hcd
Nov  4 09:42:44 tristan kernel: usb 1-1: New USB device found, 
idVendor=12d1, idProduct=4321, bcdDevice= 4.09
Nov  4 09:42:44 tristan kernel: usb 1-1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Nov  4 09:42:44 tristan kernel: usb 1-1: Product: UVC Camera
Nov  4 09:42:44 tristan kernel: usb 1-1: Manufacturer: Ruision
Nov  4 09:42:44 tristan kernel: usb 1-1: SerialNumber: 20200416
Nov  4 09:42:44 tristan kernel: usb 1-1: Found UVC 1.10 device UVC 
Camera (12d1:4321)
Nov  4 09:42:44 tristan kernel: usb 1-1: Failed to query (GET_INFO) UVC 
control 12 on unit 2: -32 (exp. 1).
Nov  4 09:42:44 tristan kernel: input: UVC Camera: UVC Camera as 
/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-1/1-1:1.0/input/input23

---------------------8<--------------------------

uname -a gives:

Linux tristan 5.14.15-gentoo #2 SMP Thu Nov 4 09:38:46 GMT 2021 x86_64 
AMD Ryzen 9 3950X 16-Core Processor AuthenticAMD GNU/Linux

- The system runs gentoo, and is up to date.
- I am using OpenRC, not systemd, and for sound I am using pulseaudio 
(in case that is relevant).
- I still have kernel images in my boot directory for 5.13.8, 5.14.6 and 
5.14.9. All of these kernels have the same result.
- I don't see any other error messages in my logs
- The camera continues to work under Windows 10, so I don't believe it 
is a hardware issue.

Please can you advise me how I can debug this issue? Unfortunately I am 
not a heavy user of the camera, so I can't pinpoint exactly when the 
problem started.

Many thanks for your continued development of the code to manage these 
devices, and for supporting me with this issue.

-- 
Paul