Continuity counter errors since switch to Fedora17
Added by Markus Bonet over 12 years ago
Hi,
I am running a Tevii S480 for roughly a year now.
Since I upgraded from Fedora 16 to 17 I encounter problems with HD channels.
Every now and then (from a few seconds to some minutes) tvheadend reports "Continuity counter errors" on the H264 stream (sometimes on Teletext or AC3 as well) which leads to some visible corruptions in the video.
I tested these different kernels, all running on Fedora 17:
kernel-3.2.9-2.fc16.x86_64 <- works perfectly
kernel-3.3.7-1.fc16.x86_64 <- works perfectly
kernel-3.3.7-1.fc17.x86_64 <- errors encountered
kernel-3.4.3-1.fc17.x86_64 <- errors encountered
kernel-3.4.4-3.fc16.x86_64 <- errors encountered
kernel-3.4.4-3.fc17.x86_64 <- errors encountered
I can't tell for sure if the amount of errors encountered is equal across all kernels I have tested, but only the first two run ok.
Suprisingly the same kernel (once compiled for F16 and once for F17) shows different behaviour.
Here is the output when the card gets initialized:
[ 2.838458] usb 3-1: Product: DVBS2BOX
[ 3.057042] usb 4-1: Product: DVBS2BOX
[ 12.782488] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 12.782728] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 12.933676] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 12.933718] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.934136] DVB: registering new adapter (TeVii S660 USB)
[ 13.188395] dvb-usb: MAC address: 00:18:bd:5b:54:c4
[ 13.349895] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
[ 13.350667] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 13.350685] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 13.350951] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 13.501942] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 13.501994] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 13.502370] DVB: registering new adapter (TeVii S660 USB)
[ 13.759354] dvb-usb: MAC address: 00:18:bd:5b:54:c5
[ 13.763834] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
[ 13.764584] dvb-usb: TeVii S660 USB successfully initialized and connected.
lsmod:
lsmod|grep -i dvb
dvb_usb_dw2102 53865 42
dvb_usb 23802 1 dvb_usb_dw2102
dvb_core 107356 1 dvb_usb
rc_core 26635 8 ir_nec_decoder,ir_rc5_decoder,ir_rc6_decoder,ir_jvc_decoder,dvb_usb,ir_sony_decoder,ir_mce_kbd_decoder,ir_lirc_codec
i2c_core 37955 8 drm,drm_kms_helper,i2c_algo_bit,i915,i2c_i801,dvb_usb,dvb_usb_dw2102,ds3000
This is the firmware I took from Tevii's homepage:
md5sum /usr/lib/firmware/dvb-usb-s660.fw
2946e99fe3a4973ba905fcf59111cf40 /usr/lib/firmware/dvb-usb-s660.fw
Any clue what might be wrong here?
Does anyone else use this card?
Thanks
Markus
PS: Since when is sorting not ok in the forums anymore?
Replies (3)
RE: Continuity counter errors since switch to Fedora17 - Added by Alex . over 12 years ago
Hi,
I think the continuity errors have to do with dropped frames/packages.
So , in fact usually it is a bandwidth problem ( you can check this by viewing both from the same device tvheadend runs on, and via the network.).
That is what I understand, so, strange error that you get: It should not change with the linux version, unless somehow there is suddenly less bandwidth available....
RE: Continuity counter errors since switch to Fedora17 - Added by wet willy over 12 years ago
I'm also experiencing Continuity counter errors, using Terratec Cinergy C PCI HD.
Is the error created between tuner and provider or between tvheadend server and client?
Could it be the tuner that is bad? I've tried different cables that work when used with a Dreambox.
RE: Continuity counter errors since switch to Fedora17 - Added by Markus Bonet over 12 years ago
Any comment from anyone who knows how this situation is identified and handled in the code?
In the meantime I had my S480 exchanged and added another Mystique twin tuner. I cannot identify any scheme whether it's kernel, driver or whatever related.