fish.zou

另外，我的init.rc也改成如下了：应该是没有问题，实在找不到原因了。
on fs
# mount mtd partitions
    # Mount /system rw first to give the filesystem a chance to save a checkpoint
    #mount yaffs2 mtd@system /system
        mount ext4 /dev/mmcblk0p2 /system
    chown root /system/bin/pppd
    chmod 4755 /system/bin/pppd
    chmod 0755 /system/lib/libztewcdma-ril.so
        mount ext4 /dev/mmcblk0p2 /system ro remount
        mount ext4 /dev/mmcblk0p3 /data nosuid nodev
        mount ext4 /dev/mmcblk0p4 /cache nosuid nodev
    #mount yaffs2 mtd@system /system ro remount
    #mount yaffs2 mtd@userdata /data nosuid nodev
    #mount yaffs2 mtd@cache /cache nosuid nodev

Wince.Android

mkyaffs2image--------------这个不是SD或者inand 启动的啊，这是nandflash启动的文件格式，你搞错了


android2.3 和android4.0.3 我都在S5PV210 上试过了，完全没问题。
你的init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/drmserver', disabling 'drm'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
mfc_firmware_request_complete_handler: failed to load MFC F/W, MFC will not working
init: cannot find '/system/bin/keystore', disabling 'keystore'
init: property (null) has no value for writing to /sys/class/android_usb/android0/iManufacturer
init: property (null) has no value for writing to /sys/class/android_usb/android0/iProduct
init: cannot find '/system/bin/sh', disabling 'console'
说明你的ramdisk 还是yaffs 的，你注意一下，下的是ramdisk-uboot.img ,这个是ramdisk.img 重新打包的，而很多系统尤其是android2.3.1 比较SB的，只要不手动删除这个ramdisk.img，重新编译根本没变的。所以会启动就像你的那样，不起来。你手动删除先，还有init.rc 在SD卡或者inand 启动的时候是从init_SDMMC.rc 过来的，你最好不要手动在原来的init.rc里面添加，否则你就悲剧了。O(∩_∩)O~
忙去了。

太忙了。

fish.zou

我现在的system.img，不是mkyaffs2image编译出来的，应该是mk_ext4这个编译出来的，具体我没深究这个，因为现在直接用file命令查看很容易就看出它是不是ext4格式的，至于楼主您说的ramdisk还是yaffs格式的，这个我还真不会看，因为我烧进sd卡中的也是ramdisk-uboot.img.  file 命令查看这个ramdisk-uboot.img好像也是对的，怎么样才能确定ramdisk也做成了ext4格式的呢？

Wince.Android

原帖由 fish.zou 于 2013-6-7 17:58 发表
我现在的system.img，不是mkyaffs2image编译出来的，应该是mk_ext4这个编译出来的，具体我没深究这个，因为现在直接用file命令查看很容易就看出它是不是ext4格式的，至于楼主您说的ramdisk还是yaffs格式的，这个我还 ...

这个关键是看init.rc文件是否已经是从init_SDMMC.rc 转过来的， 如果不是，肯定ramdisk.img 不满足要求的。

fish.zou

我编译出来的源码，out/target/product/smdkv210/root/ 有一个init.rc还有一个是init.smdkv210.rc.  其中init.rc是system/core/rootdir/下面的init.rc转过来的，init.smdkv210.rc是device/下 init.smdkv210_sdmmc.rc转过来的，这样应该是没有问题的呀。 我试过将init.rc里面关于mount fs这段修改成我上面说的那种 mount /dev/mmcblk0p2 /system这种形式，就不会存在：
yaffs: dev is 32505860 name is "mtdblock4" rw
yaffs: yaffs: Attempting MTD mount of 31.4,"mtdblock4"
yaffs: yaffs_read_super: is_checkpointed 1
yaffs: dev is 32505862 name is "mtdblock6" rw
yaffs: yaffs: Attempting MTD mount of 31.6,"mtdblock6"
yaffs: yaffs_read_super: is_checkpointed 0
yaffs: dev is 32505861 name is "mtdblock5" rw
yaffs: yaffs: Attempting MTD mount of 31.5,"mtdblock5"
yaffs: yaffs_read_super: is_checkpointed 0
这种信息。 一旦还原的话，就会存在。
需不需要有传递给kernel的参数？像这样的 CONFIG_BOOTARGS  root=/dev/mmcblk0p2

gooogleman

你搞错了吧。
init.rc yaffs2文件系统是init.rc
如果是ext 文件系统那就是init_sdmmc.rc 来的
你看一下sate210/android/device/samsung/smdkv210/device.mk这个文件就知道了。

fish.zou

好像没错呀，我查看了2.3的源码，init.rc确实是从init_sdmmc.rc里面转过来的。我现在这个版本4.0.4是这样定义的：
ifeq ($(BOARD_SDMMC_BSP),true)
source_init_rc_file := $(LOCAL_PATH)/init.smdkv210_sdmmc.rc
else
source_init_rc_file := $(LOCAL_PATH)/init.smdkv210.rc
endif
PRODUCT_COPY_FILES := \
$(source_init_rc_file):root/init.smdkv210.rc \
而且init.smdkv210_sdmmc.rc文件比init.rc文件少了很多内容，这样我就试着将init.rc中on fs部分修改成mount /dev/blkmmc0p2 /system这样。结果还是不行，同样还是找不到ramdisk。
Freeing init memory: 176K
init: /init.rc: 435: invalid option 'symlink'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot open '/initlogo.rle'
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
init: cannot find '/system/bin/netd', disabling 'netd'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/drmserver', disabling 'drm'
mfc_firmware_request_complete_handler: failed to load MFC F/W, MFC will not working
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/keystore', disabling 'keystore'
init: property (null) has no value for writing to /sys/class/android_usb/android0/iManufacturer
init: property (null) has no value for writing to /sys/class/android_usb/android0/iProduct
init: cannot find '/system/bin/sh', disabling 'console'
android_usb: already disabled
adb_bind_config
warning: `adbd' uses 32-bit capabilities (legacy support in use)
android_work: did not send uevent (0 0   (null))
adb_open
android_work: sent uevent USB_STATE=CONNECTED
android_usb gadget: high speed config #1: android
android_work: sent uevent USB_STATE=CONFIGURE
直接将init.rc用替换init.smdkv_sdmmc.rc，也起不来。

congbupt

gooogleman 发表于 2013-5-29 23:16
./make_ext4fs  -l 120M -a system system.img out/target/product/smdkv210/system
经过这么压缩
再用fi ...

你好，我用make_ext4fs制作的system镜像可以挂载上，并且也启动到了Android界面。但是很多应用程序不能使用了，比如不能放歌曲、不能看视频，不能安装应用程序。安装应用程序就会导致Android界面重启，终端提示：
binder: 465:465 transaction failed 29189, size 64-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 465:508 transaction failed 29189, size 60-0
binder: 407:407 transaction failed 29189, size 64-0
alarm_release: clear alarm, pending 0
alarm_release: clear alarm, pending 0
alarm_release: clear alarm, pending 0
request_suspend_state: wakeup (0->0) at 249555247379 (1970-01-02 19:22:47.319828253 UTC)
init: untracked pid 72 exited
init: untracked pid 556 exited
init: untracked pid 223 exited
init: untracked pid 583 exited
init: untracked pid 199 exited
init: untracked pid 572 exited
init: untracked pid 218 exited
init: untracked pid 209 exited
init: untracked pid 301 exited
init: untracked pid 352 exited
init: untracked pid 407 exited
init: untracked pid 386 exited
init: untracked pid 317 exited
init: untracked pid 398 exited
init: untracked pid 378 exited
init: untracked pid 367 exited
init: untracked pid 416 exited
init: untracked pid 287 exited
init: untracked pid 438 exited
init: untracked pid 267 exited
init: untracked pid 465 exited
init: untracked pid 304 exited
init: untracked pid 339 exited
init: untracked pid 427 exited
init: untracked pid 212 exited

gooogleman

呵呵，这个楼上问题还没解决吗？

zslzsl999

gooogleman 发表于 2014-2-20 22:37
呵呵，这个楼上问题还没解决吗？

。。。估计楼主已经解决了。。。但是我还没解决呢
你在帮分析分析被

gooogleman

zslzsl999 发表于 2014-2-21 10:30
。。。估计楼主已经解决了。。。但是我还没解决呢
你在帮分析分析被

这种问题应该是ramdisk 格式还不是ext4的，
这个要非常注意的，我记得以前遇到过，不过如果是android4.0 ，所有镜像都已经是ext 格式的了。

zslzsl999

gooogleman 发表于 2014-2-25 00:11
这种问题应该是ramdisk 格式还不是ext4的，
这个要非常注意的，我记得以前遇到过，不过如果是android4.0 ...

这个我解决了  好像是sd卡的问题  我把sd卡在ubuntu下用mkfs.ext4格式化了system分区
然后手动复制粘贴system里的东西到sd卡  在给了一个755得权限  然后上面那一堆can‘t find xxx 都没有了，变成cannot find '/system/etc/install-recovery.sh一个了
我查了一下system里确实没有这个  而且下面能看见android得字样了

但有了一个新得问题啊  跟28楼哥们类似android下面不继续走了啊  愁死我了。。。求分析
而且会按概率出现kernel panic 时有时没有
还有个问题CPUFreq driver是什么  我能把这个驱动屏蔽掉吗？

zslzsl999

EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
adb_bind_config
adb_open
s3c_udc_cable_usbdetected..
root@android:/ # PVR_K:(Warning): SysFinalise: Version string: SGX540 S5PC110 [384, drivers/gpu/pvr/s5pc110/sysconfig.c]
s3c_udc_cable_usbdetected..
s3c_udc_cable_usbdetected..
android_usb gadget: high speed config #1: android
Kernel panic - not syncing: Attempted to kill init!
[] (unwind_backtrace+0x0/0xec) from [] (panic+0x6c/0x18c)
[] (panic+0x6c/0x18c) from [] (do_exit+0xb0/0x62c)
[] (do_exit+0xb0/0x62c) from [] (do_group_exit+0x90/0xc0)
[] (do_group_exit+0x90/0xc0) from [] (get_signal_to_deliver+0x36c/0x3a8)
[] (get_signal_to_deliver+0x36c/0x3a8) from [] (do_signal+0xb0/0x5a8)
[] (do_signal+0xb0/0x5a8) from [] (do_notify_resume+0x18/0x48)
[] (do_notify_resume+0x18/0x48) from [] (work_pending+0x24/0x28)

zslzsl999

没有任何改变  这次重启的结果就和上次不一样
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
root@android:/ # adb_bind_config
adb_open
s3c_udc_cable_usbdetected..
PVR_K:(Warning): SysFinalise: Version string: SGX540 S5PC110 [384, drivers/gpu/pvr/s5pc110/sysconfig.c]
s3c_udc_cable_usbdetected..
s3c_udc_cable_usbdetected..
android_usb gadget: high speed config #1: android
init: untracked pid 1073 exited
init: untracked pid 1071 exited
init: untracked pid 1111 exited
request_suspend_state: wakeup (3->0) at 24260701941 (2010-01-01 12:00:13.061647009 UTC)
init: untracked pid 1067 exited
init: untracked pid 1112 exited
init: untracked pid 1121 exited
request_suspend_state: wakeup (0->0) at 27311611589 (2010-01-01 12:00:16.112556365 UTC)
init: untracked pid 1132 exited
init: untracked pid 1135 exited
request_suspend_state: wakeup (0->0) at 32594789880 (2010-01-01 12:00:21.395734698 UTC)
request_suspend_state: wakeup (0->0) at 37628302502 (2010-01-01 12:00:26.429247695 UTC)
init: untracked pid 1143 exited
init: untracked pid 1151 exited
request_suspend_state: wakeup (0->0) at 37654100173 (2010-01-01 12:00:26.455045198 UTC)
init: untracked pid 1149 exited
request_suspend_state: wakeup (0->0) at 42689179044 (2010-01-01 12:00:31.490124153 UTC)
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode
SysRq : Emergency Remount R/O
EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p4): re-mounted. Opts: (null)
Emergency Remount complete
Restarting system with command 'recovery'.

zslzsl999

EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
adb_bind_config
adb_open
s3c_udc_cable_usbdetected..
s3c_udc_cable_usbdetected..
s3c_udc_cable_usbdetected..
android_usb gadget: high speed config #1: android
root@android:/ # PVR_K:(Warning): SysFinalise: Version string: SGX540 S5PC110 [384, drivers/gpu/pvr/s5pc110/sysconfig.c]
binder: release 1066:1066 transaction 31 in, still active
binder: send failed reply for transaction 31 to 1067:1067
init: untracked pid 1072 exited
request_suspend_state: wakeup (3->0) at 25253189951 (2010-01-01 12:00:14.057993060 UTC)
init: untracked pid 1068 exited
init: untracked pid 1074 exited
init: untracked pid 1114 exited
init: untracked pid 1115 exited
request_suspend_state: wakeup (0->0) at 28314282807 (2010-01-01 12:00:17.119086249 UTC)
request_suspend_state: wakeup (0->0) at 33861426141 (2010-01-01 12:00:22.666228666 UTC)
init: untracked pid 1129 exited
request_suspend_state: wakeup (0->0) at 33881509641 (2010-01-01 12:00:22.686313249 UTC)
init: untracked pid 1134 exited
request_suspend_state: wakeup (0->0) at 38917158471 (2010-01-01 12:00:27.721961705 UTC)
init: untracked pid 1141 exited
request_suspend_state: wakeup (0->0) at 38939219720 (2010-01-01 12:00:27.744022871 UTC)
init: untracked pid 1146 exited
request_suspend_state: wakeup (0->0) at 43974592094 (2010-01-01 12:00:32.779395286 UTC)
init: untracked pid 1153 exited
init: untracked pid 1157 exited
request_suspend_state: wakeup (0->0) at 44000427927 (2010-01-01 12:00:32.805230869 UTC)
init: untracked pid 1159 exited
request_suspend_state: wakeup (0->0) at 48025702914 (2010-01-01 12:00:36.830506564 UTC)
request_suspend_state: wakeup (0->0) at 48041086041 (2010-01-01 12:00:36.845889899 UTC)
init: untracked pid 1168 exited
init: untracked pid 1169 exited
request_suspend_state: wakeup (0->0) at 53078770458 (2010-01-01 12:00:41.883573733 UTC)
init: untracked pid 1179 exited
init: untracked pid 1175 exited
request_suspend_state: wakeup (0->0) at 53103751620 (2010-01-01 12:00:41.908555145 UTC)

gooogleman

zslzsl999 发表于 2014-3-3 16:33
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mo ...

这个遇到过，好像是uboot内存设置的问题。是否是从1GB 改成512MB的？

zslzsl999

gooogleman 发表于 2014-3-3 22:28
这个遇到过，好像是uboot内存设置的问题。是否是从1GB 改成512MB的？

uboot直接可以用  所以我没有改

uboot启动得时候打印信息显示1GB内存  但我记得这个板子是512的
改了环境变量就可以进入kernel 所以我没太在意

请问如果修改内存设置  怎么修改  先谢了

congbupt

gooogleman 发表于 2014-2-20 22:37
呵呵，这个楼上问题还没解决吗？

这个问题是2.3系统的，还没解决。现在弄4.0 的系统，有了新问题。

就是35楼的问题。我的Android是4.0的，在BoardConfig.mk里面没发现有BOARD_SDMMC_BSP这个变量，我就直接编译出来后，使用make_ext4fs制作的system.img镜像，制作成EXT4格式的了。我的u-boot也是1.3.4版本，利用带的工具ext3format格式化的system分区，系统第一次启动之后就出现下面的错误：

Freeing init memory: 176K
init: cannot open '/initlogo.rle'
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 32237 in gd
Aborting journal on device mmcblk0p3-8.
EXT4-fs (mmcblk0p3): Remounting filesystem read-only
EXT4-fs error (device mmcblk0p3) in ext4_reserve_inode_write:5641: Journal has aborted
EXT4-fs error (device mmcblk0p3) in ext4_evict_inode:215: Journal has aborted
rtusb init rt2870 --->
usbcore: registered new interface driver rt2870
EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 26728 in gd
Aborting journal on device mmcblk0p2-8.
EXT4-fs (mmcblk0p2): Remounting filesystem read-only
EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:5641: Journal has aborted
EXT4-fs error (device mmcblk0p2) in ext4_evict_inode:215: Journal has aborted
init: Unable to open persistent property directory /data/property errno: 2

我用ls查看了一下，发现也挂载上了。但是一直打印下面的信息，停留在ANDROID字样的界面，进入不了系统。

request_suspend_state: wakeup (3->0) at 5335262707 (2014-03-02 08:59:42.414075023 UTC)
init: untracked pid 2179 exited
init: untracked pid 2184 exited
request_suspend_state: wakeup (0->0) at 9111824947 (2014-03-02 08:59:46.190638013 UTC)
init: untracked pid 2230 exited
init: untracked pid 2229 exited
request_suspend_state: wakeup (0->0) at 13894569232 (2014-03-02 08:59:50.973382464 UTC)
init: untracked pid 2290 exited
init: untracked pid 2289 exited
……

要是再次启动的话，错误就会变成：

Freeing init memory: 176K
init: cannot open '/initlogo.rle'
EXT4-fs warning (device mmcblk0p2): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
EXT4-fs warning (device mmcblk0p2): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
EXT4-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs warning (device mmcblk0p3): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
EXT4-fs warning (device mmcblk0p3): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
EXT4-fs (mmcblk0p3): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs error (device mmcblk0p3): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 32237 in gd
Aborting journal on device mmcblk0p3-8.
EXT4-fs (mmcblk0p3): Remounting filesystem read-only
EXT4-fs error (device mmcblk0p3) in ext4_reserve_inode_write:5641: Journal has aborted
EXT4-fs error (device mmcblk0p3) in ext4_evict_inode:215: Journal has aborted
rtusb init rt2870 --->
usbcore: registered new interface driver rt2870
EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:736: group 1, 25600 blocks in bitmap, 26728 in gd
Aborting journal on device mmcblk0p2-8.
EXT4-fs (mmcblk0p2): Remounting filesystem read-only
EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:5641: Journal has aborted
EXT4-fs error (device mmcblk0p2) in ext4_evict_inode:215: Journal has aborted

一样是进入不了Android系统。

zslzsl999

congbupt 发表于 2014-3-5 10:23
这个问题是2.3系统的，还没解决。现在弄4.0 的系统，有了新问题。

就是35楼的问题。我的Android是4.0 ...

握手。。。
那个BOARD_SDMMC_BSP是干啥的？

congbupt

zslzsl999 发表于 2014-3-5 10:51
握手。。。
那个BOARD_SDMMC_BSP是干啥的？

就是编译后的文件跑在emmc上，文件系统格式是EXT4，要是设置为False的话就编译的Yaffs格式。你的问题解决了吗？