On Apr 15, 2:42 am, Deva R <[email protected]> wrote: > Hi, > what is the filesystem partition size being used? > > >[ 246.085876] EXT3-fs (mmcblk0p2): using internal journal > >[ 246.091949] EXT3-fs (mmcblk0p2): recovery complete > >[ 246.112457] EXT3-fs (mmcblk0p2): mounted filesystem with writeback > >data mode > >tar: write error: No space left on device > > - can you try increasing the filessystem partition size? > > - can you also explicitly set root, mem, init fields in your bootarg? > console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1 mem=256M > init=/init omapfb.vrfb=1 > omapfb.mode=dvi:[email protected]_disp=dv3on Thu, Apr 15, 2010 at > 7:08 AM, G2 Hello,
Thanks for your answer. this "write error" is for a graphical initramfs and it has nothing to do with Android. I'm 100% sure. I have setup all arguments in kernel command line and still get the same error. Beyond Loglevel in /init.rc, is there anything else to increase log information so that I understand what's wrong in the kernel that creates this problem? Grégoire -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting To unsubscribe, reply using "remove me" as the subject.
