<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just wanted to follow up on this thread. After a fresh installation<br>
of Fedora 16 with MythTV-0.25, the problem persisted. I put in an old<br>
100Mbps PCI ethernet card and put the HDHomerun onto its own dedicated<br>
network using dhcpd. The problems have completely vanished. Although<br>
I don't see any signs of failure on the motherboard's on-board Gigabit<br>
ethernet adapter, clearly, the problem was a network-related issue.<br></blockquote></div><br>I have been running my HDHR on it's own dedicated adapter for a couple of years... rock solid.<br><br>One thing to note, there is no reason to run dhcpd. Simply assign the adapter an address in the 169.254.x.x range... the HDHR will randomly pick an address in that range if it fails to get one from DHCP (see <a href="http://en.wikipedia.org/wiki/Zero_configuration_networking">http://en.wikipedia.org/wiki/Zero_configuration_networking</a>). In fact, with some distros, zeroconf is enabled so if you set the network adapter to DHCP, it will also assign one in that range; saving you from doing any configuration at all.<br>
<br>Of course, this means that you will need to address the HDHR by device ID rather than IP in mythtv setup... but if memory serves, that is the preferred method anyway.<br><br><br>