So what improvements t=do you see with using ext4? On Tue, May 10, 2011 at 2:13 AM, andria <andri...@gmail.com> wrote:
> Hi, > > Thanks for your reply. To enable the support of ext4 I added the > following lines to .config if they were not written or if the value > was set to n. > > CONFIG_EXT4_FS=y > CONFIG_EXT4DEV_COMPAT=y > CONFIG_EXT4_FS_XATTR=y > CONFIG_EXT4_FS_POSIX_ACL=y > CONFIG_EXT4_FS_SECURITY=y > CONFIG_JBD=y > CONFIG_JBD2=y > CONFIG_FS_MBCACHE=y > CONFIG_FS_POSIX_ACL=y > > I launch make ARCH=arm CROSS_COMPILE=<froyo_path>/prebuilt/linux-x86/ > toolchain/arm-eabi-4.4.0/bin/arm-eabi- to build the new kernel. > At the end I get a new zImage file. > > Then I modify the init.rc in the froyo folder. > > mount yaffs2 mtd@userdata /data nosuid nodev -> mount ext4 > mtd@userdata /data nosuid nodev > > I launch make to get new system.img ramdisk.img and userdata.img. > > That's all I've done. I also tried to use /dev/block/mtdblock1 instead > of mtd@userdata but it didn't work. > > Andria > > > On 10 mai, 03:26, Arindam Roy <rarin...@gmail.com> wrote: > > Hello Andria, > > I am assuming you built the driver as part of kernel aend did not make it > a > > module. > > Also, how are ensuring while building the system.img, and ramdisk.img, > > proper ext4 filesystems are being built. > > Can you share the command line, or make file changes? > > Thanks, > > Arindam > > > > > > > > > > > > > > > > On Mon, May 9, 2011 at 5:44 PM, andria <andri...@gmail.com> wrote: > > > Hi, > > > > > I'm trying to moun /data with ext4 instead of yaffs2 on a froyo > > > emulator. > > > > > 1- I enabled the support of ext3 and ext4 in the .config and built a > > > new kernel > > > 2- I launched the emulator with the new zImage to make sure that there > > > was no error. No error > > > 3- I replaced yaffs2 with ext4 in the init.rc inside froyo source and > > > built new system.img and ramdisk.img > > > mount yaffs2 mtd@userdata /data nosuid nodev --> mount ext4 > > > mtd@userdata /data nosuid nodev > > > 4- I launched the emulator and I got errors. Errors occur: services > > > always die and there is problem with the framework. Here is a sample > > > of the error message: > > > > > D/AudioHardwareInterface( 152): setMode(NORMAL) > > > I/CameraService( 152): CameraService started: pid=152 > > > I/AudioFlinger( 152): AudioFlinger's thread 0xb3f0 ready to run > > > E/keystore( 158): chdir: /data/misc/keystore: No such file or > > > directory > > > D/AndroidRuntime( 157): > > > D/AndroidRuntime( 157): >>>>>>>>>>>>>> AndroidRuntime START > > > <<<<<<<<<<<<<< > > > D/AndroidRuntime( 157): CheckJNI is ON > > > E/dalvikvm( 157): Can't open dex cache '/data/dalvik-cache/ > > > system(at)framework(at)core.jar(at)classes.dex': No such file or > > > directory > > > I/dalvikvm( 157): Unable to open or create cache for /system/ > > > framework/core.jar (/data/dalvik-cache/ > > > system(at)framework(at)core.jar(at)classes.dex) > > > D/dalvikvm( 157): Unable to process classpath element '/system/ > > > framework/core.jar' > > > E/dalvikvm( 157): Can't open dex cache '/data/dalvik-cache/ > > > system(at)framework(at)ext.jar(at)classes.dex': No such file or > > > directory > > > I/dalvikvm( 157): Unable to open or create cache for /system/ > > > framework/ext.jar (/data/dalvik-cache/ > > > system(at)framework(at)ext.jar(at)classes.dex) > > > D/dalvikvm( 157): Unable to process classpath element '/system/ > > > framework/ext.jar' > > > E/dalvikvm( 157): Can't open dex cache '/data/dalvik-cache/ > > > system(at)framework(at)framework.jar(at)classes.dex': No such file or > > > directory > > > I/dalvikvm( 157): Unable to open or create cache for /system/ > > > framework/framework.jar (/data/dalvik-cache/ > > > system(at)framework(at)framework.jar(at)classes.dex) > > > D/dalvikvm( 157): Unable to process classpath element '/system/ > > > framework/framework.jar' > > > E/dalvikvm( 157): Can't open dex cache '/data/dalvik-cache/ > > > system(at)framework(at)android.policy.jar(at)classes.dex': No such > > > file or directory > > > I/dalvikvm( 157): Unable to open or create cache for /system/ > > > framework/android.policy.jar (/data/dalvik-cache/ > > > system(at)framework(at)android.policy.jar(at)classes.dex) > > > D/dalvikvm( 157): Unable to process classpath element '/system/ > > > framework/android.policy.jar' > > > E/dalvikvm( 157): Can't open dex cache '/data/dalvik-cache/ > > > system(at)framework(at)services.jar(at)classes.dex': No such file or > > > directory > > > I/dalvikvm( 157): Unable to open or create cache for /system/ > > > framework/services.jar (/data/dalvik-cache/ > > > system(at)framework(at)services.jar(at)classes.dex) > > > D/dalvikvm( 157): Unable to process classpath element '/system/ > > > framework/services.jar' > > > E/dalvikvm( 157): ERROR: no valid entries found in bootclasspath '/ > > > system/framework/core.jar:/system/framework/ext.jar:/system/framework/ > > > framework.jar:/system/framework/android.policy.jar:/system/framework/ > > > services.jar' > > > W/dalvikvm( 157): JNI_CreateJavaVM failed > > > E/AndroidRuntime( 157): JNI_CreateJavaVM failed > > > I/ServiceManager( 27): service 'media.audio_flinger' died > > > I/ServiceManager( 27): service 'media.player' died > > > I/ServiceManager( 27): service 'media.camera' died > > > I/ServiceManager( 27): service 'media.audio_policy' died > > > I/ ( 159): ServiceManager: 0xacd0 > > > D/AudioHardwareInterface( 159): setMode(NORMAL) > > > I/CameraService( 159): CameraService started: pid=159 > > > I/AudioFlinger( 159): AudioFlinger's thread 0xb3f0 ready to run > > > > > Did I miss something to mount succesfully /data with ext4? > > > > > -- > > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > > website:http://groups.google.com/group/android-kernel > > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
