[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-net
Subject:    Re: Intel EtherExpress 16 TX issue
From:       Paul Kanz <pkanz () conix ! com>
Date:       1998-05-29 17:46:31
[Download RAW message or body]


I was never getting, or at least not seeing, the 'CU wedged' error
message.  The cards where in 16-bit mode, via softset.exe.  I have 6 of
these cards in 4 test nodes - same results.  It's cheaper for me to
replace them with NE2000 clones, then trying to make something work that
may never will (as per the eexpress.c headers).

-Paul

On Thu, 28 May 1998, Philip Blundell wrote:

> Date: Thu, 28 May 1998 20:08:05 +0100
> From: Philip Blundell <Philip.Blundell@pobox.com>
> To: Paul Kanz <pkanz@conix.com>
> Cc: maillists@abacus.terraworld.net, linux-net@vger.rutgers.edu
> Subject: Re: Intel EtherExpress 16 TX issue 
> 
> >I have read eexpress.c, and found two work arounds:
> >
> >	1.  Buy new NIC
> >	2.  Setting 'mss 512' and 'window 1024'.
> 
> If you get `CU wedged' messages, the usual cause is that you're running the 
> NIC in 8-bit mode with a 2.0 kernel.  Either upgrade to 2.1 or switch to 
> 16-bit mode using SOFTSET (or refer to 1 above).
> 
> p.
> 
> 

----------------------------------------------------------------------------
Paul Kanz
Conix Consulting
pkanz@conix.com
----------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu

[prev in list] [next in list] [prev in thread] [next in thread]