From owner-freebsd-current@FreeBSD.ORG  Tue Jun 24 08:23:07 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3AE28C55
 for <freebsd-current@freebsd.org>; Tue, 24 Jun 2014 08:23:07 +0000 (UTC)
Received: from sam.nabble.com (sam.nabble.com [216.139.236.26])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1B9D82CF9
 for <freebsd-current@freebsd.org>; Tue, 24 Jun 2014 08:23:06 +0000 (UTC)
Received: from [192.168.236.26] (helo=sam.nabble.com)
 by sam.nabble.com with esmtp (Exim 4.72)
 (envelope-from <zaphod@berentweb.com>) id 1WzM0Q-0007KF-BX
 for freebsd-current@freebsd.org; Tue, 24 Jun 2014 01:23:06 -0700
Date: Tue, 24 Jun 2014 01:23:06 -0700 (PDT)
From: Beeblebrox <zaphod@berentweb.com>
To: freebsd-current@freebsd.org
Message-ID: <1403598186351-5923355.post@n5.nabble.com>
In-Reply-To: <2166664.2993364.1403565293261.JavaMail.root@uoguelph.ca>
References: <1402410667736-5919662.post@n5.nabble.com>
 <CAG=rPVciV=S8cJ67mF1qbG1yMJH_JnTCxyfSWEL-0YN2DGPTiQ@mail.gmail.com>
 <20140623202829.072ee954@rsbsd.rsb>
 <2166664.2993364.1403565293261.JavaMail.root@uoguelph.ca>
Subject: Re: Previously working PXE setup now fails
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 08:23:07 -0000

Hi and thanks for your input. If I may, I have several more Q's regarding
this issue:

> As I think I've mentioned before, a NFSv4 root fs won't work, so don't
> bother trying...
Q1: I did not realise that. I took out the "V4: " in exports. However, is it
possible to have a mixed-mode, something like /data/amd64 as V3 but /home as
V4?

Q2: I now get to the BTX loader, wireshark shows correct mount call
"192.168.2.3, 192.168.2.1, MOUNT, V3 MNT Call (Reply In 14072) /data/amd64".
Unfortunately, I get a complete black screen when I hit <enter> from BTX (it
looks like a lock-up) and wireshark shows no traffic for the problem.

To get to this point, I re-anabled some of what I had taken out before, and
I now forget which config options are necessary at this point. What I have:
(always had this) fstab: 192.168.2.1:/data/amd64  /  nfs  ro 0 0

boot/loader.conf:
boot.nfsroot.server="192.168.2.1"
boot.nfsroot.path="/data/amd64"
##_re-enabled_##
vfs.root.mountfrom="nfs:192.168.2.1:/data/amd64"
vfs.root.mountfrom="nfs"
boot.nfsroot.options="nolockd"
vfs.root.mountfrom.options="ro"

re-enabled in dhcpd.conf
option root-path "192.168.2.1:/data/amd64"; 

I can't figure out what needs to be modified and what options can be
removed?

Thanks for your help.



-----
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Previously-working-PXE-setup-now-fails-tp5919662p5923355.html
Sent from the freebsd-current mailing list archive at Nabble.com.