All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Osdoba <marcus.osdoba@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] rootfs.ubifs not able to mount by kernel
Date: Mon, 31 Jan 2011 22:18:33 +0100	[thread overview]
Message-ID: <4D472729.7000501@googlemail.com> (raw)
In-Reply-To: <20110130152021.4073fd79@surf>

Am 30.01.2011 15:20, schrieb Thomas Petazzoni:
> Hello Marcus,
>
> On Sun, 30 Jan 2011 11:30:54 +0100
> Marcus Osdoba<marcus.osdoba@googlemail.com>  wrote:
>
>> Writing a ubiFS on NAND (with RAW u-boot command) and mounting
>> afterwards is not possible. The produced ubiFS must be ubinized to a UBI
>> image.
>
> Correct. But Nataraj did create the UBI volume with U-Boot, and has
> written the UBIFS image inside this UBI volume.
True. I should have read the entire output ;-)
But what I miss is the name of the volume inside the ubiparition. 
Nataraj gave root=ubi0:rootfs on the command line. In my example project 
I set this parameter in ubinize.cfg. But the manual way with u-boot like 
Nataraj did, doesn't show a setting like:
"An ubi-volume named rootfs resides on an mtdpart named data."
I ubinized the image outside u-boot and my kernel accepts the 
root=ubi0:rootfs. As noticed, I hardly see a volume_name definition 
"rootfs" in Nataraj's u-boot log....

May be that's the problem? A mixup of the label "data" for mtdpart name 
and ubi volume name?
"U-Boot> ubi create data" should be
"U-Boot> ubi create rootfs" or "root=ubi0:data"
Without warranty ... but @Nataraj, could you try on of the above?

> Note that since recently, Buildroot is capable of generating a
> ubinize'd UBI filesystem image, thanks to the work done by Julien
> Boibessot from Armadeus. This is available in Buildroot git, and will
> be part of the next Buildroot release.
Good news.

      reply	other threads:[~2011-01-31 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  8:45 [Buildroot] rootfs.ubifs not able to mount by kernel nataraj at vaaraahi.com
2011-01-30 10:30 ` Marcus Osdoba
2011-01-30 14:20   ` Thomas Petazzoni
2011-01-31 21:18     ` Marcus Osdoba [this message]

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=4D472729.7000501@googlemail.com \
    --to=marcus.osdoba@googlemail.com \
    --cc=buildroot@busybox.net \
    /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.