Re: [Linux-uvc-devel] 174f:1420 Syntek malfunctions
Hello again
> If device do not fill uvc standards, there is nothing we can do. This
> is the reason you should check alternate os, to see if there M$ one
> more time define wort standard in other way. One example: would you
> complain to kernel devs if FireWire plug do not fit to USB interface?
> The same is about UVC. If it is almost UVC webcam, then we can almost
> support it.
I understand this. I might try Windows at some point, but right now
I'll just keep it as is.
> google talk plugin do mostly same requests like luvcvideo do. Can you
> please test if your cam works only with one specific format? On my
> system GTalk use yuv 640x480@30fps. To imitate it use:
> luvcview -f yuv -i 30 -s 640x480
>
> I doubt it has some thing todo with 64/32-bit.
I tried your command, but it failed with the same problem. I've
noticed something: usually on a fresh boot, luvcview, guvcview or
cheese work for sometime before freezing up. I was able to grab the
output of guvcview during one such session and I've attached it. After
this, all programs refuse to work, except gtalk plugin...there's got
to be something gtalk is doing to handle the webcam properly.
> Can you please test if increasing UVC_CTRL_CONTROL_TIMEOUT will help.
> You will need to edit: linux/drivers/media/video/uvc/uvcvideo.h
> and recompile kernel.
I tried this. I increased the value from 300 to 3000, but it didn't help at all.
> If not, i have no more ideas. May be Laurent will have.
Thanks for all your help and prompt responses. Hopefully someone will
have another idea
Cheers
Andres
$ guvcview 1.4.1
video device: /dev/video0
/dev/video0 - device 1
Init. USB Camera Device (location: usb-:00:1d.0-1.5)
{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'RGB3', description = 'RGB3' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'BGR3', description = 'BGR3' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'YU12', description = 'YU12' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'YV12', description = 'YV12' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
vid:174f
pid:1420
driver:uvcvideo
checking format: 1448695129
fps is set to 1/30
drawing controls
fps is set to 1/30
no codec detected for H264
no codec detected for MP3 - (lavc)
no codec detected for Dolby AC3 - (lavc)
no codec detected for ACC Low - (faac)
Could not grab image (select timeout): Resource temporarily unavailable
Could not grab image (select timeout): Resource temporarily unavailable
Could not grab image (select timeout): Resource temporarily unavailable
Could not grab image (select timeout): Resource
Re: [Linux-uvc-devel] 174f:1420 Syntek malfunctions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 12.12.2011 05:51, schrieb Andres Cimmarusti: > Hi again > >> It sounds plausibly. But in this case i would expect error -28 >> (no space), rather then -110 (time out). Any way, currently only >> you can test if it's true. If you use debian you can probably use >> precompiled ubuntu kernels: >> http://kernel.ubuntu.com/~kernel-ppa/mainline/ > > I tested the latest 3 stable kernels: 2.6.39.4, 3.0.13 and 3.1.5 > with no luck. I actually cannot use a kernel lower than 3.0.x > (permanently) because it has no support for my realtek wireless > card. > >> If still no results, then try other quirks: #define >> UVC_QUIRK_STATUS_INTERVAL 0x0001 #define >> UVC_QUIRK_PROBE_MINMAX 0x0002 #define >> UVC_QUIRK_PROBE_EXTRAFIELDS 0x0004 #define >> UVC_QUIRK_BUILTIN_ISIGHT0x0008 #define >> UVC_QUIRK_STREAM_NO_FID 0x0010 #define >> UVC_QUIRK_IGNORE_SELECTOR_UNIT 0x0020 #define >> UVC_QUIRK_FIX_BANDWIDTH 0x0080 #define >> UVC_QUIRK_PROBE_DEF 0x0100 #define >> UVC_QUIRK_RESTRICT_FRAME_RATE 0x0200 > > Tried all the quirks one by one and nothing. The PROBE_DEF 0x100 > quirk is the only one that doesn't complain in dmesg. The others > always showed this: > > [ 5626.340681] uvcvideo: UVC non compliance - GET_DEF(PROBE) not > supported. Enabling workaround. > >> then if no results, test if device works at all with some >> alternate OS :) > > Well, unfortunately this isn't an option for me. I could try, but > I'm not sure what that would accomplish, except getting the thing > to work properly. If this would help in bringing support for the > linux kernel then I would consider it. If device do not fill uvc standards, there is nothing we can do. This is the reason you should check alternate os, to see if there M$ one more time define wort standard in other way. One example: would you complain to kernel devs if FireWire plug do not fit to USB interface? The same is about UVC. If it is almost UVC webcam, then we can almost support it. > Lastly I just want to share a few more of diagnostics I've tried: > > 1. Attached is the output from the CLI utility 'v4l2-compliance > --device=/dev/video0'. It shows a failure in one of the tests: > test VIDIOC_S_PRIORITY: FAIL (-1) > > 2. Also attached is the log of the utility guvcview when I try to > use with the webcam. It almost always fails...however it worked > once without a problem... how does this make any sense? how is it > possible that it works sporadically? Jitsi, ekiga and linphone fail > right away, but cheese and luvcview also works sporadically... > > 3. The webcam works flawlessly with the google talk plugin in > conjunction with Firefox 8.0. I know that this plugin uses the > 32-bit version of libv4l. While the other applications I've been > trying are native 64-bit. Thoughts? comments? google talk plugin do mostly same requests like luvcvideo do. Can you please test if your cam works only with one specific format? On my system GTalk use yuv 640x480@30fps. To imitate it use: luvcview -f yuv -i 30 -s 640x480 I doubt it has some thing todo with 64/32-bit. Can you please test if increasing UVC_CTRL_CONTROL_TIMEOUT will help. You will need to edit: linux/drivers/media/video/uvc/uvcvideo.h and recompile kernel. If not, i have no more ideas. May be Laurent will have. - -- Regards, Alexey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7lvIAACgkQw8E0jNwoJm/fpgCfajRsxpAcDL2cHLlUDxtxMrb9 /qIAn0150abP/nsfwAFSZOKKzBhsEUhs =mdab -END PGP SIGNATURE- ___ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] 174f:1420 Syntek malfunctions
Hi again
> It sounds plausibly. But in this case i would expect error -28 (no
> space), rather then -110 (time out).
> Any way, currently only you can test if it's true. If you use debian you
> can probably use precompiled ubuntu kernels:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/
I tested the latest 3 stable kernels: 2.6.39.4, 3.0.13 and 3.1.5 with
no luck. I actually cannot use a kernel lower than 3.0.x (permanently)
because it has no support for my realtek wireless card.
> If still no results, then try other quirks:
> #define UVC_QUIRK_STATUS_INTERVAL 0x0001
> #define UVC_QUIRK_PROBE_MINMAX 0x0002
> #define UVC_QUIRK_PROBE_EXTRAFIELDS 0x0004
> #define UVC_QUIRK_BUILTIN_ISIGHT 0x0008
> #define UVC_QUIRK_STREAM_NO_FID 0x0010
> #define UVC_QUIRK_IGNORE_SELECTOR_UNIT 0x0020
> #define UVC_QUIRK_FIX_BANDWIDTH 0x0080
> #define UVC_QUIRK_PROBE_DEF 0x0100
> #define UVC_QUIRK_RESTRICT_FRAME_RATE 0x0200
Tried all the quirks one by one and nothing. The PROBE_DEF 0x100 quirk
is the only one that doesn't complain in dmesg. The others always
showed this:
[ 5626.340681] uvcvideo: UVC non compliance - GET_DEF(PROBE) not
supported. Enabling workaround.
> then if no results, test if device works at all with some alternate OS :)
Well, unfortunately this isn't an option for me. I could try, but I'm
not sure what that would accomplish, except getting the thing to work
properly. If this would help in bringing support for the linux kernel
then I would consider it.
Lastly I just want to share a few more of diagnostics I've tried:
1. Attached is the output from the CLI utility 'v4l2-compliance
--device=/dev/video0'. It shows a failure in one of the tests: test
VIDIOC_S_PRIORITY: FAIL (-1)
2. Also attached is the log of the utility guvcview when I try to use
with the webcam. It almost always fails...however it worked once
without a problem... how does this make any sense? how is it possible
that it works sporadically? Jitsi, ekiga and linphone fail right away,
but cheese and luvcview also works sporadically...
3. The webcam works flawlessly with the google talk plugin in
conjunction with Firefox 8.0. I know that this plugin uses the 32-bit
version of libv4l. While the other applications I've been trying are
native 64-bit. Thoughts? comments?
Thanks for your help, hopefully this new information will be helpful.
I didn't attach the kernel logs, because they are pretty much
identical.
Regards,
Andres
$ guvcview 1.4.1
video device: /dev/video0
/dev/video0 - device 1
Init. USB Camera Device (location: usb-:00:1d.0-1.5)
{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'RGB3', description = 'RGB3' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'BGR3', description = 'BGR3' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'YU12', description = 'YU12' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30,
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30,
{ discrete: width = 1280, height = 1024 }
Time interval between frame: 1/8,
{ pixelformat = 'YV12', description = 'YV12' }
{ discrete: width = 640, height = 480 }
Time interval between frame: 1
Re: [Linux-uvc-devel] 174f:1420 Syntek malfunctions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am 08.12.2011 20:52, schrieb Andres Cimmarusti: > Hi, > >> try UVC_QUIRK_PROBE_DEF: >> sudo rmmod uvcvideo && sudo modprobe uvcvideo quirks=0x100 > >> if it still not work, please send also dmesg with working configuration. Do >> luvcvideo works? > > Thanks for your reply. I tried what you suggested, but with no luck. > Webcam is left in an unusable state after opening jitsi and trying to > test video or establish a video call. > > I've also noticed that, upon a fresh reboot, the framerate is > abhorrent. Using luvcview (I assumed that's what you meant by > luvcvideo), I was only able to get 5 fps and then the program froze > within 10 seconds of opening. Cheese doesn't freeze, but framerate is > terrible, I tried recording a small video and it looked more like a > collection of pictures every 2 seconds or so. I've attached the > PRE-jitsi console output of luvcview and the POST-jitsi one. > > I'm curious about something. When I upgraded to kernel 3.0.12, this > was the lkml announcement: > > https://lkml.org/lkml/2011/11/28/562 > > The commit that was reverted is this one: > http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commit;h=317451c11fefcb0e05383f0a0080bb7f5445cfcf > > Could this still be affecting me here by any chance? It sounds plausibly. But in this case i would expect error -28 (no space), rather then -110 (time out). Any way, currently only you can test if it's true. If you use debian you can probably use precompiled ubuntu kernels: http://kernel.ubuntu.com/~kernel-ppa/mainline/ plese test nest and older kernels. If still no results, then try other quirks: #define UVC_QUIRK_STATUS_INTERVAL 0x0001 #define UVC_QUIRK_PROBE_MINMAX 0x0002 #define UVC_QUIRK_PROBE_EXTRAFIELDS 0x0004 #define UVC_QUIRK_BUILTIN_ISIGHT0x0008 #define UVC_QUIRK_STREAM_NO_FID 0x0010 #define UVC_QUIRK_IGNORE_SELECTOR_UNIT 0x0020 #define UVC_QUIRK_FIX_BANDWIDTH 0x0080 #define UVC_QUIRK_PROBE_DEF 0x0100 #define UVC_QUIRK_RESTRICT_FRAME_RATE 0x0200 then if no results, test if device works at all with some alternate OS :) - -- Regards, Alexey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7huKkACgkQw8E0jNwoJm9kuwCgk17XJVEcdZRn3cpCOjRGp4B/ xgMAn1ymggANBE71tmLDLwBG1wi6Ckqi =oODy -END PGP SIGNATURE- ___ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] 174f:1420 Syntek malfunctions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Andres, try UVC_QUIRK_PROBE_DEF: sudo rmmod uvcvideo && sudo modprobe uvcvideo quirks=0x100 if it still not work, please send also dmesg with working configuration. Do luvcvideo works? On 08.12.2011 15:04, Andres Cimmarusti wrote: > Hi linux-uvc-developers, > > I have a LC2131 laptop (same as Zareason Strata Pro 13 and ASI > SP13R). It comes with a Syntek UVC webcam built-in. > > It usually works fine, but certain applications fail to use it > properly like jitsi / linphone / ekiga / gstreamer-properties / > cheese > > I'm running Debian stable with a customized 3.0.12 kernel. > Attached are the logs of the problems experienced. > > Basically everytime I want to use the webcam with jitsi, it fails. > Furthermore it leaves the webcam in a "bizarre" state and cheese / > gstreamer-propertoies fails to access it. > > Cheese usually segfaults with the message: > > libv4l2: error setting pixformat: Input/output error > > Jitsi logs show the following messages: > > 00:24:47.070 SEVERE: > impl.neomedia.device.MediaDeviceImpl.createCaptureDevice().129 > Failed to create CaptureDevice from CaptureDeviceInfo USB Camera > Device (/dev/video0) : video4linux2:/dev/video0 AVFRAME, class > net.java.sip.communicator.impl.neomedia.codec.video.AVFrame, > pixFmt= 1 > > javax.media.NoDataSourceException: Error instantiating class: > net.java.sip.communicator.impl.neomedia.jmfext.media.protocol.video4linux2.DataSource > > : java.io.IOException: ioctl: request= VIDIOC_S_FMT, width= 640, > height= 480, pixelformat= 1448695129 > > Hope this helps to debug this problem. Jitsi is not the only > program that makes the webcam behave strangely. Ekiga and linphone > screw it up too...or perhaps the driver needs tweaking? I haven't > had trouble using the webcam with google video browser plugin > though. > > Let me know if you need more info > > Thanks > > Andres > > > > ___ Linux-uvc-devel > mailing list [email protected] > https://lists.berlios.de/mailman/listinfo/linux-uvc-devel - -- Regards, Alexey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7gzRMACgkQw8E0jNwoJm8nZgCgoY5OVlXh8i78MHSbW+ULwUcI N5QAmwa1jvXQBqcBjc4z2BATkLJbAwKB =KtHf -END PGP SIGNATURE- ___ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
