From owner-freebsd-questions Wed Jul 30 09:28:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12832 for questions-outgoing; Wed, 30 Jul 1997 09:28:48 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12826 for ; Wed, 30 Jul 1997 09:28:45 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id MAA07621; Wed, 30 Jul 1997 12:30:48 -0400 (EDT) Date: Wed, 30 Jul 1997 12:30:48 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Robin Melville cc: questions@FreeBSD.ORG Subject: Re: de0 driver autosense fail... doesn't reset In-Reply-To: <1.5.4.32.19970730113208.006b3370@wrcmail> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'll take this one ;) I just had the same problem with another digital card. Getting the "alternate" de driver from here: http://www.3am-software.com/de-970703.tar.gz should solve that. I just compiled with these driver parts, and I can happily plug and unplug without incident. You still get the "link down... cable problem?" messages, but on plugging it back in, a nice friendly "de0: enabling 10BT port" comes up on the console and all is well. There is a short discussion about this over on -hackers; searching on de0 and 2.2-STABLE should bring it up on the mail archives. As for the quality/reliability of this driver, it's unknown, but the author is apparently the person who originally put a de driver together, so I assume he knows what he's doing... Charles On Wed, 30 Jul 1997, Robin Melville wrote: > I recently upgraded with a couple of SMC 8432T (Dec 21041 type) ether cards > which use the 'de' driver. > > The primitives who run this hospital routinely switch off the power to test > their generator. This gives anything up to 20 secs blackout. While the > servers are protected by UPS, the UTP hubs aren't (they aren't under our > control). Previously the servers would recover network failure gracefully. > Now the de0 driver reports: 'autosense failed: cable problem?' and shuts > down the interface. I haven't yet succeeded in reactivating the interface > without rebooting. > > This is obviously not a desirable solution, and I'd prefer that the return > of patent ethernet on the card was detected. > > Questions: > > a) is there something I can do to workaround the problem? > > b) is it a hardware or driver problem? Will it be rectified, or shall I junk > the cards and get something different which works better? > > Thanks for your help. > > Robin. > > -------------------------------------------------------- > Robin Melville, Addiction & Forensic Information Service > Nottingham Alcohol & Drug Team (Extn. 49178) > Vox: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 > Email: robmel@nadt.org.uk > WWW: http://www.innotts.co.uk/nadt/ > --------------------------------------------------------- >