On 7/15/20 2:02 PM, Walter Cazzola wrote:
On Tue, 14 Jul 2020, Samuel Sieb wrote:
Do an "ls -l /dev/video*" before plugging it in and then again after it's recognized to see if any devices are getting created.
Before I've >ll /dev/video* crw-rw----+ 1 root video 81, 0 Jul 15 06:44 /dev/video0 crw-rw----+ 1 root video 81, 1 Jul 15 06:44 /dev/video1
after I've
>ll /dev/video* crw-rw----+ 1 root video 81, 0 Jul 15 06:44 /dev/video0 crw-rw----+ 1 root video 81, 1 Jul 15 06:44 /dev/video1 crw------- 1 root root 81, 2 Jul 15 22:43 /dev/video2 crw------- 1 root root 81, 3 Jul 15 22:43 /dev/video3
So it is getting recognized and added.
Try "sudo dnf install uvcdynctrl", it might already be installed. Then run "uvcdynctrl -l" and see what you get.
What is the output of "lsusb -v" when it's recognized.
To long to have it here. The result about the camera is attached.
That looks right. It shows the different resolutions it can do.
To me, it seems that the camera uses the uvcvideo driver and the problem is related to all those "not initialized" errors. But I've no idea how to fix them.
I think those might just be warnings.
Have you tried other USB ports? Do you have a USB hub you could try? Maybe a different USB cable as well.
Yes, still the same behavior: sometimes it is recognized, sometimes it is not. Never show up in the usable devices. One more thing I noticed is that once it is recognized if I run multiple times the lsusb command it shows up with different device number. E.g.,
>lsusb | grep IPEVO Bus 003 Device 016: ID 1778:d120 IPEVO Inc. IPEVO VZ-X >lsusb | grep IPEVO Bus 003 Device 019: ID 1778:d120 IPEVO Inc. IPEVO VZ-X
And sometimes doesn't show up in the list.
If you check the logs, I expect you'll find that it has disconnected and reconnected. Can you try it on a different computer? I'm wondering if there is actually a hardware problem with the device.