[U-Boot] NFS boot problems !

[U-Boot] NFS boot problems !

[Cristian Axenie]

Hi all !

I try to boot the kernel and rootfs using NFS!
Next is my u-boot env:

nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp
$fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
bootdelay=6
baudrate=115200
loads_echo=1
ethaddr=04:00:00:00:00:0A
eth1addr=04:00:00:00:00:0B
netdev=eth0
consoledev=ttyS0
fdtaddr=400000
ethact=eTSEC0
fdtfile=mpc8315erdb_default.dtb
ramdiskfile=rootfs.ext2.gz.uboot
ipaddr=192.168.1.100
othbootargs=ramdisk_size=65535
loadaddr=1000000
ramdiskaddr=2000000
sataboot=setenv bootargs root=/dev/sda1 rw console=ttyS0,115200;bootm
fe500000 - fe700000
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate
$othbootargs;bootm fe500000 fe100000 fe700000
mtdids=nor0=nor,nand0=nand
usbstick=run usbstick_args;bootm fe500000 - fe700000
usbstick_args=setenv bootargs root=/dev/sda1 ro rootdelay=5 rootfstype=ext2
init=/sbin/init console=ttyS0,115200
serverip=192.168.1.103
rootpath=/home/haustiq/development/rootfs
gatewayip=192.168.1.103
netmask=255.255.0.0
macaddr=04000000000A
hostname=haustiq
bootcmd=run nfsboot
stdin=serial
stdout=serial
stderr=serial
bootfile=/home/haustiq/development/uImage

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'.
Load address: 0x1000000
Loading: *
TFTP error: 'Access violation' (2)
Starting again

Any ideas ?

Changing file permissions on the server side shared files didn't helped !

Best !

[U-Boot] NFS boot problems !

[Cristian Axenie]

Hi all !

I try to boot the kernel and rootfs using NFS!
Next is my u-boot env:

nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp
$fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
bootdelay=6
baudrate=115200
loads_echo=1
ethaddr=04:00:00:00:00:0A
eth1addr=04:00:00:00:00:0B
netdev=eth0
consoledev=ttyS0
fdtaddr=400000
ethact=eTSEC0
fdtfile=mpc8315erdb_default.dtb
ramdiskfile=rootfs.ext2.gz.uboot
ipaddr=192.168.1.100
othbootargs=ramdisk_size=65535
loadaddr=1000000
ramdiskaddr=2000000
sataboot=setenv bootargs root=/dev/sda1 rw console=ttyS0,115200;bootm
fe500000 - fe700000
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate
$othbootargs;bootm fe500000 fe100000 fe700000
mtdids=nor0=nor,nand0=nand
usbstick=run usbstick_args;bootm fe500000 - fe700000
usbstick_args=setenv bootargs root=/dev/sda1 ro rootdelay=5 rootfstype=ext2
init=/sbin/init console=ttyS0,115200
serverip=192.168.1.103
rootpath=/home/haustiq/development/rootfs
gatewayip=192.168.1.103
netmask=255.255.0.0
macaddr=04000000000A
hostname=haustiq
bootcmd=run nfsboot
stdin=serial
stdout=serial
stderr=serial
bootfile=/home/haustiq/development/uImage

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'.
Load address: 0x1000000
Loading: *
TFTP error: 'Access violation' (2)
Starting again

Any ideas ?

Changing file permissions on the server side shared files didn't helped !

Best !

[U-Boot] NFS boot problems !

[wilbur.chan]

2009/10/24 Cristian Axenie <cristian.axenie@gmail.com>:
> Load address: 0x1000000
> Loading: *
> TFTP error: 'Access violation' (2)

Test this : mw 0x1000000 0x1234

[U-Boot] NFS boot problems !

[Cristian Axenie]

Ok !
And what do you exactly want to test with this, if I can write to the memory
?
The u-boot command returns sucessfully!
no problem with mw !


On Sat, Oct 24, 2009 at 11:57 AM, wilbur.chan <wilbur512@gmail.com> wrote:

> 2009/10/24 Cristian Axenie <cristian.axenie@gmail.com>:
> > Load address: 0x1000000
> > Loading: *
> > TFTP error: 'Access violation' (2)
>
> Test this : mw 0x1000000 0x1234
>

[U-Boot] NFS boot problems !

[Wolfgang Denk]

Dear Cristian Axenie,

In message <9c789a000910240122j776b762dodbddb97a105c942b@mail.gmail.com> you wrote:
>
> I try to boot the kernel and rootfs using NFS!

What exactly has this to do with NFS at all?

> TFTP from server 192.168.1.103; our IP address is 192.168.1.100
> Filename '/home/haustiq/development/uImage'.
> Load address: 0x1000000
> Loading: *
> TFTP error: 'Access violation' (2)

This is a TFTP error message. Not NTS.

> Any ideas ?

Well, check your server configuration. This is not a U-Boot problem.

> Changing file permissions on the server side shared files didn't helped !

You did not manage to change the right permissions, then.  In addition
to file permissions there are directory permissions, and eventually
things like hosts.allow/.deny and/or firewall rules. But the 'Access
violation'  message is pretty clear.

Fix your TFTP server config. 

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"'Tis true, 'tis pity, and pity 'tis 'tis true."
    - Poloniouius, in Willie the Shake's _Hamlet, Prince of Darkness_

[U-Boot] NFS boot problems !

[Jerry Van Baren]

Cristian Axenie wrote:
> Hi all !
> 
> I try to boot the kernel and rootfs using NFS!
> Next is my u-boot env:

[snip]

> bootfile=/home/haustiq/development/uImage

Likely wrong (see below).

> 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.

You probably want to copy your uImage to /tftpboot/uImage and use the 
file name either uImage or /uImage or /tftboot/uImage.

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.

> Load address: 0x1000000
> Loading: *
> TFTP error: 'Access violation' (2)
> Starting again
> 
> Any ideas ?

Wrong path/file.

Good luck,
gvb

[snip]

[U-Boot] NFS boot problems !

[Cristian Axenie]

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

> Cristian Axenie wrote:
>
>> Hi all !
>>
>> I try to boot the kernel and rootfs using NFS!
>> Next is my u-boot env:
>>
>
> [snip]
>
>
>  bootfile=/home/haustiq/development/uImage
>>
>
> Likely wrong (see below).
>
>
>  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 ?


>
> You probably want to copy your uImage to /tftpboot/uImage and use the file
> name either uImage or /uImage or /tftboot/uImage.
>

Yes indeed I copy my kernel image to the specified folder
(home/haustiq/development/) !

>
> 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.
>
>
>  Load address: 0x1000000
>> Loading: *
>> TFTP error: 'Access violation' (2)
>> Starting again
>>
>> Any ideas ?
>>
>
> Wrong path/file.
>
>
 I've also tried the way you mentioned , selected /tftpboot the dedicated
folder, made the appropriate modifications and moved the uImage there... and
the problem persists !


> Good luck,
> gvb
>
>
Thanks for the response !

If further ideas, please post them !

Best !


> [snip]
>

[U-Boot] NFS boot problems !

[Jerry Van Baren]

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

[U-Boot] NFS boot problems !

[Wolfgang Denk]

Dear Cristian Axenie,

In message <9c789a000910240721x1789c1d9n3fefd3abd327e07c@mail.gmail.com> you wrote:
>
> But if I changed the directory to the one mentioned before in the
> /etc/inetd.conf and didn't used /tftpboot ?

In addition to all the excellent advice JvB already gave you just one
more hint: editing /etc/inetd.conf alone is not sufficient; such
changes will only become effective after you restart the inetd server.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
In English, every word can be verbed.  Would that it were  so  in our
programming languages.

[U-Boot] NFS boot problems !

[Cristian Axenie]

On Sat, Oct 24, 2009 at 8:12 PM, Wolfgang Denk <wd@denx.de> wrote:

> Dear Cristian Axenie,
>
> In message <9c789a000910240721x1789c1d9n3fefd3abd327e07c@mail.gmail.com>
> you wrote:
> >
> > But if I changed the directory to the one mentioned before in the
> > /etc/inetd.conf and didn't used /tftpboot ?
>
> In addition to all the excellent advice JvB already gave you just one
> more hint: editing /etc/inetd.conf alone is not sufficient; such
> changes will only become effective after you restart the inetd server.
>

Thank you all for your "minimal latency" response!
I managed to make the proper configs and now I'm booting fine over NFS usign
TFTP!

Best regards !


>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> In English, every word can be verbed.  Would that it were  so  in our
> programming languages.
>