I tried dmesg but the only extra lines in the message buffer since
boot up were:
	de0: link down: cable problem?

the last line before these, i.e. the last line created during boot up
was:
	de0: enabling FUll Duplex 100BaseTX port

which is to be expected with our hub.

Reconecting the cable did not result in any new messages all though it
did stop the repeated cable problem message as you would expect. So
why do I have to issue an "UP" on de0 to get things working again ?

--Sean

On Fri, 23 Jan 1998, Matt Thomas wrote:

> At 07:10 PM 1/22/98 , Sean Witham wrote:
> >
> 
> >If I re-patch a 100TX de0 connection NetBSD 1.2 corectly reports that
> >the link is down and suggests a connection problem. However after the
> >link is re-patched the de0 device until I ifconfig de0 up the device.
> 
> It should have sensed the link being reattached.  What card are you
> using?  (dmesg output would be nice too).

As pointed out before it was on NetBSD-1.3 so about that. The card
itself was a D-Link clone (D-Link DFE-500TX) with the Dec 21141-AE
chip.

I'll reproduce this later today and run dmesg.

--Sean