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've searched this forum and the internet (via Google) for a how to or a document that simply shows how a Linux user (Slackware user) would go about troubleshooting the internet connection on a his/her machine, but found nothing complete or adequate.
In windows, if you wanted to troubleshoot the connection, you would start by checking the drivers for the network card, whether they are installed or not, if the network is enabled or disabled, what ip address the nic is getting, renew/release the ip etc...Is there anything similar to that in linux Slackware? Can someone just outline the steps that a novice would have to take to troubleshoot the internet connection on a machine that has Slackware 12.0, which is connected to a link sys router, and it gets its ip address dynamically?
The first thing I'd do is to run "ifconfig -a" to see if 1. your NIC is there and 2. it actually has an IP address. If you have N network cards in your machine, you should see devices for each of those, listed as ethx (where x = 0, 1, ..., N - 1). Do you know what kind of network card it is? If not, post the output of lspci here. Also run lsmod and post the output (that will list the kernel modules loaded, so we can see if the appropriate one for your card is loaded).
- information about what has happened since you booted; should list your ethernet card stuff too, check out the name/model at least to make sure the system acknowledges the card is in
- check if the module for your card is loaded; internet helps deducing what module it should be - if the module is not shown here, it could still be compiled into the kernel. If you find the correct module but it's not used, there's something wrong between the module ("driver") and your card.
- see if there are settings for the (first) ethernet device, and if they're correct. If you get nothing, the card and it's driver aren't co-operating. If you do get something, make sure the information is valid, and try to 'ifconfig eth0 up' to start the device.
- check to see if the connection works, but you just couldn't get DNS names resolved.
- depending on your configuration, either one of these should work and try to fetch information via DHCP to determine your ip address and the rest needed stuff. No output means it works, but if you do get output, it tells you can't get DHCP answers - maybe the error is even more informative
That's the way to go..there are several steps and several ways of checking the things. Basically you want to know:
- does the system know I have an ethernet card?
- has the system got the correct driver (kernel module) for my card?
- has the system loaded the appropriate driver (module)?
- is the device eth0 (or something) present?
- is the device eth0 configured properly?
- can I ping any IP addresses?
- can I get DHCP requests/answers all right, or not?
The tools to determine the answers for the above questions are many; dmesg, system logfiles, lsmod, modprobe, ping, ifconfig, dhclient/dhcpcd, ...
My kernel version is: 188.8.131.52. I have the 3com Etherlink III card. And yes Nylex, that is my entire screen output.
It appears that my system does not know that I have a network card attached.
Bouncer, how do you use dmesg? If I just type it, it vomits 500000 lines of text on the screen. I am a fast reader, but not that fast! Is there a way or an argument to slow the output of the dmesg so I can read it? Is there a boot.ini file somewhere that I can access. Also, how do you use modprobe?
Remember comrades, I am a beginner, a nice way of saying Newbie!
When you provide the commands, please provide the arguments that I would need to use to make the command useful.
its worth mentioning that when I installed my Slackware, I had to use the huge.s kernel instead of the default (hugesmp.s). Because I do not have a Pentium machine.
I noticed the following errors when I load into linux (only using command line):
Failed to create listening socket: address already in use
Could not reliably determine th server's fully qualifiedly domain name using 127.0.0.1 for serverName
Also, after the "Welcome to linux 184.108.40.206" message appears, i get the following error:
fileserver login: STOPPING server from pid file /var/run/mysql/mysql.pid
070724 22:50:47 mysqld ended
Oh, it appears to be an ISA card and hence wouldn't show up when you run lspci. I've also found out that the module needed is 3c509, so try loading that with "modprobe 3c509" (you'll need to be root to run this). After that, check the end of dmesg to see if there's anything important there (and "ifconfig -a", too).
If you want to see the entire dmesg output, pipe the output to less: "dmesg | less" and then you can scroll up and down with the arrow keys.