From owner-freebsd-questions Fri Feb 27 10:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27620 for freebsd-questions-outgoing; Fri, 27 Feb 1998 10:00:20 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27557 for ; Fri, 27 Feb 1998 10:00:06 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id JAA18326; Fri, 27 Feb 1998 09:57:47 -0800 (PST) Message-Id: <199802271757.JAA18326@implode.root.com> To: "Chris Jeter" cc: freebsd-questions@FreeBSD.ORG Subject: Re: device time out ed0 In-reply-to: Your message of "Fri, 27 Feb 1998 11:01:42 CST." <001501bd43a1$6097d200$078834ce@tech.media-net.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 27 Feb 1998 09:57:47 -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've recently switching out my MB and am currently running 2.2.1. apon = >booting the system back up I started getting ed0 time out errors. things = >that I have tried have include booting the generic kernel and setting it = >to probe ed0, it returns the same error, checked to make sure the card = >was still jumpered to irc 11 to match the kernel settings, swapped back = >to the old MB, reseated the card. all of these have still returned the = >time out error. any other ideas? Sounds like you might have a conflict with another device. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message