Re: [linux-dvb] scan command returning wrong FEC ?
From: Simon G [EMAIL PROTECTED] Is this a fault of the transmitter set-up here in Sweden ? What parameters does the SFN MIP on PID 0x0015 contain? If you can't decode that (no idea if dvbsnoop can), could you capture a few minutes from that channel (full TS) and make it available for download or e-mail it to me? Regards, -- Robert Schlabbach e-mail: [EMAIL PROTECTED] Berlin, Germany ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] scan command returning wrong FEC ?
Quick reply ! I couldn't get anything from PID 0x0015 so I have dumped some of the stream from /dev/dvb/adapter0/dvr0 to a file. Its at ... http://simong.net/dvb/test.ts About 59MBytes. My upload is only about 750Kbits/s so it may take a while to download. So you can try ... http://simong.net/dvb/test_small.ts Which is about 29MBytes if you want. Let me know if you need any more info, and thanks for the help. /Simon G. I am thinking that the Official receivers work because they get their configuration by software updates over the air. From: Simon G [EMAIL PROTECTED] Is this a fault of the transmitter set-up here in Sweden ? What parameters does the SFN MIP on PID 0x0015 contain? If you can't decode that (no idea if dvbsnoop can), could you capture a few minutes from that channel (full TS) and make it available for download or e-mail it to me? Regards, -- Robert Schlabbach e-mail: [EMAIL PROTECTED] Berlin, Germany ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] scan command returning wrong FEC ?
From: Simon G [EMAIL PROTECTED] http://simong.net/dvb/test.ts http://simong.net/dvb/test_small.ts Unfortunately neither is a full transport stream - both files only contained PIDs 0x0418 and 0x0419, so it's useless for analysis :( Anyway, here's how the system works: In case of an SFN (single-frequency network), the multiplex is generated at one place and SFN MIPs (megaframe initialization packets) are inserted which contain a GPS time synchronization offset and the transmission parameters to use. The transmission towers will then transmit the signal GPS time synchronized using the specified transmission parameters. In case of an MFN (multi-frequency network) where only one transmission tower is used, the transmission parameters are configured there. In any case, the DVB-T signal contains TPS (transmission parameter signalling) which contains the modulation type, FEC rates, hierarchy alpha, guard interval and transmission mode. In effect, the receiver only needs to know the carrier frequency and the channel bandwidth, and can autodetect all other parameters. So it does no harm if it is given a wrong FEC rate - at worst, it will take a little longer to lock the channel as the receiver first needs to receive the TPS, whereas it might be able to lock faster if it is given all the right parameters. The transmission parameters given in the NIT are really only informational - they SHOULD be correct but it doesn't harm if they aren't. What actually affects the reception is the parameters given in the SFN MIP (as it influences which parameters the transmission tower uses) and the TPS (as they influence what the receiver will use). Now it'd be interesting to see what happens if the transmission tower puts incorrect values in the TPS bits, but I think that's quite unlikely to ever happen... Regards, -- Robert Schlabbach e-mail: [EMAIL PROTECTED] Berlin, Germany ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] scan command returning wrong FEC ?
Thanks for the information Robert. Any tips on getting the full ts from my card. I am using a budget PCI card (Terratec Cinergy 1200 DVB-T SAA7146) And I used tzap -r to set up the dvr device. Then I just used cat to cat to the test.ts file ? Or any tips on sniffing PID 0x0015 directly from the card. /Simon. From: Simon G [EMAIL PROTECTED] http://simong.net/dvb/test.ts http://simong.net/dvb/test_small.ts Unfortunately neither is a full transport stream - both files only contained PIDs 0x0418 and 0x0419, so it's useless for analysis :( Anyway, here's how the system works: In case of an SFN (single-frequency network), the multiplex is generated at one place and SFN MIPs (megaframe initialization packets) are inserted which contain a GPS time synchronization offset and the transmission parameters to use. The transmission towers will then transmit the signal GPS time synchronized using the specified transmission parameters. In case of an MFN (multi-frequency network) where only one transmission tower is used, the transmission parameters are configured there. In any case, the DVB-T signal contains TPS (transmission parameter signalling) which contains the modulation type, FEC rates, hierarchy alpha, guard interval and transmission mode. In effect, the receiver only needs to know the carrier frequency and the channel bandwidth, and can autodetect all other parameters. So it does no harm if it is given a wrong FEC rate - at worst, it will take a little longer to lock the channel as the receiver first needs to receive the TPS, whereas it might be able to lock faster if it is given all the right parameters. The transmission parameters given in the NIT are really only informational - they SHOULD be correct but it doesn't harm if they aren't. What actually affects the reception is the parameters given in the SFN MIP (as it influences which parameters the transmission tower uses) and the TPS (as they influence what the receiver will use). Now it'd be interesting to see what happens if the transmission tower puts incorrect values in the TPS bits, but I think that's quite unlikely to ever happen... Regards, -- Robert Schlabbach e-mail: [EMAIL PROTECTED] Berlin, Germany ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] scan command returning wrong FEC ?
Merci Jean-Claude ! I found test_dvr to be useful here. Now I think I have a full ts at http://simong.net/dvb/new_test.ts This appears to include PID 0x0015 as I can read it with dvbsnoop. Any tips on a good decoding program for this PID then. Thanks again, Simon. Simon G wrote : Or any tips on sniffing PID 0x0015 directly from the card. Hi Simon, You can use the test_sections utilities from the dvb-tools package. Jean-Claude ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with Hauppauge Nova-TD
You need both antenna connectors connected if you intend to use both tuners (dual tuner mode). Tuner 0 seems to be the side connector and tuner 1 the top connector. /Henrik On Dec 14, 2007 8:49 AM, Nicolas Will [EMAIL PROTECTED] wrote: On Thu, 2007-12-13 at 23:24 +0100, Luca wrote: Well... the device seem working properly after I put the firmware in /lib/firmware... maybe before I was using the wrong one... mah! Now dib0700 module say me that loads the firmware at ... (really two different firmwares, 1.10 and 03-pre). As the wiki page says, you need to either: rename the 1.10 firmware file to the 03-pre name symlink 1.10 to 03-pre You are not using the 03-pre at all, but you need the name as the code did not change the hard-coded file name. As with every firmware change, you need to cold boot the device, by either unplugging the stick, or by *shutting off* (not just a reboot) the machine. I don't know if it can work with both antennas... I'm playing with them, because I think it's an antenna problems... The diversity feature (2 antennas) is certainly *not* supported at this time. Kaffein is awesome! But sadly I cannot find any channel... sigh... Make sure you are using the right firmware. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge WinTV Nova-TD DVB-T USB stick reception problems
Hi, I assume that it´s me you mention. I have my htpc running with a nova-TD and it´s working ok with the exception of SVT1 which for some reasons occasionaly generates disconnects as seen on the Nova-T 500. To note here is that I have a VIA usb card, using my onboard nvidia USB led to hard hangs within ~4 hours with the nova-TD. Reception is a tad better with the nova-T 500 (which also chokes on SVT1). Contact me if you need more detailed information about my kernel . /Henrik On Dec 16, 2007 5:07 PM, Tomas [EMAIL PROTECTED] wrote: Hello, I'm having problems tuning my Hauppauge WinTV Nova-TD USB DVB receiver. Scanning for channels works fine with the 'scan' utility, I have compared the result with the result from a scan performed using my Twinhan DTV Alpha USB stick (7045, not 7045A, which is another story...) and they are identical. But when it's time to record, using the same program I use with the Twinhan stick, I get (almost) no output, just a ridiculously high bit error rate (2097151) and SNR=0. I'm very surprised by this, as the channel scanning works just fine. As far as I understand, and as previously reported by Henrik Backman, the Nova-TD should work with the DVB-T broadcasts here in Sweden. Could my problems be caused by the important bug mentioned yesterday by Patrick Boettcher? If so, is there an earlier version of the driver which doesn't have this bug? The command used to test recording: ~# /usr/local/bin/dvbstream -f 49 -p V -s 27500 -c 0 -o:test.ts 1029 1028 dvbstream v0.6 - (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://www.linuxstb.org/ Processing -o:test.ts Open file test.ts Using DVB card DiBcom 7000PC tuning DVB-T (Stockholm Nacka) to 49000 Hz, Bandwidth: 8 polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC Event: Frequency: 49000 Bit error rate: 2097151 Signal strength: 65535 SNR: 0 FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC MAP 0, file test.ts: From -1 secs, To -1 secs, 2 PIDs - 1029 1028 dvbstream will stop after -1 seconds (71582788 minutes) Setting filter for PID 1029 Setting filter for PID 1028 Using 224.0.1.2:5004:2 version=2 Streaming 2 streams Caught signal 2 - closing cleanly. ~# ls -la test.ts -rw-r--r-- 1 ath ath 188 Dec 16 16:43 test.ts ~# (I'm terminating the program by pressing Ctrl-C). Whether I get any packets at all seems totally random. In this attempt I got one single packet from several minutes of running dvbstream! A sample from the scan output: ~# grep '^SVT2:' .dvb_channels SVT2:49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:1029:1028:5060 ~# I have also tried tuning with tzap and recording using cat, but tzap gives this: ~# tzap -a 0 -c ~/.dvb_channels 'SVT2' using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 49000 Hz video pid 0x0405, audio pid 0x0404 status 0f | signal b496 | snr | ber 001f | unc | status 1e | signal | snr | ber | unc | FE_HAS_LOCK status 1e | signal | snr | ber | unc | FE_HAS_LOCK ... ~# tzap -a 1 -c ~/.dvb_channels 'SVT2' using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' tuning to 49000 Hz video pid 0x0405, audio pid 0x0404 status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK ... And the 'cat' command gives just as little TS data as dvbstream does. I'm using Linux kernel 2.6.22.6, and updated the dvb drivers from the hg sources about two hours ago. Relevant dmesg output: [ 1293.235000] usb 1-2: new high speed USB device using ehci_hcd and address 2 [ 1293.35] usb 1-2: configuration #1 chosen from 1 choice [ 1293.432000] dib0700: loaded with support for 5 different device-types [ 1293.44] dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity' in cold state, will try to load a firmware [ 1293.858000] dvb-usb: downloading firmware from file ' dvb-usb-dib0700-1.10.fw' [ 1294.146000] dib0700: firmware started successfully. [ 1294.648000] dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity' in warm state. [ 1294.649000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 1294.649000] DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) [ 1294.875000] DVB: registering frontend 0 (DiBcom 7000PC)... [ 1294.907000] MT2266: successfully identified [ 1295.06] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 1295.061000] DVB: registering new adapter
Re: [linux-dvb] scan command returning wrong FEC ?
From: Simon G [EMAIL PROTECTED]
http://simong.net/dvb/new_test.ts
This appears to include PID 0x0015 as I can read it with dvbsnoop.
Yep, it's a full TS now, but no PID 0x0015, because it's an MFN:
terrestrial delivery system:
frequency = 65000 Hz, bandwidth = 8 MHz, HP stream, constellation =
64-QAM
hierarchy = none, HP_code_rate = 3/4, LP_code_rate = 1/2
guard_interval = 1/4, transmission_mode = 8k, other_frequency = YES
Frequency list descriptor:
Terrestrial frequency = 65800 Hz
Terrestrial frequency = 59400 Hz
Terrestrial frequency = 55400 Hz
Terrestrial frequency = 57000 Hz
You'd have to read the TPS information from the demodulator to see what the
actual FEC is, but anyway:
I looked at the source code:
http://linuxtv.org/hg/v4l-dvb/file/266e6dd2dcb6/linux/drivers/media/dvb/fro
ntends/tda1004x.c
and found that in lines 708 through 711, Andrew chose to only enable
automatic FEC detection on the TDA10045 - but your board has the TDA10046
on it. To fix this, you could just remove the condition in line 710, i.e.
change it from:
if (state-demod_type == TDA1004X_DEMOD_TDA10045) {
to
{
and rebuild. But you should also try to contact Teracom and tell them the
DVB-T parameters they are transmitting in their NIT are not correct...
Hope this helps,
--
Robert Schlabbach
e-mail: [EMAIL PROTECTED]
Berlin, Germany
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Conceptronic CTVCOMBOi
Hello! My name is Miguel Ángel, I'm from Oviedo (Spain) and this is my first message to the list. I've just bought a Conceptronic CTVCOMBOi DVB-T + Analog PCI card and it works fine. But it's unlisted in the DVB-T PCI wiki so I'm going to give you some information to add to the wiki. Web: http://www.conceptronic.net/site/desktopdefault.aspx?tabindex=0tabid=200Cat=20grp=2010ar=360Prod_ID=1365Prod=CTVCOMBOi Model:Conceptronic CTVCOMBOi Price: 61 € Supports: DVB-T, Analogue, Tuner/Chips: Philips SAA7131E, Philips TDA10046A Connectors: S-Video, composite, TV DVB-T antenna in, TV analogue antenna in, FM antenna in, Remonte in Notes:Supports HDTV. Works with Ubuntu 7.10: Kaffeine and MythTV. Package contents: Audio/Video Cable, remote control, infrared receiver, DVB-T antenna, FM Antenna I hope the information can be useful for you. If I find more information I'll send it to the list. Bye! _ La vida de los famosos al desnudo en MSN Entretenimiento http://entretenimiento.es.msn.com/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] VP1032 + Cryptoworks
Any suggestions for a DVB-S card supporting Cryptoworks via CAM? I've got a VP1032 CI card (PCI id 1822:0001), a Cryptoworks module by SCM, and a regular JSTV (Japanese satellite TV) subscription, but after 5 minutes or so decryption stops working with a Received short data from the tuner app. Is it a known issue of this card and/or module? I'm currently running the latest kernel and DVB tree. Thanks, David ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] scan command returning wrong FEC ?
Regarding my TDA10046 .
That explains why I was able to get a LOCK with my Nova T 500 when I set
FEC_AUTO but not the Terratec !
I gave it a try commenting out the line in the source code to force my
card into auto FEC mode, and it worked !.
Regarding the NIT info.
I suspected as much, lets see if I even get a reply to my request to fix
it. It must be just the Karlstad transmitter that has this problem as I
see other Swedish people on this list don't seem to have the same problem
running Linux.
Teracom were using 3/4 1/2 up until recently when they appear to have gone
over to 2/3 1/2.
Thanks for all help.
/Simon.
From: Simon G [EMAIL PROTECTED]
http://simong.net/dvb/new_test.ts
This appears to include PID 0x0015 as I can read it with dvbsnoop.
Yep, it's a full TS now, but no PID 0x0015, because it's an MFN:
terrestrial delivery system:
frequency = 65000 Hz, bandwidth = 8 MHz, HP stream, constellation =
64-QAM
hierarchy = none, HP_code_rate = 3/4, LP_code_rate = 1/2
guard_interval = 1/4, transmission_mode = 8k, other_frequency = YES
Frequency list descriptor:
Terrestrial frequency = 65800 Hz
Terrestrial frequency = 59400 Hz
Terrestrial frequency = 55400 Hz
Terrestrial frequency = 57000 Hz
You'd have to read the TPS information from the demodulator to see what the
actual FEC is, but anyway:
I looked at the source code:
http://linuxtv.org/hg/v4l-dvb/file/266e6dd2dcb6/linux/drivers/media/dvb/fro
ntends/tda1004x.c
and found that in lines 708 through 711, Andrew chose to only enable
automatic FEC detection on the TDA10045 - but your board has the
TDA10046 on it. To fix this, you could just remove the condition in line
710, i.e. change it from:
if (state-demod_type == TDA1004X_DEMOD_TDA10045) {
to
{
and rebuild. But you should also try to contact Teracom and tell them
the DVB-T parameters they are transmitting in their NIT are not
correct...
Hope this helps,
--
Robert Schlabbach
e-mail: [EMAIL PROTECTED]
Berlin, Germany
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Second tuner failing (dibxxx, mt2266, Terratec Cinergy DT USB XS Diversity)
While the first tuner (0) works fine, the second tuner (1) of the stick finds no channels at all when doing scan. I get filter timeouts for all frequencies. Using an existing channels.conf does not help. MythTV claims that the signal strength/quality is ok but there is very high BER and no (tuner?) lock or just a partial one. I seem to recall both tuners were working at some point with earlier code from repository. I am at least fairly certain scan found at least some channels earlier, no matter which tuner was used. The stick seems to use a DiBcom 7000PC. Thus I wonder if I am seeing the same bug here that Patrick Boettcher mentioned on 22.11. in response to Yousef Lamlum's message on 22.11, since Yousef's device seems to have the same chip/modules??? BTW, I am using the stick with force_lna_activation parameter set to 1, otherwise the sensitivity is too low and even the working tuner does not find all the channels. Is this indeed a known issue, or is there something I can do to provide more information, or test something, etc..? Thanks, Petri ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Progres on ca support for Twinhan 1034
Hello! Any progress on CA support for the Twinhan 1034. Nice work so far. Works fine in kernel 2.6.22.12 the only thing missing is now the CA/CI support. Best regards Fredrik Jonson _ Spara, redigera och organisera dina foton enkelt med Photo Gallery! http://get.live.com/photogallery/overview ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] How to scan C-Band Signal
Now i started using C-Band signal. did you connect C-band LNB to your dvb-s card ? do you use diseqc ? when i try the same command, it says tunning failed. why do you use the same command ? On Hotbird there's not any C-band transponders. Which satellites with C-band do you want watch ? so, anyway for C band you should use the option -l C-BAND for scan utilites goga:/usr/src/dvb-apps/util/scan# ./scan 80 -l C-BAND -v scanning 80 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 3525000 V 31106000 3 initial transponder 3558000 V 3215000 3 initial transponder 3562000 V 3225000 3 initial transponder 357 V 427 3 initial transponder 3576000 V 4275000 3 initial transponder 3582000 V 4285000 3 initial transponder 3588000 V 323 3 initial transponder 3625000 V 300 3 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge WinTV Nova-TD DVB-T USB stick reception problems
On Mon, 17 Dec 2007 at 1:46pm, Henrik Beckman wrote: Hi, Hello, I assume that it´s me you mention. Yeah, sorry about misspelling your last name. I have my htpc running with a nova-TD and it´s working ok with the exception of SVT1 which for some reasons occasionaly generates disconnects as seen on the Nova-T 500. To note here is that I have a VIA usb card, using my onboard nvidia USB led to hard hangs within ~4 hours with the nova-TD. I remember reading your posts about those problems, but figured I might be spared from them as I'm using an AMD based motherboard. Haven't seen any disconnects so far, but I haven't been using the stick too much either... Reception is a tad better with the nova-T 500 (which also chokes on SVT1). Contact me if you need more detailed information about my kernel . Yes, I'd appreciate it if you could tell me what kernel version you're using on the htpc (downgrading the kernel should be no problem for me) and if you're using the kernel drivers or the hg ones (and if it's the hg ones, what version?). I can't get neither the kernel drivers nor the hg ones to work, and I've got both antennaes connected (and, as I wrote, scanning works so I do have some kind of reception and working firmware etc.). (Mailing me those details off-list is perfectly ok for me, if for some reason you don't want to post them here.) /Tomas On Dec 16, 2007 5:07 PM, Tomas [EMAIL PROTECTED] wrote: Hello, I'm having problems tuning my Hauppauge WinTV Nova-TD USB DVB receiver. Scanning for channels works fine with the 'scan' utility, I have compared the result with the result from a scan performed using my Twinhan DTV Alpha USB stick (7045, not 7045A, which is another story...) and they are identical. But when it's time to record, using the same program I use with the Twinhan stick, I get (almost) no output, just a ridiculously high bit error rate (2097151) and SNR=0. I'm very surprised by this, as the channel scanning works just fine. As far as I understand, and as previously reported by Henrik Backman, the Nova-TD should work with the DVB-T broadcasts here in Sweden. Could my problems be caused by the important bug mentioned yesterday by Patrick Boettcher? If so, is there an earlier version of the driver which doesn't have this bug? The command used to test recording: ~# /usr/local/bin/dvbstream -f 49 -p V -s 27500 -c 0 -o:test.ts 1029 1028 dvbstream v0.6 - (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://www.linuxstb.org/ Processing -o:test.ts Open file test.ts Using DVB card DiBcom 7000PC tuning DVB-T (Stockholm Nacka) to 49000 Hz, Bandwidth: 8 polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC Event: Frequency: 49000 Bit error rate: 2097151 Signal strength: 65535 SNR: 0 FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC MAP 0, file test.ts: From -1 secs, To -1 secs, 2 PIDs - 1029 1028 dvbstream will stop after -1 seconds (71582788 minutes) Setting filter for PID 1029 Setting filter for PID 1028 Using 224.0.1.2:5004:2 version=2 Streaming 2 streams Caught signal 2 - closing cleanly. ~# ls -la test.ts -rw-r--r-- 1 ath ath 188 Dec 16 16:43 test.ts ~# (I'm terminating the program by pressing Ctrl-C). Whether I get any packets at all seems totally random. In this attempt I got one single packet from several minutes of running dvbstream! A sample from the scan output: ~# grep '^SVT2:' .dvb_channels SVT2:49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:1029:1028:5060 ~# I have also tried tuning with tzap and recording using cat, but tzap gives this: ~# tzap -a 0 -c ~/.dvb_channels 'SVT2' using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 49000 Hz video pid 0x0405, audio pid 0x0404 status 0f | signal b496 | snr | ber 001f | unc | status 1e | signal | snr | ber | unc | FE_HAS_LOCK status 1e | signal | snr | ber | unc | FE_HAS_LOCK ... ~# tzap -a 1 -c ~/.dvb_channels 'SVT2' using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' tuning to 49000 Hz video pid 0x0405, audio pid 0x0404 status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK ... And the 'cat' command gives just as little TS data as dvbstream does. I'm using Linux kernel 2.6.22.6, and updated the dvb drivers from the hg sources about two hours ago. Relevant dmesg output: [ 1293.235000] usb 1-2: new high speed
Re: [linux-dvb] Hauppauge WinTV Nova-TD DVB-T USB stick reception problems
Patric B. Wrote: There is an important bug inside that driver which has a big impact on the signal reception. I'll already promissed to fix that as soon as possible, but it's not yet done. I'm trying, Patrick. Hmm, I must have skipped this. Patrick, I'm not pushing (OK, yes, maybe a little bit...), but does that bug affect the NOVA-T-500 too? Am I mixing too many threads there ? Could we have a bit of background? Thanks much! Nico not pushy, nearly not but owns a nova-t-500 that could have better reception... http://www.youplala.net/linux/home-theater-pc ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Pinnacle PCTV DVB-T 72e USB stick: no frontend attached
The Pinnacle PCTV 72e is apparrently based on the DiBCom STK7070P ( see .inf file). lsusb -v --- idVendor 0x2304 Pinnacle Systems, Inc. [hex] idProduct 0x0236 bcdDevice1.00 iManufacturer 1 LITEON iProduct2 Pinnacle 72e iSerial 3 63N I use the latest development version of Patrick Boettcher's repository. By adding the USB-ID to the correspondig section in dib0700_devices.c (DiBComs Reference design, Pinnacle PCTV with Flash) , I was able to download the firmware, but the frontend does not come up. dmesg: with debug dvb-usb: found a 'Pinnacle PCTV DVB-T Solo/Standard/Ultimate' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Pinnacle PCTV DVB-T Solo/Standard/Ultimate (72e)' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Pinnacle PCTV DVB-T Solo/Standard/Ultimate) (72e) ep 0 read error (status = -32) I2C read failed on address 40 ep 0 read error (status = -32) I2C read failed on address 9 ep 0 read error (status = -32) I2C read failed on address 40 dvb-usb: no frontend was attached by 'Pinnacle PCTV DVB-T Solo/Standard/Ultimate (72e)' dvb-usb: Pinnacle PCTV DVB-T Solo/Standard/Ultimate successfully initialized and connected. Any ideas ?` Keep up the good work, Rene ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Tuning problem with Compro DVB-T300 PCI
Slogging on with the telly box :) I am having some trouble tuning this card - kernel output looks like this: saa7134[0]: found at :01:06.0, rev: 1, irq: 16, latency: 32, mmio: 0xf5005000 saa7134[0]: subsystem: 185b:c900, board: Compro Videomate DVB-T300 [card=70,autodetected] saa7134[0]: board init: gpio is 843f00 input: saa7134 IR (Compro Videomate DV as /class/input/input2 saa7134[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 87 ff ff ff ff saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 40: ff 02 00 c2 86 10 ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb saa7134[0]: i2c eeprom 60: 34 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff tuner 4-0043: chip found @ 0x86 (saa7134[0]) tda9887 4-0043: tda988[5/6/7] found @ 0x43 (tuner) tuner 4-0061: chip found @ 0xc2 (saa7134[0]) tuner 4-0061: type set to 67 (Philips TD1316 Hybrid Tuner) tuner 4-0061: type set to 67 (Philips TD1316 Hybrid Tuner) tuner 4-0068: chip found @ 0xd0 (saa7134[0]) saa7134[0]: registered device video0 [v4l2] saa7134[0]: registered device vbi0 DVB: registering new adapter (saa7134[0]). DVB: registering frontend 1 (Philips TDA10046H DVB-T)... tda1004x: setting up plls for 48MHz sampling clock tda1004x: found firmware revision 23 -- ok I have a perfectly functional WinTV-NOVA-T USB2 which can tune fine with the same signal: [EMAIL PROTECTED]:~$ tzap -a 0 BBC ONE using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 722166670 Hz video pid 0x0258, audio pid 0x0259 status 1f | signal 8a88 | snr | ber 001f | unc | FE_HAS_LOCK status 1f | signal 8a5c | snr | ber 0080 | unc | FE_HAS_LOCK status 1f | signal 8aef | snr | ber 0070 | unc | FE_HAS_LOCK status 1f | signal 8b12 | snr | ber 0160 | unc | FE_HAS_LOCK status 1f | signal 8a58 | snr | ber 00d0 | unc | FE_HAS_LOCK status 1f | signal 8a5a | snr | ber 00d0 | unc | FE_HAS_LOCK status 1f | signal 8ad1 | snr | ber 0030 | unc | FE_HAS_LOCK status 1f | signal 8af5 | snr | ber 02a0 | unc | FE_HAS_LOCK status 1f | signal 8a63 | snr | ber 0070 | unc | FE_HAS_LOCK The poor T300 looks like this: $ tzap -a 1 BBC ONE using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' tuning to 722166670 Hz video pid 0x0258, audio pid 0x0259 status 01 | signal 9292 | snr 9d9d | ber 00014890 | unc | status 00 | signal 9393 | snr 7878 | ber 0001fffe | unc | status 00 | signal 9393 | snr | ber 0001fffe | unc | status 01 | signal 9393 | snr bfbf | ber 0001fffe | unc | status 1f | signal 9292 | snr dfdf | ber 0001266e | unc | FE_HAS_LOCK status 1f | signal 9393 | snr a2a2 | ber 0001a802 | unc | FE_HAS_LOCK status 01 | signal 9393 | snr | ber 0001661c | unc | status 1f | signal 9393 | snr e1e1 | ber 00012b06 | unc | FE_HAS_LOCK status 1f | signal 9292 | snr 9494 | ber 0001a7d4 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr | ber 00013300 | unc | FE_HAS_LOCK status 1f | signal 9292 | snr | ber 00012e9e | unc | FE_HAS_LOCK status 1f | signal 9292 | snr c3c3 | ber 00014c32 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr d4d4 | ber 00014490 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr e1e1 | ber 00014de8 | unc | FE_HAS_LOCK status 01 | signal 9292 | snr 3e3e | ber 0001fffe | unc | status 1f | signal 9393 | snr | ber 00013d96 | unc | FE_HAS_LOCK status 1f | signal 9292 | snr dede | ber 00013cc0 | unc | FE_HAS_LOCK The output from mplayer is just recognisable as the right channel, but the signal appears terribly bad. scanning for channels on my local transmitter doesn't come up with any channels (the Hauppage one finds them all). At first I thought it might be interference of some kind inside the case, but the same card tunes perfectly with the same signal under Windows. The driver is definitely working and able to get some channels fine (e.g. Dave on 70580), but it seems like the signal is degraded quite badly compared to what I get from the Hauppage Any ideas where to start on this? I've seen a similar problem reported on various forums but without much technical detail, and never here, so I thought I ought to ask. I can supply any more diagnostics or an ssh login if anyone is curious - thanks in advance for any advice. -- Matthew ___ linux-dvb mailing list linux-dvb@linuxtv.org
Re: [linux-dvb] Tuning problem with Compro DVB-T300 PCI
Oops, forgot to mention that I'm not years behind... [EMAIL PROTECTED]:~$ uname -a Linux mnas 2.6.22-3-amd64 #1 SMP Tue Dec 4 07:21:33 UTC 2007 x86_64 GNU/Linux -- Matthew ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Conceptronic CTVCOMBOi
Am Montag, den 17.12.2007, 15:19 +0100 schrieb Miguel Ángel Fernández: Hello! My name is Miguel Ángel, I'm from Oviedo (Spain) and this is my first message to the list. I've just bought a Conceptronic CTVCOMBOi DVB-T + Analog PCI card and it works fine. But it's unlisted in the DVB-T PCI wiki so I'm going to give you some information to add to the wiki. Web: http://www.conceptronic.net/site/desktopdefault.aspx?tabindex=0tabid=200Cat=20grp=2010ar=360Prod_ID=1365Prod=CTVCOMBOi Model:Conceptronic CTVCOMBOi Price: 61 € Supports: DVB-T, Analogue, Tuner/Chips: Philips SAA7131E, Philips TDA10046A Connectors: S-Video, composite, TV DVB-T antenna in, TV analogue antenna in, FM antenna in, Remonte in Notes:Supports HDTV. Works with Ubuntu 7.10: Kaffeine and MythTV. Package contents: Audio/Video Cable, remote control, infrared receiver, DVB-T antenna, FM Antenna I hope the information can be useful for you. If I find more information I'll send it to the list. Bye! Holla, do you have to do anything actively? It is a dual tuner device and what about the remote so far? Please send us dmesg for the saa713x and tuner stuff. Thanks for your report! Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] New Leadtek Winfast DTV Dongle working - with mods but no RC
Hi, I just bought a new Leadtek Winfast DTV Dongle. It works with mods to the driver but the remote only allows one keypress. First, the dvb subsystem didn't even recognise it. My /var/log/messages only had Dec 17 23:17:37 oscar kernel: [ 1123.396057] usb 5-3: USB disconnect, address 7 Dec 17 23:17:40 oscar kernel: [ 1127.025373] usb 5-3: new high speed USB device using ehci_hcd and address 8 Dec 17 23:17:40 oscar kernel: [ 1127.158401] usb 5-3: configuration #1 chosen from 1 choice when I connected the stick. I hopped onto the IRC channel and crope` (thanks mate) advised me to change dvb-usb-ids.h to #define USB_PID_WINFAST_DTV_DONGLE_STK7700P0x6f01 _ds_ recommended this firmware http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw http://www.wi-bw.tfh-wildau.de/%7Epboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw Which works much better and I get a log that looks like 1. Dec 18 02:16:13 oscar kernel: [11829.495158] usb 5-3: USB disconnect, address 26 2. Dec 18 02:16:16 oscar kernel: [11833.050232 ] usb 5-3: new high speed USB device using ehci_hcd and address 27 3. Dec 18 02:16:17 oscar kernel: [11833.183117] usb 5-3: configuration #1 chosen from 1 choice 4. Dec 18 02 :16:17 oscar kernel: [11833.183361] dvb-usb: found a 'Leadtek Winfast DTV Dongle (STK7700P based)' in cold state, will try to load a firmware 5. Dec 18 02:16 :17 oscar kernel: [11833.188944] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10 .fw' 6. Dec 18 02:16:17 oscar kernel: [ 11833.392443] dib0700: firmware started successfully. 7. Dec 18 02:16: 17 oscar kernel: [11833.893458] dvb-usb: found a 'Leadtek Winfast DTV Dongle (STK7700P based )' in warm state. 8. Dec 18 02:16:17 oscar kernel: [ 11833.893544] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. 9. Dec 18 02:16:17 oscar kernel: [11833.893776] DVB: registering new adapter (Leadtek Winfast DTV Dongle (STK7700P based)) 10. Dec 18 02:16:18 oscar kernel: [11834.238046] DVB: registering frontend 0 (DiBcom 7000PC)... 11. Dec 18 02:16:18 oscar kernel: [11834.241796] MT2060: successfully identified (IF1 = 1220 ) 12. Dec 18 02:16:18 oscar kernel: [ 11834.720027] input: IR-receiver inside an USB DVB receiver as /class/input/input12 13. Dec 18 02: 16:18 oscar kernel: [11834.720063] dvb-usb: schedule remote query interval to 150 msecs. 14. Dec 18 02:16:18 oscar kernel: [11834.720067 ] dvb-usb: Leadtek Winfast DTV Dongle (STK7700P based) successfully initialized and connected. I'm able to scan and get video audio so I assume that side of everything is working. Advised again by _ds_ I checked out the remote control. Which doesn't work that well. It only registers one keypress. Any subsequent keypresses appear to be ignored. If I disconnect/reconnect I get one more keypress. /proc/bus/input/devices contains I: Bus=0003 Vendor=0413 Product=6f01 Version=0002 N: Name=IR-receiver inside an USB DVB receiver P: Phys=usb-:00:10.4-3/ir0 S: Sysfs=/class/input/input19 U: Uniq= H: Handlers=kbd event10 B: EV=3 B: KEY=14afc336 284284d 0 0 0 4 80058000 2190 4801 9e96c0 0 900200 ffd Evtest shows the following, if I press 1 but doesn't display anything after the initial keypress [EMAIL PROTECTED]:/home/keith/dvb/linuxtv-dvb-apps-1.1.1/util/av7110_loadkeys# ./evtest /dev/input/event10 Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x413 product 0x6f01 version 0x2 Input device name: IR-receiver inside an USB DVB receiver Supported events: Event type 0 (Reset) Event code 0 (Reset) Event code 1 (Key) Event type 1 (Key) Event code 0 (Reserved) Event code 2 (1) Event code 3 (2) Event code 4 (3) Event code 5 (4) Event code 6 (5) Event code 7 (6) Event code 8 (7) Event code 9 (8) Event code 10 (9) Event code 11 (0) Event code 41 (Grave) Event code 52 (Dot) Event code 55 (KPAsterisk) Event code 102 (Home) Event code 103 (Up) Event code 105 (Left) Event code 106 (Right) Event code 108 (Down) Event code 111 (Delete) Event code 113 (Mute) Event code 114 (VolumeDown) Event code 115 (VolumeUp) Event code 116 (Power) Event code 119 (Pause) Event code 128 (Stop) Event code 139 (Menu) Event code 158 (Back) Event code 164 (PlayPause) Event code 167 (Record) Event code 168 (Rewind) Event code 173 (Refresh) Event code 207 (?) Event code 208 (?) Event code 210 (?) Event code 223 (?) Event code 226 (?) Event code 352 (Ok) Event code 354 (Goto) Event code 355 (Clear) Event code 358 (Info) Event code 363 (Channel) Event code 365 (EPG) Event code 370 (Subtitle) Event code 375 (Screen) Event code 377 (TV) Event code 385 (Radio) Event code 386 (Tuner) Event code 388 (Text) Event code 389 (DVD) Event code 392
