Some experiments for what it's worth:<br><br>- changing order of cards to that DVB-S and DVB-T for live are both on HVR4000: same backend crash on DVB-T -> DVB-S zap<br>- TT-3200 drivers loaded but no adapter added into myth so myth doesn't see TT-3200: same backend crash on DVB-T -> DVB-S zap<br>
- TT-3200 drivers not loaded so no adapter exists at all for TT-3200: same backend crash on DVB-T -> DVB-S zap<br><br>So this isn't an issue of a mix of different card types. Tuning away from DVB-T on HVR4000 to DVB-S on any card kills my backend.<br>
<br>I have tried three different HVR4000 firmware revisions : all the same.<br><br>Next to try is moving to myth 0.23.1 ... I built it last night but ran out of time to test it: it will be a few days before I get back to that.<br>
<br><div class="gmail_quote">On Thu, Aug 26, 2010 at 3:08 PM, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk">mikep@randomtraveller.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Liam Friel wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
... Or I could just temporarily nuke that card out of myth ... which would<br>
presumably do more or less the same thing ...<br>
<br>
</blockquote></div>
Er, nope. The drivers get loaded at boot time. Taking it out of myth would be too late - depending on exactly when and how the potential corruption occurs.<div><div></div><div class="h5"><br>
<br>
-- <br>
<br>
Mike Perkins<br>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">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>