From: peter meng <mengsanshui@yahoo.com.cn>
To: linux-mtd@lists.infradead.org
Subject: Question relates 2K page size flash chip
Date: Sat, 3 Jan 2009 17:15:23 +0800 (CST) [thread overview]
Message-ID: <448671.97417.qm@web15703.mail.cnb.yahoo.com> (raw)
Hi
I met a problem that use K9F1G08 flash with 2K page size on Linux .
I tried jffs2 and yaffs2 file system but occurs same error info as following
----------------------------------------------------------
NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB 1,8V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
nand_read_oob: from = 0x00000000, len = 64
Bad eraseblock 0 at 0x00000000
nand_read_oob: from = 0x00020000, len = 64
Bad eraseblock 0 at 0x00020000
........
........
nand_isbad_bbt(): bbt info for offs 0x007a0000: (block 61) 0x03
block 46 is bad
nand_isbad_bbt(): bbt info for offs 0x007c0000: (block 62) 0x03
block 47 is bad
nand_isbad_bbt(): bbt info for offs 0x007e0000: (block 63) 0x03
block 48 is bad
VFS: Mounted root (yaffs2 filesystem).
Freeing init memory: 88K
Warning: unable to open an initial console.
Failed to execute /linuxrc. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
------------------------------------------------------------
I checked the /dev/console and /linuxrc is exist on rootfs .
Seems this problem is caused since 2K page size with flash ,so how to resolve this problem ? Whether need do related work within u-boot because I suppose u-boot given wrong data format to flash that Linux mtd does not know it ?
Thanks Advanced .
Best Regards.
Peter Meng
next reply other threads:[~2009-01-03 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 9:15 peter meng [this message]
2009-01-05 7:52 ` Question relates 2K page size flash chip Ricard Wanderlof
2009-01-07 2:47 ` peter meng
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=448671.97417.qm@web15703.mail.cnb.yahoo.com \
--to=mengsanshui@yahoo.com.cn \
--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