Comment 3 for bug 141343

And this is the output of dmesg when only r8169 driver is loaded.

I have also made some observations on "LINK/ACT" led of my ethernet switch and drivers functionality. To put it concisely:
1) In some cases LINK/ACT comes on just after my computer is powered, in other cases LINK/ACT turns on only after r8168 driver is loaded manually.
2) When LINK/ACT is on initially, any of the two drivers is working ok with the controller.
3) When LINK/ACT is off, only *manual* loading of r8168 can enable the network controller.
4) Manual loading of r8169 does not change the on/off status of the link.
5) (This is probably my lack of competence, but I have not succeeded yet in enabling the controller when r8168 driver is loaded automatically during the boot - only manual loading with modprobe/insmod does the trick)

So I may correct my initial statement: r8169 driver of Gutsy Gibbon alpha distribution does provide some support of my hardware; only this support is
less complete than that of r8168 driver.

I also saw some interesting effects while making attempts to suppress the loading of r8169 driver, but those are probably not directly related to the bug in question.