help with eth0

help with eth0

Post by Syso » Sun, 06 Nov 1994 10:53:00



  I need some assistance with a small problem getting Linux to talk to
my ethernet card.

  I'm using an SMC 1600C set at 280, IRQ 10 and D000.  I've tried other
addresses too.  When I boot I see the card being recognized by probe and
it reports back all the correct stats but then I try to use the port..
nothing.  If I run ifconfig I see something that doesn't look right.  On
the first line it appears something like this:

eth0 encap UNSPEC  hwaddr 00-00-00-00-00-00-00-00-00

  Down below that it says mtu 1500, up, running, metic 1 etc.

  It seems to me that somehow ifconfig can't see the address of my
ethernet.  I have this problem no matter which ethernet card I put in
the machine.  When I run netstat -ain I can see that packets have been
sent (after trying to ping another host on the network but the ping
always fails with 100% loss).

  I'm running on a 486-66 with an everex VGA color card, 16 megs of
memory and kernel version 1.0.9 (Slackware).


advance if this is in a faq somewhere, but I've been unable to find a
written solution

 
 
 

help with eth0

Post by Gary Paul Gortmak » Tue, 08 Nov 1994 15:38:07


[...]

Quote:>nothing.  If I run ifconfig I see something that doesn't look right.  On
>the first line it appears something like this:
>eth0 encap UNSPEC  hwaddr 00-00-00-00-00-00-00-00-00

--------------------------------------------------------
Link UNSPEC and HW-addr of 00-00-00-00-00-00

        When I run ifconfig with no arguments, it reports that
        LINK is UNSPEC (instead of 10Mbs Ethernet) and it
        also says that my hardware address is all zeros.

        This is because people are running a newer version of
        the `ifconfig' program than their kernel version. This
        new version of ifconfig is not able to report these properties
        when used in conjunction with an older kernel. You can either
        upgrade your kernel, `downgrade' ifconfig, or simply ignore
        it. The kernel knows your hardware address, so it really
        doesn't matter if ifconfig can't read it.
--------------------------------------------------------

Try http://sunsite.unc.edu/mdw/HOWTO/Ethernet-HOWTO
for more info.

Paul.