DEC 21143 & tulip?

[Jay Thorne]

Theo Van Dinter wrote:
> 
> | get the 0.90 driver at Don Becker's site.
> 
> as I mentioned in my original email:
> 
>         the 0.90 driver sets up the card eventually, but not before things like automount fail.
> 
> I poked a little more at it today on another test box, and what happens is the machine boots, ypbind starts, but then can't bind for a good long while.  this causes the automounter to fail, which then causes other things to fail, etc, etc, etc.  the tulip driver causes this 100% of the time, the de4x5 driver allows a bind in under 2 seconds, which is fast enough for everything else to come up.
> 
> I tried adding in a quickie little delay for ypbind (this works nicely with Solaris, so why not Linux?):
>          ypwhich 2>&1 > /dev/null
>          while [ $? != 0 ]; do
>             sleep 1
>             echo -n "."
>             ypwhich 2>&1 > /dev/null
>          done
> 
> the tulip driver sits there "indefinately" (at least 30-45 seconds) in this loop.  the de4x5 driver loops once and then continues after the bind occurs.
> 
> appropriate section of the log file: (kernel compiled with both tulip .90 and de4x5 drivers installed)
> Jan 21 13:35:39 milli kernel: tulip.c:v0.90 10/20/98 becker@cesdis.gsfc.nasa.gov
> Jan 21 13:35:39 milli kernel: eth0: Digital DS21143 Tulip at 0x1400, 00 48 54 00 d3 6f, IRQ 9.
> Jan 21 13:35:39 milli kernel: eth0:  EEPROM default media type Autosense.
> Jan 21 13:35:39 milli kernel: eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
> Jan 21 13:35:39 milli kernel: eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
> Jan 21 13:35:39 milli kernel: eth0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
> Jan 21 13:35:39 milli kernel: eth0:  Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
> [snipped]
> Jan 21 13:35:58 milli kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000021c6 ffff0001 fffbffff 8ff00008, resetting...
> Jan 21 13:35:58 milli kernel: eth0: transmit timed out, switching to 10baseT-FD media.
> Jan 21 13:36:03 milli kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0001 fff87f3d 8ff50000, resetting...
> Jan 21 13:36:03 milli kernel: eth0: transmit timed out, switching to 10baseT media.
> Jan 21 13:36:08 milli kernel: eth0: 21140 transmit timed out, status f0260000, SIA 000021c6 ffff0001 fff8ffff 8ff50000, resetting...
> Jan 21 13:36:08 milli kernel: eth0: transmit timed out, switching to 100baseTx-FD media.
> Jan 21 13:36:08 milli kernel: eth0: 21143 100baseTx sensed media.
> 
Interesting.  I've had a bad tulip card (it had a bad jack) do this. But you
are saying that the card behaves well with the de4x5.

Any reason why you don't use modules?  For me it let me diddle with insmod
commands and options to check to see what it was doing.

Also, you can force media types with the tulip.  What is the conection?  Is
is supposed to be 100BaseTx?  The media selection time-out cycle of the
tulip driver is a bit long. (5 seconds as you see.  So you get 20 seconds in
total while it gets to the right media.


-- 
Jay Thorne  The Net Result System Services jay@result.com   
Http://net.result.com
Zoom 505 Effect page http://net.result.com/~jay 
Zoom 5xx series Patch Database: http://net.result.com/~jay/db.html