[Kernel-packages] [Bug 1132156] Re: Realktek r8169 driver unrelaible with r8101/02

2014-02-04 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

Re: [Kernel-packages] [Bug 1132156] Re: Realktek r8169 driver unrelaible with r8101/02

2013-12-06 Thread Chris B
Unfortunately I will not have access to the machine in question until the end of this month. I suggest the bug be closed for now to conserve everybody's time. When I re-test, I will open it again if necessary. Chris On 6 December 2013 01:46, Christopher M. Penalver

[Kernel-packages] [Bug 1132156] Re: Realktek r8169 driver unrelaible with r8101/02

2013-12-05 Thread Christopher M. Penalver
Chris B, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com

[Kernel-packages] [Bug 1132156] Re: Realktek r8169 driver unrelaible with r8101/02

2013-11-05 Thread Ivan Frederiks
I found solution for this issue, at least for my case: one has to set correct MAC-address before bringing up the interface. On my board RTL8102E works without EEPROM, so MAC value is unpredictable. In many cases this random value has multicast bit set to 1. This fact breaks driver and (or) TCP

[Kernel-packages] [Bug 1132156] Re: Realktek r8169 driver unrelaible with r8101/02

2013-09-08 Thread Panagiotis Papadakos
The r8169 is unreliable also in my system. I am using latest saucy distribution with 3.11.0-5 kernel. The link is unstable, most of the times does not connect and also sometimes leads to hard lockups. This is on a RTL8101E/RTL8102E. ** Changed in: linux (Ubuntu) Status: Expired = New