请问内核启动过程中 使用sdk包中的rootfs 镜像文件
arago-sc-mcsdk-base-image-glibc-ipk-2011.06-tci6614-evm.ubifs.img
arago-sc-mcsdk-recovery-image-glibc-ipk-2011.06-tci6614-evm.ubifs.img
可以正常启动,为何使用自己生成的rootfs镜像文件内核启动会崩溃?
制作过程如下:
rootfs原文件是从sdk的arago-sc-mcsdk-base-image-tci6614-evm.tar.gz解压后得到
然后
mkdir rootfs
cp arago-sc-mcsdk-base-image-tci6614-evm/ rootfs/
./mkfs.ubifs -r rootfs -F -o tci6614-rootfs.ubifs.img -m 2048 -e 126976 -c 214
mkdir rootfs-recovery
cp arago-sc-mcsdk-recovery-base-image-tci6614-evm/ rootfs-recovery/
然后再修改ubinize.cfg
[rootfs-recovery]
mode=ubi
image=tci6614-rootfs-revory.ubifs.img
[rootfs]
mode=ubi
image=tci6614-rootfs.ubifs.img
最后
./ubinize -o tci6614-evm-ubifs.ubi -m 2048 -p 128KiB -s 2048 -O 2048 ubinize.cfg
制作tci6614-evm-ubifs.ubi后烧到nand中引导内核启动出现下面的异常?
...
Bridge firewalling registered
Ebtables v2.0 registered
8021q: 802.1Q VLAN Support v1.8
sctp: Hash tables configured (established 16384 bind 32768)
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
UBIFS: parse sync
UBIFS: start fixing up free space
UBIFS: free space fixup complete
UBIFS: mounted UBI device 0, volume 2, name "rootfs"
UBIFS: file system size: 33140736 bytes (32364 KiB, 31 MiB, 261 LEBs)
UBIFS: journal size: 4571136 bytes (4464 KiB, 4 MiB, 36 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 168K
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
