Re: Mantis – anyone?
Hi Manu, Just to give you some feedback on the first issue as well: Am 06.12.2009 13:52, schrieb Matthias Wächter: > • Can’t lock to 19.2/11303h (looks like something new, related to the > change of the transponder’s feed, but other cards – e.g. TBS 6920 and > Tevii 470 – do sync without a problem). Looks like a frontend issue to > me (STB0899/STB6100), as mantis and budget-ci cards are affected in the > same way. This correlates with perfect and quick lock of 19.2/11362h > which is about the same frequency and has the same DVB parameters > (22000/hC23M5O35S1). One guy on vdrportal.de tried his card under Windows, and he can there lock to that transponder. He tells that locking took quite some time, though, and it appears that transponder shows unexpected low signal strength, but I would take that with a grain of salt as it might be different frontend handling and value scaling. – Matthias -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Mantis – anyone?
Manu, Am 06.12.2009 13:52, schrieb Matthias Wächter: > • Sometimes very slow lock at transponder change, slow enough to trace > it in femon. femon first shows high BER rates and the picture is blocky, > reducing within 3 or 4 Seconds to BER=0 and perfect picture. I should be > able to repeat that and give you some logs if you need it. > > • Sometimes lock to a transponder only in certain order of previous > transponder. Hard to formalize, though. Verbose module output shows 1 to > 2 unsuccessful locking attempts per second by the driver. > • Currently no lock on 19.2/12693h either, but this may be a signal > quality issue on my side. After playing some more, I think those are all related: Lock to a transponder takes from <1 second to minutes, and sometimes I was not patient enough to wait for the lock to finally happen. The no-lock on 19.2°/11303h does not seem to be related to that. – Matthias -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Mantis – anyone?
Manu, Thanks for taking care. > Please try http://jusst.de/hg/v4l-dvb > and report the issues It looks as if dependencies and frontends are not in line. • dependencies for my card’s relevant frontends STB0899, STB6100, and LNBP21 are missing from Kconfig, • dependency for CU1216 is in, but frontend driver source missing. It’s neither in my kernel 2.6.32 sources nor in linuxtv’s v4l-dvb. So, mantis_core is automatically selected and compiled, hopper too, but not mantis. Worked around it by adding/replacing the dependencies (in fact, removing the dependency for CU1216 should have enabled build of mantis). Remaining issues for me: • Can’t lock to 19.2/11303h (looks like something new, related to the change of the transponder’s feed, but other cards – e.g. TBS 6920 and Tevii 470 – do sync without a problem). Looks like a frontend issue to me (STB0899/STB6100), as mantis and budget-ci cards are affected in the same way. This correlates with perfect and quick lock of 19.2/11362h which is about the same frequency and has the same DVB parameters (22000/hC23M5O35S1). • Sometimes very slow lock at transponder change, slow enough to trace it in femon. femon first shows high BER rates and the picture is blocky, reducing within 3 or 4 Seconds to BER=0 and perfect picture. I should be able to repeat that and give you some logs if you need it. • Sometimes lock to a transponder only in certain order of previous transponder. Hard to formalize, though. Verbose module output shows 1 to 2 unsuccessful locking attempts per second by the driver. • Still no 0x-0x SNR and STR range. • Currently no lock on 19.2/12693h either, but this may be a signal quality issue on my side. • Have not yet tried it with two mantis cards in a system, but there was a problem at least with ci handling in such a setup using s2-liplianin for a friend of mine. Will test that next week. • Have not tried IR (I use a radio RCU with lirc). – Matthias -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Mantis – anyone?
2009/11/26 Matthias Wächter : > I am now playing around with the available code for quite some time now > with mixed success, but no solution comes near the term “stable”. > > • kernel: nothing in there. Well, reasonable. > • v4l-dvb: nothing in there. > • s2-liplianin: mantis available, but obviously not under > development/bugfixing. IR seems to work, CI handling looks quite broken, > hangups/lockups are the rule, additional problems with more than one of > these cards in the system. > • mantis-v4l: does not compile out of the box for recent kernels. When > hand-knitting the files into a kernel source directory (2.6.31), works > quite unstable, module reloading frequently segfaults. IR does not work > (at least for VDR), CI handling looks better than s2-liplianin. > > Conclusion: Stability is way below a level for reasonable usage while > bug fixing. > > [1] gives an overview of the current state of (non-)development. Does > this still apply? > > My questions are: > > • Is there someone feeling responsible for that baby? > • What is the main part of the mantis stuff not working – mantis itself, > the frontend, or adaptions from multiproto to s2api? > • What can someone owning some of these cards (one Terratec, two > Technisat) do to help the (former) authors to continue their work? > • Is there some documentation available which would enable ‘the > community’ to work on that further? Please try http://jusst.de/hg/v4l-dvb and report the issues Regards, Manu -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Mantis – anyone?
I am now playing around with the available code for quite some time now with mixed success, but no solution comes near the term “stable”. • kernel: nothing in there. Well, reasonable. • v4l-dvb: nothing in there. • s2-liplianin: mantis available, but obviously not under development/bugfixing. IR seems to work, CI handling looks quite broken, hangups/lockups are the rule, additional problems with more than one of these cards in the system. • mantis-v4l: does not compile out of the box for recent kernels. When hand-knitting the files into a kernel source directory (2.6.31), works quite unstable, module reloading frequently segfaults. IR does not work (at least for VDR), CI handling looks better than s2-liplianin. Conclusion: Stability is way below a level for reasonable usage while bug fixing. [1] gives an overview of the current state of (non-)development. Does this still apply? My questions are: • Is there someone feeling responsible for that baby? • What is the main part of the mantis stuff not working – mantis itself, the frontend, or adaptions from multiproto to s2api? • What can someone owning some of these cards (one Terratec, two Technisat) do to help the (former) authors to continue their work? • Is there some documentation available which would enable ‘the community’ to work on that further? Cheers, – Matthias 1: http://linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_%28VP-1041%29#Drivers -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
