We are using Xubuntu Feisty and testing Hardy with a Kontron COMexpress CPU module with the RealTek 8111/8168 PCI-E adapter and had similar issues to other bugs reported here.
The manufacturer's r8168 driver (now at 8.005.00 as of 2008-01-29) for the 8111/8168 family(PCI id 10EC:8168) is generally much more robust than the r8169 driver in the kernel. With the mfg's r8168 (8168, that is, not 8169), I don't need to periodically restart the network any more, and it also fixed a major issue for us - the network adapter only worked if the adapter was physically connected at startup, the network would come up but not quite work right if connected after startup.
I don't know the process for this, but based on our experience, we would recommend that the mfg's 8168 driver be incorporated into the kernel, and the [10EC:8168] pci id to be unassociated with the r8169 driver.
Some more feedback on this -
We are using Xubuntu Feisty and testing Hardy with a Kontron COMexpress CPU module with the RealTek 8111/8168 PCI-E adapter and had similar issues to other bugs reported here.
The manufacturer's r8168 driver (now at 8.005.00 as of 2008-01-29) for the 8111/8168 family(PCI id 10EC:8168) is generally much more robust than the r8169 driver in the kernel. With the mfg's r8168 (8168, that is, not 8169), I don't need to periodically restart the network any more, and it also fixed a major issue for us - the network adapter only worked if the adapter was physically connected at startup, the network would come up but not quite work right if connected after startup.
I don't know the process for this, but based on our experience, we would recommend that the mfg's 8168 driver be incorporated into the kernel, and the [10EC:8168] pci id to be unassociated with the r8169 driver.
For those needing a workaround, the mfg's site is: www.realtek. com.tw/ downloads/ downloadsView. aspx?Langid= 1&PNid= 13&PFid= 5&Level= 5&Conn= 4&DownTypeID= 3&GetDown= false
http://