From owner-freebsd-arm@FreeBSD.ORG Mon Jul 8 05:43:50 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 526A552A for ; Mon, 8 Jul 2013 05:43:50 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id E9942191F for ; Mon, 8 Jul 2013 05:43:49 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.65]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Uw4EV-0004aY-1y; Sun, 07 Jul 2013 22:43:36 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: NFS root on BeagleBone Black From: Oleksandr Tymoshenko In-Reply-To: <0D94186F-F592-44C4-9F76-9E4B4B487468@ieee.org> Date: Sun, 7 Jul 2013 22:43:12 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0D94186F-F592-44C4-9F76-9E4B4B487468@ieee.org> To: Douglas Beattie X-Mailer: Apple Mail (2.1503) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2013-07-07, at 10:06 PM, Douglas Beattie wrote: > Working with the BeagleBone Black, I'm hoping to achieve boot to NFS root. > Thinking I'm fairly far along, I'm stuck with an 'error 19' at the final steps of > booting the kernel. Here's a little background -- any hints would be appreciated. > > On FreeBSD 9.1, I have a TFTP server, plus an NFS export on the same folder; > here are a few snippets from the console, which confirm this. > > [bsd03: /root/oss/crochet-freebsd]# tail -n2 /etc/inetd.conf > tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /opt/tftpboot > tftp dgram udp6 wait root /usr/libexec/tftpd tftpd -l -s /opt/tftpboot > [bsd03: /root/oss/crochet-freebsd]# cat /etc/exports > /opt/tftpboot -maproot=0 -alldirs -network 192.168.0.0 -mask 255.255.255.0 > [bsd03: /root/oss/crochet-freebsd]# showmount -e > Exports list on localhost: > /opt/tftpboot 192.168.0.0 > > I have built (using the excellent crochet facility) and can boot FreeBSD from > the microSD card, and I have verified that I can NFS mount the exported folder. > > Then, I created a custom kernel configuration, BEAGLEBONENFSROOT, with > just a couple changes, as follows: > > options NFS_ROOT #NFS usable as /, requires NFSCL > options ROOTDEVNAME=\"nfs:192.168.0.198:/opt/tftpboot/beaglebone\" > > And, then I built the kernel from the command line, with DESTDIR into my target > folder for NFS root, doing all the make targets in turn; buildworld, buildkernel, > installkernel, installworld, distrib-dirs, distribution ... [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: ieee.org] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2013 05:43:50 -0000 On 2013-07-07, at 10:06 PM, Douglas Beattie wrote: > Working with the BeagleBone Black, I'm hoping to achieve boot to NFS = root. > Thinking I'm fairly far along, I'm stuck with an 'error 19' at the = final steps of > booting the kernel. Here's a little background -- any hints would be = appreciated. >=20 > On FreeBSD 9.1, I have a TFTP server, plus an NFS export on the same = folder; > here are a few snippets from the console, which confirm this. >=20 > [bsd03: /root/oss/crochet-freebsd]# tail -n2 /etc/inetd.conf=20 > tftp dgram udp wait root /usr/libexec/tftpd tftpd = -l -s /opt/tftpboot > tftp dgram udp6 wait root /usr/libexec/tftpd tftpd = -l -s /opt/tftpboot > [bsd03: /root/oss/crochet-freebsd]# cat /etc/exports > /opt/tftpboot -maproot=3D0 -alldirs -network 192.168.0.0 -mask = 255.255.255.0 > [bsd03: /root/oss/crochet-freebsd]# showmount -e > Exports list on localhost: > /opt/tftpboot 192.168.0.0=20 >=20 > I have built (using the excellent crochet facility) and can boot = FreeBSD from > the microSD card, and I have verified that I can NFS mount the = exported folder. >=20 > Then, I created a custom kernel configuration, BEAGLEBONENFSROOT, with > just a couple changes, as follows: >=20 > options NFS_ROOT #NFS usable as /, requires = NFSCL > options = ROOTDEVNAME=3D\"nfs:192.168.0.198:/opt/tftpboot/beaglebone\" >=20 > And, then I built the kernel from the command line, with DESTDIR into = my target > folder for NFS root, doing all the make targets in turn; buildworld, = buildkernel, > installkernel, installworld, distrib-dirs, distribution ... I'm not 100% sure but it might be NFS version mismatch. AFAIR we have now both NFSv3 and NFSv4 in kernel. NFSv3 prefix is oldnfs, NFSv4 prefix = is nfs (or is it newnfs too?). NFSv3 is enabled by NFSCLIENT. Make sure you = server NFS and client NFS versions are synced.=20