Posts by TheTroll

    Hi,


    yes there is no log in-between.

    I sent you the full log thanks!

    Hi, I still have the same problem with you patch kls  


    Oct 25 13:09:22 nuc vdr: [6267] frontend 0/1 regained lock on channel 4 (CANAL +), tp 212012

    Oct 25 13:09:23 nuc vdr: [6264] frontend 0/0 lost lock on channel 1 (TF1), tp 234


    it's trying to use both frontend at the same time


    Thanks I have 'almost' the same issue as described, when using symlinks.


    Hi,


    I know that there is already a subject opened about a similar issue (link), but this one is actually a bit different.

    This card has 2 signal inputs (one for terrestrial and one for Sat).

    At the end, the TBS driver creates only 1 adapter but with 2 frontends.


    VDR seems to discover them well:

    Code
    1. Oct 9 15:16:18 nuc vdr: [11352] probing /dev/dvb/adapter0/frontend0
    2. Oct 9 15:16:18 nuc vdr: [11352] frontend 0/0 provides DVB-T,DVB-T2,DVB-C,ISDBT,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("TurboSight TBS 5520SE DVB-T/T2/C/C2/ISDB-T")
    3. Oct 9 15:16:18 nuc vdr: [11356] frontend 0/0 tuner thread started (pid=11352, tid=11356, prio=high)
    4. Oct 9 15:16:18 nuc vdr: [11352] probing /dev/dvb/adapter0/frontend1
    5. Oct 9 15:16:18 nuc vdr: [11352] frontend 0/1 provides DVB-S,DVB-S2,DSS with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("TurboSight TBS 5520SE DVB-S/S2/S2X")
    6. Oct 9 15:16:18 nuc vdr: [11359] frontend 0/1 tuner thread started (pid=11352, tid=11359, prio=high)


    The thing is that it does not handle them well.

    When switching from one to the other, it seems to think that there are actually 2 demuxes...



    Has anyone experienced this ?


    Thanks!

    The crash can be fixed like this:


    Hi,


    this is where it crashes:


    Hi,


    thanks for the patch!
    Here is another one that finally let me use the hdsm kernel module on my 2.6.36.2 kernel with PAE and 4GB of ram...