From owner-freebsd-current Sat Aug 24 19:30: 8 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 2D50A37B400 for ; Sat, 24 Aug 2002 19:30:04 -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 8475D43E6A for ; Sat, 24 Aug 2002 19:30:03 -0700 (PDT) (envelope-from rodrigc@attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.12.3/8.12.3) id g7P2UGX5000298 for freebsd-current@freebsd.org; Sat, 24 Aug 2002 22:30:16 -0400 (EDT) (envelope-from rodrigc) Date: Sat, 24 Aug 2002 22:30:15 -0400 From: Craig Rodrigues To: freebsd-current@freebsd.org Subject: Re: 3COM 3c509 "eeprom failed to come ready" Message-ID: <20020824223015.A267@attbi.com> References: <20020825001032.JUGF14185.rwcrmhc51.attbi.com@rwcrwbc58> <20020825010026.3DA986BF@nebula.anchoragerescue.org> <20020824213320.A162@attbi.com> <20020825021649.1FCE66BF@nebula.anchoragerescue.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020825021649.1FCE66BF@nebula.anchoragerescue.org>; from akbeech@sinbad.net on Sat, Aug 24, 2002 at 06:16:48PM -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 06:16:48PM -0800, Beech Rintoul wrote: > On Saturday 24 August 2002 05:33 pm, Craig Rodrigues wrote: > > On Sat, Aug 24, 2002 at 05:00:25PM -0800, Beech Rintoul wrote: > > > > ep0: eeprom failed to come ready > > > > ep0: eeprom failed to come ready > > > > ep0: eeprom failed to come ready > > > > ep0: eeprom failed to come ready > > > > ep0: Ethernet address 00:00:00:00:00:00 > > Well, your mileage may vary, but I had exactly the same error message with > one of those cards about 3 months ago. Re-running the setup utils fixed it. > If my memory serves me correctly, I also disabled PNP-OS in the bios. I already have PNP-OS disabled in the BIOS, (I needed to do this 4 years ago when running Linux.) This problem seems to only occur with the CURRENT snapshot 20020818 which I obtained from current.freebsd.org. Do you think if I switch to an earlier CURRENT snapshot I may get further along? -- 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