[linux-dvb] ADS PTV 305 sound issues
I have a fedora 5 box running fedora 5 (kernel 2.6.18-1.2257.fc5) and mythtv. I recently got a ADS PTV 305 tv tuner card (as part of ADS MCE 3000 media kit) which I installed on my computer. I am able to get the picture (there is a crossweave like patter though) but no sound. So my questions are : 1) I can not get sound working on it - Do I need to attach a audio cable from some jumper to motherboard (I have onboard audio). ? Will 'cd in' port work or I need to install a separate sound card which has 'aux in'. I tried v4l2-ctl -d 1 -f 61.25 --set-ctrl=mute=0 command but still can't get the sound (without cable). 2) Any way to get better picture ? This card is supposed to have hardware encoding (??) but my cpu usage (1.6Ghz intel with 512 MB RAM) is about 50% when watching live TV. Most of it is from mythbackend. Is it actually using hardware encoding ? Here is my dmesg output [EMAIL PROTECTED] ~]# dmesg | grep cx cx2388x alsa driver version 0.0.6 loaded CORE cx88[0]: subsystem: 1421:0305, board: KWorld HardwareMpegTV XPert [card=45,insmod option] cx2388x v4l2 driver version 0.0.6 loaded cx88[0]/1: CX88x/0: ALSA support for cx2388x boards cx88[0]/0: found at :02:0a.0, rev: 5, irq: 177, latency: 32, mmio: 0xdc00 tuner 1-004b: chip found @ 0x96 (cx88[0]) cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 cx88[0]/0: registered device radio0 cx2388x blackbird driver version 0.0.6 loaded cx88[0]/2: found at :02:0a.2, rev: 5, irq: 177, latency: 32, mmio: 0xde00 cx88[0]/2: cx23416 based mpeg encoder (blackbird reference design) cx88[0]/2: registered device video1 [mpeg] cx2388x dvb driver version 0.0.6 loaded [EMAIL PROTECTED] ~]# dmesg | grep tuner TV tuner 54 at 0x1fe, Radio tuner -1 at 0x1fe tuner 1-004b: chip found @ 0x96 (cx88[0]) tuner 1-004b: setting tuner address to 61 tuner 1-004b: type set to tda8290+75 Can anyone help ? Will really appreciate any help/pointer. Regards M A Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO Dual Digital 4 and remote
Bonne Eggleston wrote: > On 11/15/07, Robert Backhaus <[EMAIL PROTECTED]> wrote: > > Two questions: > 1. Some keys do not generate an event (I've been testing it using > xev). Does anyone know how to get all keys to work (an example is the > "DVD" key) > I can't recall if this is expected, or necessary. See next response. > 2. Has anyone gone and mapped the keycodes to their equivalents? I > would normally do it using Xmodmap, but there's probably a better way. > I'll do it if noone else already has, but no need to duplicate work ;) > Once you have your input device working correctly, just attach lirc to the event device with the 'dev/input' lirc driver and use it like a regular remote - this gives you far more power, and should allow you to map all the buttons. Just follow a tutorial for the DD2 and you should be pretty much there. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [BUG] video capture is broken
Am Montag, den 19.11.2007, 22:46 +0100 schrieb Halim Sahin: > Hi, > Hmm where can I get the patch? > Regards > > Halim Hi, Mauro pulled it already into v4l-dvb master 4 hours back. Cheers, Hermann > On Mo, Nov 19, 2007 at 08:02:32 +0100, e9hack wrote: > > Brandon Philips schrieb: > > > I am guessing this a saa7136 based device. > > > > The card is saa7146 based. I think you mean the saa7146. > > > > > Could you please test this > > > patch? If it is in fact not a saa7136, what driver is it? > > > > The patch does fix the problem, thanks! > > > > - Hartmut > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [BUG] video capture is broken
Em Seg, 2007-11-19 às 12:02 -0800, Brandon Philips escreveu: > On 20:02 Mon 19 Nov 2007, e9hack wrote: > > Brandon Philips schrieb: > > > I am guessing this a saa7136 based device. > > > > The card is saa7146 based. I think you mean the saa7146. > > > > > Could you please test this > > > patch? If it is in fact not a saa7136, what driver is it? > > > > The patch does fix the problem, thanks! > > Gah, I was not subscribed so my messages never made it to this list. > > For everyones reference this is the patch: > http://ifup.org/hg/v4l-dvb?cmd=changeset;node=65d65eecf8a5;style=gitweb > > Mauro has been asked to pull this change into his repository. Patch applied, thanks. Btw, maybe, we should remove this code, calling, instead videobuf_cgmbuf. The implementation seems to be common on all videobuf clients. Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [BUG] video capture is broken
Hi, Hmm where can I get the patch? Regards Halim On Mo, Nov 19, 2007 at 08:02:32 +0100, e9hack wrote: > Brandon Philips schrieb: > > I am guessing this a saa7136 based device. > > The card is saa7146 based. I think you mean the saa7146. > > > Could you please test this > > patch? If it is in fact not a saa7136, what driver is it? > > The patch does fix the problem, thanks! > > - Hartmut > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Halim Sahin E-Mail: halim.sahin (at) t-online.de ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] m920x device: Genius TVGo DVB-T02Q
Hello
I'm new to the list. I've got a T02Q working (or that's what it seems,
although I can't tune anything yet, but I think is a matter of signal
strength). Some weeks ago my brother gave me a capturer of this model,
so I started to look for linux support. I read this conversation:
[linux-dvb] m920x device: Genius TVGo DVB-T02Q
http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019856.html
There is a problem in the perl script used to parse the snoopy logs
(I've got it from the wiki). You need to add a plus sign to the regexp
at the function write_bytes (lines passed to it had extra spaces which
caused empty values within array @bytes, thus giving extra zeros to
the resultant firmware). Here's the tuned script I used:
m920x_snoopypro_parser.pl
---
#!/usr/bin/perl
$linenum = 0;
open(out,">fw") || die "Can't open fw";
sub get_tf_data {
$full = "";
$line = ; $linenum++;
while($line =~ m/^\S\S\S\S: ([0-9a-f ]+)/) {
$full .= $1;
$line = ; $linenum++;
}
return $full;
}
sub write_bytes {
my($str) = @_;
@bytes = split(/ +/, $str); ## look at this line
foreach(@bytes){
print out pack("C", hex($_));
}
}
while($line = ) { $linenum++;
if($line =~ m/SetupPacket:/) {
$setup_linenum = $linenum;
$setup = get_tf_data();
while($line = ) { $linenum++;
if($line =~ m/TransferBuffer: 0x0040/) {
#print "setup: " . $setup . "\n";
@bytes = split(/ /, $setup);
print out pack("v", hex($bytes[3] . $bytes[2]));
print out pack("v", hex($bytes[5] . $bytes[4]));
print out pack("v", hex("0x40"));
$lid = get_tf_data();
print "lid : " . $lid . "\n";
write_bytes($lid);
last;
}elsif($line =~ m/No TransferBuffer/) {
last;
}elsif($line =~ m/TransferBuffer:/) {
last;
}
}
}
}
--
I've attached the firmware I've got with it. If you're interested in
the two usblogs I got with snoopypro thru a kvm-virtualized windows,
let me know (my last message was bounced for being too long). They're
two because the first is where the driver uploads the firmware to the
device, and the second is the conversation after the device reattaches
itself to the usb bus.
As for the patch to m920x.c, I won't waste my time trying to get the
last files on the repository again and making a diff again and getting
my mail message bounced again. The job done by Pere Blay was
marvelous, use that. The only important difference with mine is
structure "tvgot02q_zl10353_config": .demod_address should be 0x0f,
not 0x1e.
That's all for now.
--
Román.
dvb-usb-t02q-02.fw
Description: Binary data
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] CAM inserted/used reduces signal and SNR ?
On 11/18/2007 10:34 AM, Luc Brosens wrote: > Hi, > > side note : > the problems in my previous post "KNC1 TV-Station S, revision 0x1894, doesn't > tune", were related to the PCI-slots of the motherboard I used > rebuilt the machine around a new motherboard, both KNC1's are now recognized > and able to tune > lesson learnt : check the hardware before complaining about the software ... > > next step is accessing the scrambled signals > > as I said, the cards scan OK and using "szap" I can tune to them : > [EMAIL PROTECTED]:~> szap -a 1 -c channels.conf VT4 > reading channels from file 'channels.conf' > zapping to 795 'VT4': > sat 0, frequency = 12669 MHz V, symbolrate 2200, vpid = 0x03af, apid = > 0x039b sid = 0x31e5 > using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' > status 05 | signal 9ffb | snr 21f6 | ber ea08 | unc | > status 1f | signal d430 | snr dad3 | ber 0100 | unc | FE_HAS_LOCK > status 1f | signal d47e | snr dab5 | ber | unc | FE_HAS_LOCK > status 1f | signal d5b8 | snr dacd | ber | unc | FE_HAS_LOCK > status 1f | signal d458 | snr dac7 | ber | unc | FE_HAS_LOCK > status 1f | signal d5bc | snr daf7 | ber | unc | FE_HAS_LOCK > status 1f | signal d460 | snr da9a | ber | unc | FE_HAS_LOCK > status 1f | signal d47c | snr daac | ber | unc | FE_HAS_LOCK > status 1f | signal d46c | snr dac1 | ber | unc | FE_HAS_LOCK > status 1f | signal d465 | snr dabe | ber | unc | FE_HAS_LOCK > status 1f | signal d481 | snr dabb | ber | unc | FE_HAS_LOCK > status 1f | signal d46f | snr dab5 | ber | unc | FE_HAS_LOCK > status 1f | signal d43b | snr daa0 | ber | unc | FE_HAS_LOCK > status 1f | signal d468 | snr dabe | ber | unc | FE_HAS_LOCK > status 1f | signal d47e | snr daa6 | ber | unc | FE_HAS_LOCK > status 1f | signal d342 | snr dac1 | ber | unc | FE_HAS_LOCK > > [EMAIL PROTECTED]:~> szap -a 1 -c channels.conf VTM > reading channels from file 'channels.conf' > zapping to 793 'VTM': > sat 0, frequency = 12669 MHz V, symbolrate 2200, vpid = 0x03ad, apid = > 0x0399 sid = 0x31e3 > using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' > status 1f | signal d404 | snr b772 | ber c000 | unc | FE_HAS_LOCK > status 1f | signal d479 | snr da8b | ber | unc | FE_HAS_LOCK > status 1f | signal d5b7 | snr daac | ber | unc | FE_HAS_LOCK > status 1f | signal d5b6 | snr da97 | ber | unc | FE_HAS_LOCK > status 1f | signal d47c | snr daa0 | ber | unc | FE_HAS_LOCK > status 1f | signal d5bb | snr da70 | ber | unc | FE_HAS_LOCK > status 1f | signal d342 | snr da97 | ber | unc | FE_HAS_LOCK > status 1f | signal d480 | snr daa6 | ber | unc | FE_HAS_LOCK > status 1f | signal d340 | snr da97 | ber | unc | FE_HAS_LOCK > status 1f | signal d481 | snr da40 | ber | unc | FE_HAS_LOCK > status 1f | signal d47e | snr da6a | ber | unc | FE_HAS_LOCK > status 1f | signal d340 | snr da6d | ber | unc | FE_HAS_LOCK > status 1f | signal d468 | snr da91 | ber | unc | FE_HAS_LOCK > > both VTM and VT4 are encrypted channels here, so no mpg-output at this time > > I have found one (1) encrypted channel that works using gnutv : > > [EMAIL PROTECTED]:~> gnutv -adapter 1 -channels channels.conf -out dvr VTM > Using frontend "ST STV0299 DVB-S", type DVB-S > status SCVYL | signal d47c | snr dac1 | ber ff00 | unc | > FE_HAS_LOCK > CAM Application type: 01 > CAM Application manufacturer: 0100 > CAM Manufacturer code: > CAM Menu string: CANALDIGITAAL > CAM supports the following ca system ids: > 0x0100 > Received new PMT - sending to CAM... > [EMAIL PROTECTED]:~> > > using mplayer, I have a clear picture > this proves to me that descrambling works > > but I have yet to find another channel that works, even on the same > transponder frequency none of the others work !? > > what's more, it looks like it's the CAM that's the cause of things : > > first, remove the CAM from the CI slot : > > [EMAIL PROTECTED]:~> gnutv -adapter 1 -channels channels.conf -out dvr VT4 > Using frontend "ST STV0299 DVB-S", type DVB-S > status SCVYL | signal d464 | snr da9a | ber a700 | unc | > FE_HAS_LOCK > > the lock is immediate > > insert the CAM, same command : > > [EMAIL PROTECTED]:~> gnutv -adapter 1 -channels channels.conf -out dvr VT4 > Using frontend "ST STV0299 DVB-S", type DVB-S > CAM Application type: 0140 | snr 83c1 | ber ff00 | unc | > CAM Application manufacturer: 0100 > CAM Manufacturer code: > CAM Menu string: CANALDIGITAAL > CAM supports the following ca system ids:e
Re: [linux-dvb] [BUG] video capture is broken
On Nov 19, 2007 9:02 PM, Brandon Philips <[EMAIL PROTECTED]> wrote: > On 20:02 Mon 19 Nov 2007, e9hack wrote: > > Brandon Philips schrieb: > > > I am guessing this a saa7136 based device. > > > > The card is saa7146 based. I think you mean the saa7146. > > > > > Could you please test this > > > patch? If it is in fact not a saa7136, what driver is it? > > > > The patch does fix the problem, thanks! > > Gah, I was not subscribed so my messages never made it to this list. > > For everyones reference this is the patch: > http://ifup.org/hg/v4l-dvb?cmd=changeset;node=65d65eecf8a5;style=gitweb > > Mauro has been asked to pull this change into his repository. This must have been what was causing VDR to go defunt with my Nexus-S on startup. I could not kill the pid and I could not unload the drivers because they were still in use by VDR. Regards. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [BUG] video capture is broken
On 20:02 Mon 19 Nov 2007, e9hack wrote: > Brandon Philips schrieb: > > I am guessing this a saa7136 based device. > > The card is saa7146 based. I think you mean the saa7146. > > > Could you please test this > > patch? If it is in fact not a saa7136, what driver is it? > > The patch does fix the problem, thanks! Gah, I was not subscribed so my messages never made it to this list. For everyones reference this is the patch: http://ifup.org/hg/v4l-dvb?cmd=changeset;node=65d65eecf8a5;style=gitweb Mauro has been asked to pull this change into his repository. Thanks, Brandon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [BUG] video capture is broken
Brandon Philips schrieb: > I am guessing this a saa7136 based device. The card is saa7146 based. I think you mean the saa7146. > Could you please test this > patch? If it is in fact not a saa7136, what driver is it? The patch does fix the problem, thanks! - Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [BUG] video capture is broken
Hi, changesets 6600 - 6603 break video capture on my TT-C2300 FF card. The call 'ioctl(videoDev, VIDIOCGMBUF, &mbuf)' doesn't return. It isn't possible to kill the affected application. - Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Compro U500 with new product ID 0x1e82 not working.
Hi all I have previously had the Compro U500 USB running under FC6 using an older version of the V4L DVB modules and the help of these fine people in this mailing list. On the last occasion, I simply changed the Compro U500 product ID in "linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h" from 1e78 to 1e82 then made and installed and loaded the modules. However, I have just upgraded with a fresh install of Fedora 8 and puled down the v4l-dvb source and changed the previous line as before but am getting major issues as soon as I start dvbscan to test it. There also is another Compro listed to cofuse me... #define USB_PID_COMPRO_VIDEOMATE_U500 0x1e78 #define USB_PID_COMPRO_VIDEOMATE_U500_PC0x1e80 I have tried to change both IDs to 1e82 on two separate occasions with no success. It appears to work, successfully loading the firmware to a warm state, but as soon as I dvbscan get : [EMAIL PROTECTED] ~]$ dvbscan /usr/share/dvb/dvb-t/au-Melbourne > channels.conf Segmentation fault [EMAIL PROTECTED] ~]$ Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: Oops: [#1] SMP Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: CPU:0 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: EIP:0060:[]Tainted: PVLI Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: EFLAGS: 00210246 (2.6.23.1-49.fc8 #1) Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: EIP is at dvb_frontend_open+0x152/0x1e6 [dvb_core] Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: eax: ebx: ecx: edx: c2ae5000 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: esi: c5b39800 edi: cf62a800 ebp: c5b39800 esp: c2ae5e98 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: Process dvbscan (pid: 23839, ti=c2ae5000 task=ec191230 task.ti=c2ae5000) Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: Stack: f8ea67c0 c04f2a5e c0483317 d2592900 c4738ae0 f8ea6820 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel:f8ea688c d2592900 f8e97362 c4738ae0 0003 f8ea67c0 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel:c4738ae0 c0483732 d2592900 0003 d2592900 c4738ae0 c0483621 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: Call Trace: Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] kobject_get+0xf/0x13 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] cdev_get+0x26/0x38 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] dvb_device_open+0xad/0x102 [dvb_core] Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] chrdev_open+0x111/0x14e Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] chrdev_open+0x0/0x14e Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] __dentry_open+0xd5/0x18c Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] nameidata_to_filp+0x24/0x33 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] do_filp_open+0x37/0x3e Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] __sched_text_start+0x594/0x638 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] get_unused_fd_flags+0x52/0xc5 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] do_sys_open+0x48/0xca Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] sys_open+0x1c/0x1e Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] syscall_call+0x7/0xb Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: [] xfrm_parse_spi+0x94/0xc8 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: === Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: Code: 00 00 c7 86 e0 01 00 00 01 00 00 00 c7 86 c0 01 00 00 00 00 00 00 c7 86 b8 01 00 00 00 00 00 00 0f ae f0 89 f6 8b 87 cc 01 00 00 <8b> 00 c7 44 24 08 34 16 ea f8 89 7c 24 04 c7 04 24 54 d7 e9 f8 Message from [EMAIL PROTECTED] at Nov 20 02:18:31 ... kernel: EIP: [] dvb_frontend_open+0x152/0x1e6 [dvb_core] SS:ESP 0068:c2ae5e98 - This shuts off my USB to make it unusable. any ideas where to go from here? what other changes ,if any, are needed for the source? Any help at all would be appreciated. Thanks Craig ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Artec T14BR DVB-T
Hi all, I've just returned from Finland where I picked up a Artec T14BR DVB-T USB 2.0, thinking it was compatible with the fully supported Artec T14. No such luck I'm afraid. A few google searches later and it looks like this particular device is not currently supported but the chipset it uses might be. The device has a USB id of 05d8:810f and (according to another list member) it uses DiBcom 7070PB and 0700C which appear to be supported by v4l-dvb drivers. There is a little here: http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices#Artec_T14BR_DVB-T My question is, has anyone looked into providing support for this device? If so is there anything I can do to assist? Many thanks, Yousef. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] szap2
answer from Darron Broad = by default v4l-dvb will turn off the frontend when it isn't open if you want to tune using szap, either leave it running or change the module param for dvb_core: parm: dvb_shutdown_timeout:wait seconds after close() before suspending hardware (int) bye ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] szap2
Ola Ekedahl schrieb: > It gets a LOCK on my signal and everything, but if I for some reason > lose the signal (if I want to force the problem to occure I simply pull > the signal), and then get the signal back, just a couple of seconds > later, szap2 won't LOCK again. I need to restart szap2 to get a LOCK again. > > Is this a known problem, or am I doing something wrong? > I think this is not limited to szap2, but generally for all zap applications. It only tried to tune after startup. The loop just gets the current status. If the card loses the tuning for some reason, szap will not try to tune again until you restart it. Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] szap2
Hi everyone, I'm having some small troubles with the szap2 application downloaded from here: http://dev.kewl.org/hvr4000/utils/ It gets a LOCK on my signal and everything, but if I for some reason lose the signal (if I want to force the problem to occure I simply pull the signal), and then get the signal back, just a couple of seconds later, szap2 won't LOCK again. I need to restart szap2 to get a LOCK again. Is this a known problem, or am I doing something wrong? (sorry if this has been asked before, I'm new to the ML). Best regards ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
