From: Artem Bityutskiy <dedekind@infradead.org>
To: axel.lin@mitac-mtc.com.tw
Cc: linux-mtd@lists.infradead.org
Subject: Re: Failed to mount jffs2 on mtd device
Date: Mon, 05 Feb 2007 10:45:22 +0200 [thread overview]
Message-ID: <1170665122.3628.80.camel@sauron> (raw)
In-Reply-To: <427d64720702041910o2cc7c5d2q32e467be6a1ae5fd@mail.gmail.com>
On Mon, 2007-02-05 at 11:10 +0800, axel lin wrote:
> Uncompressing Linux.........................................................................................................
> done, booting the kernel.
> Linux version 2.6.14-intc1 (axel@kdc.example.com) (gcc version 3.4.3)
Quite old kernel...
> Relocation table recognized, totally 57 block relocated
> Block 0x1 relocate to Block 0x:3ff
> Block 0x2 relocate to Block 0x:3fe
Hmm, interesting, what is this relocation table? You relocate bad
blocks?
> jffs2_check_nand_cleanmarker(): Cleanmarker node not detected in block
> at 00000000
> OOB at 00000000 was ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e3 6b a8 ad 4f 0f fd 21 3f 2a 9d 0a dc 89 e5 88 9d 06 0d a3 70 c3 28
> 0c
Something unknown in OOB instead of a clean marker - JFFS2 yells but it
is harmless. How do you flash your image on the device?
> JFFS2: Erase block at 0x00fe0000 is not formatted. It will be erased
> VFS: Mounted root (jffs2 filesystem).
So you mounted it, everything is OK.
> nand_erase: Device is write protected!!!
> Erase at 0x008c0000 failed immediately: errno -5
This is your problem. Realize why your device is read-only. I guess this
relocation stuff is something simple and RO.
You seems to have standard flash but use some strange drivers which make
it RO. I am not sure, just guess. If so, use standard drivers and be
happy!
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-02-05 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 3:10 Failed to mount jffs2 on mtd device axel lin
2007-02-05 3:35 ` Jagota Rakesh
2007-02-05 8:45 ` Artem Bityutskiy [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=1170665122.3628.80.camel@sauron \
--to=dedekind@infradead.org \
--cc=axel.lin@mitac-mtc.com.tw \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox