motioneyeos icon indicating copy to clipboard operation
motioneyeos copied to clipboard

UVC webcam was working with 20160410 release, no longer with 20160705

Open glaurent opened this issue 9 years ago • 12 comments

I was happily using a USB Creative Labs webcam which is UVC, it was working without problems with a previous release of motionEye but with the current release it no longer displays an image (I only get the barred camera icon).

I get this in dmesg :

[ 3.280774] usb 1-1.3: New USB device found, idVendor=041e, idProduct=4058 [ 3.280785] usb 1-1.3: New USB device strings: Mfr=1, Product=0, SerialNumber=0 [ 3.280792] usb 1-1.3: Manufacturer: Creative Labs [ 3.308462] uvcvideo: Found UVC 1.00 device (041e:4058) [ 3.311126] input: UVC Camera (041e:4058) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input0 [ 3.311273] usbcore: registered new interface driver uvcvideo [ 3.311280] USB Video Class driver (1.1.1) [ 3.354993] usbcore: registered new interface driver snd-usb-audio

any clues ? Should I downgrade ?

Thanks

glaurent avatar Jul 30 '16 14:07 glaurent

Hmm nope. Let's make it work as it should work with the latest version, unless there's a hardware fault. First off, did you try the latest Raspbian? motionEyeOS inherits the kernel used with Raspbian, and that's the only thing I can think of that might have changed between the two versions and could affect your USB camera.

ccrisan avatar Jul 30 '16 19:07 ccrisan

Actually it's not working with the latest raspbian either, and I was surprised that it worked out of the box with motionEyeOS. So I guess that points to the raspbian kernel.

glaurent avatar Jul 30 '16 20:07 glaurent

Yeap, you should probably take this to the Raspbian forum (and keep us posted). In the meantime you should probably downgrade or use a different camera model.

ccrisan avatar Jul 31 '16 10:07 ccrisan

Finally got around to post about it on the Raspbian forum : https://www.raspberrypi.org/forums/viewtopic.php?uid=187128&f=28&t=170382&start=0

I've also downgraded to 20160410.

glaurent avatar Jan 06 '17 16:01 glaurent

Thanks for keeping us posted. Let's hope the driver gets fixed soon. I'll make sure to update the kernel with each release.

ccrisan avatar Jan 06 '17 17:01 ccrisan

@glaurent whats the status of this?

bortek avatar Jun 01 '17 08:06 bortek

Unchanged, as far as I know :-(.

glaurent avatar Jun 01 '17 08:06 glaurent

You have to ride people's or company's asses into the ground if you want anything done. I'll take my turn to ride the buck horse.

StevenRaccoon avatar Oct 14 '22 13:10 StevenRaccoon

They didnt even respond. Just locked the thread. What pricks. Thatll give me some ammunition

StevenRaccoon avatar Oct 14 '22 13:10 StevenRaccoon

@StevenRaccoon How about using something a bit more current, instead of responding on a ticket that is 5+ years old?

starbasessd avatar Oct 14 '22 14:10 starbasessd

Why?

StevenRaccoon avatar Oct 15 '22 05:10 StevenRaccoon

If you want help, vs just to complain, help can be found with using 20200606 and dev20201026. I don't know of anyone willing to help with 20160410. Many changes, and bug fixes were applied since then. I try to reproduce user issues to see if it is a bug or user issue, but, like most major software companies, I won't support, or even TRY to support something more than a few versions back. But, if all you want to do is 'file a complaint', consider it noted, and ignored.

starbasessd avatar Oct 15 '22 10:10 starbasessd