Is my newly installed NIC DOA?

I run Fedora 7. My PC is a seven-year-old Dell Dimension 4100.It did not
come with either integrated or standalone NIC. My Internet access is
dial-up only.

In order to have capability for DSL, I purchased an Intel PRO/100 M NIC
from a highly-rated seller on EBay. I've performed two tests to
determine if the NIC is OK. Both tests appear to have failed. But I have
zero experience with networking. So I'd like some guidance on whether
I'm using the correct tests, and whether they indeed have failed.

The first test is taken from the DSL Howto.

It consists of three steps:

1. Attempt to bring up interface: ifconfig eth0 10.0.0.1 up

2. Check response (ping it): ping -c 50 10.0.0.1

3. Use ifconfig to check for errors: ifconfig eth0

The rtt times reported by ping lead me to think that data was
transmitted, but the RX bytes and TX bytes reported by ifconfig are both
zero.



The second test is taken from the Intel PRO/100 M users guide,
describing how to run NIC diagnostics under Linux:

ethtool -t eth0

The output from this test is: FAIL


Following is a screen capture from both tests:

Script started on Mon 09 Jul 2007 01:29:29 PM EDT
]0;root@localhost:~ [?1034h[root@localhost ~]# ping -c 50 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.163 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.112 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.115 ms
64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.119 ms
<snip>

--- 10.0.0.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49001ms
rtt min/avg/max/mdev = 0.109/0.115/0.163/0.015 ms
]0;root@localhost:~ [root@localhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:07:E9:01:B2:09
inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

]0;root@localhost:~ [root@localhost ~]# ethtool -t eth0
The test result is FAIL
The test extra info:
Link test (on/offline) 1
Eeprom test (on/offline) 0
Self test (offline) 0
Mac loopback (offline) 0
Phy loopback (offline) 0

]0;root@localhost:~ [root@localhost ~]#
Script done on Mon 09 Jul 2007 01:31:21 PM EDT

On Mon, 09 Jul 2007 19:39:12 +0000, Allen Weiner wrote:

> I run Fedora 7. My PC is a seven-year-old Dell Dimension 4100.It did not
> come with either integrated or standalone NIC. My Internet access is
> dial-up only.
>
> In order to have capability for DSL, I purchased an Intel PRO/100 M NIC
> from a highly-rated seller on EBay. I've performed two tests to
> determine if the NIC is OK. Both tests appear to have failed. But I have
> zero experience with networking. So I'd like some guidance on whether
> I'm using the correct tests, and whether they indeed have failed.
>
> The first test is taken from the DSL Howto.
>
> It consists of three steps:
>
> 1. Attempt to bring up interface: ifconfig eth0 10.0.0.1 up
>
> 2. Check response (ping it): ping -c 50 10.0.0.1
>
> 3. Use ifconfig to check for errors: ifconfig eth0
>
> The rtt times reported by ping lead me to think that data was
> transmitted, but the RX bytes and TX bytes reported by ifconfig are both
> zero.
>
>
>
> The second test is taken from the Intel PRO/100 M users guide,
> describing how to run NIC diagnostics under Linux:
>
> ethtool -t eth0
>
> The output from this test is: FAIL
>
>
> Following is a screen capture from both tests:
>
> Script started on Mon 09 Jul 2007 01:29:29 PM EDT
> ]0;root@localhost:~ [?1034h[root@localhost ~]# ping -c 50 10.0.0.1
> PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
> 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.163 ms
> 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms
> 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.112 ms
> 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.115 ms
> 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.119 ms
> <snip>
>
> --- 10.0.0.1 ping statistics ---
> 50 packets transmitted, 50 received, 0% packet loss, time 49001ms
> rtt min/avg/max/mdev = 0.109/0.115/0.163/0.015 ms
> ]0;root@localhost:~ [root@localhost ~]# ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:07:E9:01:B2:09
> inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> ]0;root@localhost:~ [root@localhost ~]# ethtool -t eth0
> The test result is FAIL
> The test extra info:
> Link test (on/offline) 1
> Eeprom test (on/offline) 0
> Self test (offline) 0
> Mac loopback (offline) 0
> Phy loopback (offline) 0
>
> ]0;root@localhost:~ [root@localhost ~]#
> Script done on Mon 09 Jul 2007 01:31:21 PM EDT


.... what's the question... are you worried about the 0 counts for TX and
RX? if your pinging your local address, no packets go out on the NIC so
it will stay as 0 counts. I just tested this on one of my boxes.. I
disconnected my lan cable, pinged my IP Address ( NOT the 127.0.0.1
address ) and I got 10 good packets and no increase in RX or TX counts
for eth0.

If you can talk to the card enough to assign an IP Address, you should be
good to go.... I've had plenty of times where the card was not recoginized...
if this happens, you can't even assign an IP Address to it.

jack

--
D.A.M. - Mothers Against Dyslexia

see http://www.jacksnodgrass.com for my contact info.

jack - Grapevine/Richardson

Jack Snodgrass wrote:
> On Mon, 09 Jul 2007 19:39:12 +0000, Allen Weiner wrote:
>
>> I run Fedora 7. My PC is a seven-year-old Dell Dimension 4100.It did not
>> come with either integrated or standalone NIC. My Internet access is
>> dial-up only.
>>
>> In order to have capability for DSL, I purchased an Intel PRO/100 M NIC
>> from a highly-rated seller on EBay. I've performed two tests to
>> determine if the NIC is OK. Both tests appear to have failed. But I have
>> zero experience with networking. So I'd like some guidance on whether
>> I'm using the correct tests, and whether they indeed have failed.
>>
>> The first test is taken from the DSL Howto.
>>
>> It consists of three steps:
>>
>> 1. Attempt to bring up interface: ifconfig eth0 10.0.0.1 up
>>
>> 2. Check response (ping it): ping -c 50 10.0.0.1
>>
>> 3. Use ifconfig to check for errors: ifconfig eth0
>>
>> The rtt times reported by ping lead me to think that data was
>> transmitted, but the RX bytes and TX bytes reported by ifconfig are both
>> zero.
>>
>>
>>
>> The second test is taken from the Intel PRO/100 M users guide,
>> describing how to run NIC diagnostics under Linux:
>>
>> ethtool -t eth0
>>
>> The output from this test is: FAIL
>>
>>
>> Following is a screen capture from both tests:
>>
>> Script started on Mon 09 Jul 2007 01:29:29 PM EDT
>> ]0;root@localhost:~ [?1034h[root@localhost ~]# ping -c 50 10.0.0.1
>> PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
>> 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.163 ms
>> 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms
>> 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.112 ms
>> 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.115 ms
>> 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.119 ms
>> <snip>
>>
>> --- 10.0.0.1 ping statistics ---
>> 50 packets transmitted, 50 received, 0% packet loss, time 49001ms
>> rtt min/avg/max/mdev = 0.109/0.115/0.163/0.015 ms
>> ]0;root@localhost:~ [root@localhost ~]# ifconfig eth0
>> eth0 Link encap:Ethernet HWaddr 00:07:E9:01:B2:09
>> inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>
>> ]0;root@localhost:~ [root@localhost ~]# ethtool -t eth0
>> The test result is FAIL
>> The test extra info:
>> Link test (on/offline) 1
>> Eeprom test (on/offline) 0
>> Self test (offline) 0
>> Mac loopback (offline) 0
>> Phy loopback (offline) 0
>>
>> ]0;root@localhost:~ [root@localhost ~]#
>> Script done on Mon 09 Jul 2007 01:31:21 PM EDT
>
>
> ... what's the question... are you worried about the 0 counts for TX and
> RX? if your pinging your local address, no packets go out on the NIC so
> it will stay as 0 counts. I just tested this on one of my boxes.. I
> disconnected my lan cable, pinged my IP Address ( NOT the 127.0.0.1
> address ) and I got 10 good packets and no increase in RX or TX counts
> for eth0.
>
> If you can talk to the card enough to assign an IP Address, you should be
> good to go.... I've had plenty of times where the card was not recoginized...
> if this happens, you can't even assign an IP Address to it.
>
> jack
>

Thanks for the reply. Yes, I was concerned that the RX and TX counts are
zero. The screenshots in the DSL Howto show nonzero counts for RX and
TX. But your explanation addresses my concern. I guess something else
was going on in the system they were using for the howto. (As I stated
in the original post, I have *zero* experience with networking.)

My other concern is that I would *really* like to run the NIC
diagnostics, which I tried to do via ethtool. I just reran it, and
specified "offline" (which is supposed to be the default). I got a
slightly different result for phy loopback, but everything else was the
same. This looks like something is wrong.

Allen Weiner wrote:
> Jack Snodgrass wrote:
>> On Mon, 09 Jul 2007 19:39:12 +0000, Allen Weiner wrote:
>>
>>> I run Fedora 7. My PC is a seven-year-old Dell Dimension 4100.It did
>>> not come with either integrated or standalone NIC. My Internet access
>>> is dial-up only.
>>>
>>> In order to have capability for DSL, I purchased an Intel PRO/100 M
>>> NIC from a highly-rated seller on EBay. I've performed two tests to
>>> determine if the NIC is OK. Both tests appear to have failed. But I
>>> have zero experience with networking. So I'd like some guidance on
>>> whether I'm using the correct tests, and whether they indeed have
>>> failed.
>>>
>>> The first test is taken from the DSL Howto.
>>>
>>> It consists of three steps:
>>>
>>> 1. Attempt to bring up interface: ifconfig eth0 10.0.0.1 up
>>>
>>> 2. Check response (ping it): ping -c 50 10.0.0.1
>>>
>>> 3. Use ifconfig to check for errors: ifconfig eth0
>>>
>>> The rtt times reported by ping lead me to think that data was
>>> transmitted, but the RX bytes and TX bytes reported by ifconfig are
>>> both zero.
>>>
>>>
>>>
>>> The second test is taken from the Intel PRO/100 M users guide,
>>> describing how to run NIC diagnostics under Linux:
>>>
>>> ethtool -t eth0
>>>
>>> The output from this test is: FAIL
>>>
>>>
>>> Following is a screen capture from both tests:
>>>
>>> Script started on Mon 09 Jul 2007 01:29:29 PM EDT
>>> ]0;root@localhost:~ [?1034h[root@localhost ~]# ping -c 50 10.0.0.1
>>> PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
>>> 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.163 ms
>>> 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.116 ms
>>> 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.112 ms
>>> 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.115 ms
>>> 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.119 ms
>>> <snip>
>>>
>>> --- 10.0.0.1 ping statistics ---
>>> 50 packets transmitted, 50 received, 0% packet loss, time 49001ms
>>> rtt min/avg/max/mdev = 0.109/0.115/0.163/0.015 ms
>>> ]0;root@localhost:~ [root@localhost ~]# ifconfig eth0
>>> eth0 Link encap:Ethernet HWaddr 00:07:E9:01:B2:09
>>> inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
>>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>
>>> ]0;root@localhost:~ [root@localhost ~]# ethtool -t eth0
>>> The test result is FAIL
>>> The test extra info:
>>> Link test (on/offline) 1
>>> Eeprom test (on/offline) 0
>>> Self test (offline) 0
>>> Mac loopback (offline) 0
>>> Phy loopback (offline) 0
>>>
>>> ]0;root@localhost:~ [root@localhost ~]#
>>> Script done on Mon 09 Jul 2007 01:31:21 PM EDT
>>
>>

About the NIC diagnostics, the "link test" is failing because I don't
have anything connected to the NIC! (I don't have anything to connect).
The other tests are not being run at all????

"Allen Weiner" schrieb
> I run Fedora 7. My PC is a seven-year-old Dell Dimension 4100.
> It did not come with either integrated or standalone NIC.
> My Internet access is dial-up only.
>
> In order to have capability for DSL, I purchased an
> Intel PRO/100 M NIC from a highly-rated seller on EBay.
> I've performed two tests to determine if the NIC is OK.
> Both tests appear to have failed.
>
Start up your system administration tool and let it first
try to recognize the hardware and configure it. Dunno how this
is called in Fedora.

HTH
Martin

Allen Weiner <(E-Mail Removed)> wrote:
> Allen Weiner wrote:
>> Jack Snodgrass wrote:
>>> On Mon, 09 Jul 2007 19:39:12 +0000, Allen Weiner wrote:
>>>
....

>>>> --- 10.0.0.1 ping statistics ---
>>>> 50 packets transmitted, 50 received, 0% packet loss, time 49001ms
>>>> rtt min/avg/max/mdev = 0.109/0.115/0.163/0.015 ms
>>>> ]0;root@localhost:~ [root@localhost ~]# ifconfig eth0
>>>> eth0 Link encap:Ethernet HWaddr 00:07:E9:01:B2:09
>>>> inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
>>>> UP BROADCAST MULTICAST MTU:1500 Metric:1

Something's wrong, although I know not what. You should see RUNNING in
addition to "UP BROADCAST MULTICAST" in the line above regardless of
whether there is a connection to the card or not. This same problem
arose in a thread some time ago but there was no resolution.

>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:1000
>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>>
>>>> ]0;root@localhost:~ [root@localhost ~]# ethtool -t eth0
>>>> The test result is FAIL
>>>> The test extra info:
>>>> Link test (on/offline) 1
>>>> Eeprom test (on/offline) 0
>>>> Self test (offline) 0
>>>> Mac loopback (offline) 0
>>>> Phy loopback (offline) 0
>>>>
>>>> ]0;root@localhost:~ [root@localhost ~]#
>>>> Script done on Mon 09 Jul 2007 01:31:21 PM EDT
>>>
> About the NIC diagnostics, the "link test" is failing because I don't
> have anything connected to the NIC! (I don't have anything to connect).

You have probably tried "ethtool -t eth0 online" Did it fail?

> The other tests are not being run at all????

Dunno, you introduced me to ethtool. :| Here's what it gave me for an
"UP BROADCAST RUNNING MULTICAST" NIC with no connection:

corncob:~# ethtool -t eth0
Cannot test: Operation not supported

It was the same with online appended. See BUGS in man ethtool - I think!

--
Clifford Kite
/* In my book, the first poster to resort to personal abuse in a Usenet
debate loses by default. - Rod Smith */

Hello,

Allen Weiner a écrit :
>
> 1. Attempt to bring up interface: ifconfig eth0 10.0.0.1 up
> 2. Check response (ping it): ping -c 50 10.0.0.1
> 3. Use ifconfig to check for errors: ifconfig eth0
>
> The rtt times reported by ping lead me to think that data was
> transmitted, but the RX bytes and TX bytes reported by ifconfig are both
> zero.

Sending packets to any local address (i.e. any address configured on any
local interface of the same host) always uses the loopback interface,
not the interface the address is assigned to. "ifconfig lo" should show
the increasing TX and RX counters. So this test does not tell anything
about the physical interface.

Clifford Kite wrote:
> Allen Weiner <(E-Mail Removed)> wrote:
>> Allen Weiner wrote:
>>> Jack Snodgrass wrote:
>>>> On Mon, 09 Jul 2007 19:39:12 +0000, Allen Weiner wrote:
>>>>
> ....
>
>>>>> --- 10.0.0.1 ping statistics ---
>>>>> 50 packets transmitted, 50 received, 0% packet loss, time 49001ms
>>>>> rtt min/avg/max/mdev = 0.109/0.115/0.163/0.015 ms
>>>>> ]0;root@localhost:~ [root@localhost ~]# ifconfig eth0
>>>>> eth0 Link encap:Ethernet HWaddr 00:07:E9:01:B2:09
>>>>> inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
>>>>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>
> Something's wrong, although I know not what. You should see RUNNING in
> addition to "UP BROADCAST MULTICAST" in the line above regardless of
> whether there is a connection to the card or not. This same problem
> arose in a thread some time ago but there was no resolution.
>
>>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:1000
>>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>>>
>>>>> ]0;root@localhost:~ [root@localhost ~]# ethtool -t eth0
>>>>> The test result is FAIL
>>>>> The test extra info:
>>>>> Link test (on/offline) 1
>>>>> Eeprom test (on/offline) 0
>>>>> Self test (offline) 0
>>>>> Mac loopback (offline) 0
>>>>> Phy loopback (offline) 0
>>>>>
>>>>> ]0;root@localhost:~ [root@localhost ~]#
>>>>> Script done on Mon 09 Jul 2007 01:31:21 PM EDT
>> About the NIC diagnostics, the "link test" is failing because I don't
>> have anything connected to the NIC! (I don't have anything to connect).
>
> You have probably tried "ethtool -t eth0 online" Did it fail?
>
>> The other tests are not being run at all????
>
> Dunno, you introduced me to ethtool. :| Here's what it gave me for an
> "UP BROADCAST RUNNING MULTICAST" NIC with no connection:
>
> corncob:~# ethtool -t eth0
> Cannot test: Operation not supported
>
> It was the same with online appended. See BUGS in man ethtool - I think!
>

The ethtool -t eth0 online produced the same failure.

That's bad news you gave me that I should also see "RUNNING" in my
result for ifconfig eth0. Based on the initial reply to this thread, I
went ahead and signed up for DSL service!