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 have a dual-boot laptop (asus k53sv) ubuntu 12.04.2 LTS and windows 8. My wired internet connection on windows 8 works fine but on ubuntu I cannot connect to the internet. In order to connect to the internet, I must restart the modem (yes I can access the setup page of the modem) but when I re-plug the cable or restart ubuntu, I cannot access the internet anymore.

sudo lshw -C network: http://paste.ubuntu.com/5603124/

ifconfig -a: http://paste.ubuntu.com/5603126/

My wired network adapter is "RTL8111/8168B PCI Express Gigabit Ethernet controller". I have changed the driver r8169 to r8168 but it doesn't help.

P/S: (1) When I cannot connect to the internet, I can access the modem's setup page. (2) But when I have the internet connection (after restarting the modem), I cannot access the setup page (I was prompted for the password but it doesn't accept my password). And when I re-plug the cable or the reboot ubuntu, I'm back to (1).

Could someone help me to ge rid of this annoying problem? Many thanks :-).

share|improve this question
    
Please check the PCI ID of the adapter by lspci -nn, it's something like 10ec:???? –  grimpitch Apr 26 '13 at 3:26
    
@grimpitch: It shows [10ec:8168] on the network adapter. –  Bao Bui Apr 26 '13 at 3:48
    
I have an adapter of the same type in my laptop, and it works perfectly on 12.10 and 13.04 with the r8169 driver. I have never used 12.04 on this hardware, but I will try with a live CD. This adapter also needs a firmware to be installed, so make sure that the linux-firmware package is installed. Another thing I have noticed, is the virtual bridge interface virbr0. Are you using any other virtualization system besides VMware? –  grimpitch Apr 26 '13 at 4:45
    
@grimpitch: the linux-firmware package is already installed on my laptop. Yes, I'm using kvm virtualization besides VMware. Are there any problems with that? –  Bao Bui Apr 26 '13 at 4:52
    
Not really, I'm just guessing, it might be something messing up the default route or is a name server access problem. Compare the output of the route -n command in the two situations, when you can access the internet, and when you cannot. Also, do the same with ping 8.8.8.8. –  grimpitch Apr 26 '13 at 5:23
show 1 more comment

Your Answer

 
discard

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

Browse other questions tagged or ask your own question.