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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have no idea why it was named eth1 on my old computer since it only had a wired connection. But when I put that old hdd in my new machine (which also only has one wired network card (nothing wireless), internet did work, so I renamed the network from eth0 to eth1 on the new disc, wrongly thinking that would solve the connection problem... Hope you understand what I'm trying to say, my brain is slowly melting here...
And I think you should read through it just in case they have done something you haven't. I think the most relevant section is at the bottom, it suggests:
sudo service network-manager stop
sudo dhclient3 eth0 (eth1 for you)
Remember your internet interface is eth1 not eth0. If that works for you, read on the bottom of the link posted above it describes how to get your network manager working again. Otherwise I will keep searching, but most results are what you have already tried. Switching from 89 to 88 module.
I went back and caught my brainskip and apologize again.
I am fresh out of ideas. I've not encountered a Linux distro that did not sense a wired ethernet connection, given that the ethernet card was working, and you indicated that yours worked under Windows. Then, again, I don't think I've had a box with a Realtek chipset.
All I'm left with is to suggest booting some Live CDs and see whether you can get a connection with one of them. I think I'd start with Knoppix or Porteus.
You might also run the lspci and ifconfig commands under them to verify that there's no inconsistency.
I have to go away for a couple of days, but when I'm back I'm going to carefully try all your suggestions again.
flyinggeorge: I tried dhclient3, but command was not found.. maybe I should just by a new nic? I don't really like the idea because I don't have much money and stubborn me is thinking that this card SHOULD work!! Peace and see you later!
frankbell: I tried soooo many different distros allready with the same resault (no wired connection). But I kind of liked the Porteus one you suggested, call me oldschool but I like the simple interface of xfce and lxde, used to run xubuntu and was very pleased with that! Thanx for trying to help, see ya!
my thoughts - have you tried this with a live distro rather than installing it? I am just wondering whether there was a problem a the install stage (don't ask me what) and this is never going to work. A fresh install perhaps?
I have Win7/Linux Mint 15 installed.
And I've tried many distros in Live-mode.
Internet is not working in live mode, during linux install or after full install.
Just now I tried an old Xubuntu (12.04), which, i guess, is only 32bit, but it instantly connected to the Internet without any modification to drivers or anything!?!?
Can you use
lspci -vv | grep Realtek
To find out what driver you are using? I don't know if it's possible to use a 32-bit driver or module on a 64-bit system. I think you would probably get an error about the wrong symbols. A quick google on the subject does not look promising.
I'm starting to think maybe this option can be configured in the kernel. Based on this thread:
I don't have much time right now to look up a solution though. I'll see if I can find an option for Realtek NICs with menuconfig later. Don't be afraid of recompiling the kernel.
*Edit: for some reason it seems like the 2.6 kernel handles this card much better. Can you use an older 64-bit distrobution? Maybe you can find a live CD/DVD. I know Slackware 13.37 ships with 2.6X kernel, but is not a live distro. Of course using the 2.6 kernel would not be preferred, but maybe it could help us find out if it "just works."
*Edit #2: Could you try a modern 32-bit live distrobution? i.e. one with 3.X kernel? Try 'uname -r' to find out which version of the kernel you have.
Last edited by flyinggeorge; 07-28-2013 at 03:01 PM.