CPiA cam problem
I have an old Ezonics EZCam P10U that I dug up and tried to get working.. but wasn't able to get any video from it. dmesg and relevant VLC messages below. Tested on Debian linux kernel 2.6.32-3-amd64. Am I doing something wrong? Those cpia error messages don't look too happy.. VLC gives the same error when testing on Windows XP. Is my camera dead? dmesg: [76283.900014] usb 8-1: new full speed USB device using uhci_hcd and address 2 [76284.069063] usb 8-1: New USB device found, idVendor=0553, idProduct=0002 [76284.069067] usb 8-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [76284.069070] usb 8-1: Product: USB Camera [76284.069175] usb 8-1: configuration #1 chosen from 1 choice [76284.104794] Linux video capture interface: v2.00 [76284.115534] V4L-Driver for Vision CPiA based cameras v1.2.3 [76284.115536] Since in-kernel colorspace conversion is not allowed, it is disab led by default now. Users should fix the applications in case they don't work wi thout conversion reenabled by setting the 'colorspace_conv' module parameter to 1 [76284.116615] USB driver for Vision CPiA based cameras v1.2.3 [76284.116634] USB CPiA camera found [76284.197067] cpia data error: [8] len=0, status=FFEE [76284.197070] cpia data error: [9] len=0, status=FFEE [76284.197072] cpia_usb_complete: usb_submit_urb ret -2 [76284.197077] cpia data error: [0] len=0, status=FFEE [76284.197079] cpia data error: [1] len=0, status=FFEE [76284.197081] cpia data error: [2] len=0, status=FFEE [76284.197083] cpia data error: [3] len=0, status=FFEE [76284.197085] cpia data error: [4] len=0, status=FFEE [76284.197087] cpia data error: [5] len=0, status=FFEE [76284.197088] cpia data error: [6] len=0, status=FFEE [76284.197090] cpia data error: [7] len=0, status=FFEE [76284.197092] cpia data error: [8] len=0, status=FFEE [76284.197094] cpia data error: [9] len=0, status=FFEE [76284.197096] cpia_usb_complete: usb_submit_urb ret -2 [76284.938150] CPiA Version: 1.30 (2.10) [76284.938153] CPiA PnP-ID: 0553:0002:0100 [76284.938155] VP-Version: 1.0 0141 [76284.938179] usbcore: registered new interface driver cpia vlc complaining: [0x12ad758] v4l2 demux debug: Trying direct kernel v4l2 [0x12ad758] v4l2 demux debug: opening device '/dev/video0' [0x12ad758] v4l2 demux error: cannot get video capabilities (Invalid argument) [0x12ad758] v4l2 demux debug: Trying libv4l2 wrapper [0x12ad758] v4l2 demux debug: opening device '/dev/video0' libv4l2: error getting capabilities: Invalid argument [0x12ad758] v4l2 demux error: cannot get video capabilities (Invalid argument) [0x12ad758] main demux warning: no access_demux module matching v4l2 could be loaded (... it goes on like that a few more times.) Thank you for your help, --Mike Akey -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Remaining drivers that aren't V4L2?
Hans Verkuil wrote: On Friday 12 March 2010 21:11:49 Devin Heitmueller wrote: Hello, I know some months ago, there was some discussion about a few drivers which were stragglers and had not been converted from V4L to V4L2. Do we have a current list of driver which still haven't been converted? These drivers are still v4l1: arv bw-qcam c-qcam cpia_pp cpia_usb ov511 se401 stradis stv680 usbvideo w9966 Some of these have counterparts in gspca these days so possibly some drivers can be removed by now. Hans, can you point those out? arv, bw-qcam, c-qcam, cpia_pp and stradis can probably be moved to staging and if no one steps up then they can be dropped altogether. Does this mean that the bw-qcam driver will be removed in future revisions or does this mean it will just never be updated to v4l2? According to my notes I should be able to test cpia_usb. I would have to verify that, though. I think it is only used in a USB microscope. It is effectively a webcam. I can also test usbvideo (USB 1 TV capture device). The latter is probably the most important driver that needs converting, because I think these are not uncommon. However, I have no time to work on such a driver conversion. But if someone is seriously willing to put time and effort in that, then I am willing to mail the hardware. I started doing some more tvtime work last night, and I would *love* to drop V4L support (and *only* support V4L2 devices), since it would make the code much cleaner, more reliable, and easier to test. If there are only a few obscure webcams remaining, then I'm willing to tell those users that they have to stick with whatever old version of tvtime they've been using since the last release four years ago. To my knowledge the usbvideo driver is probably the least obscure device that is still using V4L1. Regards, Hans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: scan/scan-s2 doesn't tune, but dvbtune does?
Steven Toth wrote: On Tue, Dec 15, 2009 at 4:53 AM, Lou Otway louis.ot...@tripleplay-services.com wrote: Michael Akey wrote: I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone off, C with tone on. Speaking of which, is there a way to manually set the tone from the arguments on the scan utilities? Here's what I've tried and the results: $ ./scan-s2 -a 0 -v -o zap -l 10750 INIT API major 5, minor 0 scanning INIT using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder DVB-S 1210 H 2000 AUTO AUTO AUTO initial transponder DVB-S2 1210 H 2000 AUTO AUTO AUTO -- Using DVB-S tune to: 12100:h:0:2 DVB-S IF freq is 135 tuning status == 0x03 tuning status == 0x01 tuning status == 0x03 tuning status == 0x01 tuning status == 0x03 tuning status == 0x00 tuning status == 0x01 tuning status == 0x03 tuning status == 0x00 tuning status == 0x00 WARNING: tuning failed!!! tune to: 12100:h:0:2 (tuning failed) DVB-S IF freq is 135 tuning status == 0x03 tuning status == 0x01 tuning status == 0x00 tuning status == 0x00 ...snip... Same thing happens if I use just 'scan' and not 'scan-s2.' If I use dvbtune, it works though.. $ dvbtune -f 135 -p H -s 2 -c 0 -tone 0 -m Using DVB card Conexant CX24116/CX24118 tuning DVB-S to L-Band:0, Pol:H Srate=2000, 22kHz=off polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Bit error rate: 0 Signal strength: 51648 SNR: 26215 FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|) Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|) The tuning file 'INIT' contains only the following line: S 1210 H 2000 AUTO I'm using v4l-dvb drivers from the main repo as of about a week ago. I am running kernel 2.6.32 on Debian testing. Any help is appreciated ..and hopefully it's just a simple flub on my part! --Mike Try using a non-auto FEC and rolloff. Some devices won't accept auto for these parameters. Michael, The silicon in question doesn't do automatic FEC detection. Be sure to specify which FEC you need for the sat. If in doubt, walk through them all manually. Pilot auto detect is done in s/w was was added a long time ago. - Steve Steve et al, It would appear that it does in fact do auto FEC since I don't specify it with dvbtune and it works just fine (with both my Prof 7300 and 7301.) I think it's a tone issue, but then again, why does attempting to scan something on both bands C and Ku (tone on, and tone off respectively) not work? I figured if it's a tone issue that only one band would work. I tried setting the FEC and even the delivery system (S1 rather than S) and it makes no difference. I could try the DVB-S2 NBC mux on that satellite too.. but I'm not sure why that would make a difference. If you folks have any other ideas, let me know. Thanks for your responses so far! --Mike -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
scan/scan-s2 doesn't tune, but dvbtune does?
I can't get the scan/scan-s2 utilities to lock any transponders (DVB-S). My test satellite is AMC1 103W, the Pentagon Channel tp. This is probably some simple user error on my part, but I can't figure it out. I have a Corotor II with polarity changed via serial command to an external IRD. C/Ku is switched by 22KHz tone, voltage is always 18V. Ku is with tone off, C with tone on. Speaking of which, is there a way to manually set the tone from the arguments on the scan utilities? Here's what I've tried and the results: $ ./scan-s2 -a 0 -v -o zap -l 10750 INIT API major 5, minor 0 scanning INIT using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder DVB-S 1210 H 2000 AUTO AUTO AUTO initial transponder DVB-S2 1210 H 2000 AUTO AUTO AUTO -- Using DVB-S tune to: 12100:h:0:2 DVB-S IF freq is 135 tuning status == 0x03 tuning status == 0x01 tuning status == 0x03 tuning status == 0x01 tuning status == 0x03 tuning status == 0x00 tuning status == 0x01 tuning status == 0x03 tuning status == 0x00 tuning status == 0x00 WARNING: tuning failed!!! tune to: 12100:h:0:2 (tuning failed) DVB-S IF freq is 135 tuning status == 0x03 tuning status == 0x01 tuning status == 0x00 tuning status == 0x00 ...snip... Same thing happens if I use just 'scan' and not 'scan-s2.' If I use dvbtune, it works though.. $ dvbtune -f 135 -p H -s 2 -c 0 -tone 0 -m Using DVB card Conexant CX24116/CX24118 tuning DVB-S to L-Band:0, Pol:H Srate=2000, 22kHz=off polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Bit error rate: 0 Signal strength: 51648 SNR: 26215 FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Signal=51648, Verror=0, SNR=26215dB, BlockErrors=0, (S|L|C|V|SY|) Signal=51776, Verror=0, SNR=26624dB, BlockErrors=0, (S|L|C|V|SY|) The tuning file 'INIT' contains only the following line: S 1210 H 2000 AUTO I'm using v4l-dvb drivers from the main repo as of about a week ago. I am running kernel 2.6.32 on Debian testing. Any help is appreciated ..and hopefully it's just a simple flub on my part! --Mike -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
DVB Hardware blind scan - frontend?
I'm looking to take advantage of blind-scan support in the STV0903 DVB-S/S2 frontend. What does this entail? I'm not seeing anything in linux/dvb/frontend.h in regards to frontend capabilities and the ability to do frequency and symbol rate scans. drivers/media/dvb/dvb-core/dvb_frontend.h has talk of defining different search types and algorithms.. Where can I get more information about this? Any example code I can look over out there? Is blind-scan support still hardware-specific or does DVB API v5 support it? Thanks for any help on the matter! --Mike -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
