hai,
yes u r right , i try to mount my file system using nfs,
i also cross checked my rootfs that shows that /bin/bash file not
available ..
i dont know how that was missed ..!!!
when i look out my targetNFS directory (which is my actual nfs mount folder)
the following dir's available
*bin dev home media proc sbin sys usr*
*boot etc lib mnt run tmp var*
inside /bin i'm not able to find any executable like *bash.*
*but all the files are compiled for arm arch . *
*i ran *
*targetNFS/bin#file **
*ash: symbolic link to `busyboxbusybox:
ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, strippedcat:
symbolic link to `busybox'chattr:
symbolic link to `busybox'chgrp: symbolic
link to `busybox'chmod: symbolic link to
`busybox'chown: symbolic link to `busybox'*
and so on ..
i compiled the busybox using the following procedure:
*http://balau82.wordpress.com/2010/03/27/busybox-for-arm-on-qemu/*
and i installed the kernel modules into this busybox/_install directory
and i renamed it to *targetNFS to make available for nfs booting .*
was anything wrong with busybox compilation?? . else shall i need to do
some thing more for beaglebone black..
pls share your thoughts how to compile a busybox for beaglebone black.
also suggest me if any books or articles that taught about internals of
kernel architectures and procedure for building a kernel for arm platform
regards
siva
On Thursday, 20 March 2014 07:15:31 UTC+5:30, djerome wrote:
>
> I went back in this email chain and see that you are
> trying an NFS boot. Have you verified that the file
> system you need is at the NFS mount? Where did you get
> that file system? There seems to be a problem, like
> the programs aren't arm programs or the lib directory
> is missing.
>
> I think either /bin/bash really is not at the NFS mount,
> or it is not an arm executable, or something is is wrong
> in <mountpoint>/lib with a missing or wrong format .so
> file.
>
>
> On 03/19/14 10:24, siva kumar wrote:
> > hai all,
> >
> > i already tried with init=/bin/bash and also init=/sbin/init but the my
> > output was the same
> > kernel panic not sync no init found !!!
> >
> > thanks&
> > regards
> > siva
> >
> >
> > On Tuesday, 18 March 2014 06:54:32 UTC+5:30, djerome wrote:
> >
> > Control yourself. Stop doing random things.
> >
> > Put the directories back into the file system. Change to
> > using init=/bin/bash and see if you get a shell prompt
> > when you boot.
> >
> > On 03/17/14 06:05, siva kumar wrote:
> > >
> > > hai,
> > >
> > > i tried to debug the boot process..
> > > i went with some ideas to find the why such error comes..
> > > [1] i tried to boot the kernel with init=/hello_world option.. i
> > removed
> > > all the rootfs files like /dev /usr /opt /bin /sbin folder and
> > files
> > > except hello_world option
> > > ----to make sure that my print is able to execute
> > when
> > > booting was done
> > > but i got different reply from my kernel
> > > error log1
> > > =======
> > > [ 5.800505] VFS: Mounted root (nfs filesystem) on device 0:12.
> > > [ 5.807034] devtmpfs: error mounting -2
> > > [ 5.811496] Freeing init memory: 288K
> > > [* 5.818299] Failed to execute /hello_arm. Attempting
> > defaults...*
> > > [ 5.825859] Kernel panic - not syncing: No init found. Try
> > passing
> > > init= option to kernel. See Linux Documentation/init.txt for
> > guidance.
> > > also i'm not able to get the printed message !!!!
> > > procedure i followed to boot the kernel from my board .i h'v done
> > the
> > > booting with sd card using uEnv.txt file...
> >
> > --
> > For more options, visit http://beagleboard.org/discuss
> > ---
> > You received this message because you are subscribed to the Google
> > Groups "BeagleBoard" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to [email protected] <javascript:>
> > <mailto:[email protected] <javascript:>>.
> > For more options, visit https://groups.google.com/d/optout.
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.