From owner-freebsd-stable@FreeBSD.ORG  Thu Feb 26 18:07:48 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B41C016A4CE
	for <stable@FreeBSD.ORG>; Thu, 26 Feb 2004 18:07:48 -0800 (PST)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ACD0F43D1D
	for <stable@FreeBSD.ORG>; Thu, 26 Feb 2004 18:07:48 -0800 (PST)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 9F43F72DCB; Thu, 26 Feb 2004 18:07:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 9B58A72DB5; Thu, 26 Feb 2004 18:07:48 -0800 (PST)
Date: Thu, 26 Feb 2004 18:07:48 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: Mike Tancsa <mike@sentex.net>
In-Reply-To: <6.0.3.0.0.20040226131930.10513908@209.112.4.2>
Message-ID: <20040226180719.T54635@carver.gumbysoft.com>
References: <6.0.3.0.0.20040226131930.10513908@209.112.4.2>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: stable@FreeBSD.ORG
Subject: Re: bad em NIC or new unrecognized NIC ?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2004 02:07:48 -0000

On Thu, 26 Feb 2004, Mike Tancsa wrote:

> Hi all,
>
> One of the EM nics we just got in comes up with
>
> em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.19> port
> 0x9000-0x903f mem 0xe8700000-0xe871ffff,0xe86e0000-0xe86fffff irq 5 at
> device 0.0 on pci1
> em0: The EEPROM Checksum Is Not Valid
> em0: Unable to initialize the hardware
> device_probe_and_attach: em0 attach returned 5
>
> when booting. Is this just a dud or just not recognized ?

Last time I saw this, it was because there was a new rev of the silicon.
If its an onboard, check for a new BIOS for your system.

>
> none0@pci1:0:0: class=0x020000 card=0x11138086 chip=0x10768086 rev=0x00
> hdr=0x00
>      vendor   = 'Intel Corporation'
>      class    = network
>      subclass = ethernet
>
> 4.9-STABLE FreeBSD 4.9-STABLE #1: Thu Jan  8 14:19:25 EST 2004
> --------------------------------------------------------------------
> Mike Tancsa,                          	          tel +1 519 651 3400
> Sentex Communications,     			  mike@sentex.net
> Providing Internet since 1994                    www.sentex.net
> Cambridge, Ontario Canada			  www.sentex.net/mike
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org