Ubuntu destroyed my Network Card - RTL8111

[ttguy]

As mentioned above I had this issue. And so I attempted to fix it following the suggestions from sandrogalli.

I thought I should update this thread about my experience.

I made the changes while running the 2.6.31-22-generic Ubuntu 9.10 - the Karmic Koala. I was on this version - because I restored this version from an image after my network died on my Lucid install. The restore did not fix networking - see my previous post - and so I tried following sadrogallis instructions under Karmic.

11/6/2010
Get info about the installed network card

 lspci | grep Ethernet 
 
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

get info about what driver is loaded - I have 8169 drivers for a 8168B card like sandrogalli.

Which he thinks is the problem and fixes as described below.

But others just fix it by unplugging the pc for 3 mins

 lsmod | grep r816* 
r8169                  32160  0  
mii                     5212  1 r8169

download the 8168 linux drivers and untar and install them

tar -xvf r8168-8.018.00.tar.bz2 
 
 sudo ./autorun.sh 
 
$ sudo rmmod r8169 
$ sudo modprobe r8168 
$ sudo /etc/init.d/networking restart

At this point my networking is still down. So I UNPLUG the PC for one hour (posts say 3mins in enough)
This is supposed to make the Network card forget everything and have to reload the drivers.
When I restart I have networking back but lsmod | grep r816* still reports r8169

I then restore a disk image to give 2.6.32-22-generic Ubuntu 10.04 LTS - the Lucid Lynx
When this boots up after the restore networking is working.
$ lsmod | grep r816* reports the same ie I still 8169 drivers for a 8168B card - but it is working

r8169                  33980  0  
mii                     4381  1 r8169

12/6/2010 The 2.6.32-22-generic Ubuntu 10.04 LTS - the Lucid Lynx is still working - net work fine.
13/6/2010 - install a bunch of updates
kernal is still 2.6.32-22-generic
networking still working after these

So I don't really know what actually fixed it. I don't seem to have changed my drivers. It may have just been having the modem off for long enough.