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.
Ok - It all started when I first installed RedHat 7.1 - I expected everything to load correctly and it almost did except for my LinkSys LNE100TX card (it's labeled as a Lite-On and it has a PNIC chip on the actual PCI card).
When I first booted into RedHat (dualbooting with Windows 2000), when it was trying to initialize eth0, it failed or delayed, but failed after couple minutes of making my network card click.
After that for a couple of months, I did not use RedHat much cause I was disappointed in not being able to explore RedHat without an internet connection as a source of knowledge.
Now, I am determined to get my network card up and running. So, in hopes that RedHat would've added better drivers or fixed whatever problem this might be in RedHat 7.2, i upgraded to 7.2.
When I first booted, all I saw was all [OK] (Greens) even the eth0 after two clicking sounds from my network card! I was hoping that I was able to set the network information in netconfig correctly and I tried mutliple times to connect or ping a web site without much luck.
I went to the linksys site and they had this thing about compiling the kernal or module - but since im a newbie, its way over my head and it didn't seem to work when I first attempted to fix this problem with RedHat 7.1.
Ifconfig allows you to configure your network interfaces, and, when used with no options, shows you statistics for those interfaces. If you just type "ifconfig" at a command prompt it should give you information about the loopback device (lo) and any other active network interfaces, such as eth0, eth1, etc. If typing ifconfig alone only returns info regarding lo, try "ifconfig -a". The "-a" option forces ifconfig to report information about all interfaces, active or not.
If you are assigned a static IP by your campus, you don't want/need to use DHCP. You just need to enter the IP,subnet, gateway, DNS, etc. info they give you in the appropriate places in the net config utility.
Your card uses, as far as I know, the "tulip" driver, which is natively supported in the kernels that ship with Redhat 7.x. You should be able to choose it from the list of available modules in Redhat's network configuration utility. If the module will not load, or the card fails to come up at boot, try some of these generic, manual troubleshooting tips (which apply to static addressing only):
1. Check the screen output at bootup. If the NIC is being properly initialized, you should see a line that says: "Bringing up eth0- O.K." If you see "failed" or "delaying" instead, you've got problems (see #3).
2. Assuming the NIC comes up, you can do the configuration with the graphical configuration tools linuxconf or netconf. Click on Basic host information->Adaptor 1. From there, select eth0 as the device, choose the correct module for your NIC from the drop-down list of kernel modules,and enable the device. Then either choose DHCP (if you're using it), or enter your IP information manually. After that, fill in your DNS and gateway/routing info under the appropriate sections. The previous might not apply for you, since Redhat stopped using Linuxconf/Netconf somewhere in their 7.x releases
3. If you get a failure on bootup, you may have a resource conflict with another device. Try turning off Plug-N-Play support in your BIOS, it can cause conflicts with some cards.
4. Log in as root, go to the command line or terminal window, and type "cat /proc/pci" or "lspci" and verify that your NIC is being recognized. Type "cat /proc/interrupts" and make sure your NIC's IRQ isn't conflicting with another device. Type "cat /proc/ioports" and check the address ranges for conflicts. If you have resource conflicts, you can try rearranging the slot order of your PCI cards.
5. You can also verify the IRQ/address info by typing "ifconfig". There should be stats for the loopback device (lo) and eth0.
6. If the module isn't loading, try to load it manually by typing "insmod <your module's name>" or "modprobe <your module's name>". After that, type "lsmod" to list all loaded modules; the module should show up there.
7. You can then manually configure the NIC by typing "ifconfig eth0 xxx.xxx.xxx.xxx up", where xxx.xxx.xxx.xxx is your IP address.
I'm posting this message using Mozilla from RedHat 7.2!
That's the good news, that I can finally connect to sites without a problem...
another thing thats kinda weird is that when I boot up, eth0 initializes fine, but when i log in and try to connect to a site using mozilla, it won't be able to connect.
I ping google.com and it says that google.com can't be resolved - so i do ifup/ifdown a couple of times. And i also go to the System Settings > Network Configuration and mess around with that some more, and i set it back to what I had before when it was working... and it works again
The output of ifconfig looks good except for the RX/TX errors, but they could be due to flakiness on the campus net or bogus wiring. You might want to check with some of the other people on the system and see if they're getting errors also.
If you can't reach sites with your browser or ping them by URL, but you can ping them by their IP address, you've got DNS issues. The next time sites become unreachable, do these three things:
1. ping the IP of your NIC (22.214.171.124)
2. ping another machine on the campus net (or ping the DNS servers) by IP
3. Ping an outside address by IP (try 126.96.36.199)
If these work, check /etc/resolv.conf and verify that the IPs entered there for your Primary and Secondary DNS servers are correct.
How often do you lose connectivity? Is it possible that there are problems on the DNS servers' end?