Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!marque!uunet!mcvax!enea!kth!draken!ragge
From: ragge@nada.kth.se (Ragnar Sundblad)
Newsgroups: comp.unix.aux
Subject: Re: problems with ethernet interface
Message-ID: <586@draken.nada.kth.se>
Date: 4 Oct 88 20:52:49 GMT
References: <1959@spdcc.COM> <12275@steinmetz.ge.com> <7247@bloom-beacon.MIT.EDU>
Reply-To: ragge@nada.kth.se (Ragnar Sundblad)
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 31

In article <7247@bloom-beacon.MIT.EDU> dyer@arktouros.MIT.EDU (Steve Dyer) writes:
>In my experience, "ifconfig ae0 up" was a no-op.  Programs complained
>"network down" anyway.  Someone else placed the line
>ifconfig ae0 down; ifconfig ae0 up
....
>Steve Dyer

That's probably one of the bugs in the National DP8390 (described in
DP8390 Tech Update, problem #3).

"
	Problem 3
	Suspended Operation After Transmission: If Collision (COL) is
	asserted during the transmission of the last byte, the NIC will
	suspend all operations. This problem is manifested when the
	Command Register continually reads 26H.
	The NIC must be hardware reset to resume operation.

	NOTE: In a properly operating IEEE 802.3 network, a collision will
	never occur during the last byte of transmission.
"

You can find the command register at the byte at address
	0xFSSE003C, where S = slot number (in a MacII 9 <= S <= E)
if you would like to check it out. (and if you somehow manage to
look at this address).

If this is the problem, you'd better check your ethernet.

Note: I don't THINK that the EtherTalk card exchange some months ago
solved this problem.