All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Dan Wilson <dwilson@dslextreme.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ram-disk root file system
Date: Wed, 17 Jan 2007 02:54:02 -0500	[thread overview]
Message-ID: <45ADD61A.7020005@dlasys.net> (raw)
In-Reply-To: <200701162102050578.1213ACC0@smtp.dslextreme.com>

Dan Wilson wrote:
> We are attempting to use an initrd ram-disk as the permanent root file system for a MPC8541-based system.
>
> We are using ELDK 4 to cross-compile, and are running linux 2.6.15 kernel, with u-boot 1.1.6 as our bootloader.
>
> I built an initrd file system, compressed it, then ran mkimage against it, and it seems to be successfully loaded by u-boot, and linux sees the initrd file and claims to have mounted it.  However, it then reports that it is unable to find any files on the mounted root file system, as shown in the log below.  I added some additional diagnostics to show what the error codes were, and what was happening, but do not understand what I might have done wrong.  If I boot linux from an NFS system or from compact flash, I am able to mount the image and see all the files, so I believe the initrd file system was created correctly.
    I had similar problems with a permanent initramfs filesystem. It is
possible your problem has nothing to do with your filesystem.

    First, I presume the debugging you added was in init/main.c.
          Before you attempt to exec init, you can add code to open
anyfile that you want on the ramdisk. opening a file requires less
things to be right than exec'ing and that may isolate your problem
further. I beleive you can enable system call tracing and find out more
about where things are going off the rails.
          You can also write a trivial hello world - one that does not
use any libraries and very little code, and see if you can exec that.

    When you boot Linux NFS - are you using the same linux kernel ?
         
   


-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

  reply	other threads:[~2007-01-17  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  5:02 ram-disk root file system Dan Wilson
2007-01-17  7:54 ` David H. Lynch Jr. [this message]
2007-01-18  2:22   ` Dan Wilson
  -- strict thread matches above, loose matches on Subject: below --
2007-01-17 22:57 dwilson

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=45ADD61A.7020005@dlasys.net \
    --to=dhlii@dlasys.net \
    --cc=dwilson@dslextreme.com \
    --cc=linuxppc-embedded@ozlabs.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 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.