Comment 53 for bug 141343

No, it is NOT fixed. I have tested with my two motherboards (listed in the
history of this bug) and it is still broken. I am able to DHCP but even
simple pings on my internal network stop working after about 5 tries.
Dean

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
scientus
Sent: Friday, October 31, 2008 10:19 PM
To: <email address hidden>
Subject: [Bug 141343] Re: r8169 driver does not work with Realtek
"PCI-E"8111B integrated network controller

Is this fixed in intrepid x64, i wont upgrade until it is and it was
broken in intrepid x32

ECS NFORCE9M-A

--
r8169 driver does not work with Realtek "PCI-E" 8111B integrated network
controller
https://bugs.launchpad.net/bugs/141343
You received this bug notification because you are a direct subscriber
of the bug.

Status in Ubuntu: Invalid
Status in "linux" source package in Ubuntu: Fix Committed
Status in "linux-source-2.6.22" source package in Ubuntu: Won't Fix
Status in The Hardy Heron: Invalid
Status in linux in Ubuntu Hardy: Fix Released
Status in linux-source-2.6.22 in Ubuntu Hardy: Invalid

Bug description:
Binary package hint: linux-source-2.6.22

Hello!
(I have already submitted information via Kubuntu device database;
Submission Id: 47f10a94b24e91a660a54f0bf6d0ddf2).

I use Kubuntu Gutsy Tribe 5 and made updates recommended by adept notfier.
Current kernel version on my system is
2.6.22-11-generic. I have Athlon x2 4000+ with MSI K9AG Neo2-Digital
motherboard. The motherboard has integrated Gigabit
Realtek 8111B controller; however, my network switch supports only 100Mbps.

When computer boots, module r8169 is loaded, but the adapter is not
functioning (pinging gateway gives "network is unreachable" message). I had
to download and compile r8168-8.003.00.tar.bz2 from realtek.com.tw .
Driver r8168 works for my controller, but I could not get rid of r8169,
which loads after each reboot and gets in the way. When I do manually unload
r8169 and load r8168.ko and restart the network service, then only LAN comes
up.

To summarize the problems:
1) Gutsy Gibbon alpha includes a driver (r8169.ko) which does not actually
support the hardware (RTL8111B) it detects as supportable.
2) Gutsy Gibbon alpha does not include r8168.ko driver which DOES support
that hardware.
3) The two drivers conflict with each other: when r8169 is loaded before
r8168 , the network controller is not operative.

--
Yuri Baranov