[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#611954: Same problem on a VIA E-900 board



I am having the same problem with a VIA E-900 motherboard and this device:

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
        Subsystem: Elitegroup Computer Systems Device 811e
        Flags: bus master, fast devsel, latency 0, IRQ 68
        I/O ports at c800 [size=256]
        Memory at fbffb000 (64-bit, prefetchable) [size=4K]
        Memory at fbffc000 (64-bit, prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number
        Kernel driver in use: r8169

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610302 suggests to try a newer kernel version. This helps a bit, in the sense that initramfs will load firmware patch, but the problem remains.

To illustrate, kernel 2.6.32-5 when running "ifup eth0" after boot:

r8169 0000:05:00.0: firmware: requesting rtl_nic/rtl8168e-1.fw
r8169 0000:05:00.0: eth0: link down
r8169 0000:05:00.0: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
r8169 0000:05:00.0: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

In this case kernel is trying to load rtl8168e-1.fw and succeeding. I assume it didn't succeed with regards to the initramfs and that's why it's loading it later when "ifup" was run.

Kernel 3.2.0-0.bpo.2:

r8169 0000:05:00.0: eth0: link down
r8169 0000:05:00.0: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
r8169 0000:05:00.0: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

In this case firmware patch rtl8168e-1.fw was successfully loaded during boot, however networking still didn't come up.

Also see: http://serverfault.com/questions/384165/after-installing-debian-stable-no-ipv4-but-ipv6-is-up/384221



Reply to: