You state that ifconfig does not show any information on eth0 when you run
just "ifconfig".  However if you run "ifconfig eth0" then you get some
information.  I submit to you that this is the normal operation of ifconfig
provided that your system is not initializing/starting your network card on
boot.  If the eth0 interface has not been started or has failed in it's
attempt to start, then ifconfig will not report it.  Try running "/sbin/ifup
eth0".  What do you get?  If this fails or gives you a message about
delaying initialization, run "/sbin/lsmod".  Do you see a reference to the
tulip module?  If not, run "/sbin/modprobe tulip".  Did this succeed, check
with "/sbin/lsmod".  If so, run "/sbin/ifup eth0".  Now, did this succeed?
If so, you will most likely want to add the following line to your
"/etc/conf.modules" or "/etc/modules.conf"

alias eth0 tulip

Jamin W. Collins

-----Original Message-----
From: ShaneMRyan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 15, 2000 12:49 PM
To: [EMAIL PROTECTED]
Subject: Installing an ethernet card.


I installed a Kingston ethernet card into my linux box.  Kudzu found it, and
it uses the tulip driver.  However, an ifconfig doesn't show it.  If I run,
"ifconfig eth0", it will show some info about it.  I am dual booting WinME.
This box is connected via a cross over cable to a W2K box.  When windows ME
is started, I can ping my W2K server.  However, when I assign a static ip on
the same class c subnet to the linux box I can't ping the W2K box through
the crossover cable.  Any hints with using linux and ethernet nic cards?



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to