From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 05:31:24 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 54625106566B; Thu, 23 Aug 2012 05:31:24 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id 348F58FC16; Thu, 23 Aug 2012 05:31:23 +0000 (UTC) Received: from [192.168.2.82] (jn@c-67-182-217-170.hsd1.ut.comcast.net [67.182.217.170]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id q7N5OJQx068596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Aug 2012 01:24:20 -0400 (EDT) (envelope-from lists@jnielsen.net) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) Content-Type: text/plain; charset=iso-2022-jp From: John Nielsen X-Priority: 3 In-Reply-To: Date: Wed, 22 Aug 2012 23:24:37 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <02E5BFB9-901B-4AA3-9594-160C3259AE66@jnielsen.net> References: To: Daisuke Aoyama X-Mailer: Apple Mail (2.1485) X-DCC-sonic.net-Metrics: ns1.jnielsen.net 1117; Body=3 Fuz1=3 Fuz2=3 X-Virus-Scanned: clamav-milter 0.97.5 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: iSCSI boot driver 0.2.5 (isboot.ko) has been released. 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, 23 Aug 2012 05:31:24 -0000 On Aug 21, 2012, at 11:43 PM, Daisuke Aoyama wrote: > You can download the source file from: > http://www.peach.ne.jp/archives/isboot/isboot-0.2.5.tar.gz > ... Daisuke-san- Thank you for this great work! I can see a lot of potential applications = for it. I set up a test machine and got as far as booting the FreeBSD = 10-CURRENT kernel from an istgt LUN, but it failed to find the root = device--the isboot.ko module loaded fine but the iBFT handoff didn't = happen so the network was not configured early enough. This machine has = an sk(4) NIC, and I am chain-loading gPXE using the "undionly.kpxe" = image. I have a few questions for you (or other knowledgeable people on the = list): 1) Does iBFT require hardware support in the NIC? 2) Does iBFT require NIC driver support? 3) Is anything required in loader.conf besides = isboot_load=3D"YES"? 3) How hard would it be to get this working with sk(4)? 4) Is it likely to work (better) if I find an em(4) card = instead? Thanks, JN