Eth0 Not Being Recognized

Hello Everyone,

I'm a newbie and have been using Slackware 9.1 (kernel 2.4.26) for
about three weeks now. Everything was going fine until yesterday when
I installed a new memory card. My pc recognized the new memory with
no problem but now I've got a problem with Slack recognizing eth0
which is the interface to my D-link System ethernet card for my cable
modem. My system recognizes the hardware, but the interface itself
isn't be created/loaded. When I run "ifconfig", it shows only the lo
interface. When I run "ifconfig eth0" it displays some information
for eth0, but no IP address (I'm assuming because I couldn't get DHCP
to recognize eth0, since it doesn't really exist). In the KDE Info
Center I see that the system recognizes the ethernet card, but not the
eth0 interface (it shows only the lo interface). So it seems the
hardware is being recognized but not the interface.

I've checked all my cable and card connections but nothing seems to be
loose. Everything else in the system works fine. Any thoughts I what
I should try next? Should I try to reinstall some packages from the
Slack 9.1 cd to see if eth0 can be recognized? I'm just not sure what
to try next.

Thanks in advance,
Lucinda

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.networking Lucinda <(E-Mail Removed)> suggested:
> Hello Everyone,

> I'm a newbie and have been using Slackware 9.1 (kernel 2.4.26) for
> about three weeks now. Everything was going fine until yesterday when
> I installed a new memory card. My pc recognized the new memory with
> no problem but now I've got a problem with Slack recognizing eth0
> which is the interface to my D-link System ethernet card for my cable
[..]

Show us the output of (from some xterm/kvt):

grep eth /etc/modules.conf

/sbin/lspci

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAq+K8AkPEju3Se5QRAm5/AJ9hKR2Edp7XFVdIgQEHjaQAO88NlwCgij4p
I0w343WrD5uKNPGu35nv8M0=
=s4dt
-----END PGP SIGNATURE-----

On Wed, 19 May 2004 22:42:05 +0000, Michael Heiming wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> NotDashEscaped: You need GnuPG to verify this message
>
> In comp.os.linux.networking Lucinda <(E-Mail Removed)> suggested:
>> Hello Everyone,
>
>> I'm a newbie and have been using Slackware 9.1 (kernel 2.4.26) for
>> about three weeks now. Everything was going fine until yesterday when
>> I installed a new memory card. My pc recognized the new memory with
>> no problem but now I've got a problem with Slack recognizing eth0
>> which is the interface to my D-link System ethernet card for my cable
> [..]
>
> Show us the output of (from some xterm/kvt):
>
> grep eth /etc/modules.conf
>
> /sbin/lspci

also the output of lsmod would be usefull, if your not getting dhcp try
forcing an IP addr eg: ifconfig eth0 192.168.0.1 up
assuming 192.168.0 is your network and 192.168.0.1 is not in use by
another host.

--
http://www.lgw.co.nz/

Lucinda <(E-Mail Removed)> wrote:

> Everything was going fine until yesterday when I installed a new
> memory card.

> My system recognizes the hardware, but the interface itself isn't be
> created/loaded.

Hmm, it's possible that there was some static damage which damaged the
NIC (and maybe other components). This is one reason why its nice (for
Fast Ethernet anyway) to have the NIC as an expansion card, and not
on-board.

> When I run "ifconfig eth0" it displays some information for eth0, but
> no IP address (I'm assuming because I couldn't get DHCP to recognize
> eth0, since it doesn't really exist).

This would lend weight to my theory of damaged componentry. I suggest
that you run diagnostics on the ethernet card. If you run lspci you
can tell what the chipset is.

Under Linux, you can test the card using nictools. Under Debian, you can
use the following packages. (Yes, I realise youre using Slackware 9.1)

nictools-nopci - Diagnostic tools for many non-PCI ethernet cards
nictools-pci - Diagnostic tools for many PCI ethernet cards

An easy way to see if the interface is failing is inspecting the
ifconfig error counters.

ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:40:F4:6F:BB:F0
...
RX packets:3667146 errors:0 dropped:0 overruns:0 frame:0
TX packets:6363756 errors:0 dropped:0 overruns:0 carrier:0
...

If the various error counters are increasing as traffic is transmitted
or received, that's a good indication that there is a problem with
either the NIC, cable, or the active network equipment attached to the
NIC. If you use something like ping on one virtual terminal to generate
traffic, you can run this command on another.

watch /sbin/ifconfig eth0

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!