On Mon, Jan 25, 2010 at 3:14 PM, Steve D... <[email protected]> wrote: > On Mon, Jan 25, 2010 at 2:38 PM, Denis Heidtmann > <[email protected]> wrote: >> On Mon, Jan 25, 2010 at 12:33 PM, Steve D... <[email protected]> wrote: >> >>>> Do you see this as an accurate assessment? >>> >>> Pretty much... Your available choices are: >>> >>> 1) Deal with it... You many have to "ifconfig up" your eth port from >>> time to time. :-) >>> >>> 2) Nail your NIC and switch port to 1000-Full. This will only works >>> on a managed switch. Only nailing one side can result in a >>> duplex-mismatch. >>> >>> 3) Install a different NIC. I like the Intel cards. Make sure to >>> replace the distro's in-box driver. The latest and greatest Intel >>> Linux drivers up on Sourceforge are pretty good. >>> >>> 4) Open up an issue with your NIC manufacture. They may be willing to >>> troubleshoot the problem and provide a fixed driver. This would be >>> good for the Linux community. Somebody has to be willing to feel the >>> pain so we can all reap the benefits. :-) >>> >>> Steve D... >>> >> Once again I thank you for the information. I have been thinking that >> the thing which changes from one power-on--boot to the next is the >> time from when the juice is connected to the desktop to when I press >> the front panel button. The stuff about the ME may fit in with this. >> I can explore this when I feel not having a connection will not be too >> painful. > > Put a Mark 1 Eyeball on the NIC LEDs the next time you have an > error. I suspect your LEDs will show 10-Full. That would be an > indication that the ME went into a power saving mode and then failed > to renegotiate after waking up. > ... > Steve D... > We have been keeping the power on, yet shutting down regularly (~2-3 times/day) and had no failures for 7 days. Then we started powering off the modem and the computer after shutdown, and powering up the modem and the computer to restart (push front button 2-10 seconds after turning on the power). After 3 days of this we had a network failure--same as before--no ping response from the modem. I shut down and restarted w/o power interruption 3 times, and each time it came up w/ the network failed. Then I shut down and then turned the power off to the computer (sw. on back), leaving the modem powered. After about 30 seconds of this I repowered the computer and restarted. Network came up functional.
When in the failed state I checked the lights on the NIC: speed steady orange meaning 100Mbps; Activity slow blinking yellow meaning data activity. The blinking is synchronized with the blinking on the modem. When in a functional state the lights are the same. I neglected to try ifconfig eth0 ifup/ifdown routines. Next time. -Denis _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
