From: cjjoy1980 <cjjoy1980@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NFS TFTP problem
Date: Tue, 5 Aug 2008 19:24:41 -0700 (PDT) [thread overview]
Message-ID: <18843233.post@talk.nabble.com> (raw)
I have enabled nfs booting on ppc based embedded board. I had placed my
kernel and rootfs in tftp directory, and had set the u-boot enivironment
varialbes as:
setenv bootfile /image/kernel
setenv root_path /tftpboot/image
The board was booting with this configuration...
Now I have placed the kernel image and rootfs in /exports directory and have
set the uboot variables as:
setenv bootfile /exports/image/kernel
setenv root_path /exports/image
I am not able to boot the board with the above directory. I am getting the
error
Loading: T
TFTP error: 'File not found' (1)
Starting again.
TFTP by default looks for /tftpboot directory.. How can we make the server
to fetch files apart from the default one??
--
View this message in context: http://www.nabble.com/NFS-TFTP-problem-tp18843233p18843233.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2008-08-06 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 2:24 cjjoy1980 [this message]
2008-08-06 4:22 ` [U-Boot-Users] NFS TFTP problem Ben Warren
2008-08-06 6:33 ` Hebbar
2008-08-06 11:31 ` Jerry Van Baren
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=18843233.post@talk.nabble.com \
--to=cjjoy1980@gmail.com \
--cc=u-boot@lists.denx.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