Hello all,
I tried to upgrade kernel to 2.6.20 just to notice that one multiplex on
our local "Welho" cable (138 Mhz, QAM128, 6.9msym/s). With 2.6.18.1 it
works just fine:
mythtv:/home/mythtv# czap -a 1 -c ~mythtv/.czap/channels.conf "Discovery"
using '/dev/dvb/adapter1/frontend0' and '/dev/d
Hello
Setup: 2 x Technotrend DVB-C 1500, one has CI module connected
Tuning to all channels work fine in 2.6.18.1. I have tried 2.6.20 and
2.6.20.4, czap is not getting lock with channels on 138 Mhz. Other
(higher) frequencies work fine. Anyone have idea what has changed to
cause this behav
>I have had similar experience like You with the same card (TT DVB
C1500)
>regarding QAM64. I discovered that there had been a successful fix for
>this done for QAM128 by changing the sweeprate, see
>http://www.linuxtv.org/pipermail/linux-dvb/2006-February/008439.html
>So I made some test to fin
Hello
Hardware: Technotrend DVB-C 1500, CI, Conax CAM, Asus P5B
Am I the only one left alone without working system with current
development v4l tree? Somewhere between 2.6.18.1 and 2.6.20 (and current
mercurial, also) something changed, and tuning to Discovery channel no
longer works at le
