Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This 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!


  Search this Thread
Old 01-07-2002, 08:46 PM   #1
LQ Newbie
Registered: Jan 2002
Location: Atlanta, GA
Posts: 4

Rep: Reputation: 0
eth0 connecting when booting - but no connection

Hi guys,

Need some help as a newbie to the world of linux.

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.

I can ping localhost but it won't ping or anything!

This just seems like too much trouble for getting this network card up and running... so I'm running out of hope.

The bad news is that since I'm dual booting and the network card works fine in Windows 2000, I keep having to switch OSs whenever I found new information when I search on and etc.

I hope someone can help me out what the problem is because I have no clue where to even begin.

Thanks for any help!
Old 01-07-2002, 09:13 PM   #2
LQ Newbie
Registered: Jan 2002
Distribution: Redhat 7.2
Posts: 2

Rep: Reputation: 0

I have the same problem with linksys wireless usb adapter...

My bet is you and I (and all the other Linksys users) will have to start learning how to recompile their kernals...

I think Windows 2000 server may be the final solution to get my computer running on the net as a starting server.

Old 01-07-2002, 11:49 PM   #3
Registered: Aug 2001
Location: Salt Lake City, UT
Distribution: REDHAT 7.1
Posts: 32

Rep: Reputation: 15

what does
ifconfig eth0
Are you using DHCP or STATIC from ISP?

More Info Sweetheart!
Old 01-07-2002, 11:54 PM   #4
LQ Newbie
Registered: Jan 2002
Location: Atlanta, GA
Posts: 4

Original Poster
Rep: Reputation: 0
hmm, i never tried ifconfig eth0 - or maybe i did but i don't remember?

hmm, anyways, im in a dorm room and everyone here gets a static IP address.

DHCP is available but someone who helped me install redhat said i shouldn't enable dhcp in redhat for some reason... even if i did enabled dhcp, it didn't do much good...

what does ifconfig eth0 do?

Old 01-08-2002, 01:16 AM   #5
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986

Rep: Reputation: 30

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 up", where is your IP address.

8. Last, type "alias eth0 <your module's name>".

Last edited by DMR; 01-08-2002 at 01:20 AM.
Old 01-08-2002, 03:05 PM   #6
LQ Newbie
Registered: Jan 2002
Location: Atlanta, GA
Posts: 4

Original Poster
Rep: Reputation: 0
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 and it says that 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

anyway, when i do ifconfig, i get:

eth0 Link encap:Ethernet HWaddr 00:A0:CC:30:69:32
inet addr: Bcast: Mask:
RX packets:6452 errors:14 dropped:0 overruns:0 frame:0
TX packets:947 errors:143 dropped:0 overruns:0 carrier:64
collisions:1885 txqueuelen:100
RX bytes:1170978 (1.1 Mb) TX bytes:174595 (170.5 Kb)
Interrupt:11 Base address:0x6000

lo Link encap:Local Loopback
inet addr: Mask:
RX packets:108 errors:0 dropped:0 overruns:0 frame:0
TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7464 (7.2 Kb) TX bytes:7464 (7.2 Kb)

Old 01-08-2002, 08:59 PM   #7
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986

Rep: Reputation: 30
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 (
2. ping another machine on the campus net (or ping the DNS servers) by IP
3. Ping an outside address by IP (try

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?
Old 01-27-2002, 10:01 PM   #8
LQ Newbie
Registered: Jan 2002
Location: Macon, Ga
Distribution: RedHat
Posts: 2

Rep: Reputation: 0
Talking linux gets more and more exciting....

when everything begins to make sense


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
eth0 not connecting graystarr Mandriva 13 07-09-2006 05:59 PM
FC4 Eth0 not connecting dsheller Linux - Networking 3 10-26-2005 02:12 PM
Setting eth0 to load or not when booting javb Ubuntu 1 04-05-2005 12:56 PM
Booting Error (eth0 won't load) julienroger Linux - Newbie 4 08-15-2004 01:00 AM
booting eth0 with DHCP ridertech Linux - Networking 5 02-19-2004 06:25 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 09:55 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration