From: Woody Wu <narkewoody@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ubifs rootfs attached error
Date: Tue, 13 Aug 2013 22:08:40 +0800 [thread overview]
Message-ID: <20130813140840.GA5063@zuhnb712> (raw)
In-Reply-To: <520A36FB.80403@gmail.com>
On Tue, Aug 13, 2013 at 03:39:07PM +0200, Stefan Peter wrote:
> Dear Woody Wu,
>
> On 13.08.2013 15:04, Woody Wu wrote:
> > Hi,
> ...
> > Firstly, below are the kernel error messages:
> >
> > ------------------------------------------------------------------
> > NAND_ECC_NONE selected by board driver. This is not recommended !!
>
> Modern flash chips actually rely on specific forms of cyclic redundancy
> checks in order to be able to correct for bit errors in NAND flash.
> Without using the proper CRC algorithm, you can never be sure to be able
> to read from the flash what you have written to it. Another hint at this
> problem are the "Bad eraseblock" messages that follow.
>
> Check your kernel configuration and the documentation of your target for
> the proper ECC settings for the NAND flash.
Stefan, thanks for the hints. Yes, my kernel configuration disalbed the
NAND ECC. I like to study on that. But, do you think this is reason why
my ubifs did not get attached? Thanks.
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
I can't go back to yesterday - because I was a different person then
next prev parent reply other threads:[~2013-08-13 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:04 [Buildroot] ubifs rootfs attached error Woody Wu
2013-08-13 13:39 ` Stefan Peter
2013-08-13 14:08 ` Woody Wu [this message]
2013-08-13 18:21 ` Stefan Peter
2013-08-13 22:12 ` Woody Wu
2013-08-13 16:44 ` Arnout Vandecappelle
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=20130813140840.GA5063@zuhnb712 \
--to=narkewoody@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox