From owner-freebsd-stable@FreeBSD.ORG  Thu Feb 26 11:26:50 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 155C716A4CE
	for <stable@freebsd.org>; Thu, 26 Feb 2004 11:26:50 -0800 (PST)
Received: from gidgate.gid.co.uk (gid.co.uk [194.32.164.225])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2CABB43D1D
	for <stable@freebsd.org>; Thu, 26 Feb 2004 11:26:49 -0800 (PST)
	(envelope-from rb@gid.co.uk)
Received: (from rb@localhost)
	by gidgate.gid.co.uk (8.11.7/8.11.6) id i1QJQUL34551;
	Thu, 26 Feb 2004 19:26:30 GMT
	(envelope-from rb)
Message-Id: <6.0.1.1.2.20040226192403.03dddb28@gid.co.uk>
X-Sender: rbmail@gid.co.uk (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 26 Feb 2004 19:26:26 +0000
To: Mike Tancsa <mike@sentex.net>
From: Bob Bishop <rb@gid.co.uk>
In-Reply-To: <6.0.3.0.0.20040226131930.10513908@209.112.4.2>
References: <6.0.3.0.0.20040226131930.10513908@209.112.4.2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Thu, 26 Feb 2004 19:26:50 -0000

Hi,

At 18:25 26/2/04, 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 ?

FWIW I get something very similar under 5.2.1-RC2 on my shiny new ThinkPad 
T41, so it's likely just not recognised.

--
Bob Bishop		    +44 (0)118 977 4017
rb@gid.co.uk		fax +44 (0)118 989 4254