On Fri, Oct 28, 2011 at 12:21 PM, Jarry <mr.ja...@gmail.com> wrote: > On 28-Oct-11 18:02, Michael Mol wrote: >> On Fri, Oct 28, 2011 at 11:38 AM, Jarry<mr.ja...@gmail.com> wrote: >>> On 28-Oct-11 17:24, Michael Mol wrote: >>>> On Fri, Oct 28, 2011 at 11:06 AM, Jarry<mr.ja...@gmail.com> wrote: >>>>> On 28-Oct-11 16:52, Michael Mol wrote: >>>>>> On Fri, Oct 28, 2011 at 10:46 AM, Jarry<mr.ja...@gmail.com> >>>>>> wrote: >>>>> # uname -r >>>>> 3.0.6-gentoo >>>>> # lsmod | grep r8169 >>>>> r8169 33932 0 >>>>> firmware_class 5085 9 r8169,tg3,aic94xx,... >>>> lsmod -k >>>> >>>> Find the line for the Realtek device >>>> >>>> lsmod -vn > > # lspci -k > <snip> > 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B > PCI Express Gigabit Ethernet Controller (rev 02) > Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard > Kernel driver in use: r8169 > Kernel modules: r8169 > > # lspci -vn > <snip> > 03:00.0 0200: 10ec:8168 (rev 02) > Subsystem: 1458:e000 > Flags: bus master, fast devsel, latency 0, IRQ 44 > I/O ports at ee00 [size=256] > Memory at fdcff000 (64-bit, prefetchable) [size=4K] > Memory at fdce0000 (64-bit, prefetchable) [size=64K] > [virtual] Expansion ROM at fdc00000 [disabled] [size=64K] > Capabilities: [40] Power Management version 3 > Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ > Capabilities: [70] Express Endpoint, MSI 01 > Capabilities: [b0] MSI-X: Enable- Count=2 Masked- > Capabilities: [d0] Vital Product Data > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > Capabilities: [160] Device Serial Number 12-34-56-78-12-34-56-78 > Kernel driver in use: r8169 > Kernel modules: r8169 > > Is there anything suspicious?
Not to my eye; the kernel sees the device and associates it appropriately. > BTW, in between I've put one more > drive inside and installed Windows7. Ethernet is automatically > detected, driver installed, and it works. In BIOS I also see > everything as normal, device enabled, cable-connection detected. > So I do not think the eth-chip is damaged... I think the next step is to check udev. Find something like 70-persistant-net.rules under /etc/udev/rules.d. Make a backup of that file, then delete the one in the folder. Reboot, see if that solves the problem. -- :wq
