From owner-freebsd-hackers Tue Jan 28 10:05:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28000 for hackers-outgoing; Tue, 28 Jan 1997 10:05:41 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA27995 for ; Tue, 28 Jan 1997 10:05:35 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0vpAAb-0000Jh-00; Tue, 28 Jan 1997 01:49:37 -0800 Date: Tue, 28 Jan 1997 01:49:37 -0800 (PST) From: Tom Samplonius To: Joe McGuckin cc: hackers@freebsd.org Subject: Re: Ethernet bug - 2.1.6-RELEASE In-Reply-To: <199701280527.VAA23113@monk.via.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Jan 1997, Joe McGuckin wrote: > I've noticed that if I disconnect the ethernet cable from my > de0 NIC, I no longer see the warning message about the cable > being unplugged. Also, when I plug it back in, I no longer > see the message about the UTP cable being plugged in. > > Also, once disconnected, the ethernet port no longer works and > the machine must be rebooted to restore functionality. > > joe This seems somewhat dependant on the kind of card used. A SMC Etherpower 10/UTP behaves correctly, if disconnected and reconnected. A D-Link (DE-650?) with BNC/UTP did not do this properly. Fooling about with "ifconfig de0 -linkX" did manage to get it working again. I think the problem is that some cards don't properly indicate whether a particular interface is working, or not working, to the driver, except on power-on. Tom