原本这块板子带的系统是2.6.28的内核 ，我现在想升到2.6.32，于是，我下了一个2.6.32的内核，然后解压，
再运行
make smdk6400_defconfig ,
make menuconfig
加入启动参数
root=/dev/mtdblock2 rootfstype=cramfs init=/linuxrc console=ttySSAC0,115200 mem=256M
make
把编好的zimge烧到板子上，出现错误如下：
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
mousedev: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
VFS: Cannot open root device " mtdblock2" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c002f63c>] (unwind_backtrace+0x0/0xf8) from [<c01df4c4>] (panic+0x58/0x19c)
[<c01df4c4>] (panic+0x58/0x19c) from [<c0008e54>] (mount_block_root+0x180/0x2c0
由此可以看出，内核已经可以启动，串口也配置好了，但是还没有识别出mtdblock2分区，这个是还没有加上nand flash的驱动的原因
所以我便把飞凌自带的2.8.28内核里的nand驱动直接复制进去
再把yaffs2文 件系统也加进去了
#make menuconfig
Device Drivers --->
<*> Memory Technology Device (MTD) support --->
MTD partitioning support
<*> NAND Device Support --->
<*> NAND Flash support for S3C/S3C SoC
再把这个选项选上
device drivers ->
Memory Technology Device (MTD) support --->
Caching block device access to MTD devices
把yaffs2文 件系统也选上了
<*> YAFFS2 file system support │ │
│ │ -*- 512 byte / page devices │ │
│ │ [ ] Use older-style on-NAND data format with pageStatus byt│ │
│ │ [ ] Lets Yaffs do its own ECC │ │
│ │ -*- 2048 byte (or larger) / page devices │ │
│ │ [*] Autoselect yaffs2 format │ │
│ │ [ ] Disable YAFFS from doing ECC on tags by default │ │
│ │ [ ] Disable lazy loading │ │
│ │ [*] Turn off wide tnodes │
再把cramfs也选上了
<*> Compressed ROM file system support (cramfs)
编译通过
再把zimage烧进去
*************************************************************************************************************
出现以下别我头痛到现在的问题
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd5 (Samsung NAND 2GiB 3,3V 8-bit)
Creating 4 MTD partitions on "NAND 2GiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "Bootloader"
0x000000040000-0x000000400000 : "Kernel"
0x000000400000-0x000005400000 : "Rootfs"
0x000005400000-0x000080000000 : "User File System"
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Buffer I/O error on device mtdblock2, logical block 3
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[<c0024b7c>] (unwind_backtrace+0x0/0xdc) from [<c01d3010>] (panic+0x40/0x114)
[<c01d3010>] (panic+0x40/0x114) from [<c0008fd0>] (mount_block_root+0x25c/0x2ac)
[<c0008fd0>] (mount_block_root+0x25c/0x2ac) from [<c00091e8>] (prepare_namespace
+0x164/0x1bc)
[<c00091e8>] (prepare_namespace+0x164/0x1bc) from [<c00085c0>] (kernel_init+0xd
下面再分析一下出现这个问题的原因
显示结果表明，已经能够找到31:3这个节点，nand flash 的驱动也已经移植成功（也不知是不是真的成功了），但是出现了unknown-block(31,2)，于是我上网查了，说是文件系统没有加上去，因为我做的根文 件系统是cramfs，但是那个我已经在内核上配置了呀，并且yaffs2文 件系统也加进去了呀，这是为什么呢？
我以为是我做的那个根文件系统文件有问题，所以我重做了一个，并用飞凌自带的内核测试一下完全可以，但是烧进去板子后，结果还是这样。后来上网也查了很多资料
如 http://topic.csdn.net/u/20110216/12/dae77874-593b-40ed-be7f-83e0610b037d.html
http://topic.csdn.net/u/20110216/12/dae77874-593b-40ed-be7f-83e0610b037d.html
其发觉我的操作也是这样呀，怎么他们行，我的就不行呢？
之后我还拿了飞凌别版本的内核2.6.36下的nand flash的驱动搞进去也是这样，后来发狂的把原来2.6.28下的cramfs全部复制到新内核下编进去也是一样什么方法都试过啦，但是就是不行，
各位高手，你们有谁知道我的操作到底错在哪里吗？我感觉该做的我都做了呀！
13 个解决方案
#1
Buffer I/O error on device mtdblock2, logical block 3
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
rootfs有刷进去吗？试试用NFS能不能跑起？
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
rootfs有刷进去吗？试试用NFS能不能跑起？
#2
我觉得这句话是重点
No filesystem could mount root, tried: cramfs
No filesystem could mount root, tried: cramfs
#3
有呀，我的根文件系统是cramfs呀
#4
对于这一点，我也查过很多资料，根据他们的提示来做也不行
http://blog.sciencenet.cn/home.php?mod=space&uid=39626&do=blog&id=332358
大侠有什么好的点子吗？
#5
用开发板自带的kernel和rootfs烧一遍，然后用tftp的方式将自己的内核下载到内存启动，看能不能正常挂载文件系统，看看你现在出的这个问题是文件系统的问题还是内核的问题。
#6
Buffer I/O error on device mtdblock2, logical block 3
这句提示不是你的nandflash有问题，就是你nand驱动有问题，或者是分区有问题。导致mtdblock2读取异常，rootfs自然就加不上。
这句提示不是你的nandflash有问题，就是你nand驱动有问题，或者是分区有问题。导致mtdblock2读取异常，rootfs自然就加不上。
#7
现在我重新烧一遍就变成这样啦
Uncompressing Linux.............................................................
.............................. done, booting the kernel.
Linux version 2.6.32 (root@localhost.localdomain) (gcc version 4.3.2 (Sourcery G
++ Lite 2008q3-72) ) #43 Sat Jan 7 20:10:19 CST 2012
CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: SMDK6410
Memory policy: ECC disabled, Data cache writeback
CPU S3C6410 (id 0x36410101)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C64XX: PLL settings, A=532000000, M=532000000, E=24000000
S3C64XX: HCLK2=266000000, HCLK=133000000, PCLK=66500000
mout_apll: source is fout_apll (1), rate is 532000000
mout_epll: source is fout_epll (1), rate is 24000000
mout_mpll: source is mpll (1), rate is 532000000
mmc_bus: source is mout_epll (0), rate is 24000000
mmc_bus: source is mout_epll (0), rate is 24000000
mmc_bus: source is mout_epll (0), rate is 24000000
usb-bus-host: source is clk_48m (0), rate is 48000000
uclk1: source is dout_mpll (1), rate is 66500000
spi-bus: source is mout_epll (0), rate is 24000000
spi-bus: source is mout_epll (0), rate is 24000000
audio-bus: source is mout_epll (0), rate is 24000000
audio-bus: source is mout_epll (0), rate is 24000000
irda-bus: source is mout_epll (0), rate is 24000000
camera: source is hclk2 (0), rate is 266000000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: root=/dev/mtdblock2 rootfstype=cramfs console=ttySAC0,11520
0
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 256640KB available (2476K code, 353K data, 84K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:246
VIC @f4000000: id 0x00041192, vendor 0x41
VIC @f4010000: id 0x00041192, vendor 0x41
Console: colour dummy device 80x30
console [ttySAC0] enabled
Calibrating delay loop... 530.84 BogoMIPS (lpj=2654208)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
S3C6410: Initialising architecture
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c-i2c s3c2440-i2c.0: slave address 0x10
s3c-i2c s3c2440-i2c.0: bus frequency set to 64 KHz
s3c-i2c s3c2440-i2c.0: i2c-0: S3C I2C adapter
s3c-i2c s3c2440-i2c.1: slave address 0x10
s3c-i2c s3c2440-i2c.1: bus frequency set to 64 KHz
s3c-i2c s3c2440-i2c.1: i2c-1: S3C I2C adapter
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
yaffs Jan 7 2012 17:13:02 Installing.
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
s3c6400-uart.0: s3c2410_serial0 at MMIO 0x7f005000 (irq = 16) is a S3C6400/10
s3c6400-uart.1: s3c2410_serial1 at MMIO 0x7f005400 (irq = 20) is a S3C6400/10
s3c6400-uart.2: s3c2410_serial2 at MMIO 0x7f005800 (irq = 24) is a S3C6400/10
s3c6400-uart.3: s3c2410_serial3 at MMIO 0x7f005c00 (irq = 28) is a S3C6400/10
brd: module loaded
loop: module loaded
at24 0-0050: 1024 byte 24c08 EEPROM (writable)
at24 1-0057: 16384 byte 24c128 EEPROM (writable)
S3C NAND Driver, (c) 2008 Samsung Electronics
S3C NAND Driver is using hardware ECC.
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd5 (Samsung NAND 2GiB 3,3V 8-bit)
Creating 4 MTD partitions on "NAND 2GiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "Bootloader"
0x000000040000-0x000000400000 : "Kernel"
0x000000400000-0x000005400000 : "Rootfs"
0x000005400000-0x000080000000 : "User File System"
usbmon: debugfs is not available
usbcore: registered new interface driver wusb-cbaf
idmouse: 0.6:Siemens ID Mouse FingerTIP Sensor Driver
usbcore: registered new interface driver idmouse
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using PIO
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
mmc0: Minimum clock frequency too high for identification mode
s3c6410_setup_sdhci0_cfg_card: CTRL 2=c0004100, 3=80808080
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[<c0023b50>] (unwind_backtrace+0x0/0xdc) from [<c01b7e40>] (panic+0x40/0x114)
[<c01b7e40>] (panic+0x40/0x114) from [<c0008fd0>] (mount_block_root+0x25c/0x2ac)
[<c0008fd0>] (mount_block_root+0x25c/0x2ac) from [<c00091e8>] (prepare_namespace
+0x164/0x1c8)
[<c00091e8>] (prepare_namespace+0x164/0x1c8) from [<c00085c0>] (kernel_init+0xd8
/0x10c)
[<c00085c0>] (kernel_init+0xd8/0x10c) from [<c001ee04>] (kernel_thread_exit+0x0/
0x8)
#8
现在nand没问题了，No filesystem could mount root, tried: cramfs可能的原因
1，你的cramfs工具有没有问题，支持的是大页还是小页的nand。你板上的nand是大页还是小页这要对应
2，uboot有没有问题，是否支持对 cramfs文件系统的烧写
3，内核对 cramfs的支持有没有问题。
从上面三点 看看能不能找到问题所在
1，你的cramfs工具有没有问题，支持的是大页还是小页的nand。你板上的nand是大页还是小页这要对应
2，uboot有没有问题，是否支持对 cramfs文件系统的烧写
3，内核对 cramfs的支持有没有问题。
从上面三点 看看能不能找到问题所在
#9
那个UBOOT是用的是原来飞凌2.6.28的内核的UBOOT，并且新内核里的分区表也是跟原来内核一样的，所以这点应该没有问题
cramfs 工具应该没有问题，我用这个工具有自己做过cramfs根文件系统，在原来内核下可以正常识别出文件系统。至于这个大页和小页，我只是把原来内核下的nand flash的驱动复制过来，没有改过什么东西，包括分区表，这个应该没有问题吧（不知有没有）
至于内核对cramfs的支持，已经有选择这个编译了呀，还要配置什么吗？
我看过别人移植的日记，感觉他们也只是做了这几个步骤呀？
#10
怎么没有人回答我的问题了，自己顶一下！
#11
终于解决了，我用NFS挂载根文件系统，在终端里把mtdblock2 挂载为yaffs2发现报出一大堆ecc错误，原来是nand flash驱动的移植还有一点问题，解决后,一切都OK啦，困扰了我很久了！
#12
楼主解决方法能不能详细点啊？
#13
遇到同样的问题了，楼主还在么？能不能详细解释一下？
#1
Buffer I/O error on device mtdblock2, logical block 3
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
rootfs有刷进去吗？试试用NFS能不能跑起？
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
rootfs有刷进去吗？试试用NFS能不能跑起？
#2
我觉得这句话是重点
No filesystem could mount root, tried: cramfs
No filesystem could mount root, tried: cramfs
#3
有呀，我的根文件系统是cramfs呀
#4
对于这一点，我也查过很多资料，根据他们的提示来做也不行
http://blog.sciencenet.cn/home.php?mod=space&uid=39626&do=blog&id=332358
大侠有什么好的点子吗？
#5
用开发板自带的kernel和rootfs烧一遍，然后用tftp的方式将自己的内核下载到内存启动，看能不能正常挂载文件系统，看看你现在出的这个问题是文件系统的问题还是内核的问题。
#6
Buffer I/O error on device mtdblock2, logical block 3
这句提示不是你的nandflash有问题，就是你nand驱动有问题，或者是分区有问题。导致mtdblock2读取异常，rootfs自然就加不上。
这句提示不是你的nandflash有问题，就是你nand驱动有问题，或者是分区有问题。导致mtdblock2读取异常，rootfs自然就加不上。
#7
现在我重新烧一遍就变成这样啦
Uncompressing Linux.............................................................
.............................. done, booting the kernel.
Linux version 2.6.32 (root@localhost.localdomain) (gcc version 4.3.2 (Sourcery G
++ Lite 2008q3-72) ) #43 Sat Jan 7 20:10:19 CST 2012
CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: SMDK6410
Memory policy: ECC disabled, Data cache writeback
CPU S3C6410 (id 0x36410101)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C64XX: PLL settings, A=532000000, M=532000000, E=24000000
S3C64XX: HCLK2=266000000, HCLK=133000000, PCLK=66500000
mout_apll: source is fout_apll (1), rate is 532000000
mout_epll: source is fout_epll (1), rate is 24000000
mout_mpll: source is mpll (1), rate is 532000000
mmc_bus: source is mout_epll (0), rate is 24000000
mmc_bus: source is mout_epll (0), rate is 24000000
mmc_bus: source is mout_epll (0), rate is 24000000
usb-bus-host: source is clk_48m (0), rate is 48000000
uclk1: source is dout_mpll (1), rate is 66500000
spi-bus: source is mout_epll (0), rate is 24000000
spi-bus: source is mout_epll (0), rate is 24000000
audio-bus: source is mout_epll (0), rate is 24000000
audio-bus: source is mout_epll (0), rate is 24000000
irda-bus: source is mout_epll (0), rate is 24000000
camera: source is hclk2 (0), rate is 266000000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: root=/dev/mtdblock2 rootfstype=cramfs console=ttySAC0,11520
0
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 256640KB available (2476K code, 353K data, 84K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:246
VIC @f4000000: id 0x00041192, vendor 0x41
VIC @f4010000: id 0x00041192, vendor 0x41
Console: colour dummy device 80x30
console [ttySAC0] enabled
Calibrating delay loop... 530.84 BogoMIPS (lpj=2654208)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
S3C6410: Initialising architecture
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c-i2c s3c2440-i2c.0: slave address 0x10
s3c-i2c s3c2440-i2c.0: bus frequency set to 64 KHz
s3c-i2c s3c2440-i2c.0: i2c-0: S3C I2C adapter
s3c-i2c s3c2440-i2c.1: slave address 0x10
s3c-i2c s3c2440-i2c.1: bus frequency set to 64 KHz
s3c-i2c s3c2440-i2c.1: i2c-1: S3C I2C adapter
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
yaffs Jan 7 2012 17:13:02 Installing.
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
s3c6400-uart.0: s3c2410_serial0 at MMIO 0x7f005000 (irq = 16) is a S3C6400/10
s3c6400-uart.1: s3c2410_serial1 at MMIO 0x7f005400 (irq = 20) is a S3C6400/10
s3c6400-uart.2: s3c2410_serial2 at MMIO 0x7f005800 (irq = 24) is a S3C6400/10
s3c6400-uart.3: s3c2410_serial3 at MMIO 0x7f005c00 (irq = 28) is a S3C6400/10
brd: module loaded
loop: module loaded
at24 0-0050: 1024 byte 24c08 EEPROM (writable)
at24 1-0057: 16384 byte 24c128 EEPROM (writable)
S3C NAND Driver, (c) 2008 Samsung Electronics
S3C NAND Driver is using hardware ECC.
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd5 (Samsung NAND 2GiB 3,3V 8-bit)
Creating 4 MTD partitions on "NAND 2GiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "Bootloader"
0x000000040000-0x000000400000 : "Kernel"
0x000000400000-0x000005400000 : "Rootfs"
0x000005400000-0x000080000000 : "User File System"
usbmon: debugfs is not available
usbcore: registered new interface driver wusb-cbaf
idmouse: 0.6:Siemens ID Mouse FingerTIP Sensor Driver
usbcore: registered new interface driver idmouse
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using PIO
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
mmc0: Minimum clock frequency too high for identification mode
s3c6410_setup_sdhci0_cfg_card: CTRL 2=c0004100, 3=80808080
List of all partitions:
1f00 256 mtdblock0 (driver?)
1f01 3840 mtdblock1 (driver?)
1f02 81920 mtdblock2 (driver?)
1f03 2011136 mtdblock3 (driver?)
No filesystem could mount root, tried: cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[<c0023b50>] (unwind_backtrace+0x0/0xdc) from [<c01b7e40>] (panic+0x40/0x114)
[<c01b7e40>] (panic+0x40/0x114) from [<c0008fd0>] (mount_block_root+0x25c/0x2ac)
[<c0008fd0>] (mount_block_root+0x25c/0x2ac) from [<c00091e8>] (prepare_namespace
+0x164/0x1c8)
[<c00091e8>] (prepare_namespace+0x164/0x1c8) from [<c00085c0>] (kernel_init+0xd8
/0x10c)
[<c00085c0>] (kernel_init+0xd8/0x10c) from [<c001ee04>] (kernel_thread_exit+0x0/
0x8)
#8
现在nand没问题了，No filesystem could mount root, tried: cramfs可能的原因
1，你的cramfs工具有没有问题，支持的是大页还是小页的nand。你板上的nand是大页还是小页这要对应
2，uboot有没有问题，是否支持对 cramfs文件系统的烧写
3，内核对 cramfs的支持有没有问题。
从上面三点 看看能不能找到问题所在
1，你的cramfs工具有没有问题，支持的是大页还是小页的nand。你板上的nand是大页还是小页这要对应
2，uboot有没有问题，是否支持对 cramfs文件系统的烧写
3，内核对 cramfs的支持有没有问题。
从上面三点 看看能不能找到问题所在
#9
那个UBOOT是用的是原来飞凌2.6.28的内核的UBOOT，并且新内核里的分区表也是跟原来内核一样的，所以这点应该没有问题
cramfs 工具应该没有问题，我用这个工具有自己做过cramfs根文件系统，在原来内核下可以正常识别出文件系统。至于这个大页和小页，我只是把原来内核下的nand flash的驱动复制过来，没有改过什么东西，包括分区表，这个应该没有问题吧（不知有没有）
至于内核对cramfs的支持，已经有选择这个编译了呀，还要配置什么吗？
我看过别人移植的日记，感觉他们也只是做了这几个步骤呀？
#10
怎么没有人回答我的问题了，自己顶一下！
#11
终于解决了，我用NFS挂载根文件系统，在终端里把mtdblock2 挂载为yaffs2发现报出一大堆ecc错误，原来是nand flash驱动的移植还有一点问题，解决后,一切都OK啦，困扰了我很久了！
#12
楼主解决方法能不能详细点啊？
#13
遇到同样的问题了，楼主还在么？能不能详细解释一下？