<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 1 March 2016 at 07:07, Will Dormann <span dir="ltr"><<a href="mailto:wdormann@gmail.com" target="_blank">wdormann@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 2/28/16 9:37 AM, Mike Perkins wrote:<br>
> The point is not that firewire works for him, but that if there is a<br>
> reasonable alternative he can remove the FW card from his box and<br>
> substitute an Ethernet card instead, thus resolving his networking problem.<br>
<br>
<br>
</span>Right. Depending on the amount of time/effort I would consider spending<br>
on getting reliable gigabit, I could possibly:<br>
<br>
1) Get the IR blaster capability of my HD-PVR working:<br>
<a href="https://www.mythtv.org/wiki/Hauppauge_HD-PVR#Steps_to_Enable_IR_Transmitter" rel="noreferrer" target="_blank">https://www.mythtv.org/wiki/Hauppauge_HD-PVR#Steps_to_Enable_IR_Transmitter</a><br>
<br>
2) Build one of Gary's cables:<br>
<a href="https://github.com/garybuhrmaster/misc/tree/master/IR_Blaster_to_Comcast_DTA_direct_connect_cable" rel="noreferrer" target="_blank">https://github.com/garybuhrmaster/misc/tree/master/IR_Blaster_to_Comcast_DTA_direct_connect_cable</a><br>
<br>
3) Connect my cable box to the HD-PVR using said cable.<br>
<br>
4) Purchase a known-reliable PCIe NIC.<br>
<br>
<br>
Guaranteed costs:<br>
- Time / troubleshooting<br>
- Equipment<br>
<br>
<br>
Guaranteed functionality loss:<br>
- Inability to power on cable box programmatically. As outlined in<br>
another thread of mine, I've seen my cable box revert to a powered-off<br>
state after Verizon pushes out a software update. Currently I have a<br>
hacky job that periodically checks that the cable box is on, and w/o<br>
firewire, that'll no longer be possible.<br>
<br>
<br>
Expected benefit:<br>
- Gigabit network speed<br>
<br>
<br>
My goal was to know what my options are, but I suspect that in this case<br>
I'll likely just put up with 100Mbit.<br>
<span class=""><font color="#888888"><br>
<br>
<br>
-WD<br>
</font></span><div class=""><div class="h5"><br></div></div></blockquote><div><br></div><div>Interestingly I'm seeing dropped RX packets on my ION.....</div><div><br></div><div>eth0 Link encap:Ethernet HWaddr 00:01:2e:2d:7b:7f</div><div> inet addr:172.16.107.35 Bcast:172.16.107.255 Mask:255.255.255.0</div><div> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1</div><div> RX packets:31218566 errors:0 dropped:21133 overruns:0 frame:0</div><div> TX packets:7515035 errors:0 dropped:0 overruns:0 carrier:0</div><div> collisions:0 txqueuelen:1000</div><div> RX bytes:41674891228 (41.6 GB) TX bytes:633613359 (633.6 MB)</div><div> </div><div><div>$ sudo ethtool -S eth0</div><div>NIC statistics:</div><div> tx_packets: 147713737</div><div> rx_packets: 618834072</div><div> tx_errors: 0</div><div> rx_errors: 146</div><div> rx_missed: 41954</div><div> align_errors: 9634</div><div> tx_single_collisions: 0</div><div> tx_multi_collisions: 0</div><div> unicast: 605320215</div><div> broadcast: 5342240</div><div> multicast: 9274562</div><div> tx_aborted: 0</div><div> tx_underrun: 0</div></div><div><br></div><div><br></div><div><br></div><div>From</div><div>$ lspci -v<br></div><div>04:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)<br></div><div><br></div><div>seems to be a rather common error, some people have suggested in my case to upgrade the realtek driver </div></div></div></div>