I followed your method and still getting no connection for the internal network.

I have noticed when I rmmod r8169, the file still exists within the lib/modules/2.6.27-17-generic/kernel/drivers/net/ file. When I search for it through terminal, then "ls"(list) the net folder.

My 1st attempt at following the Wiki, I downloaded and installed the r8169 file. It was only when I read the Wiki a 2nd time I realized that I had downloaded the wrong file, so then proceeded to download the r8168 from the site you recommended and install. I then tried to delete the r8169 file. After deletion I noticed by using the ls method in terminal that the 2 files are the only 2 highlighted in bright yellow.(whatever that means)

Just wondering if I have maybe corrupted something by my mistake?

Also wondering if there is a brute force way in deleting the r8169 file before I go down the dreaded reformat route...

Just to confirm, it is the r8168 you are downloading from Realtek and trying to use. We are trying to remove and blacklist the r8169, which is known to be problematic for newer motherboards.

Try removing it with "modprobe -r r8169" instead? No idea what the yellow means. You could also try adding "sudo blacklist r8169" to the blacklist file instead of "blacklist r8169", might make a difference. Remember to update list again.

Regarding the reformat; was it working before then? And it randomly stopped? If so, do a...

Listening on LPF/eth0/00:30:bd:6d:61:68Sending on LPF/eth0/00:30:bd:6d:61:68Sending on Socket/fallbackDHCPREQUEST of 192.168.0.4 on eth0 to 255.255.255.255 port 67DHCPACK of 192.168.0.4 from 192.168.0.1bound to 192.168.0.4 -- renewal in 34768 seconds.

Because I was having trouble downloading the driver this morning I have attached the one I built for use with this motherboard. This is the r8168.ko file built from the above mentioned sources on kernel 2.6.27-17-generic (the latest, and current, 0810 kernel).

Copy r8168.ko to /lib/modules/2.6.27-17-generic/kernel/drivers/net/ and replace the existing file of the same name. You may need to blacklist the 8169 driver, to do this add a line 'blacklist r8169' to the file /etc/modprobe.d/blacklist (the r8169.ko file will still exist in the /lib/modules/2.6.27-17-generic/kernel/drivers/net/ directory) and reboot your system.

Try that out.

J

PS, ah, after reading your posts again it seems you're having trouble blacklisting the r8169 driver. I think I actually built a new r8169 driver from the sources at realtek and placed that in my .../drivers/net/ directory. The problem is that the PCI device ID already exists in the old r8169 driver and the kernel picks it before the new r8168 driver. Building a new r8169 driver from the realtek sources should fix this.