From owner-freebsd-mobile@FreeBSD.ORG  Mon Jun 14 04:19:43 2004
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0653816A4CE
	for <freebsd-mobile@freebsd.org>;
	Mon, 14 Jun 2004 04:19:43 +0000 (GMT)
Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CB8C943D2F
	for <freebsd-mobile@freebsd.org>;
	Mon, 14 Jun 2004 04:19:42 +0000 (GMT)
	(envelope-from dan@langille.org)
Received: from wocker (wocker.unixathome.org [192.168.0.99])
	by bast.unixathome.org (Postfix) with ESMTP
	id 18A613D34; Mon, 14 Jun 2004 00:19:42 -0400 (EDT)
From: "Dan Langille" <dan@langille.org>
To: Randy Bush <randy@psg.com>
Date: Mon, 14 Jun 2004 00:19:35 -0400
MIME-Version: 1.0
Message-ID: <40CCEF17.17295.6997F42F@localhost>
Priority: normal
In-reply-to: <16589.9727.538844.260373@ran.psg.com>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
cc: freebsd-mobile@freebsd.org
Subject: Re: suspend/resume issues on ThinkPad T41 under 5.2.1-RELEASE 
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2004 04:19:43 -0000

On 13 Jun 2004 at 21:13, Randy Bush wrote:

> > ifconfig em0 up
> > dhclient em0
> 
> dhclient will up the interface
> 
> > em0: The EEPROM Checksum Is Not Valid
> > em0: Unable to initialize the hardware
> 
> i have had that.  i don't remember what made it go away.
> 
> are you -current?

I tried snapshots from CURRENT-20040524 and CURRENT-20040611.

Both installs detected em0 during probing without issue but panic'd. 
One panic'd before I could get to /stand/sysintall.  The other 
panic'd right after pressing Q in FDISK.  I can't recall which was 
which there.

I tried the above -current's when 5.2.1 detected em0, but gave the 
above errors.
-- 
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/