You can't use an ext filesystem directly one a raw mtd device. To use a raw mtd device you need to use either yaffs2, jffs2, ubifs On a MMC device you can use an ext filesystem but you cannot use yaffs2, jffs2 or ubifs
On Wed, May 11, 2011 at 2:53 PM, andria <andri...@gmail.com> wrote: > rarin > The patch command prints that there are malformed patch lines > so I manually did the update. I'm now able to compile gingerbread > thanks to you. > mike > I need ext4 because I'll have to use the extended attributes. > > I'm on gingerbread now. I did the same steps to enable the support of > ext4 but I got the same errors. I noticed that I didn't post the dmesg > output. Here is what is logged > <6>yaffs: dev is 32505856 name is "mtdblock0" > <6>yaffs: passed flags "" > <4>yaffs: Attempting MTD mount on 31.0, "mtdblock0" > <4>yaffs_read_super: isCheckpointed 0 > <4>save exit: isCheckpointed 0 > <4>goldfish_nand_read: invalid read, start 400, len 200, dev_size > 4000000, write_size 800 > <3>end_request: I/O error, dev mtdblock1, sector 2 > <3>EXT4-fs: unable to read superblock > <6>yaffs: dev is 32505858 name is "mtdblock2" > <6>yaffs: passed flags "" > <4>yaffs: Attempting MTD mount on 31.2, "mtdblock2" > <4>yaffs_read_super: isCheckpointed 0 > > There is an error when the system tries to mount /data. Do you think > that it is due to system.img and/or ramdisk.img? Maybe they are meant > to be used with yaffs2. > > Thanks > > On 10 mai, 21:30, mike digioia <mpd...@gmail.com> wrote: > > But you don't need anything special on your build computer except the > > updated tools necessary for 64 bit. Like java 6 etc. My computer I am > using > > for Gingerbread development is an old (7years old) IBM thinkpad. > > > > > > > > > > > > > > > > On Tue, May 10, 2011 at 12:18 PM, <rarin...@gmail.com> wrote: > > > Can you try this out Andria? > > > > http://osdir.com/ml/android-porting/2010-12/msg00272.html#0_undefined,0_ > > > -----Original Message----- > > > From: andria > > > Sent: 10/05/2011, 2:47 PM > > > To: Android Linux Kernel Development > > > Subject: [android-kernel] Re: froyo : ext4 instead of yaffs2 > > > > > One more thing, I use froyo because I don't have a 64 bit computer. > > > when I try to compile a newer version than froyo, it writes that I > > > need a 64-bit computer. > > > > > Thanks > > > > > Andria > > > > > On 10 mai, 03:34, Arindam Roy <rarin...@gmail.com> wrote: > > > > Also, in Froyo, it might not be a good idea to enable ext4. > > > > Because the framework code may not be handling the buffering issue > for > > > ext4, > > > > as being done in GB. > > >http://android-developers.blogspot.com/2010/12/saving-data-safely.html > > > > > > < > http://android-developers.blogspot.com/2010/12/saving-data-safely.html> > > > > Thanks, > > > > Arindam > > > > > > On Tue, May 10, 2011 at 6:56 AM, 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 > > -- > 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
