On 29.02.2012 12:29, Johannes Truschnigg wrote:
Hi list,

my CAM drops out every once in a while, too. It's rather annoying, but I don't
know how to fix the problem, so I decided to work around it. Whenever my CAM
fails, the kernel/DVB driver seems to notice, and the debug ringbuffer
contents reflect this. An error message like

"dvb_ca adapter 0: DVB CAM link initialisation failed :("

also makes its way into syslog that way (because rsyslog retrieves messages
from /dev/kmsg).

I wrote a simple Python program that monitors a given logfile for the
appearance of this message, and then tries to trigger the appropriate SVDRP
HITK sequence via a plain and simple socket connection. So far, it works quite
well (no manual CAM resets had to be performed by my parents for the last four
weeks this way). If anyone happens to know a more reliable way to externally
trigger a CAM reset via VDR/SVDRP, please let me know - right now, everything
depends on the unchanged ordering of main menu entries, which is kind of

I also see this message in my log file from time to time.
So this means that the driver apparently recognizes a CAM
failure. Now the question is: why doesn't the driver report
this fact to the application (VDR)? If VDR would receive
this information, it could automatically do a reset.


vdr mailing list

Reply via email to