From owner-freebsd-stable@FreeBSD.ORG Thu Sep 6 22:27:37 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DCEF9106564A for ; Thu, 6 Sep 2012 22:27:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0058FC14 for ; Thu, 6 Sep 2012 22:27:37 +0000 (UTC) Received: by vcbgb30 with SMTP id gb30so4068566vcb.13 for ; Thu, 06 Sep 2012 15:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mdmBFgKD4sjRIXix1kAK/Li3EspsN8s2kRvVDCE8XFo=; b=G+7/xY4LnX1WuBXwfUdPu/Uy0t2TOOtItRmeYGJk+5Lmpc6H3NlskMYHCGaA+VEtU1 QMVEWkf38Xc4vAChdD9j3YFrRMgAmgqMyP8DiwfZHsSwgBk/3PsWUfIr+E6+ydsHjrWO Xmdcirgof/kNv67tfRGdW4Mr9MsaPyLZtfSjQvywPZr+uN4KcaxSzlcSgt02s79vrqAg Dsqnjq0KkgHDZCH3w+shBThYHWJYda5qF7nYn+jKSxOQoSMgIqdukbBT5OjkxvD4PlUc Hb1R7O9kjMKfsOTivt/UBDrFyyi/Blo8xpzKgjbSvBiPKneWX2fNcXiaRHBUvLUyAA6r 3CwA== MIME-Version: 1.0 Received: by 10.58.196.174 with SMTP id in14mr5069012vec.18.1346970456643; Thu, 06 Sep 2012 15:27:36 -0700 (PDT) Received: by 10.58.68.8 with HTTP; Thu, 6 Sep 2012 15:27:36 -0700 (PDT) In-Reply-To: <50491E26.1010106@omnilan.de> References: <50491E26.1010106@omnilan.de> Date: Thu, 6 Sep 2012 15:27:36 -0700 Message-ID: From: Jack Vogel To: Harald Schmalzbauer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable@freebsd.org Subject: Re: intel 82579 nic support? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Sep 2012 22:27:37 -0000 82579 is not a NIC, its a PHY, and it you look at the current code you will see the support is in there. So the real question is what the actual NIC is, how about a pciconf -lv? Next, how are you trying "to pass through the device into my FreeBSD VM", what is the virtualization environment. Widely spread, uh ya, but not virtualized, so tell me more about the environment. Jack On Thu, Sep 6, 2012 at 3:05 PM, Harald Schmalzbauer < h.schmalzbauer@omnilan.de> wrote: > Hello, > > I'm playing with releng_9_1 on a neat intel server, pre-production. > Since ESXi5.0-768111 doesn't supprot the second on-board NIC/PHY of my > BearTooth board, I tied to pass through the device into my FreeBSD VM. > The NIC get's recogniced, but isn't usable because "Setup of Shared code > failed". > According to the man page, 82597 isn't supported by em (or igb) at all, > but at least it tries to attach. > What's the current status of this by now widly spread PHY/NIC? > > Thanks, > > -Harry > > >