Re: Re: High level CI support in MythTV

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have applied Henriks patch to both dvb and myth on a 2.6.15 kernel. I have a Twinhan DVB-T card.

Sometimes the machine becomes unresponsive. I can't ssh into it, but I can ping it. Since my TV is on repair, I don't have a local screen attached, so I have to do a hard reset. This is what I find in /var/log/messages after reboot (i am not even watching or recording anything):

Mar 18 17:34:35 buddha kernel:  CA_INFO = [ 0x0500]
Mar 18 17:34:35 buddha kernel: ca_send_message: -->CA_INFO_ENQUIRY Success !
Mar 18 17:34:35 buddha kernel: dst_ca_ioctl:  Getting message
Mar 18 17:34:35 buddha kernel: ca_get_message:  Message = [9f 80 31]
Mar 18 17:34:35 buddha kernel: ca_get_message:  Command=[0x9f8031]
Mar 18 17:34:35 buddha kernel: dst_ca_ioctl:  -->CA_GET_MSG Success !
Mar 18 17:39:53 buddha kernel: dst_ca_open:  Device opened [e4420a18]
Mar 18 17:39:53 buddha kernel: dst_ca_ioctl:  Getting Slot capabilities
Mar 18 17:39:53 buddha kernel: put_checksum:  Computing string checksum.
Mar 18 17:39:53 buddha kernel: put_checksum:   -> string length : 0x07
Mar 18 17:39:53 buddha kernel: put_checksum:   -> checksum      : 0xb5
Mar 18 17:39:53 buddha kernel: dst_put_ci:  Put Command
Mar 18 17:39:54 buddha kernel: dst_ci_command:  Write not successful, trying to recover
Mar 18 17:39:54 buddha kernel: ca_get_slot_caps:  -->dst_put_ci SUCCESS !
Mar 18 17:39:54 buddha kernel: ca_get_slot_caps:  Slot cap = [0]
Mar 18 17:39:54 buddha kernel: ===================================
Mar 18 17:39:54 buddha kernel:  70 2 0 0 6 2 0 0 215 248 4 0 234 1 18 192 0 0 0 0 236 254 232 228 192 117 224 248
235 103 56 192 46 0 0 0 159 0 18 192 160 0 255 223 20 59 23 192 0 0 0 0 84 255 232 228 198 132 22 192 0 160 177 23
3 70 2 0 0 0 4 0
Mar 18 17:39:54 buddha kernel: dst_ca_ioctl:  -->CA_GET_CAP Success !
Mar 18 17:39:54 buddha kernel: dst_ca_ioctl:  Sending message
Mar 18 17:39:54 buddha kernel: ca_send_message:
Mar 18 17:39:54 buddha kernel: ca_send_message:  Command=[0x9f8030]
Mar 18 17:39:54 buddha kernel:
Mar 18 17:39:54 buddha kernel: ca_send_message:  Getting Cam CA information
Mar 18 17:39:54 buddha kernel: put_checksum:  Computing string checksum.
Mar 18 17:39:54 buddha kernel: put_checksum:   -> string length : 0x07
Mar 18 17:39:54 buddha kernel: put_checksum:   -> checksum      : 0xb7
Mar 18 17:39:54 buddha kernel: dst_put_ci:  Put Command


After that the log is empty.
This is the only occurence of "dst_ci_command:  Write not successful, trying to recover"
in the log.

Any ideas? How do I enable more verbose logging?

/Hans
_______________________________________________

linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux