I surely appreciate the feedback, I wish it was the EEPROM...
here's the results of ifconfig
-bash-2.05b# ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:69:41:09:53
inet addr:10.0.110.39 Bcast:10.0.110.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2084 errors:0 dropped:0 overruns:0 frame:0
TX packets:1448 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:39
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
looks good...
Here's the results of running route:
-bash-2.05b# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
smi-ssd * 255.255.255.0 U 0 0
0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 10.0.110.1 0.0.0.0 UG 0 0
0 eth0
which looks good... inetd is running just fine and dandy...and the
eth0 bootp is static.
Problem occurs when I try to ping the gateway... I also notice that
the led on the switch is off... like the ethernet device never came up...
Wondering about power supply I read somewhere in the linux rags that
the reason why the ethernet driver could fail is power intermittence?
If that was true, how can I diagnose the board to make sure all the
devices/peripherals are running at their optimal level?
Hmmm... I don't want to just RMA this board due to a bad NIC, I just
bought this board 3 months ago...the MTBF should be years not months?
Any help is appreciated.
Jayne
--- In Mel Wilson <> wrote:
>
> Jayne Dickinson wrote:
> > I am having the same problem, I didn't change anything on my factory
> > default TS7400 board and now my ethernet device doesn't work
anymore...
> >
> > dmesg is showing when I try to ping my router, all my other boards are
> > just fine ( they use the same switch and gateway ):
> > NETDEV WATCHDOG: eth0: transmit timed out
> >
> > I tried different ethernet cables and got the same result..heck I even
> > took the ethernet cable that is plugged into my bad TS7400 and swapped
> > it with a working TS7400... what type of diagnostics are available
> > from TS to trouble shoot this problem?
>
> Something like this happened to us. In our case, the MAC address kept
> in EEPROM got erased -- we never found evidence to tell us how.
>
> IIRC, if you get a serial login through the TS-94?? card (or
> otherwise), you can use "ifconfig eth0" to find out what eth0 thinks
> its MAC address is. All hex FF would mean erased, anything reasonable
> would mean OK.
>
> Mel.
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|