NFS booting Failed

Hello friends,

            I tried to boot (Mini6410) via NFS... The following error
occurs how can i resolve this problem..


***************************************************************************
ALSA device list:
  #0: MINI6410
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
s3c-rtc s3c64xx-rtc: setting system clock to 2000-02-24 04:56:30 UTC
(951368190)

Freeing init memory: 1408K
mount: RPC: Remote system error - Network is unreachable
1Wire touchscreen OK
/init: line 103: can't open /r/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
[<c0177c44>] (unwind_backtrace+0x0/0xe4) from [<c0514828>]
(panic+0x58/0x174)
[<c0514828>] (panic+0x58/0x174) from [<c0189e48>] (do_exit+0x68/0x5e4)
[<c0189e48>] (do_exit+0x68/0x5e4) from [<c018a688>]
(do_group_exit+0x90/0xc4)
[<c018a688>] (do_group_exit+0x90/0xc4) from [<c018a6cc>]
(sys_exit_group+0x10/0x
18)
one_wire_status: 2
[<c018a6cc>] (sys_exit_group+0x10/0x18) from [<c01725e0>]
(ret_fast_syscall+0x0/
0x30)
one_wire_status: 4


***************************************************************************


Thanks in advance..

I would suggest going to:
http://www.oselas.org/oselas/bsp/pengutronix/mini2440_bsp_en.html
and grabbing a copy of the:
OSELAS.BSP-Pengutronix-Mini2440-Quickstart.pdf 

There is a good explanation of setting up NFS that might provide some clues
to why you are getting:

Remote system error - Network is unreachable

Good luck!

I would like to develop an application with camera and ethernet....

Is it possible to develop an application in qtopia with out NFS boot 

but i can able to mount/access the shared NFS folder

Is it possible to develop an application in Qtopia without using NFS
(network file system).

Don't know why the word <boot> is in the same sentence.

Sure, it is possible.

But, then I don't understand your last sentence.  You can copy files onto
the mini2440 using tftp or ftp or SDcard or USB flashdrive or NFS.

NFS is only for your root filesystem.  The kernel could be loaded by tftp
or USB.  NFS allows you to make changes to your application on the host and
have them running instantly on the target.

Maybe, things are different is some aspects on the mini6410, sorry I have
no hands-on experience.

Somebody else please chip in.

Hi

Dave is correct. I use it on the Mini6410. 

Use tftp to boot the kernel and nfs for rootfs. Great for development.

Make sure you get the host set up correctly with permissions to directories
and firewall settings done correctly for nfs! Looks as if the tftp part is
working.

Sean

Its quit difficult for me to understand your technical speech...

Because I am new to Linux as well as arm11 


I have installed linux via usb by using the manual dated on 16-04-11

and i share the root folder successfully from the server and mount it in
Clint(Mini6410) 

I tried to boot via nfs by setting the boot parameter command

************************************************************************

console=ttySAC0 root=/dev/nfs
nfsroot=192.168.0.84:/opt/FriendlyARM/mini6410/linux/root_qtopia_qt4 
ip=192.168.0.72:192.168.0.84:192.168.0.1:255.255.255.0:mini6410.arm9.net:eth0:of
f

************************************************************************





but i got this error


*************************************************************************

eth0: link down
IP-Config: Complete:
     device=eth0, addr=192.168.0.72, mask=255.255.255.0, gw=192.168.0.1,
     host=mini, domain=, nis-domain=(none),
     bootserver=192.168.0.84, rootserver=192.168.0.84, rootpath=
Freeing init memory: 1408K
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
mount: RPC: Remote system error - No route to host
1Wire touchscreen OK
/init: line 103: can't open /r/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
[<c0177c44>] (unwind_backtrace+0x0/0xe4) from [<c0514828>]
(panic+0x58/0x174)
[<c0514828>] (panic+0x58/0x174) from [<c0189e48>] (do_exit+0x68/0x5e4)
[<c0189e48>] (do_exit+0x68/0x5e4) from [<c018a688>]
(do_group_exit+0x90/0xc4)
[<c018a688>] (do_group_exit+0x90/0xc4) from [<c018a6cc>]
(sys_exit_group+0x10/0x
18)
one_wire_status: 2
[<c018a6cc>] (sys_exit_group+0x10/0x18) from [<c01725e0>]
(ret_fast_syscall+0x0/
0x30)
one_wire_status: 4

************************************************************************




could you please help me to resolve this problem

I only way I can help is for you to follow some procedure that I am
familiar with, ie the link I posted and make sure that you have set your
host up correctly and then to look at your error messages.

For example, there are some hints in that procedure about looking at
/var/log/syslog on your host to gain insight into where the problem might
be.

Section 8.2 NFS with PTXdist and Barebox

What does your NFS server at your host reports, when your target tries to
connect it?

k. i will try it ...

Tanks u davef

No reports from nfs server...  Mr.Juergen Beisert

Then I guess the message "mount: RPC: Remote system error - No route to
host" from your kernel means your target is not able to contact your host.
Firewall?

Hi

For a Fedora distribution.

On the server (host pc) you need to install: mountd, nfsd, and portmapper
=> done by installing nfs-utils

A configuration file will exist at /etc/exports or /etc/exports.d in later
versions. 

Do a man exports on the host to understand how to set permissions in
configuration file to directories you want to give access to and the
associated and security risks. You are going to give permission to the 
directory you want to access from the target. 

You need to look at the security settings on your firewall on the host.
Initially disconnect from the internet, only have ethernet cable between pc
and target, and disable the firewall to test.

On target:

busybox mount -t nfs host.ip.address:/home/../your_directory_on_host  /mnt

ls -la /mnt  ( and enjoy the linux magic )

Hope this helps

Read the following:

http://www.3open.org/d/oe/use_rootfs_on_nfs

If your host system has enabled SELinux try disabling it. Google for the
appropriate way for your system to disable it. Later on if it works you can
edit permissions allow NFS passing the SELinux policies. F. e. on Fedora
you have no chance with default SELinux configuration.

Tank u all for your valuable comment....




Mr.sean_h 

I have no problem up to this command 

ls /mnt  - it executes successfully 

When i try to boot via nfs an error occurs as per my previous post..

That indicates that your rootfs is broken or your boot parameters are
incorrect.

what does the folder rootfs contains....

Because when i install all packages 

i execute 

logomaker 

error:

error while loading shred libraries: libjpeg.so.62: cannot open shared
object file: no such file or directiory

why this error occured...?

could u plz resolve it?

I suggest you read the book: Building Embedded Linux Systems by Yaghmour,
Masters, Ben-Yossef and Gerum.

The rootfs typically follows the Filesystems Hierarchy Standard (FHS) and
would have the directories: /home /bin /lib /sbin etc etc. i.e. the same as
 you would see on your host if you did a: ls -la / 

You should not be installing anything. 

The last action of the kernel is to start the init program before handing
over to user space. If this fails you will get "kernel panic". You should
get a login prompt or a user application should be running ( not likely in
your case ) on completion of the init process. 

You should have extracted a rootfs for your embedded platform on the host,
or built one with a cross compiler, at the directory you decided to share
on the host, via NFS, such as /mnt/rootfs.

Stay away from / and treat "root" user with respect on the host.  

Good luck.

Thank u all 



Now i can able to boot via nfs...

What is next step to develop the application int qtopia 2.2....?

Thank in advance...

It would be nice if you report to others what your problem was, how did you
solve it or why you now can work with NFS root.

Use direct link of Ethernet cable from pc to target board... 
It'll work fine...