mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: NFS boot - could not open /.tftp_tmp_path
Date: Fri, 10 Aug 2018 08:08:04 +0200	[thread overview]
Message-ID: <20180810060804.GA11096@ravnborg.org> (raw)
In-Reply-To: <6ry3dfhgb0.fsf@pengutronix.de>

Hi Ulrich.
> > Hi Ulrich
> >> > Then when I try to boot from nfs I get the following output:
> >> >
> >> > barebox: boot nfs://192.168.86.201/nfsboot/arm9/
> >> 
> >> you already have the slash separating the host part of the URL and the
> >> path part, but you missed the slash that is needed at the beginning of
> >> the absolute path:
> >> 
> >>   boot nfs://192.168.86.201//nfsboot/arm9/
> >> 
> >> (with a two slashes) should hopefully do the trick.
> >
> > Hmm, no luck:
> > barebox:/ boot nfs://192.168.86.201//nfsboot/arm9/
> > eth0: DHCP client bound to address 192.168.86.20
> > T T T T T T T T T T T T T T could not open /.tftp_tmp_path/zImage-at91sam9263ekt
> >
> > barebox:/ boot nfs://192.168.86.201//nfsboot/arm9
> > eth0: DHCP client bound to address 192.168.86.20
> > T T T T T T T T T T T T T T could not open /.tftp_tmp_path/zImage-at91sam9263ekt
> >
> > I will try to add some debugging and see whats going on.
> 
> Do you see anything of interest in the server's log?


I got it working, using a slighly different approach.

I now have:

barebox: cat /env/init/automount
#!/bin/sh

mkdir -p /mnt/nfs
automount -d /mnt/nfs 'ifup -a && mount -t nfs 192.168.86.201:/nfsboot/arm9 /mnt/nfs'

barebox: cat /env/boot/nfs
#!/bin/sh

nfsdir="/mnt/nfs"

global.bootm.image="${nfsdir}/boot/zImage"

nfsroot="192.168.86.201:/nfsboot/arm9"

global.linux.bootargs.base="rw rootwait init=/usr/bin/system-init.sh"
global.linux.bootargs.dyn.root="root=/dev/nfs nfsroot=${nfsroot},v3,tcp"


Then I can nfsboot my kernel using "boot nfs"

The solution has my NFS server IP IP hardcoded as the NFS server IP
is not the same as the DHCP IP, so no way to find it automagically.

In the linux kernel I also selected NFS + NFS boot to make it work.

With the above I have something that do what I need - good!

Thanks for the help/hints.

	Sam

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-08-10  6:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09  9:51 Sam Ravnborg
2018-08-09 11:07 ` Ulrich Ölmann
2018-08-09 11:14   ` Sam Ravnborg
2018-08-09 12:31     ` Ulrich Ölmann
2018-08-10  6:08       ` Sam Ravnborg [this message]
2018-08-10  6:26         ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180810060804.GA11096@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=u.oelmann@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox