From owner-freebsd-chat Mon Nov 3 09:41:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA17525 for chat-outgoing; Mon, 3 Nov 1997 09:41:51 -0800 (PST) (envelope-from owner-freebsd-chat) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA17517 for ; Mon, 3 Nov 1997 09:41:48 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.7/8.8.5) with SMTP id MAA14321; Mon, 3 Nov 1997 12:30:25 -0500 (EST) Date: Mon, 3 Nov 1997 12:30:25 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Wes Peters cc: Petri Helenius , chat@FreeBSD.ORG Subject: Re: de driver In-Reply-To: <199711030842.BAA20209@obie.softweyr.ml.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I know that at least in 10BT mode, getting the 3am driver will fix this problem. It's really frustrating to have to manually bring the thing up like this... Why not just pull down the 3am driver and call it ours? Owner of a dozen de cards, Charles On Mon, 3 Nov 1997, Wes Peters wrote: > Petri Helenius writes: > > I pulled the cable from a SMC de0 card and put it back on. All link > > lights, etc came nicely back on but the OS thought that: > > [...] > > At the failure it logged: > > de0: link down: cable problem? > > Yeah, silly isn't it? You can just 'ifconfig de0 up' to get it back. > This really bit my using FreeBSD for a test station, until I switched > from using a crossover cable to a hub and two cables; we change the > unit the FreeBSD machine is connected to every 96 seconds. ;^) > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://www.xmission.com/~softweyr softweyr@xmission.com >