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

.

Relevant Pages

  • Re: handling errors through catch
    ... Since the value returned, wtitten in a point-info window, is correct I ... If the following code expects that $num_pnt exists and contains a floating-point number value, then it will fail, as in the error case num_pnt will not be set to anything. ... If the script completes with no errors, then this variable is set to the result of the script. ... It might be appropriate to set num_pnt to some default value in this case, or you may want to exit from the procedure, or raise a different error. ...
    (comp.lang.tcl)
  • Re: Date Transformation from YYYYMMDD - yet another question
    ... I would check first in your script that the date length is that expected ... > dim i_Month ... > fields that fail and it excedes the error limit. ... > can tell the DTS job to just skip rows that fail instead of having the ...
    (microsoft.public.sqlserver.dts)
  • Re: pipes ifs and suggestions
    ... is quite common (and will fail in many other circumstances as well, ... as the last command of the script. ...
    (comp.unix.shell)
  • Re: pipes ifs and suggestions
    ... is quite common (and will fail in many other circumstances as well, ... as the last command of the script. ...
    (comp.unix.shell)
  • Re: Office 2000 network installs cannot access original install share anymore
    ... The WI doesn't fail with access denied then. ... It only fails when the system calls WI for some reason at boot-time. ... The time you've spent writing this message you could have already run the script and analysed the log file. ...
    (microsoft.public.office.setup)