[mythtv-users] Nova-T 500 musings...
latepaul at gmail.com
Sun Oct 28 13:59:25 UTC 2007
On 27/10/2007, James Fidell <james at fidell.co.uk> wrote:
> Anyone else have a Nova-T500 tuner and still getting mt2060 I2C write
Yes. I'm running SuSe 10.2 with a 2.6.22 kernel. The write errors cause
mythbackend to lose connection to the tuner, so I have a script that checks
for write errors and restarts the backend. If I'm unlucky it'll happen in
the middle of a recording and so I get a recording in two parts. I can live
I'm running CentOS5 (2.6.18 kernel + RedHat updates) with new v4l-dvb
> drivers taken from linuxtv.org a couple of weeks ago and the latest
> firmware. I still get mt2060 I2C read and write errors. As far as I
> can tell the read errors don't seem that serious, but the write errors
> seem to break tuning somehow so that I end up with a failed recording.
> Thus far I've resolved this by stopping mythbackend and unloading and
> reloading all the dvb modules whenever I've seen a writer error. This
> seems to work ok, but it's a pita.
I never need to reload the drivers, but I do have to restart mythbackend.
Yesterday, more out of irritation than any real understanding of the
> code, I changed the mt2060 driver code that calls write_regs to retry
> if the first attempt fails. Thus far I've had a couple of fails that
> have worked ok on the second attempt and I've had no failed recordings.
That's cool. I might try that myself.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users