Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I just installed Ocelot on my new machine (with an ASUS M5A99X EVO motherboard and on-board gigabit ethernet), and I asked it to download updates while it installed. The install took forever, the longest part being the download of updates, which should have been my first clue. Post install, accessing the internet is sketchy at best, but mostly just broken. The adapter consistently fails to pull down down an ip address or the DNS addresses from my router.

I should also note that I know this isn't a hardware problem, because I can boot into Windows 7 (dual boot), and the ethernet works just fine. Actually, blazing fast might be a better word. But there are many things (primarily software development) that I need to do in Ubuntu instead of Windows.

I feel that it is a driver issue, but I don't even know where to start, since I've always just relied on Ubuntu to install the correct driver automatically for me. Why would the driver be wrong, and what should I do about it?

share|improve this question

2 Answers 2

up vote 3 down vote accepted

I googled the problem as Yongchao describe it and found these instructions. However, the RTL8168B driver from Realtek is only for linux 2.6, and would require a patch for linux 3.0 (which ships with Oneiric).

However, the same search pulled up this bug report, which suggested installing the following "backport" module to update the r8169 driver to work correctly. My steps were as follows:

sudo add-apt-repository ppa:leannogasawara/ppa
sudo apt-get update
sudo apt-get install linux-backports-modules-net-`uname -r`

And then reboot.

Once the machine rebooted, the internet poured in like liquid gold. Thanks to Yongchao Liu for pointing me in the right direction!

share|improve this answer
    
The instructions link is down. Thank you for the link to the bug report! –  tvn Feb 16 '12 at 17:39

if you search the internet a bit, there is a reason why this is failing. If you do lspci in the shell. you might see your network interface card is using 8168B. However, if you lsmod, you can see the system load the r8169 driver which is not the correct one.

Just google how to change the r8169 driver back to r8168 and blacklist the r8169. I have the same issue before. But it can be solved.

share|improve this answer
    
Thanks for the tip! I'll try it out shortly. –  flintinatux Nov 2 '11 at 0:00
1  
Would be great if you are able to describe this process in detail. So the information could be available in one step. :-) –  tvn Feb 16 '12 at 17:36

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.