On Mon, Jan 25, 2010 at 2:38 PM, Denis Heidtmann <denis.heidtm...@gmail.com> wrote: > On Mon, Jan 25, 2010 at 12:33 PM, Steve D... <blitt...@gmail.com> 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. > With regard to your steps above. 1) I have tried ifdown/ifup to no > avail. I have not tried ifconfig up. When I break the network I will > try it. The latest distros use a Network Manger to control the NICs. This is a response to the wide use of laptops and wireless connections. The Network Manager is suppose to auto-magically switch to the correct link as you move your laptop around. The ifup and ifdown scripts in /etc/networks may no longer exist. The "ifconfig eth0 up/down" command should still work. If not, go into the sys-config-network GUI and unselect the Network Manager control. YMMV Redhat, Ubuntu, and Debian all do the network control things a little different. I like to open a second console with "tail -f /var/log/messages" running so I can watch what's going on. > 2) my modem does not support 1000, and I have no switch. 3) A > new card is on my list. 4) I plan to do that, but the thought of > dealing with ASUS (the MB mfg.) makes me think of a tar pit. You may be able to nail the modem to 100-Full if it has a management interface. Set both sides to 100-Full. The ethernet link will come up without negotiation, Problem solved! A cheap switch in the middle may also solve your problem. The ethernet PHY in the switch will probably be a different type than the one in the modem. Your system would be negotiating with a different link partner, which may not have experience the error. Steve D... -- "Every perception is a gamble" Robert Anton Wilson _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
