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.
Sorry I didnt read through the thread you linked but have you got the module you need for your card loaded?
Intel Corporation 82557/8/9
lsmod will show you whether it is loaded or not. If it is not then you will have to compile it into your kernel or as a module.
If it does show up as loaded then run through netconfig again. Or maybe just ifconfig eth0 up.
Ok so whats you setup like any routers, you do want a dynamic ip right? I am sorry that I wont be able to stay and help you more. But I can offer you this http://slackbook.org/html/book.html
Look at the part about static and dhcp learn to do it from the command line and it will pay off. It is a simple matter of making sure that module is the correct one for your card, making sure its loaded. Then setting up your ip and then your done. Good luck, but I have to go to sleep now.
PS: Dont fret Im sure someone lese will come alon really soon to fill the rest in.
And Im truly sorry if anything I posted was wrong.
Make sure you've got the correct and most updated driver for your card, and compile it locally on the system. That's how I've always gotten network cards to work with linux. I have very bad luck with pre-built anything. For example, here's my makefile for my rtl8139 card (driver can by found somewhere at scyld.com)
If you can type 'gcc' or 'make' then you can do this. Setting up a network card is always the first thing I do on a new machine (which are usually 5 year old boxes someone gave to me). Rarely do the default modules do the trick for me (I don't use the user-friendly distros). I configure things like this:
1) use lspci(8) to find exactly what my card is and which bus its on.
2) find the linux driver, and compile using something like that makefile I posted
3) install the driver in /lib/modules/`uname -r`/net (or wherever your kernel modules go)
4) become root
5) run 'depmod -a'
6) run 'modprobe <modulename>' where <modulename> is the same as the *.o file you compiled minus the '.o', (for rtl8139.o, the module name is rtl8139).
7) look at the tail of dmesg to find out if the module installed correctly
7.a) if it didn't, then either your card is fried or the module is wrong or your system is cursed.
8) find whatever it is on your system which creates /etc/modules.conf. on Debian, is update-modules(8).
9) add an alias for eth0 (this might not be needed). Here's what it is on my system ->
$ cat /etc/modutils/net
alias eth0 rtl8139
options rtl8139 debug=6 full_duplex=1,0,1
btw, I'm pretty sure 'eth0' is just a string. You could name your network interface 'alfonz0' if you wanted. But I've never tried that.
If eepro100 loads into the kernel, then the driver believes there is hardware there to talk to. Forgive me for asking a potentially insulting question, but there is no onboard LAN (ie, another ethernet controller)? For if the driver loads, yet you do not even get a link light when plugging a live cable into your card, the card is likely broken.