On Thursday 17 July 2008, [EMAIL PROTECTED] wrote: > Thanks for the reply. I can no longer access my modem (192.168.1.1) at all. > When I boot either Fedora or Ubuntu, eth0 fails to come up. With Fedora, I > have quiet boot disabled, so I see all the boot messages. When Fedora tries > to start eth0, it displays a red "failed". > > If I issue ifconfig -a after boot, eth0 is not displayed. But ethtool eth0 > does report 100 Mbps, and "link-detected=yes". This leads me to believe my > NIC is OK.
Based on the behavior you're seeing, I suspect the NIC is at least part of the problem, and is probably dead. > If I issue "service network start" after boot, I get a message SIOCFFLAGS > (sp?), "resource temporarily unavailable". > > I read a post on an Anandtech forum about a lightning damaged modem where > the modem worked OK, but the ethernet interface was destroyed. On the last > day I had Internet connectivity, I remained online with no problem for six > hours after the (very mild and distant) thunderstorm. On reboot the next > day, and on all subsequent days, eth0 fails to start. It actually isn't surprising that the NIC that now acts dead, yet worked for six hours -- that very much sounds like a "latent ESD failure". [ESD = ElectroStatic Discharge] An ESD event can sometimes cause hardware failure hours, days, weeks, or even _months_ after the event occured, with working operation in-between. There's generally no good way to detect them ahead of time, either. -- Chris -- Chris Knadle [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 4 - Sqeak! and eToys Jul 2 - KVM (Tenative) Aug 6 - Zenos Sep 3 - TBD
