Comment 21 for bug 181081

Revision history for this message
Shane Guillory (shane-rppl) wrote : Re: r8169 module for PCI ID 1043:11f5 doesn't work well with hardy heron kernel 2.6.24

Regarding the inability to reproduce the problem, the problems that we have observed are squirrelly and vary from unit to unit. The only thing that we can consistently reproduce with our Kontron COMExpress-CD boards is that the network does not work with r8169 driver if the cable is not connected at boot time (even if the driver is re-loaded once the network is connected).

RealTek's r8168 driver works gloriously every time; it seems that it does a better job of initializing the device and clearing pathological states that stochastically come up in the boards that we are using.

Given that RealTek has found it necessary to release a separate driver for the r8168 (which they are keeping up to date and releasing under GPL), and multiple users are reporting that it fixes issues for them on their specific hardware compared to the r8169, is there a compelling reason NOT to use this driver in the kernel for R8168/8111 devices instead of the r8169?