Monkey boy needs help! Transmit timed out:...

Gisli Ottarsson
Sat Oct 23 21:00:48 1999

I took v1.09t for a spin but experienced the same behavior as I
described earlier with the r model.

BTW, please don't fail to fail into account the possiblity that my
card is broken.  It has never been tested in another application.
Or has mii-diag proven that the card is OK?



>>>>> On Sun, 24 Oct 1999 01:23:59 +0200 (CEST), you said:
  BK> On 23 Oct 1999, Gisli Ottarsson wrote:
  >> Unfortunatly, the driver does not solve the problem I described.  The
  >> behavior is subtly different from what I descibed in my earlier post,
  >> but the effect is the same.  One of the main differences is that I
  >> start seeing the "Transmit timed out" messages as soon as I give the
  >> 'ifup eth0' command, whereas earlier the messages didn't start
  >> appearing until I started to ping.  Also, the status on the timeout
  >> is 2050.

  BK> Thanks for the info. The next item to sort out would be to try
  BK> the latest development driver from Donald. It's at:

  BK> It should be: v1.09t 9/29/99
  BK> If I you have a problem compiling it, tell me.
  BK> Tell how this driver does.

  >> To my untrained eye, it looks like the main problem is evidenced by
  >> the message from 'eepro100-diag -f -a' that
  >> The transmit unit state is 'Suspended' 
  >> The receive unit state is 'Ready'
  >> How can I move the transmit unit from a 'Suspended' state?

  BK> After having the results from the v1.09t, I'll look further.

  BK> Regards,
  BK> Bernd

  >> Thanks again
  >> Gisli