Date: Sun, 7 Jul 2013 22:49:08 -0700 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Douglas Beattie <beattidp@ieee.org> Cc: freebsd-arm@freebsd.org Subject: Re: NFS root on BeagleBone Black Message-ID: <7E3BAAE7-45FD-428F-9AAA-5C2E2E51D6DA@bluezbox.com> In-Reply-To: <DC8D950E-B664-49F7-804E-3F461F15D19C@bluezbox.com> References: <0D94186F-F592-44C4-9F76-9E4B4B487468@ieee.org> <DC8D950E-B664-49F7-804E-3F461F15D19C@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-07-07, at 10:43 PM, Oleksandr Tymoshenko <gonzo@bluezbox.com> = wrote: >=20 > On 2013-07-07, at 10:06 PM, Douglas Beattie <beattidp@ieee.org> wrote: >=20 .. skipped... > 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 FWIW here is my kernel config for NFS root (my NFS server is -CURRENT): # NFS support options NFSCL options NFSLOCKD # Uncomment this for NFS root options NFS_ROOT #NFS usable as /, requires NFSCL options BOOTP_NFSROOT options BOOTP_COMPAT options BOOTP options BOOTP_NFSV3 options BOOTP_WIRED_TO=3Dcpsw0=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7E3BAAE7-45FD-428F-9AAA-5C2E2E51D6DA>