<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 24, 2013 at 8:34 AM, Eric Sharkey <span dir="ltr"><<a href="mailto:eric@lisaneric.org" target="_blank">eric@lisaneric.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Sep 24, 2013 at 10:59 AM, Jay Ashworth <<a href="mailto:jra@baylink.com">jra@baylink.com</a>> wrote:<br>
> Any chance, Eric, that you could take a look at that pastebin and see<br>
> if you see anything in the dmesg that looks whacky? Or is that more<br>
> properly a question for the ivtv list people?<br>
<br>
</div>It sounds like an ivtv problem to me. Since the problem is affecting<br>
both cards (right?) it is unlikely to be hardware, but both cards are<br>
using the same driver.<br>
<br>
I'll take a look at your dmesg output if you like, but you haven't<br>
actually posted the url. Your message from yesterday has two links to<br>
the mythfilldatabase output, and none to the dmesg output.<br>
<span class="HOEnZb"><font color="#888888"><br>
Eric</font></span><br></blockquote><div><br></div><div>What about the firmware files? Maybe double-check that they're being loaded correctly (I think dmesg will tell you this), and that the MD5 (or whatever) hash matches a known good version?<br>
<br></div><div>Karl<br></div></div></div></div>