linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jerry Van Baren <vanbaren_gerald@si.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: NFS root woes: No init found
Date: Wed, 04 Dec 2002 17:47:09 -0500	[thread overview]
Message-ID: <5.1.0.14.2.20021204174346.0243ead8@falcon.si.com> (raw)
In-Reply-To: <200212041730.00480.waite@skycomputers.com>


Thoughts...

Does your mount command
* use the defaults options (-o defaults) or equivalent?
   - includes read/write and execute privileges

Does your host
* have "no_root_squash" (may not be necessary)?
* allow write access to the remote host?

gvb


At 05:30 PM 12/4/2002 -0500, Brian Waite wrote:

>I tried loading the ash shell statically linked., along with a dynamically
>linked bash. No executables seem to load. I have traced the execve call and
>it progresses as far as walking the format list to determine what format the
>file is in. After walking all the available formats, it can't find one and
>fails. I have the floowing formats in my kernel:
>CONFIG_KCORE_ELF=y
>CONFIG_BINFMT_ELF=y
>CONFIG_KERNEL_ELF=y
>
>and the ash executale is an elf:
>ash.static: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1,
>statically linked, stripped
>
>Any thoughts? I see the packets getting revieved by the gt64260_eth driver and
>passed up to the higher layers. I also look at the various MIB counters and
>see no errant packets so I can't why NFS is so cranky.
>
>Thanks
>Brian
>
>On Wednesday 04 December 2002 5:20 pm, you wrote:
> > Hello,
> >
> > if you get to the bash prompt you could try to start the init program
> > manually. This should result in more useful error messages.
> >
> > Hope it helps,
> >
> > Wolfgang.
> >
> > On 12/04/2002 11:11 PM Brian Waite wrote:
> > > I did this. I tried to start a staticly linked ash shell to no avail. No
> > > libs are better than any libs :)
> > > Thanks
> > > Brian
> > >
> > > On Wednesday 04 December 2002 4:48 pm, Dan Malek wrote:
> > >> Brian Waite wrote:
> > >> > ...Then I get the message No init found.
> > >>
> > >> First, try using something simple like /bin/bash as your init program.
> > >> Trying to start up the init program relies on lots of things being
> > >> present in the file system.  If the program starts, and then exits,
> > >> you still get this message.
> > >>
> > >> Just use a trivial, simple file system to get started.  A shell,
> > >> couple of commands and minimal libraries are easier to debug.
> > >>
> > >> Good luck :-)
> > >>
> > >>    -- Dan
> > >
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-12-04 22:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 21:35 NFS root woes: No init found Brian Waite
2002-12-04 21:48 ` Dan Malek
2002-12-04 22:11   ` Brian Waite
2002-12-04 22:20     ` Wolfgang Grandegger
2002-12-04 22:30       ` Brian Waite
2002-12-04 22:47         ` Jerry Van Baren [this message]
2002-12-04 23:03           ` Brian Waite
2002-12-04 22:49         ` Roland Dreier
2002-12-04 22:52           ` Brian Waite
2002-12-04 22:27 ` Roland Dreier
2002-12-04 22:36   ` Brian Waite
2002-12-05  8:50     ` Dan Vatca
2002-12-05 15:20       ` Brian Waite
2002-12-05 15:58         ` Allen Curtis
  -- strict thread matches above, loose matches on Subject: below --
2002-12-07  1:36 Pagnotta, Chris
2002-12-07 11:02 ` Wolfgang Denk

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=5.1.0.14.2.20021204174346.0243ead8@falcon.si.com \
    --to=vanbaren_gerald@si.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).