<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">James Fidell</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>><br>Date: Oct 28, 2007 12:44 AM
<br>Subject: [mythtv-users] Nova-T 500 musings...<br>To: Discussion about mythtv <<a href="mailto:email@example.com">firstname.lastname@example.org</a>><br><br></span>Anyone else have a Nova-T500 tuner and still getting mt2060 I2C write
<br>errors?<br><br>I'm running CentOS5 (2.6.18 kernel + RedHat updates) with new v4l-dvb<br>drivers taken from <a href="http://linuxtv.org">linuxtv.org</a> a couple of weeks ago and the latest<br>firmware. I still get mt2060 I2C read and write errors. As far as I
<br>can tell the read errors don't seem that serious, but the write errors<br>seem to break tuning somehow so that I end up with a failed recording.<br>Thus far I've resolved this by stopping mythbackend and unloading and
<br>reloading all the dvb modules whenever I've seen a writer error. This<br>seems to work ok, but it's a pita.<br><br>Yesterday, more out of irritation than any real understanding of the<br>code, I changed the mt2060 driver code that calls write_regs to retry
<br>if the first attempt fails. Thus far I've had a couple of fails that<br>have worked ok on the second attempt and I've had no failed recordings.<br><br>I'll be watching things over the next few days to see what happens.
<br>What I've done is without doubt a hack rather than a genuine fix, but<br>if it mostly resolves the problem for me, I think I can live with that<br>until such time as someone who understands the problem properly can
<br>do the job right.<br><br>James<br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:email@example.com">firstname.lastname@example.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">