[nSLUG] Happy Meal Ethernet

Peter Cordes peter at llama.nslug.ns.ca
Wed Mar 19 00:46:26 AST 2003


On Fri, Mar 14, 2003 at 11:15:02AM -0400, Dop Ganger wrote:
> On Fri, 14 Mar 2003, Donald Teed wrote:
> 
> > The typical trigger point for the ethernet to fail is a burst of data.
> > For example, an nmap probe from another machine, or fast scrolling text
> > output from a ssh session will cause the connection to close or fail.
> 
> I have an identical problem with one of my laptops (x86) with an Intel
> chipset. The only solution I've found to get around this without rebooting
> is to compile the driver as a module, then when it hangs do ifdown eth0 ;
> rmmod eepro100 ; modprobe eepro100 ; ifup eth0. Not much of a solution
> but it should save on rebooting, at least.

 Have you tried newer eepro drivers?  I thought I read about that problem
being tracked down and fixed.

-- 
#define X(x,y) x##y
Peter Cordes ;  e-mail: X(peter at llama.nslug. , ns.ca)

"The gods confound the man who first found out how to distinguish the hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BC



More information about the nSLUG mailing list