No wired internet during linux install
 

Hi everyone!

I just recently bought all the parts for a computer and my brother helped me to put it together. Then we tried to install Ubuntu, but it could not connect to the Internet so he installed windows 7 for me to search the net for a solution. I have since tried many distros, but none can connect during install or after, through the wired (onboard wired realtek pcie gbe family controller).

I then put in the hdd from my (very) old computer that has xubuntu 32bit installed and it instantly connected to the net!
The only difference I could find was that on this disc, the network was called eth1, but when I try to install Linux on the new computer (with all the new hardware and 64bit, it is being called eth0. I found out how to rename eth0 to eth1, but it makes no difference.

This is so strange, everything else is working perfect. From what I read, many people have problems with wireless connection and other hardware issues, but not with a simple nic.

I am not an advanced Linux user, I normaly just install it and everything is working. But just ask me if you need any more info about my system and so on.

Really hope anyone can help me with this so I can get Bill G out of my life again and feel free :)

Peace to ya'll!

I'm not really sure on this one, try to give a specific version of your ethernet card with something like:

Also what does the shell say when you try to use dhcpcd on eth0? eg '# dhcpcd eth0'

Hi flyinggeorge, thanx for your reply,

I logged into the linux mint which I have installed along with win7 and tried to run your comands, but the first one gave no answer whatsoever and the second said it could'nt find eth0.

I then run ifconfig:



ifconfig eth1
eth1 Link encap:Ethernet HWaddr 94:de:80:0f:b5:b1
inet6 addr: fe80::96de:80ff:fe0f:b5b1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:724 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:141 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:92811 (92.8 KB) TX bytes:0 (0.0 B)


ifconfig -a
eth1 Link encap:Ethernet HWaddr 94:de:80:0f:b5:b1
inet6 addr: fe80::96de:80ff:fe0f:b5b1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:873 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:188 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:108699 (108.6 KB) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Hope this helps you in any way!

Okay, in the first example it's probably the | grep bit that's screwing you up. It's looking for a case sensitive "realtek" try to post the complete output of "lspci -v" As for the second try dhcpcd on eth1 I didn't realize you had changed it from the typical eth0. Sorry about that.

Just to make your posts more readible, try to utilize the {code} blocks {/code} replace { with [ the code blocks are useful when you have to post output from the shell, makes it easier to tell who is saying what.

Ok, I hope I get this right, sorry for newbe-mistakes!

I haven't looked through all of your lspci yet, but not having dhcpcd seems odd to me. I have always in the past used dhcpcd to connect an interface to the internet. My first thought is to see if you can find a *.deb for dhcpcd. Hopefully someone else will come along and correct me if I am wrong, but I'm pretty sure the network manager uses dhcpcd to connect to the internet also. I'm going to read around a bit hopefully I can help you.

Edit: According to some reading, you might have dhclient instead of dhcpcd. Try 'dhclient eth1'

Edit #2: I should have researched this a little more before posting my initial post. According to your lspci, you have a Realtek RTL8111/8168B which apparently does not work out of the box due to modprobe loading the wrong driver. See the link below for more information.

http://forums.linuxmint.com/viewtopic.php?f=49&t=80757

Yeah, I think you may be right there, the network manager is trying to connect for a while, then it sais disconnected and it starts all over again. But why is dhcpcd not being installed?

Thanx for trying to help, i really want to get Linux working so I can start enjoying my new machine!!

I edited my post above it seems the modprobe is loading a faulty module for your internet card out of the box. The fix seems to be downloading the correct driver from realtek and installing it. You should end up with a *.ko file which you can then load with modprobe. This should fix your issue. If not feel free to report back with any problems. That link again:

http://forums.linuxmint.com/viewtopic.php?f=49&t=80757

As for dhcpcd not being installed, check if you have dhclient.

Allright, will check this out and report back!

I tried to load the new driver as mentioned. Did it even twice, once the mint distro and then on ubuntu as seen below:

Still don't get no connection, but i found a new entry in BIOS: BIOS Features > Network Device BBs Priorities > Boot Option #1 = Realtek PXE B03 D00
So something must have happened!?

I also tried dhclient and I was told I had no permission for that??

Giving up is not an option since I really don't want to use Windows, but maybe there are other Linux distros that would work better for me, do you know any?

dhclient has to be run as root. Try sudo dhclient eth1. Second, it looks like you haven't blacklisted the old module.

The above command needs to be run as root. Try adding sudo to it. Another option is using 'sudo su' to gain access to a root shell when you will be doing lots of work that you need to be root for. This way you don't have to sudo yourself to death. I think sudo -l or -i does something similar. I would bet that r8169 is still loading over the new r8168 module. Once you blacklist the module, just for fun, use rmmod or modprobe -r r8169. Finally, run 'dhclient eth1' all of this needs to be done as root or with 'sudo' in front of it. I don't think it is Ubuntu/Mint's fault. But personally, I have fallen in love with Slackware. Although Slackware is more for users that really want to learn more about the way Linux works. But before you go and re-install or anything, try the above. I bet we can work this out for you.

Also, don't forget to load the new module after blacklisting/rmmoding the old one.

still not working, but maybe because I did not load the new module as you said, how do I do that?

the lspci -command now returns more info and it says that I'm now using the right driver:

I do want to learn more about Linux, until now I have just used it as any OS for getting online and doing everyday stuff. I just recently picked up three books from the library to learn more, but there is nothing on the problem we are trying to solve here. But maybe one day I join you using Slackware :)

You did load the correct module, that's what modprobe r8168 did for you. dhclient should return a lot more information. Just to verify, post the output of ifconfig eth1 on here for us. Chances are you won't find the solution to this issue in a book. This is driver specific problem. I used to have a laptop with a Broadcom 4312 wireless chip and I spent a very long time configuring it. But you are using the correct module now. So please boot back up to your linux and make sure you are using the correct module ('modprobe r8168') then run 'ifconfig eth1' to make sure that the interface is up.

For example, if I run 'ifconfig eth0 down' (I'm using wlan0 but I still have the wired interface eth0) I get: (when running 'ifconfig eth0' eth1 for you)
Then if I turn the interface back on with 'ifconfig eth0 up' I get:

Notice that under flags, there is "UP"

If your device is up, there should be no problem using dhclient. And if you are using the same connection from Windows to access the internet we can safely rule out that it is faulty.

Edit: I hope one day you do join me using Slackware. I haven't used another distro in two years. Couldn't be happier.

The 'dhclient eth1' takes some time, then I am being returned to the promt without getting any info.
The same goes for 'ifconfig eth0 up', it gives me nothing.
Yes, I'm using windows on the same machine to connect to the Internet. So I have to boot between the two, thats one of the reasons why I'm taking so long between posts..

well here is what I get from 'ifconfig':

Maybe I'm missing something, but eth0 commonly refers to a wired connection and eth1 (sometimes wlan0) commonly refers to a wireless connection. I saw this in your first post:

I doubt this is helping the situation; instead, I suspect it's muddying the water.

Have you tested with a wired connection?

Edit: I see you have. pardon my brainskip.