From owner-freebsd-current Sat Aug 24 20:12: 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 4436437B400 for ; Sat, 24 Aug 2002 20:12:05 -0700 (PDT) Received: from nebula.anchoragerescue.org (115-7-237-24-cable.anchorageak.net [24.237.7.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73F8943E6A for ; Sat, 24 Aug 2002 20:12:04 -0700 (PDT) (envelope-from akbeech@sinbad.net) Received: from there (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with SMTP id 655CE6BF; Sat, 24 Aug 2002 19:12:03 -0800 (AKDT) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul Reply-To: akbeech@sinbad.net Organization: Sinbad Network Communications Inc. To: Craig Rodrigues , freebsd-current@freebsd.org Subject: Re: 3COM 3c509 "eeprom failed to come ready" Date: Sat, 24 Aug 2002 19:12:02 -0800 X-Mailer: KMail [version 1.3] References: <20020825001032.JUGF14185.rwcrmhc51.attbi.com@rwcrwbc58> <20020825021649.1FCE66BF@nebula.anchoragerescue.org> <20020824223015.A267@attbi.com> In-Reply-To: <20020824223015.A267@attbi.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020825031203.655CE6BF@nebula.anchoragerescue.org> 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 Saturday 24 August 2002 06:30 pm, Craig Rodrigues wrote: > 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? 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? Beech -- ------------------------------------------------------------------- Beech Rintoul - SysAdmin - akbeech@sinbad.net /"\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message