On Wednesday 31 Aug 2005 14:16, Jesper S?rensen wrote: > Johannes Stezenbach skrev: > >On Mon, Aug 29, 2005 at 01:00:41AM +0200, Johannes Stezenbach wrote: > >>On Wed, Aug 24, 2005 Marian Durkovic wrote: > >>> I found a big thread on linux-dvb list couple of months old, about > >>> problems with retuning after lost lock. > >>> > >>> I was experiencing the same situation - but only with dvb-kernel > >>> drivers. My old boxes with 2.4.20 kernel and DVB branch never had this > >>> problem. The new box was never able to retune even after signal > >>> degradation by heavy rain or after cable disconnecting/reconnecting. > >>> > >>> My oscilloscope was showing the 22 kHz signal even after lost lock, > >>> but the card was not able to retune. Restarting the application always > >>> solved the problem. > >>> > >>> Finally I found the reason - it's the following code in > >>> dvb_frontend.c: > >>> > >>> /* if we're tuned, then we have determined the > >>> correct i nversion */ > >>> if ((!(fe->info->caps & FE_CAN_INVERSION_AUTO)) > >>> && (fe->parameters.inversion == INVERSION_AUTO)) { > >>> fe->parameters.inversion = fe->inversion; } > >>> > >>> If this is commented out, the frontend is able to retune. > >> > >>Has anyone had time to look into this? Anyone else seeing the > >>problem, and if yes does that change fix it? > > > >No more people with SAT-equipment willing to test and/or comment > >on this? > > I have a Nova-S-CI too (budget-ci & stv0299) and I've seen some weird > problems with lock loss on a specific transponder (Thor 1.0?W, 11 229 > MHz, H polarity) but I'm not sure if it is related to this issue. Maybe > it has something to do with the polarity since most of the other > transponders (which work fine) use V polarity...? > > Symptoms are: good lock at first but then the lock is lost after a > couple of seconds up to a few minutes and it doesn't retune > automatically. When this happens it is very reproducable but when I try > again a few hours later everything can be perfectly fine so I don't know > what could be causing it? I have this problem as well at one site only. No idea why it happens, but you're not alone.