All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gerhard TAEUBL" <Gerhard.TAEUBL@frequentis.com>
To: <linuxppc-embedded@lists.linuxppc.org>,
	<flavio.pereira@za.flextronics.com>
Subject: Re: Cramfs root file system
Date: Thu, 21 Nov 2002 12:20:51 +0100	[thread overview]
Message-ID: <sddccfb6.046@mail.frequentis.com> (raw)


Hi!

First try root=/dev/mtdblock3 rw.

I try a long time ago this with my 'flashdisk' I copied at runtime all needed files, and reload the kernel (I use the comandline as fixcoded string..) and it works. Important is, that the kernel supports your filesystem at boottime! I think it isn't a good idea to use it as module!

Have fun
Gerhard

>>> "Flavio Pereira" <flavio.pereira@za.flextronics.com> 11/21/02 12:09pm >>>

Hi All

Im trying to use a cramfs image as a root-file system at kernel boot
time.

I've built a cramfs image, copied it into my flash device (mtd3), and
can successfully mount it at runtime.

However at boot time I use root=dev/mtdblock3 (or dev/mtd3 im not sure
which one to use) and I get the following errors...

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
request_module[block-major-2]: Root fs not mounted
VFS: Cannot open root device "mtdblock3" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00

Now, is it possible to do what Im trying to do, if so are there any
suggestions as to what I'm doing wrong?

Thanks
Flavio Pereira


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

             reply	other threads:[~2002-11-21 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 11:20 Gerhard TAEUBL [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22  7:25 Cramfs root file system Flavio Pereira
2002-11-21 11:09 Flavio Pereira
2002-11-21 19:17 ` Dennis Khoo

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=sddccfb6.046@mail.frequentis.com \
    --to=gerhard.taeubl@frequentis.com \
    --cc=flavio.pereira@za.flextronics.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 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.