From owner-freebsd-hackers Thu May 29 18:26:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20999 for hackers-outgoing; Thu, 29 May 1997 18:26:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20987 for ; Thu, 29 May 1997 18:26:07 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA22812; Fri, 30 May 1997 10:54:29 +0930 (CST) From: Michael Smith Message-Id: <199705300124.KAA22812@genesis.atrad.adelaide.edu.au> Subject: Re: ed0 : device timeout In-Reply-To: <199705291506.RAA01207@oskar.nanoteq.co.za> from Pierre Van Leeuwen at "May 29, 97 05:06:46 pm" To: pvl@nanoteq.com Date: Fri, 30 May 1997 10:54:29 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Pierre Van Leeuwen stands accused of saying: > Hi > > I wrote to questions about this earlier, but that didn't solve my > problem. > > I get the following message : > ed0 : device timeout The ususal reasons for this are : - you have an IRQ mismatch, in that the card is set to one value, and the driver another. - you have a cabling/termination problem on your network. - your card is faulty. > It doesn't seem to be fatal all the time though. Sounds like cabling - a bad RJ/BNC connector, T-piece, terminator or hub port. > Pierre_Andre van Leeuwen -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[