[vdr] Timeouts and lost locks

Jan Ekholm jan.ekholm at smultron.net
Fri May 22 09:07:01 CEST 2009


Good morning,

I see logging like this all the time in my syslog file:

May 22 06:36:45 hex vdr: [31292] frontend 0 timed out while tuning to channel 
31, tp 298
May 22 06:37:06 hex vdr: [31292] frontend 0 timed out while tuning to channel 
33, tp 322

And:

May 22 09:59:58 hex vdr: [31292] frontend 0 lost lock on channel 41, tp 338
May 22 09:59:59 hex vdr: [31292] frontend 0 regained lock on channel 41, tp 
338
May 22 10:00:01 hex vdr: [31292] frontend 0 lost lock on channel 41, tp 338
May 22 10:00:01 hex vdr: [31292] frontend 0 regained lock on channel 41, tp 
338

What does this mean? The channels referred to (31, 33 and 41) are channels 
that we never, ever watch as they are encrypted. Normally these three or 
neighbor channels are referred to in the error logging. We almost never use 
channels above 20. So, why does VDR try to tune into them and why would it 
fail? We have two FF cards but we still would like them both to do something 
that benefits us, not go randomly tune into uninteresting channels. :)

Best regards,
    Jan Ekholm

-- 
               "Stercus, stercus, stercus, moriturus sum."
                                       -- Terry Pratchett, Interesting Times




More information about the vdr mailing list