mt2060 I2C read failed<br>mt2060 I2C write failed<br><br>Is a known issue with the Nova-T 500, there is ongoing work on the issue and there has been a few patches the last weeks.<br>Bad reception and EIT scanning can provoke the problem, but with the latest firmware the problem seems to occur only with bad reception.
<br>Hopefully the latest patches will have this solved once and for all, people are still testing this.<br><br>IIRC only the write fail is fatal, though someone on this list had a retry patch for this.<br><br>One workaround is to have a script that monitors and restarts the backend when this happens, might have to do more, my memory is bad.
<br><br>Look at the wiki and the linux-dvb mailinglist for more info.<br><br><br>/Henrik<br><br><div class="gmail_quote">On Jan 21, 2008 10:56 PM, M1ANH <<a href="mailto:m1anh@hotmail.com">m1anh@hotmail.com</a>> wrote:
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>RE: First tuner stops working, in Mythweb "0B" is displayed in the file size
<br>and no screen shot is avaliable.<br>In the console (dmesg) I get a mix of:<br><br>mt2060 I2C read failed<br>mt2060 I2C write failed<br><div class="Ih2E3d"><br><br>Oliver Maunder-3 wrote:<br>><br>><br>> but it looks like it could be related to EIT scanning.
<br></div><div class="Ih2E3d">> In the console I get lots of entries like:<br>><br>> [735440.608000] mt2060 I2C read failed<br>><br></div><div class="Ih2E3d">> I was going to try disabling EIT and setting up XMLTV instead, but I think
<br>> I'll wait until Radio Times sort out their listings!<br>><br><br></div>After reading this I changed my setting in the Mythbackend - Sources to "No<br>Grabber"<br>It has now been running for a week with no missed recording.
<br>So I changed it back to the EIT Data source, waited an hour, and "mt2060 I2C<br>read failed" was reported in the console.<br>Currently I am manually updating the guide by turning on and off the EIT<br>data in the sources to work around the problem.
<br>There must be a bug here some where? I was going to have a channel tidy up,<br>It could be trying to tune in to a channel that has no or invalid data.<br>Possibly an encrypted channel. I no very little about how this works, but
<br>you are on to something here. Thanks for the post.<br><font color="#888888">--<br>View this message in context: <a href="http://www.nabble.com/1st-tuner-on-Nova-t-500-can%27t-tune-tp14515576s15552p14989799.html" target="_blank">
http://www.nabble.com/1st-tuner-on-Nova-t-500-can%27t-tune-tp14515576s15552p14989799.html</a><br>Sent from the mythtv-users mailing list archive at <a href="http://Nabble.com" target="_blank">Nabble.com</a>.<br></font><div>
<div></div><div class="Wj3C7c"><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></div></div></blockquote></div><br>