All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NFS boot problems !
Date: Sat, 24 Oct 2009 10:39:02 -0400	[thread overview]
Message-ID: <4AE31186.10102@gmail.com> (raw)
In-Reply-To: <9c789a000910240721x1789c1d9n3fefd3abd327e07c@mail.gmail.com>

Cristian Axenie wrote:
> On Sat, Oct 24, 2009 at 5:09 PM, Jerry Van Baren <gvb.uboot@gmail.com>wrote:
> 
>> Cristian Axenie wrote:
>>
>>> Hi all !

[snip]

>>  My problem is that when I
>>> run bootcmd
>>>
>>> I get :
>>>
>>> Speed: 100, full duplex
>>> Using eTSEC0 device
>>> TFTP from server 192.168.1.103; our IP address is 192.168.1.100
>>> Filename '/home/haustiq/development/uImage'.
>>>
>> This does *NOT* look like a valid path.  TFTP servers typically serve out
>> of a dedicated directory (often /tftpboot) and the paths to the files are
>> usually relative to the root folder.
> 
> But if I changed the directory to the one mentioned before in the
> /etc/inetd.conf and didn't used /tftpboot ?

The TFTP protocol has *NO* security, so changing the root folder to a 
subdirectory your home directory is *NOT* a good practice.

The tftp server very likely doesn't have read permission to read the 
directory you set it to.  Your /home directory is probably not 
world-readable.  Setting it to be world readable is not a good practice. 
  This will probably "fix" your problem, but IS A BAD PRACTICE:
   chmod -R o+r /home/haustiq

You need to configure your tftp server properly.

DO THIS:

>> Do a "tftp get" from a computer, preferably not your tftp server computer,
>> to figure out your TFTP server path and file names before trying to TFTP
>> from u-boot.
>>
>> If you run stuck, use wireshark on your server to see what is going on on
>> the wire.

[snip]

Best regards,
gvb

  reply	other threads:[~2009-10-24 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-24  8:17 [U-Boot] NFS boot problems ! Cristian Axenie
2009-10-24  8:22 ` Cristian Axenie
2009-10-24  9:43   ` Wolfgang Denk
2009-10-24 14:09   ` Jerry Van Baren
     [not found]     ` <9c789a000910240721i3a5ff36aoa08c0e5ee5761070@mail.gmail.com>
2009-10-24 14:21       ` Cristian Axenie
2009-10-24 14:39         ` Jerry Van Baren [this message]
2009-10-24 17:12         ` Wolfgang Denk
2009-10-24 21:08           ` Cristian Axenie
2009-10-24  8:57 ` wilbur.chan
2009-10-24  9:03   ` Cristian Axenie

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=4AE31186.10102@gmail.com \
    --to=gvb.uboot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.