From: Sascha Hauer <s.hauer@pengutronix.de>
To: Nataraj S Narayan <natarajsn@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: ubifs: u-boot vs barebox
Date: Tue, 23 Aug 2011 08:29:12 +0200 [thread overview]
Message-ID: <20110823062912.GD31404@pengutronix.de> (raw)
In-Reply-To: <CAK8HZO+gSazgxyNQ1eDCWXEg820mXTZwdAZ7CricBN4SjDkj_A@mail.gmail.com>
On Tue, Aug 23, 2011 at 06:06:37AM +0000, Nataraj S Narayan wrote:
> Hi Sascha
>
> I am able to boot a ubifs filesystem in barebox, after writing the
> file system in u-boot. But the reverse doesn't work.
>
> After a
>
> ubiattach /dev/nand0.data;
> ubimkvol /dev/ubi0 data 0
> tftp rootfs.ubifs.nat /dev/ubi0.data
>
> in barebox, I replaced barebox with u-boot, keeping the same kernel
> and FS, which of course didn't boot giving me:-
>
> corrupted PEBs are: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
> 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 43
> UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:data", error -19
I really suspect your nand driver is broken. Sorry, I have no idea what
is going wrong here, but the ubi code is derived from the kernel, I
don't expect these kinds of bugs here.
You should first make sure that you have a working kernel. You have ubi
errors there aswell, right? I would expect that the kernel driver and
ubi layer is in better shape, also the audience will be bigger if
something is going wrong in the kernel.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-08-23 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 6:06 Nataraj S Narayan
2011-08-23 6:29 ` Sascha Hauer [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=20110823062912.GD31404@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=natarajsn@gmail.com \
/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