On 13/08/12 19:50, James B. Byrne wrote:
>
> On Mon, August 13, 2012 10:37, Ned Slider wrote:
>
>> Faulty hardware maybe? Try a reboot and see if it reappears. If it's
>> located on a card try reseating the card (although I suspect this is
>> an integrated NIC on the motherboard?).
>>
>> The chipset is not necessarily the same in the second example
>> (different revision); RTL8111/8168B is not RTL8168d/8111d. They
>> probably do use the same driver but I'd need to see the
>> Vendor:Device ID pairing to know for sure.
>
>
> Eth1 is an xpci card sold by StarTech. A system with an identical
> card reports this:
>
OK, I'd definitely try reseating the card and if you still get no joy
I'd swap it out for a replacement.
> for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1
> }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done
>
<snip>
>
> 01:00.0 "Ethernet controller" "Realtek Semiconductor Co., Ltd."
> "RTL8111/8168B PCI Express Gigabit Ethernet controller" -r03 "Realtek
> Semiconductor Co., Ltd." "TEG-ECTX Gigabit PCI-E Adapter [Trendnet]"
> 01:00.0 0200: 10ec:8168 (rev 03)
>
kmod-r8168 is the correct driver for this device. If you'd like to try
the updated driver from elrepo, just install kmod-r8168 and reboot.
lsmod should then show r8168 in use and not the native kernel driver
r8169. Many have found this driver to be more reliable than the native
kernel driver, assuming the hardware isn't defective.
Hope that helps.