Re: [linux-dvb] Re: [v4l-dvb-maintainer] VBI OOPS 2.6.17.8
hello,
Michael Hunold wrote:
Hello Philipp,
I trimmed LKML from the CC list.
on 14.08.2006 11:37 Philipp Matthias Hahn said the following:
Starting kdetv by accident on my Siemens DVB-C 1.x produced the
following OOPS, because kdetv did open /dev/vbi0. The OOPS is
100% reproduceable.
this is a known issue with the analogtuner part of siemens dvb-c,
ive stated that in my mail with my patch, the tuner code is buggy
and may oops with tvtime or kdetv, cause of their driver access/capture
behaviour.
but it has worked for months here with xawtv 3.94.
checking further...
libzvbi:capture_v4l2k_new: /dev/vbi0 (dvb) is a v4l2 vbi device,
This is about VBI capture on the *analog* parts of a DVB-C card, ie. on
the analog cable channels that can be viewed through the saa711x on the
saa7146 input channel b.
What is the current status anyway? Did somebody ever got this to work?
yes, see list archives and attachment.
CVBS imput and tuning is working here fine with xawtv since i created the patch.
the patch was created to be able to use the saa7113 input from the analog card extension board,
i suggested to plug in an old VHS or other as tuner, since the tda9819 analog part of the
siemens card is low analogtv-demodulation quality anyway...
If not, then the easiest fix is to remove V4L2_CAP_VBI_CAPTURE from
struct saa7146_ext_vv av7110_vv_data_c in av7110_v4l.c
objection, thats no solution so far.
CU
Michael.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
y
tom schorpp
---BeginMessage---
The patch titled
dvb: av7110: Siemens DVB-C analog video input support
has been removed from the -mm tree. Its filename is
dvb-av7110-siemens-dvb-c-analog-video-input-support.patch
This patch was probably dropped from -mm because
it has already been merged into a subsystem tree
or into Linus's tree
Patches currently in -mm which might be from [EMAIL PROTECTED] are
From: thomas schorpp [EMAIL PROTECTED]
Add support for analog video inputs (CVBS and Y/C) of the
analog module for the Siemens DVB-C card.
Signed-off-by: thomas schorpp [EMAIL PROTECTED]
Signed-off-by: Johannes Stezenbach [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
drivers/media/dvb/ttpci/av7110_v4l.c | 74 +--
1 files changed, 54 insertions(+), 20 deletions(-)
diff -puN
drivers/media/dvb/ttpci/av7110_v4l.c~dvb-av7110-siemens-dvb-c-analog-video-input-support
drivers/media/dvb/ttpci/av7110_v4l.c
---
devel/drivers/media/dvb/ttpci/av7110_v4l.c~dvb-av7110-siemens-dvb-c-analog-video-input-support
2005-09-09 12:33:08.0 -0700
+++ devel-akpm/drivers/media/dvb/ttpci/av7110_v4l.c 2005-09-09
12:33:08.0 -0700
@@ -70,7 +70,7 @@ static int msp_readreg(struct av7110 *av
return 0;
}
-static struct v4l2_input inputs[2] = {
+static struct v4l2_input inputs[4] = {
{
.index = 0,
.name = DVB,
@@ -87,6 +87,22 @@ static struct v4l2_input inputs[2] = {
.tuner = 0,
.std= V4L2_STD_PAL_BG|V4L2_STD_NTSC_M,
.status = 0,
+ }, {
+ .index = 2,
+ .name = Video,
+ .type = V4L2_INPUT_TYPE_CAMERA,
+ .audioset = 0,
+ .tuner = 0,
+ .std= V4L2_STD_PAL_BG|V4L2_STD_NTSC_M,
+ .status = 0,
+ }, {
+ .index = 3,
+ .name = Y/C,
+ .type = V4L2_INPUT_TYPE_CAMERA,
+ .audioset = 0,
+ .tuner = 0,
+ .std= V4L2_STD_PAL_BG|V4L2_STD_NTSC_M,
+ .status = 0,
}
};
@@ -212,24 +228,44 @@ static int av7110_dvb_c_switch(struct sa
}
if (0 != av7110-current_input) {
+ dprintk(1, switching to analog TV:\n);
adswitch = 1;
source = SAA7146_HPS_SOURCE_PORT_B;
sync = SAA7146_HPS_SYNC_PORT_B;
memcpy(standard, analog_standard, sizeof(struct
saa7146_standard) * 2);
- dprintk(1, switching to analog TV\n);
- msp_writereg(av7110, MSP_WR_DSP, 0x0008, 0x); //
loudspeaker source
- msp_writereg(av7110, MSP_WR_DSP, 0x0009, 0x); // headphone
source
- msp_writereg(av7110, MSP_WR_DSP, 0x000a, 0x); // SCART 1
source
- msp_writereg(av7110, MSP_WR_DSP, 0x000e, 0x3000); // FM matrix,
mono
- msp_writereg(av7110, MSP_WR_DSP, 0x, 0x4f00); //
loudspeaker + headphone
- msp_writereg(av7110, MSP_WR_DSP, 0x0007, 0x4f00); // SCART 1
volume
- if (av7110-analog_tuner_flags ANALOG_TUNER_VES1820) {
-
[linux-dvb] dvb driver port to OpenSolaris
Hallo, is there a plan to port the DVB Driver to OpenSolaris? Regards Herbert ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB3000MC : autosearch doesn't work
Hi, If I try to scan some transponders with the initial file [1] and the scan utility from dvb-apps [2], the autosearch works for the configuration 2/3 NONE QAM64 8k 1/32 NONE but not for the configuration 3/4 NONE QAM64 8k 1/8 NONE. It seems dib3000mc_autosearch_is_irq return 1 (failed), when I try to tune to T 58600 8MHz AUTO NONE QAM64 AUTO AUTO NONE. What's the meaning of failed ? Have you got an idea with the autosearch failed ? Regards, Matthieu [1] T 47400 8MHz AUTO NONE QAM64 AUTO AUTO NONE T 47400 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 58600 8MHz AUTO NONE QAM64 AUTO AUTO NONE T 58600 8MHz 3/4 NONE QAM64 8k 1/8 NONE [2] initial transponder 47400 0 9 9 3 2 4 0 initial transponder 47400 0 2 9 3 1 0 0 initial transponder 58600 0 9 9 3 2 4 0 initial transponder 58600 0 3 9 3 1 2 0 tune to: 47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE 0x 0x0201: pmt_pid 0x NTN -- Direct 8 (running) 0x 0x0202: pmt_pid 0x NTN -- TMC (running) 0x 0x0203: pmt_pid 0x NTN -- BFM TV (running) 0x 0x0204: pmt_pid 0x NTN -- iTELE (running) 0x 0x0205: pmt_pid 0x NTN -- Europe 2 TV (running) 0x 0x0206: pmt_pid 0x NTN -- Gulli (running) Network Name 'réseau numérique terrestre français' tune to: 47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE 0x 0x0201: pmt_pid 0x NTN -- Direct 8 (running) 0x 0x0202: pmt_pid 0x NTN -- TMC (running) 0x 0x0203: pmt_pid 0x NTN -- BFM TV (running) 0x 0x0204: pmt_pid 0x NTN -- iTELE (running) 0x 0x0205: pmt_pid 0x NTN -- Europe 2 TV (running) 0x 0x0206: pmt_pid 0x NTN -- Gulli (running) Network Name 'réseau numérique terrestre français' tune to: 58600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 58600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 58600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x 0x0101: pmt_pid 0x GR1 -- France 2 (running) 0x 0x0103: pmt_pid 0x GR1 -- France 4 (running) 0x 0x0104: pmt_pid 0x GR1 -- France 5 (running) 0x 0x0105: pmt_pid 0x GR1 -- ARTE (running) 0x 0x0106: pmt_pid 0x GR1 -- LCP (running) 0x 0x0111: pmt_pid 0x Reg -- France 3 (running) 0x 0x01ff: pmt_pid 0x ATH -- (null) (running) WARNING: filter timeout pid 0x0010 tune to: -10:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE WARNING: tuning failed!!! tune to: -10:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! dumping lists (21 services) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB3000MC : autosearch doesn't work
matthieu castet wrote: Hi, If I try to scan some transponders with the initial file [1] and the scan utility from dvb-apps [2], the autosearch works for the configuration 2/3 NONE QAM64 8k 1/32 NONE but not for the configuration 3/4 NONE QAM64 8k 1/8 NONE. It seems dib3000mc_autosearch_is_irq return 1 (failed), when I try to tune to T 58600 8MHz AUTO NONE QAM64 AUTO AUTO NONE. What's the meaning of failed ? Have you got an idea with the autosearch failed ? I forgot to say that the old DiB3000MC driver autosearch works : initial transponder 47400 0 9 9 3 2 4 0 initial transponder 47400 0 2 9 3 1 0 0 initial transponder 58600 0 9 9 3 2 4 0 initial transponder 58600 0 3 9 3 1 2 0 tune to: 47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE 0x 0x0201: pmt_pid 0x NTN -- Direct 8 (running) 0x 0x0202: pmt_pid 0x NTN -- TMC (running) 0x 0x0203: pmt_pid 0x NTN -- BFM TV (running) 0x 0x0204: pmt_pid 0x NTN -- iTELE (running) 0x 0x0205: pmt_pid 0x NTN -- Europe 2 TV (running) 0x 0x0206: pmt_pid 0x NTN -- Gulli (running) Network Name 'réseau numérique terrestre français' tune to: 47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE 0x 0x0201: pmt_pid 0x NTN -- Direct 8 (running) 0x 0x0202: pmt_pid 0x NTN -- TMC (running) 0x 0x0203: pmt_pid 0x NTN -- BFM TV (running) 0x 0x0204: pmt_pid 0x NTN -- iTELE (running) 0x 0x0205: pmt_pid 0x NTN -- Europe 2 TV (running) 0x 0x0206: pmt_pid 0x NTN -- Gulli (running) Network Name 'réseau numérique terrestre français' tune to: 58600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_64:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE 0x 0x0101: pmt_pid 0x GR1 -- France 2 (running) 0x 0x0103: pmt_pid 0x GR1 -- France 4 (running) 0x 0x0104: pmt_pid 0x GR1 -- France 5 (running) 0x 0x0105: pmt_pid 0x GR1 -- ARTE (running) 0x 0x0106: pmt_pid 0x GR1 -- LCP (running) 0x 0x0111: pmt_pid 0x Reg -- France 3 (running) 0x 0x01ff: pmt_pid 0x ATH -- (null) (running) WARNING: filter timeout pid 0x0010 tune to: 58600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x 0x0101: pmt_pid 0x GR1 -- France 2 (running) 0x 0x0103: pmt_pid 0x GR1 -- France 4 (running) 0x 0x0104: pmt_pid 0x GR1 -- France 5 (running) 0x 0x0105: pmt_pid 0x GR1 -- ARTE (running) 0x 0x0106: pmt_pid 0x GR1 -- LCP (running) 0x 0x0111: pmt_pid 0x Reg -- France 3 (running) 0x 0x01ff: pmt_pid 0x ATH -- (null) (running) WARNING: filter timeout pid 0x0010 tune to: -10:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE WARNING: tuning failed!!! tune to: -10:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] TDA10046H very slow to tune
I'm noticing that the KWORLD DVB-T 220 with the TDA10046H tuner is very slow to tune 2 to 5 seconds. Cards like the AverMedia 771 tune in less then a second. Is this a problem with the driver or the chip? Barry ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Remote control key recognition
Hi everybody ! I have a pinnacle PCTV usb stick, it just works. The only problem is with the remote control, indeed all keys are not recognized by xev, and number key such as 1, 2 etc are recognized as é , because I use a french layout for my keyboard. So I just want to know how to add IR code/signal that are not recognized and in which file I can change the conversion between IR Code and Key code. PS : I use em2880_dvb, em28xx module and the stick info are eb1a:2870 eMPIA Technology, Inc. Kind Regards. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] es-Sevilla DVB-T
Hello. # DVB-T Sevilla (Andalucia) by x2 15 Agosto 2006 # T freq bw fec_hi fec_lo mod transm-mode guard-interval hierarchy T 76200 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C57 T 79400 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C61 T 83400 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C66 T 84200 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C67 T 85000 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C68 T 85800 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C69 Detalle de canales ###57 TV #TVE 1 http://www.tve.es/ #TVE 2 http://www.tve.es/ #24H TVE http://www.tve.es/ #Clan/50 TVE http://www.tve.es/ ###57 RADIO #RNE1 http://www.rtve.es/rne/web/index.php #RNEC http://www.rtve.es/rne/web/index.php #RNE3 http://www.rtve.es/rne/web/index.php ###61 TV #Canal 2 Andalucia http://www.canalsur.es/ #Canal Sur TV http://www.canalsur.es/ ###66 TV #TELEDEPORTE http://www.tve.es/ #VEO http://www.veo.es/ #SETenVEO http://www.veo.es/ #NET TVhttp://www.nettv.es/ ###67 TV #CUATROhttp://www.cuatro.com/ #CNN+ http://www.plus.es/codigo/noticias/noticias.asp #40 LATINO http://www.40tv.com/ #laSexta http://www.lasexta.com/ 68 TV #Telecinco http://www.telecinco.es/ #T5 Estrellas http://www.telecinco.es/ #T5 Sport http://www.telecinco.es/ #FLYMUSIC http://www.flymusic.tv/ 69 TV #ANTENA 3 http://www.antena3tv.com/ #ANTENA.NEOX http://www.antena3tv.com/ #ANTENA.NOVA http://www.antena3tv.com/ #Telehit http://www.esmas.com/telehit/ 69 RADIO #ONDA CERO http://www.ondacero.es/ #EUROPA FM http://www.europafm.com/ #ONDA MELODIA http://www.ondacero.es/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: es-Sevilla DVB-T
Good bye to all I erase of the list. El mar, 15-08-2006 a las 15:14 +0200, x2 escribió: Hello. # DVB-T Sevilla (Andalucia) by x2 15 Agosto 2006 # T freq bw fec_hi fec_lo mod transm-mode guard-interval hierarchy T 76200 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C57 T 79400 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C61 T 83400 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C66 T 84200 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C67 T 85000 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C68 T 85800 8MHz 2/3 NONE QAM64 8k 1/4 NONE # C69 Detalle de canales ###57 TV #TVE 1 http://www.tve.es/ #TVE 2 http://www.tve.es/ #24H TVE http://www.tve.es/ #Clan/50 TVE http://www.tve.es/ ###57 RADIO #RNE1 http://www.rtve.es/rne/web/index.php #RNEC http://www.rtve.es/rne/web/index.php #RNE3 http://www.rtve.es/rne/web/index.php ###61 TV #Canal 2 Andalucia http://www.canalsur.es/ #Canal Sur TV http://www.canalsur.es/ ###66 TV #TELEDEPORTE http://www.tve.es/ #VEO http://www.veo.es/ #SETenVEO http://www.veo.es/ #NET TVhttp://www.nettv.es/ ###67 TV #CUATROhttp://www.cuatro.com/ #CNN+ http://www.plus.es/codigo/noticias/noticias.asp #40 LATINO http://www.40tv.com/ #laSexta http://www.lasexta.com/ 68 TV #Telecinco http://www.telecinco.es/ #T5 Estrellas http://www.telecinco.es/ #T5 Sport http://www.telecinco.es/ #FLYMUSIC http://www.flymusic.tv/ 69 TV #ANTENA 3 http://www.antena3tv.com/ #ANTENA.NEOX http://www.antena3tv.com/ #ANTENA.NOVA http://www.antena3tv.com/ #Telehit http://www.esmas.com/telehit/ 69 RADIO #ONDA CERO http://www.ondacero.es/ #EUROPA FM http://www.europafm.com/ #ONDA MELODIA http://www.ondacero.es/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Hello! Can anybody show me where I can read some RTFM about Twinhan 1025 DVB card? My problem for this moment is than the /dev/dvb/adapter0/frontend0 didn't created. Sysinfo: Ububntu 6.06, kernel 2.6.15, can post additional info if required. -- Best Regards, Nick Fedchik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Nick Fedchik wrote: Hello! Can anybody show me where I can read some RTFM about Twinhan 1025 DVB card? My problem for this moment is than the /dev/dvb/adapter0/frontend0 didn't created. Sysinfo: Ububntu 6.06, kernel 2.6.15, can post additional info if required. 2.6.15 is too old. Use the latest Hg tree.. http://www.linuxtv.org/repo/ Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-SPCICard
Dave Schile wrote: Well, I tried different compiles and saw nothing different. I found that this LNB uses an oscillator running at 11.25 GHz. So I put these lines in the dvb_defaults.h file for dvbtune: /* DVB-S */ // With a diseqc system you may need different values per LNB. I hope // no-one ever asks for that :-) #define SLOF (11700*1000UL) #define LOF1 (11250*1000UL) #define LOF2 (11250*1000UL) is that right? Still, the unit seems not to tune at all. I keep thinking I'm missing something simple. Also, the Opperation not supported messages have me dumbfounded while trying to 'dvbtune -m' The operation not supported message is fine. You can ignore it safely. Some people in North America with Circular polarizations have got back with problems with scan. Is it the same issue, other than the LNB LOF settings ? Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCI Card
Dave Schile wrote: I just tried using the modules from the kernel source 2.6.17.8 (that is the latest stable kernel as of this writing) the dst module couldn't even find the device. Here is dmesg after 'modprobe dst verbose=4' I think the latest changes is not yet in mainline kernel. Use the one from http://linuxtv.org/repo Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCI Card
Dave Schile wrote: I just used hg to download the latest v4l-dvb and dvb-apps from Mercurial and everything compiled and installed fine. The drivers all modprobe fine. I modpobe in this order: dvb-core bttv dvb-bt8xx dst Is there anything I'm missing there? dmesg says: ###dmesg# DVB: registering new adapter (bttv0). dst(0) dst_get_device_id: Recognise [DST-03T] dst(0) dst_get_device_id: Unsupported dst(0) dst_check_mb86a15: Found a MB86A15 NIM dst(0) dst_get_device_id: [DST-03T] has a [MB 86A15] dst(0) dst_get_device_id: [DST-03T] has a [MB 86A15] DST type flags : 0x2 ts204 0x4 symdiv 0x10 firmware version = 2 dst(0) dst_get_mac: MAC Address=[00:08:ca:19:d2:00] DVB: registering frontend 0 (DST DVB-S)... ### this seems fne to me. frontend and card driver 's everything 's fine and perfect. Now the problems... dvbtune to the satellite Galaxy 10R at 123 degrees west., I'm in southern California: # dvbtune -f 1180 -p V -s 26657 Using DVB card DST DVB-S tuning DVB-S to L-Band:0, Pol:V Srate=26657000, 22kHz=off polling Getting frontend event FE_STATUS: polling polling polling Looks like no signal. Something else is wrong .. ? Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
My problem for this moment is than the /dev/dvb/adapter0/frontend0 didn't created. Sysinfo: Ububntu 6.06, kernel 2.6.15, can post additional info if required. 2.6.15 is too old. Use the latest Hg tree.. http://www.linuxtv.org/repo/ Are You sure than that tree has a Twinhan 1025 support? ( http://www.twinhan.com/product_satellite_3.asp ) Well I will try that one... -- Best Regards, Nick Fedchik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan CAM
[EMAIL PROTECTED] wrote: Hi All! Trying for more than one year to get my Twinhan CAM module (IRDETO) to work with without success I have now decided to give it a try myself... However I have inspected the code parts around Twinhan-CI and DVB / DVB-APPS CI code and I am now unsure where to start... Can someone explain how the code in dvb-apps/libdvben50221, dvb/dvb-core/dvb_ca_* and bt8xx/dst_ca is related? dst_ca does not sue dvb-core/dvb_ca_* but is dependent on dvb-apps for PMT generation from the incoming stream. So far I understand that there is a high-level layer API for the Twinhan-DST card (bt8xx/dst_ca?). But is it meant to be used from the (lower level? api ?=) This all seems a little odd to me... Maybe someone can shed some light in this Use zap alone (from dvb-apps util/zap), It should work for you. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Nick Fedchik wrote: My problem for this moment is than the /dev/dvb/adapter0/frontend0 didn't created. Sysinfo: Ububntu 6.06, kernel 2.6.15, can post additional info if required. 2.6.15 is too old. Use the latest Hg tree.. http://www.linuxtv.org/repo/ Are You sure than that tree has a Twinhan 1025 support? ( http://www.twinhan.com/product_satellite_3.asp ) Well I will try that one... Yep, the VP-1025/VP-1032 are the only devices that come with a Fujitsu MB86A15 Silicon tuner Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvb driver port to OpenSolaris
On Tue, Aug 15, 2006 at 08:43:20AM +, Birgit Halegmaier wrote: is there a plan to port the DVB Driver to OpenSolaris? a) not that i know of b) there afaik are massive licence issues since the linux dvb drivers are gpl and opensolaris isn't (its CDDL). also see http://www.gnu.org/philosophy/license-list.html and scroll down to CDDL. --snip-- So, a module covered by the GPL and a module covered by the CDDL cannot legally be linked together. --/snip-- so as far as my interpretation (i'm not a lawyer) is concerned, its a total no-go. sun shot itself into the foot with this license. sorry to be the bad-news-teller. -- kind regards Joachim Steiger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Are You sure than that tree has a Twinhan 1025 support? ( http://www.twinhan.com/product_satellite_3.asp ) Well I will try that one... Yep, the VP-1025/VP-1032 are the only devices that come with a Fujitsu MB86A15 Silicon tuner I seen that MB86A15 on a card. But how can it help me to set up /dev/dvb/adapter0/frontend0 ? What the module should I insert? PS: Sorry, I see than my questions looks dummy, but just I newby in DVB/V4L -- Best Regards, Nick Fedchik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: [v4l-dvb-maintainer] VBI OOPS 2.6.17.8
Hello thomas, please forgive me, this is a webmail client. thomas schorpp writes: Michael Hunold wrote: this is a known issue with the analogtuner part of siemens dvb-c, ive stated that in my mail with my patch, the tuner code is buggy and may oops with tvtime or kdetv, cause of their driver access/capture behaviour. Even when the application uses the API in a very creative way, it should never result in an oops. Something is not correctly handled or initialized, probably in my saa7146 vbi code. This is about VBI capture on the *analog* parts of a DVB-C card, ie. on the analog cable channels that can be viewed through the saa711x on the saa7146 input channel b. What is the current status anyway? Did somebody ever got this to work? yes, see list archives and attachment. CVBS imput and tuning is working here fine with xawtv since i created the patch. the patch was created to be able to use the saa7113 input from the analog card extension board, i suggested to plug in an old VHS or other as tuner, since the tda9819 analog part of the siemens card is low analogtv-demodulation quality anyway... I know that tuning and using the cvbs input works, but I'm particularly interested if VBI capturing ever worked. So: did anybody use VBI capturing on the analog input of a DVB-C card yet? If not, then the easiest fix is to remove V4L2_CAP_VBI_CAPTURE from struct saa7146_ext_vv av7110_vv_data_c in av7110_v4l.c objection, thats no solution so far. I did not mean to remove support for analog tv completely, just for the vbi capturing parts. I tried to get it to work in 2004, but gave up when I realised that the saa7113 and the saa7146 probably don't play together. IIRC it was not possible that the BRS of the saa7146 correctly syncronizes to the saa7113 output. If nobody has tried to get it to run since then, then I vote for doing the fix I described in the other mail. Best regards Michael Hunold. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Are You sure than that tree has a Twinhan 1025 support? ( http://www.twinhan.com/product_satellite_3.asp ) Well I will try that one... Yep, the VP-1025/VP-1032 are the only devices that come with a Fujitsu MB86A15 Silicon tuner I seen that MB86A15 on a card. But how can it help me to set up /dev/dvb/adapter0/frontend0 ? What the module should I insert? PS: Sorry, I see than my questions looks dummy, but just I newby in DVB/V4L -- Best Regards, Nick Fedchik Nick: I have the same card and I'm stumbling through getting it to work. With the 2.6.17.8 Kernel and the latest v4l-dvb modules from hg, I modprobe dvb-core, bttv, dvb-bt8xx, and dst. After all those, it appears the /dev/dvb/adapter0 nodes get built. Manu: You mention the Fujitsu MB86A15 Silicon tuner, but I don't see it in mercurials linux/Documentation/video4linux/CARDLIST.tuner file. Should that tuner be specified as an option with dst? Best, Dave Schile ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Dave Schile wrote: Are You sure than that tree has a Twinhan 1025 support? ( http://www.twinhan.com/product_satellite_3.asp ) Well I will try that one... Yep, the VP-1025/VP-1032 are the only devices that come with a Fujitsu MB86A15 Silicon tuner I seen that MB86A15 on a card. But how can it help me to set up /dev/dvb/adapter0/frontend0 ? What the module should I insert? PS: Sorry, I see than my questions looks dummy, but just I newby in DVB/V4L -- Best Regards, Nick Fedchik Nick: I have the same card and I'm stumbling through getting it to work. With the 2.6.17.8 Kernel and the latest v4l-dvb modules from hg, I modprobe dvb-core, bttv, dvb-bt8xx, and dst. After all those, it appears the /dev/dvb/adapter0 nodes get built. Manu: You mention the Fujitsu MB86A15 Silicon tuner, but I don't see it in mercurials linux/Documentation/video4linux/CARDLIST.tuner file. Should that tuner be specified as an option with dst? the tuner handling is in firmware. using the dst module alone should help Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Nick Fedchik wrote: Are You sure than that tree has a Twinhan 1025 support? ( http://www.twinhan.com/product_satellite_3.asp ) Well I will try that one... Yep, the VP-1025/VP-1032 are the only devices that come with a Fujitsu MB86A15 Silicon tuner I seen that MB86A15 on a card. But how can it help me to set up /dev/dvb/adapter0/frontend0 ? What the module should I insert? modprobe dst verbose=4 modprobe dvb-bt8xx It is documented in bt8xx.txt under Documentation Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
I seen that MB86A15 on a card. But how can it help me to set up /dev/dvb/adapter0/frontend0 ? What the module should I insert? PS: Sorry, I see than my questions looks dummy, but just I newby in DVB/V4L Nick: I have the same card and I'm stumbling through getting it to work. With the 2.6.17.8 Kernel and the latest v4l-dvb modules from hg, I modprobe dvb-core, bttv, dvb-bt8xx, and dst. After all those, it appears the /dev/dvb/adapter0 nodes get built. Oh, it's very important note if I need to use work. With the 2.6.17.8 Kernel and the latest v4l-dvb modules from hg because I unsuccessfully tried it in vanilla 2.6.17.8 kernel Ok, I'll try it tonight and report here ASAP -- Best Regards, Nick Fedchik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCI Card
From: Manu Abraham [EMAIL PROTECTED] To: Dave Schile [EMAIL PROTECTED] CC: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCI Card Date: Tue, 15 Aug 2006 17:48:00 +0400 MIME-Version: 1.0 Received: from py-out-1112.google.com ([64.233.166.183]) by bay0-mc10-f5.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, 15 Aug 2006 06:48:07 -0700 Received: by py-out-1112.google.com with SMTP id e30so1426161pyafor [EMAIL PROTECTED]; Tue, 15 Aug 2006 06:48:07 -0700 (PDT) Received: by 10.35.77.1 with SMTP id e1mr15530077pyl;Tue, 15 Aug 2006 06:48:07 -0700 (PDT) Received: from ?192.168.1.239? ( [83.110.77.204])by mx.gmail.com with ESMTP id 18sm2366249nzo.2006.08.15.06.48.03;Tue, 15 Aug 2006 06:48:05 -0700 (PDT) X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ucejPgvNE/9gAfw8XENwPbVE78b/JHQbpkZbKozbqge+HgkDiE2jWnJWtaEJjQf+HEMocdMvfljhxcZSPRuKphjQj14qDBy0/d2Hy6mjX2nG54c82yP/LULd+cUF/0kgjANVXtDI4+w2IdwEBZ9mFZt1O9c4BkyXFWwtcj0xEfY= Return-Path: [EMAIL PROTECTED] User-Agent: Thunderbird 1.5.0.5 (X11/20060719) References: [EMAIL PROTECTED] X-OriginalArrivalTime: 15 Aug 2006 13:48:08.0108 (UTC) FILETIME=[70B056C0:01C6C071] Dave Schile wrote: I just used hg to download the latest v4l-dvb and dvb-apps from Mercurial and everything compiled and installed fine. The drivers all modprobe fine. I modpobe in this order: dvb-core bttv dvb-bt8xx dst Is there anything I'm missing there? dmesg says: ###dmesg# DVB: registering new adapter (bttv0). dst(0) dst_get_device_id: Recognise [DST-03T] dst(0) dst_get_device_id: Unsupported dst(0) dst_check_mb86a15: Found a MB86A15 NIM dst(0) dst_get_device_id: [DST-03T] has a [MB 86A15] dst(0) dst_get_device_id: [DST-03T] has a [MB 86A15] DST type flags : 0x2 ts204 0x4 symdiv 0x10 firmware version = 2 dst(0) dst_get_mac: MAC Address=[00:08:ca:19:d2:00] DVB: registering frontend 0 (DST DVB-S)... ### this seems fne to me. frontend and card driver 's everything 's fine and perfect. Now the problems... dvbtune to the satellite Galaxy 10R at 123 degrees west., I'm in southern California: # dvbtune -f 1180 -p V -s 26657 Using DVB card DST DVB-S tuning DVB-S to L-Band:0, Pol:V Srate=26657000, 22kHz=off polling Getting frontend event FE_STATUS: polling polling polling Looks like no signal. Something else is wrong .. ? Manu I suppose it could be a weak signal. I am using an inline signal meter to aim the dish and it shows a signal. How about polarization? It turns out this LNB is Circular only (thank you Steven Toth). How do I get dvbtune or other szap to use circular (L or R) polarity? Is this supported in v4l-dvb? Also, How do I get the dst_test to work? I always get an error stating that the frontend can't open /dev/dvb/adapter0/ca0 Even after I create that node manually and set it's permissions I get that error with all invocations of dst_test. Thanks much! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0)
Dave Schile From: Nick Fedchik [EMAIL PROTECTED] To: Manu Abraham [EMAIL PROTECTED] CC: Dave Schile [EMAIL PROTECTED], linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Twinhan 1025 (/dev/dvb/adapter0/frontend0) Date: Tue, 15 Aug 2006 19:11:10 +0300 (EEST) MIME-Version: 1.0 Received: from vatra.dib.ukrsat.com ([212.35.172.164]) by bay0-mc1-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, 15 Aug 2006 09:15:06 -0700 Received: from localhost (localhost.localdomain [127.0.0.1])by vatra.dib.ukrsat.com (Postfix) with ESMTP id 27F6FE6359;Tue, 15 Aug 2006 19:11:11 +0300 (EEST) Received: from vatra.dib.ukrsat.com ([127.0.0.1]) by localhost (vatra.dib.ukrsat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00560-09; Tue, 15 Aug 2006 19:11:10 +0300 (EEST) Received: by vatra.dib.ukrsat.com (Postfix, from userid 96)id A9AC3E6305; Tue, 15 Aug 2006 19:11:10 +0300 (EEST) Received: from irtc.oss.dg.net.ua ([213.186.207.66])(SquirrelMail authenticated user [EMAIL PROTECTED])by www.dib.ukrsat.com with HTTP;Tue, 15 Aug 2006 19:11:10 +0300 (EEST) X-Message-Info: LsUYwwHHNt0q6joVD1vf1aH+DeHJxBQe3t9OoqZADNw= References: [EMAIL PROTECTED] [EMAIL PROTECTED] User-Agent: SquirrelMail/1.4.7 X-Virus-Scanned: by amavisd-new at dib.ukrsat.com Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 15 Aug 2006 16:15:07.0395 (UTC) FILETIME=[F964BD30:01C6C085] I seen that MB86A15 on a card. But how can it help me to set up /dev/dvb/adapter0/frontend0 ? What the module should I insert? PS: Sorry, I see than my questions looks dummy, but just I newby in DVB/V4L Nick: I have the same card and I'm stumbling through getting it to work. With the 2.6.17.8 Kernel and the latest v4l-dvb modules from hg, I modprobe dvb-core, bttv, dvb-bt8xx, and dst. After all those, it appears the /dev/dvb/adapter0 nodes get built. Oh, it's very important note if I need to use work. With the 2.6.17.8 Kernel and the latest v4l-dvb modules from hg because I unsuccessfully tried it in vanilla 2.6.17.8 kernel Ok, I'll try it tonight and report here ASAP -- Best Regards, Nick Fedchik Yeah, the dst module in the 2.6.17.8 kernel from kernel.org doesn't seem to find the frontend on this card (the Twinhan VP1025). And therefore the device nodes don't get built. Dave ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Twinhan Sat-CI 1034 v1.2 Is there any progress?
On juli 20th there was some conversation going on about the Twinhan Sat-CI 1034 v1.2 card. The conversation was about that there is not yet support for this card in linux dvb but Manu Abraham said it would take probably some weeks. Is there any repository allready available with some work for this card or is no one yet working on it. I have such a card and would like to help to develop the driver. I am not a driver developer but I do have programming experience and am willing to do testing. Regards, Michel. Info about the chips on the card: Twinhan 1034 ver1.2 board One chip with text: Japan MB86A16L D610 K0B E1 (Is a Fujitsu Tuner and Decoder in one) Could not find detailed specs yet only what it should be capable of. And one: Mantis K61468.2A-2 041213 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Hi Manu, Manu Abraham wrote: Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? To check once more, I have just setup once again: = linux-2.6.17.8 = hg v4l-dvb (fresh clone of today) At a fresh 'make' on v4l-dvb, I do get several warnings about missing kernel configuration flags, but it seems that I can ignore those, as none of those seems to affect my configuration. The output of dvbscan -v is: tune to: 30675:INVERSION_AUTO:690:FEC_NONE:QAM_64 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 WARNING: tuning failed!!! tune to: 30675:INVERSION_AUTO:690:FEC_NONE:QAM_64 (tuning failed) tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 ... and no PMTs get reported. Also vlc complains that 'dvb access warning: no lock, tuning again' every 20 seconds or so. Unfortunately I cannot test 20060115's snapshot against linux-2.6.17.8 because the MODULE_PARM macro is no longer supported in 2.6.17 and I get a compile error. But if I compile with linux-2.6.13.3: = vlc-dvb-20060115 works (provided I take out TS204 from DCT-CI record) = vlc-dvb hg clone does not work. So something seems to be broken... Z. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCICard
I suppose it could be a weak signal. I am using an inline signal meter to aim the dish and it shows a signal. How about polarization? It turns out this LNB is Circular only (thank you Steven Toth). How do I get dvbtune or other szap to use circular (L or R) polarity? Is this supported in v4l-dvb? I don't fully understand the real electrical/RF implications of circular left/right vs linear horizontal/vertical other than to say that it's related to how the signal is sent (polarised) from the satellite (it's polarisation) and that you have to have a matching LNB of the same polarisation. In some cases I've been able to receive circular right with a H/V LNB but that was a rare exception, circular left never worked. I'd say buy a linear H/V LNB if your goals are to tune to H/V feeds. I'm not suggesting this is your only issue but it's certainly one of the most important. If you have access to a spectrum analyzer when you could see very quickly the L-band representation to see whether the LNB is down-converting correctly, or whether you have a tuner related issue. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCI Card
Dave Schile wrote: I suppose it could be a weak signal. I am using an inline signal meter to aim the dish and it shows a signal. How about polarization? It turns out this LNB is Circular only (thank you Steven Toth). How do I get dvbtune or other szap to use circular (L or R) polarity? Is this supported in v4l-dvb? The 1025 is not that sensitive to weak signals. Whether it is H/V or L-R/R-L, both translates to 13/18V. There are some LNB 's which don't work just alongwith 13/18V for a polarization change. Also, How do I get the dst_test to work? I always get an error stating that the frontend can't open /dev/dvb/adapter0/ca0 Even after I create that node manually and set it's permissions I get that error with all invocations of dst_test. dst_test is meant for CA devices only, not for FTA devices Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCICard
I don't fully understand the real electrical/RF implications of circular left/right vs linear horizontal/vertical other than to say that it's related to how the signal is sent (polarised) from the satellite (it's polarisation) and that you have to have a matching LNB of the same polarisation. In some cases I've been able to receive circular right with a H/V LNB but that was a rare exception, circular left never worked. I'd say buy a linear H/V LNB if your goals are to tune to H/V feeds. I'm not suggesting this is your only issue but it's certainly one of the most important. If you have access to a spectrum analyzer when you could see very quickly the L-band representation to see whether the LNB is down-converting correctly, or whether you have a tuner related issue. Steve Thanks, Steve. I was getting confused because it appears that even if you specify R or L in channels.conf file, the response from szap still only shows V or H. Other documentation that I found says that circular right is activated on the LNB with 13 volts, the same as linear vertical would be activated. Circular left is activated with 18 volts the same way linear horizontal would be. Does that sound correct? I am now starting to think that possibly the signal I'm trying to tune to is too weak. I am only using a small 18 inch DirecTV dish. Any insights on this? Thanks much. David ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan Sat-CI 1034 v1.2 Is there any progress?
Michel Verbraak wrote: On juli 20th there was some conversation going on about the Twinhan Sat-CI 1034 v1.2 card. The conversation was about that there is not yet support for this card in linux dvb but Manu Abraham said it would take probably some weeks. Is there any repository allready available with some work for this card or is no one yet working on it. Work is going on. This device is a bit different from other frontends (It is a DC receiver and lot of strange things it brings along). Repository is not available yet. It is not only the frontend that is different for this card, but the PCI bridge and everything is completely new. I have such a card and would like to help to develop the driver. I am not a driver developer but I do have programming experience and am willing to do testing. Have couple of cards here CA and FTA types, work still in progress. Current status is that PCI bridge is done and work is going on with the frontends. Lot of new cards, with the same PCI bridge. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan Sat-CI 1034 v1.2 Is there any progress?
Thanks for the answer. Looking forward for the first examples. Regards, Michel. Manu Abraham schreef: Michel Verbraak wrote: On juli 20th there was some conversation going on about the Twinhan Sat-CI 1034 v1.2 card. The conversation was about that there is not yet support for this card in linux dvb but Manu Abraham said it would take probably some weeks. Is there any repository allready available with some work for this card or is no one yet working on it. Work is going on. This device is a bit different from other frontends (It is a DC receiver and lot of strange things it brings along). Repository is not available yet. It is not only the frontend that is different for this card, but the PCI bridge and everything is completely new. I have such a card and would like to help to develop the driver. I am not a driver developer but I do have programming experience and am willing to do testing. Have couple of cards here CA and FTA types, work still in progress. Current status is that PCI bridge is done and work is going on with the frontends. Lot of new cards, with the same PCI bridge. Manu ___ 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] Unable to rmmod dst and dvb-bt8xx
Since the most recent build of the v4l-dvb modules I have not been able to rmmod dst without the -f (force) option. dst is removed with -f, but then I am completely unable to rmmod dvb-bt8xx, even with -f. It returns: ERROR: Removing 'dvb_bt8xx': Device or resource busy but 'lsmod | grep dvb-bt8xx' returns: dvb_bt8xx 18052 0 dvb_core 80552 1 dvb_bt8xx bt878 11048 1 dvb_bt8xx dvb_pll14724 1 dvb_bt8xx bttv 172404 2 dvb_bt8xx,bt878 firmware_class 10496 2 dvb_bt8xx,bttv i2c_core 21520 8 dvb_bt8xx,dvb_pll,tuner,bttv,tveeprom,nvidia,i2c_viapro,i2c_algo_bit which makes me think dvb-bt8xx isn't being used by anything. What would cause this module to be busy? At this point my abilities in linux make rebooting the only option to re-insmod the dvb modules. Thanks for any help with this. Dave ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Zoilo Gomez wrote: Hi Manu, Manu Abraham wrote: Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? To check once more, I have just setup once again: = linux-2.6.17.8 = hg v4l-dvb (fresh clone of today) At a fresh 'make' on v4l-dvb, I do get several warnings about missing kernel configuration flags, but it seems that I can ignore those, as none of those seems to affect my configuration. The output of dvbscan -v is: ... and no PMTs get reported. Also vlc complains that 'dvb access warning: no lock, tuning again' every 20 seconds or so. Unfortunately I cannot test 20060115's snapshot against linux-2.6.17.8 because the MODULE_PARM macro is no longer supported in 2.6.17 and I get a compile error. But if I compile with linux-2.6.13.3: = vlc-dvb-20060115 works (provided I take out TS204 from DCT-CI record) = vlc-dvb hg clone does not work. So something seems to be broken... Is this a card with a CI or just a FTA card ? Is it the same card ..? http://thadathil.net:8000/gallery/album12 loading dst with verbose=4 and then tuning what messages do you get ? Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TDA10046H very slow to tune
Hi, Barry Barry Scott wrote: I'm noticing that the KWORLD DVB-T 220 with the TDA10046H tuner is very slow to tune 2 to 5 seconds. Cards like the AverMedia 771 tune in less then a second. Is this a problem with the driver or the chip? Barry This is not normal, do you use a recent version of driver and firmware? The tuning takes about 0.5 seconds. With good signals, the TDA10046 locks within a second. You need to add the time for the DVB application to fill its buffers and to find an I-frame. This is longer but the same for all cards. But: the first lock in a session (open dvb device) always takes longer becase the chips need to recover from sleep mode, check and download the firmware and determine some parameters. This is partly intention, partly chip behaviour. If the lock always takes longer, this might be due to poor signal quality. Updating the firmware might help. There also is one special issue with the TDA8275a silicon tuner: Due to its pinciple, it is sensitive to strong transmitters on another channel. Classic tuner cans handle this better. Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
I believe I have the same card, because the same TS204 stuff applies and tuning is a real pain. Only some old modified drivers work. My card has CI, but the link you gave doesn't seem to work. What did you mean by: In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems? I'm away from that PC but I'll ssh and try to get the debug info. Manu Abraham wrote: Zoilo Gomez wrote: Hi Manu, Manu Abraham wrote: Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? To check once more, I have just setup once again: = linux-2.6.17.8 = hg v4l-dvb (fresh clone of today) At a fresh 'make' on v4l-dvb, I do get several warnings about missing kernel configuration flags, but it seems that I can ignore those, as none of those seems to affect my configuration. The output of dvbscan -v is: ... and no PMTs get reported. Also vlc complains that 'dvb access warning: no lock, tuning again' every 20 seconds or so. Unfortunately I cannot test 20060115's snapshot against linux-2.6.17.8 because the MODULE_PARM macro is no longer supported in 2.6.17 and I get a compile error. But if I compile with linux-2.6.13.3: = vlc-dvb-20060115 works (provided I take out TS204 from DCT-CI record) = vlc-dvb hg clone does not work. So something seems to be broken... Is this a card with a CI or just a FTA card ? Is it the same card ..? http://thadathil.net:8000/gallery/album12 loading dst with verbose=4 and then tuning what messages do you get ? Manu ___ 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] Unable to rmmod dst and dvb-bt8xx
Dave Schile wrote: Since the most recent build of the v4l-dvb modules I have not been able to rmmod dst without the -f (force) option. dst is removed with -f, but then I am completely unable to rmmod dvb-bt8xx, even with -f. It returns: ERROR: Removing 'dvb_bt8xx': Device or resource busy but 'lsmod | grep dvb-bt8xx' returns: dvb_bt8xx 18052 0 dvb_core 80552 1 dvb_bt8xx bt878 11048 1 dvb_bt8xx dvb_pll14724 1 dvb_bt8xx bttv 172404 2 dvb_bt8xx,bt878 firmware_class 10496 2 dvb_bt8xx,bttv i2c_core 21520 8 dvb_bt8xx,dvb_pll,tuner,bttv,tveeprom,nvidia,i2c_viapro,i2c_algo_bit which makes me think dvb-bt8xx isn't being used by anything. What would cause this module to be busy? At this point my abilities in linux make rebooting the only option to re-insmod the dvb modules. Does the attached patch help ? rmmod dvb-bt8xx rmmod dst_ca rmmod dst Manu diff -Naurp v4l-dvb.orig/linux/drivers/media/dvb/bt8xx/dst.c v4l-dvb/linux/drivers/media/dvb/bt8xx/dst.c --- v4l-dvb.orig/linux/drivers/media/dvb/bt8xx/dst.c 2006-08-15 23:19:20.0 +0400 +++ v4l-dvb/linux/drivers/media/dvb/bt8xx/dst.c 2006-08-15 23:21:40.0 +0400 @@ -1721,9 +1721,6 @@ static void dst_release(struct dvb_front symbol_put(dst_ca_attach); #endif } -#ifdef CONFIG_DVB_CORE_ATTACH - symbol_put(dst_attach); -#endif kfree(state); } ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-SPCICard
I don't fully understand the real electrical/RF implications of circular left/right vs linear horizontal/vertical other than to say that it's related to how the signal is sent (polarised) from the satellite (it's polarisation) and that you have to have a matching LNB of the same polarisation. In some cases I've been able to receive circular right with a H/V LNB but that was a rare exception, circular left never worked. I'd say buy a linear H/V LNB if your goals are to tune to H/V feeds. I'm not suggesting this is your only issue but it's certainly one of the most important. If you have access to a spectrum analyzer when you could see very quickly the L-band representation to see whether the LNB is down-converting correctly, or whether you have a tuner related issue. Steve Thanks, Steve. I was getting confused because it appears that even if you specify R or L in channels.conf file, the response from szap still only shows V or H. Other documentation that I found says that circular right is activated on the LNB with 13 volts, the same as linear vertical would be activated. Circular left is activated with 18 volts the same way linear horizontal would be. Does that sound correct? Yes. dvbtune (via the standard linux API) really uses V/H to set 13/18. R and L basically mean the same thing (13/18). The electronics on the LNB however (triggered by 13/18) deal with the polarisations differently. If you trying to receive a V/H signal on a R/L LNB this is going to be a problem. You need to match a R/L LNB with a R/L polarised satellite feed. It's an easy test, re-align your dish to 119deg where you have regular DVB feeds running on R/L polarisations - matching your DSS circular LNB. (I did a whole bunch of tests with a spectrum anaylzer and rotating circular lnbs, no effect what-so-ever on the downconverted carrier. V/H on the other hand, well, it started to bleed energy from the opposite polarisation). In the end we bought a quad LNB for the lab in New York, able to put out Linear and Circular polarisations on a pair of cables. The LNB specifically handles polarisations for V/H, R/L. I am now starting to think that possibly the signal I'm trying to tune to is too weak. I am only using a small 18 inch DirecTV dish. Any insights on this? I used a 18 inch dish for DVB-S work at ome on 119 degress, I'd suggest you give it a try. Regards, Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Ok, attached my dmesg from scan -v myscanfile. scan didn't return anything, only tuning status == 0x00. But get this, strangely scan -c returns the channels that are on that frequency. Tried 2 frequencies. No dmesg from scan -c though. So basically the card tunes but the driver doesn't understand it? Using latest hg. dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0)
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Manu Abraham wrote: Zoilo Gomez wrote: Hi Manu, Manu Abraham wrote: Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? To check once more, I have just setup once again: = linux-2.6.17.8 = hg v4l-dvb (fresh clone of today) At a fresh 'make' on v4l-dvb, I do get several warnings about missing kernel configuration flags, but it seems that I can ignore those, as none of those seems to affect my configuration. The output of dvbscan -v is: ... and no PMTs get reported. Also vlc complains that 'dvb access warning: no lock, tuning again' every 20 seconds or so. Unfortunately I cannot test 20060115's snapshot against linux-2.6.17.8 because the MODULE_PARM macro is no longer supported in 2.6.17 and I get a compile error. But if I compile with linux-2.6.13.3: = vlc-dvb-20060115 works (provided I take out TS204 from DCT-CI record) = vlc-dvb hg clone does not work. So something seems to be broken... Is this a card with a CI or just a FTA card ? It is a Twinhan Cab/CI 2031. Is it the same card ..? http://thadathil.net:8000/gallery/album12 The connection refused when attempting to contact http://thadathil.net:8000/gallery/album12; Anyway it is this card: http://www.twinhan.com/product_cable_2.asp loading dst with verbose=4 and then tuning what messages do you get ? On 2.6.17.8 + v4l-dvb (catch of the day) it says: dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 1 dst(0) read_dst: reply is 0x0 dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) dst_get_device_id: Recognise [DCT-CI] dst(0) dst_type_print: DST type: cable dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 0 dst(0) read_dst: reply is 0x0 dst(0) dst_get_mac: MAC Address=[00:08:ca:16:15:00] dst(0) dst_get_tuner_info: DST TYpe = MULTI FE dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 0 dst(0) read_dst: reply is 0xbc dst(0) dst_get_tuner_info: DST type has TS=188 dst(0) dst_get_tuner_info: DST has Daughterboard dst_ca_attach: registering DST-CA device On 2.6.13.3 + v4l-dvb-20060115 it says: dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004]
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Manu Abraham wrote: Zoilo Gomez wrote: Hi Manu, Manu Abraham wrote: Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? To check once more, I have just setup once again: = linux-2.6.17.8 = hg v4l-dvb (fresh clone of today) At a fresh 'make' on v4l-dvb, I do get several warnings about missing kernel configuration flags, but it seems that I can ignore those, as none of those seems to affect my configuration. The output of dvbscan -v is: ... and no PMTs get reported. Also vlc complains that 'dvb access warning: no lock, tuning again' every 20 seconds or so. Unfortunately I cannot test 20060115's snapshot against linux-2.6.17.8 because the MODULE_PARM macro is no longer supported in 2.6.17 and I get a compile error. But if I compile with linux-2.6.13.3: = vlc-dvb-20060115 works (provided I take out TS204 from DCT-CI record) = vlc-dvb hg clone does not work. So something seems to be broken... Is this a card with a CI or just a FTA card ? Is it the same card ..? http://thadathil.net:8000/gallery/album12 loading dst with verbose=4 and then tuning what messages do you get ? Oh sorry, you meant during tuning of course: On 2.6.17.8 + v4l-dvb (catch of the day): dst(0) dst_set_freq: set Frequency 30675 dst(0) dst_set_frontend: Set Frequency=[30675] dst(0) dst_set_symbolrate: set symrate 690 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 04 ae 3e 00 1a f4 40 b9 ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 42 dst(0) read_dst: reply is 0x9 0x0 0x4 0xae 0x3e 0x0 0x1a 0xf4 0x40 0xb9 dst(0) dst_get_tuna: checksum failure? And on 2.6.13.3 + vlc-dvb=20060115: dst_set_freq: set Frequency 30675 dst_set_frontend: Set Frequency=[30675] dst_set_symbolrate: set symrate 690 dst_write_tuna: type_flags 0x19 dst_comm_init: Initializing DST. dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] rdc_reset_state: Resetting state machine dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 04 ae 3e 00 1a f4 40 b9 ] dst_gpio_outb: mask=[], enbb=[], outhigh=[] read_dst: reply is 0xff dst_wait_dst_ready: dst wait ready after 2 read_dst: reply is 0x9 0x0 0x4 0xae 0x3e 0x0 0x1a 0xf4 0x40 0xb9 Mmmmh, that checksum error in todays hg looks suspicious Z. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Hurray, I am not the only one ! ( just when I thought I was getting crazy ..) Raido wrote: Ok, attached my dmesg from scan -v myscanfile. scan didn't return anything, only tuning status == 0x00. But get this, strangely scan -c returns the channels that are on that frequency. Tried 2 frequencies. No dmesg from scan -c though. So basically the card tunes but the driver doesn't understand it? Using latest hg. dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 05 e3 d0 00 1a db 40 0a ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x9 0x0 0x5 0xe3 0xd0 0x0 0x1a 0xdb 0x40 0xa dst(0) dst_get_tuna: checksum failure? dst(0) dst_set_freq: set Frequency 38600 dst(0) dst_set_frontend: Set Frequency=[38600] dst(0) dst_set_symbolrate: set symrate 6875000 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002],
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Zoilo Gomez wrote: Hurray, I am not the only one ! ( just when I thought I was getting crazy ..) Saw that as well. Just try this out .. in dst.c line 1360 !(state-dst_type == DST_TYPE_IS_CABLE) comment out that line and see whether you are getting any further. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Got it! Line 1360 in dst_get_tuna checks for !(state-dst_type == DST_TYPE_IS_CABLE); if I drop that condition the tuning problem seems fixed. Zoilo Gomez wrote: Manu Abraham wrote: Zoilo Gomez wrote: Hi Manu, Manu Abraham wrote: Zoilo Gomez wrote: I decided to do some tests using kernel 2.6.13.3, with following results: 1) locking problems occur using dvbscan -v (nut also (vlc -v) in the following situations: = 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060115: locks fine, dvb-scan returns 0x1f and dumps PMT quickly = 2.6.13.3 kernel with downloaded snapshot 20060715: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded snapshot 20060717: no lock, dvb-scan returns 0x00 + timeout! = 2.6.13.3 kernel with downloaded hg snapshot: no lock, dvb-scan returns 0x00 + timeout! So it seems that something has gone wrong between snapshots from January and July, with these locking problems as a result. The strange thing is that the locking problems do not prevent xine or vlc from coming up with streaming data (picture), however in between vlc -v prints 'no lock' every 15 seconds or so, but keeps going anyway Of course I would prefer to use the latest dvb-version, but I cannot get it to work for reasons mentioned above. What could possibly be wrong? Can someone tell me who has a more recent working combination (recent kernel + recent dvb-snapshot)? 2) in all dvb-snapshot versions that have I tested, I always need to remove the DST_TYPE_HAS_TS204 flag from the DCT-CI record in dst_list (dst.c), or I will not get a picture; only a long list of TS discontinuities. Aren't the necessary patches (Sept 2005) present in recent snapshots? I don't understand why I keep running into this problem In the latest v4l-dvb HEAD if you have the TS204 flag, it fixes your problems ? To check once more, I have just setup once again: = linux-2.6.17.8 = hg v4l-dvb (fresh clone of today) At a fresh 'make' on v4l-dvb, I do get several warnings about missing kernel configuration flags, but it seems that I can ignore those, as none of those seems to affect my configuration. The output of dvbscan -v is: ... and no PMTs get reported. Also vlc complains that 'dvb access warning: no lock, tuning again' every 20 seconds or so. Unfortunately I cannot test 20060115's snapshot against linux-2.6.17.8 because the MODULE_PARM macro is no longer supported in 2.6.17 and I get a compile error. But if I compile with linux-2.6.13.3: = vlc-dvb-20060115 works (provided I take out TS204 from DCT-CI record) = vlc-dvb hg clone does not work. So something seems to be broken... Is this a card with a CI or just a FTA card ? Is it the same card ..? http://thadathil.net:8000/gallery/album12 loading dst with verbose=4 and then tuning what messages do you get ? Oh sorry, you meant during tuning of course: On 2.6.17.8 + v4l-dvb (catch of the day): dst(0) dst_set_freq: set Frequency 30675 dst(0) dst_set_frontend: Set Frequency=[30675] dst(0) dst_set_symbolrate: set symrate 690 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 04 ae 3e 00 1a f4 40 b9 ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 42 dst(0) read_dst: reply is 0x9 0x0 0x4 0xae 0x3e 0x0 0x1a 0xf4 0x40 0xb9 dst(0) dst_get_tuna: checksum failure? And on 2.6.13.3 + vlc-dvb=20060115: dst_set_freq: set Frequency 30675 dst_set_frontend: Set Frequency=[30675] dst_set_symbolrate: set symrate 690 dst_write_tuna: type_flags 0x19 dst_comm_init: Initializing DST. dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] rdc_reset_state: Resetting state machine dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 09 00 04 ae 3e 00 1a f4 40 b9 ] dst_gpio_outb: mask=[], enbb=[], outhigh=[] read_dst: reply is 0xff dst_wait_dst_ready: dst wait ready after 2 read_dst: reply is 0x9 0x0 0x4 0xae 0x3e 0x0 0x1a 0xf4 0x40 0xb9 Mmmmh, that checksum error in todays hg looks suspicious Z. ___ 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] Twinhan DVB Cab/CI (2031) problems
Manu Abraham wrote: Zoilo Gomez wrote: Hurray, I am not the only one ! ( just when I thought I was getting crazy ..) Saw that as well. Just try this out .. in dst.c line 1360 !(state-dst_type == DST_TYPE_IS_CABLE) comment out that line and see whether you are getting any further. Exactly (I just found and posted the same result). That fixes the problem! Thank you very much for your support, Z. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Zoilo Gomez wrote: Got it! Line 1360 in dst_get_tuna checks for !(state-dst_type == DST_TYPE_IS_CABLE); if I drop that condition the tuning problem seems fixed. Cool. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: [v4l-dvb-maintainer] VBI OOPS 2.6.17.8
[EMAIL PROTECTED] wrote: Hello thomas, please forgive me, this is a webmail client. thomas schorpp writes: Michael Hunold wrote: this is a known issue with the analogtuner part of siemens dvb-c, ive stated that in my mail with my patch, the tuner code is buggy and may oops with tvtime or kdetv, cause of their driver access/capture behaviour. Even when the application uses the API in a very creative way, it should never result in an oops. Something is not correctly handled or initialized, probably in my saa7146 vbi code. This is about VBI capture on the *analog* parts of a DVB-C card, ie. on the analog cable channels that can be viewed through the saa711x on the saa7146 input channel b. What is the current status anyway? Did somebody ever got this to work? yes, see list archives and attachment. CVBS imput and tuning is working here fine with xawtv since i created the patch. the patch was created to be able to use the saa7113 input from the analog card extension board, i suggested to plug in an old VHS or other as tuner, since the tda9819 analog part of the siemens card is low analogtv-demodulation quality anyway... I know that tuning and using the cvbs input works, but I'm particularly interested if VBI capturing ever worked. So: did anybody use VBI capturing on the analog input of a DVB-C card yet? If not, then the easiest fix is to remove V4L2_CAP_VBI_CAPTURE from struct saa7146_ext_vv av7110_vv_data_c in av7110_v4l.c objection, thats no solution so far. I did not mean to remove support for analog tv completely, just for the vbi capturing parts. I tried to get it to work in 2004, but gave up when I realised that the saa7113 and the saa7146 probably don't play together. IIRC it was not possible that the BRS of the saa7146 correctly syncronizes to the saa7113 output. If nobody has tried to get it to run since then, then I vote for doing the fix I described in the other mail. Best regards Michael Hunold. ah ok. thats another thing. capture to file using xawtv with streamer has worked, if its that what You mean... but I've got no more old VHS movies to sample... I vote for OOPS removal too ;) y tom ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan DVB Cab/CI (2031) problems
Very cool, even my CAM works now. Took 6 months but its good now. Just out of curiosity, any comments on this? Are our cards different from the usual Cab-CI or are there just so few users of this card that this didn't come up earlier? This fix going into the main tree? Manu Abraham wrote: Zoilo Gomez wrote: Got it! Line 1360 in dst_get_tuna checks for !(state-dst_type == DST_TYPE_IS_CABLE); if I drop that condition the tuning problem seems fixed. Cool. Manu ___ 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] Twinhan DVB Cab/CI (2031) problems
Raido wrote: Very cool, even my CAM works now. Took 6 months but its good now. Just out of curiosity, any comments on this? There are 2 versions of the DCT-CI. One is a FTA card and the other the CI based card. Somebody else wanted this change and hence it went in, but that went in unnoticed. People don't test the relevant trees often and hence such breakages occur. well, all i can do is ask people to test it on a major change. If people don't want to test, can't help then. I can only test whether all the cards respond fine, but not tune and test it. Are our cards different from the usual Cab-CI or are there just so few users of this card that this didn't come up earlier? This fix going into the main tree? Yes, will fix such that both the card variants are fine. Temporarily use the fix outlined. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Twinhan Cab/CI 2031: always need to tune twice
With the locking problem fixed, it's time to move to the next problem with the Twinhan Cab/CI 2031 card. I have a Twinhan Cab/CI 2031 (well, actually I have 3 of them) and a KNC1. Using vlc, on the KNC1, when I tell the card to start streaming a program, it may take several seconds before it starts, but it works the first time. Using the Twinhan, I always have to enter the command twice; the first time nothing will happen. Then I Ctrl-C, rerun the same command and it works. So far I hav not been able to figure out where things go wrong. Sample dst output with verbose-5 during such a failing 'first tune': dst_ca_open: Device opened [df682140] dst_ca_ioctl: Getting Slot capabilities put_checksum: Computing string checksum. put_checksum: - string length : 0x07 put_checksum: - checksum : 0xb5 dst_put_ci: Put Command dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_set_freq: set Frequency 35475 dst(0) dst_set_frontend: Set Frequency=[35475] dst(0) dst_set_symbolrate: set symrate 690 dst(0) dst_set_symbolrate: DCT-CI dst(0) dst_write_tuna: type_flags 0x1219 dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 07 40 02 00 02 00 00 b5 ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 1 dst(0) read_dst: reply is 0xa 0x40 0x0 0x0 0x2 0x3 0x0 0x1 0x18 0x1 0x97 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ca_get_slot_caps: --dst_put_ci SUCCESS ! ca_get_slot_caps: Slot cap = [1] === 10 64 0 0 2 3 0 1 24 1 151 dst_ca_ioctl: --CA_GET_CAP Success ! dst_ca_ioctl: Getting Slot info put_checksum: Computing string checksum. put_checksum: - string length : 0x07 put_checksum: - checksum : 0xfb dst_put_ci: Put Command dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 00 05 00 00 00 00 00 fb ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 2 dst(0) read_dst: reply is 0x0 0x5 0x0 0x14 0x88 0x51 0x0 0xe 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff ca_get_slot_info: --dst_put_ci SUCCESS ! ca_get_slot_info: Slot info = [20] === 0 5 0 20 136 81 0 14 dst_ca_ioctl: --CA_GET_SLOT_INFO Success ! dst_ca_ioctl: Sending message ca_send_message: ca_send_message: Command=[0x9f8020] ca_send_message: Getting Cam Application information put_checksum: Computing string checksum. put_checksum: - string length : 0x07 put_checksum: - checksum : 0xb7 dst_put_ci: Put Command dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 07 40 01 00 01 00 00 b7 ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 1 dst(0) read_dst: reply is 0xd 0x40 0x0 0x0 0x1 0x6 0x0 0x0 0x3 0x1 0x0 0x41 0x0 0x67 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Re: [linux-dvb] TDA10046H very slow to tune
Am Dienstag, den 15.08.2006, 21:11 +0200 schrieb Hartmut Hackmann: Hi, Barry Barry Scott wrote: I'm noticing that the KWORLD DVB-T 220 with the TDA10046H tuner is very slow to tune 2 to 5 seconds. Cards like the AverMedia 771 tune in less then a second. Is this a problem with the driver or the chip? Barry This is not normal, do you use a recent version of driver and firmware? The tuning takes about 0.5 seconds. With good signals, the TDA10046 locks within a second. You need to add the time for the DVB application to fill its buffers and to find an I-frame. This is longer but the same for all cards. But: the first lock in a session (open dvb device) always takes longer becase the chips need to recover from sleep mode, check and download the firmware and determine some parameters. This is partly intention, partly chip behaviour. If the lock always takes longer, this might be due to poor signal quality. Updating the firmware might help. There also is one special issue with the TDA8275a silicon tuner: Due to its pinciple, it is sensitive to strong transmitters on another channel. Classic tuner cans handle this better. Hi, at least I can confirm what Hartmut just outlined even on a tda8275a. You should be able to see it on xawtv4 that it not caused by tuning delay, but by buffering, for the price to have some artifacts in the very beginning. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] BBC HD TS file
Nico, if you upload a sample to incoming I'll give it a look I've uploaded a sample to ftp.mplayerhq.hu/MPlayer/incoming/soyebhdsample.ts . The sample is about 70MB. I'm sorry for the large file size, but the files are enormous even for a few seconds of recording. If I play the sample with simply mplayer filename then it plays one channel, but if I try mplayer -nosound filename then I get another channel and the repeating error: [h264 @ 0x87c3808]MBAFF + spatial direct mode is not implemented There is one possibility, I had to change channels in VLC whilst recording to get the correct channel recorded (VLC always chooses the wrong channel to start with), so could it be a bit of recording from the first channel then the second channel? But if that's the case then why does the first channel only appear when I'm using -nosound? Did you have a chance to take a look at this? Regards, Soyeb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
