Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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.
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.
Last edited by flyinggeorge; 07-24-2013 at 01:37 PM.
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.
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:
I tried to load the new driver as mentioned. Did it even twice, once the mint distro and then on ubuntu as seen below:
Code:
danne@ubuntu:~/Dokument$ cd r8168-8.036.00
danne@ubuntu:~/Dokument/r8168-8.036.00$ ls
autorun.sh Makefile README src
danne@ubuntu:~/Dokument/r8168-8.036.00$ sudo ./autorun.sh
sudo] password for danne:
Check old driver and unload it.
rmmod r8169
Build the module and install
Can't read private key
Backup r8169.ko
rename r8169.ko to r8169.bak
DEPMOD 3.8.0-19-generic
load module r8168
Updating initramfs. Please wait.
update-initramfs: Generating /boot/initrd.img-3.8.0-19-generic
Warning: No support for locale: sv_SE.utf8
Completed.
danne@ubuntu:~/Dokument/r8168-8.036.00$ echo "blacklist r8169" >> /etc/modprobe.d/blacklist.conf
bash: /etc/modprobe.d/blacklist.conf: Permission denied
danne@ubuntu:~/Dokument/r8168-8.036.00$ sudo cp src/r8168.ko /lib/modules/3.8.0-19-generic/kernel/drivers/net/
danne@ubuntu:~/Dokument/r8168-8.036.00$ sudo depmod
danne@ubuntu:~/Dokument/r8168-8.036.00$ sudo modprobe r8168
danne@ubuntu:~/Dokument/r8168-8.036.00$
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?
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.
Last edited by flyinggeorge; 07-24-2013 at 06:12 PM.
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:
Code:
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Flags: bus master, fast devsel, latency 0, IRQ 74
I/O ports at d000 [size=256]
Memory at d0004000 (64-bit, prefetchable) [size=4K]
Memory at d0000000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-68-4c-e0-00
Kernel driver in use: r8168
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)
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.
Last edited by flyinggeorge; 07-24-2013 at 08:06 PM.
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..
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:
Quote:
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.
I doubt this is helping the situation; instead, I suspect it's muddying the water.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
No wired internet during linux install
