From owner-freebsd-current Sat Aug 24 22:34:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8CA237B400 for ; Sat, 24 Aug 2002 22:34:44 -0700 (PDT) Received: from dibbler.ne.client2.attbi.com (dibbler.ne.client2.attbi.com [24.61.41.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id F097B43E65 for ; Sat, 24 Aug 2002 22:34:43 -0700 (PDT) (envelope-from rodrigc@dibbler.ne.client2.attbi.com) Received: from dibbler.ne.client2.attbi.com (localhost [127.0.0.1]) by dibbler.ne.client2.attbi.com (8.12.5/8.12.5) with ESMTP id g7P1YvsW000768 for ; Sun, 25 Aug 2002 01:34:57 GMT (envelope-from rodrigc@dibbler.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.12.5/8.12.5/Submit) id g7P1Yukc000767 for freebsd-current@freebsd.org; Sun, 25 Aug 2002 01:34:56 GMT Date: Sun, 25 Aug 2002 01:34:56 +0000 From: Craig Rodrigues To: freebsd-current@freebsd.org Subject: Re: 3COM 3c509 "eeprom failed to come ready" Message-ID: <20020825013456.A753@attbi.com> References: <20020825001032.JUGF14185.rwcrmhc51.attbi.com@rwcrwbc58> <20020825021649.1FCE66BF@nebula.anchoragerescue.org> <20020824223015.A267@attbi.com> <20020825031203.655CE6BF@nebula.anchoragerescue.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020825031203.655CE6BF@nebula.anchoragerescue.org>; from akbeech@sinbad.net on Sat, Aug 24, 2002 at 07:12:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Aug 24, 2002 at 07:12:02PM -0800, Beech Rintoul wrote: > I'm not sure about an earlier -current, but I can tell you I'm running one of > those cards with yesterday's -current with no problems. You didn't say which > kernel you're running, but if it's GENERIC it has device ep uncommented. The > only way I could get rid of that eeprom error was to re-run the setup util. > Mine however wasn't hanging the boot it would go on and define the card as > ep1. One thing you might try is putting the card in another slot and see if > it will boot. > > Anyone else have this problem with -current? Hi, I am indeed having this problem with the GENERIC kernel that is included with the 20020818 -current snapshot. Here is some more information: - instead of booting the GENERIC kernel that gets installed with 20020818, if I boot with the kernel from the floppy disk that comes with 20020818, and then from the command-prompt specify the root filesystem as ufs:ad0s2a (which is where I installed -current), then the system boots up fine, and I have no problem with ep0, and in fact I can use ep0 successfully. So, there is something different between the GENERIC kernel and the kernel on the bootdisk in 20020818. Any idea what it could be? Thanks. -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message