From owner-freebsd-current@FreeBSD.ORG Mon Jul 13 10:31:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B40141065672 for ; Mon, 13 Jul 2009 10:31:07 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 0398E8FC0C for ; Mon, 13 Jul 2009 10:31:06 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: (qmail invoked by alias); 13 Jul 2009 10:04:25 -0000 Received: from dialbs-213-023-190-146.static.arcor-ip.net (EHLO [192.168.10.5]) [213.23.190.146] by mail.gmx.net (mp007) with SMTP; 13 Jul 2009 12:04:25 +0200 X-Authenticated: #3631242 X-Provags-ID: V01U2FsdGVkX1/IlvhHXPnI0lXpNQ4aFmQHhri+XFgescZ941Inbu WQ+Ji+dUUGzp6x Message-ID: <4A5B06B3.5020004@gmx.net> Date: Mon, 13 Jul 2009 12:04:35 +0200 From: Michael Schmiedgen User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Jack Vogel References: <58c737d70907082058s4e97223fuc0bdbdfaabc3a0a5@mail.gmail.com> <20090709153940.4544bfa8.stas@FreeBSD.org> <58c737d70907091052g7a6f962jf87e94974f7e46aa@mail.gmail.com> <2a41acea0907091135j12f4c0efn963859f8def1d9cd@mail.gmail.com> <2a41acea0907091713v6291f7dbt33b61c10ee7db893@mail.gmail.com> <58c737d70907100058u263ab795g442c62d67ba2345f@mail.gmail.com> <2a41acea0907101026j65c16017kfb57cbd77c72577c@mail.gmail.com> In-Reply-To: <2a41acea0907101026j65c16017kfb57cbd77c72577c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 Cc: freebsd-current@freebsd.org Subject: Re: no em0 with r195477 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2009 10:31:07 -0000 Hi, I got this on my boot console, revision is from last week: em0: The EEPROM Checksum Is Not Valid device_attach: em0 attach returned 5 It's a Supermicro workstation board with Intel chipset and build-in NIC. I am dual boot and WinXP works fine, so the checksum message is perhaps not correct. I am not at machine at the moment but let me know if you want to get further, detailed information. Michael