Well if it's worked before then it oughta work now!

Out of suggestions I'm afraid :(

On Thu, 21 May 2009, Marcus Stong wrote:

Hi David. I reformatted the card exactly as I've been doing for the last 3 months while testing all of the android images, and haven't had a problem until now.

I've been formatting them like this after running fdisk.

 # mkfs.vfat -v -n and-media /dev/mmcblk0p1
 # mkfs.ext3 -v -L and-data /dev/mmcblk0p2

Is this correct?

Marcus

David Hicks wrote:

have you formatted the SD card correctly?

You need two partitions. The first one should be fat (or vfat, can't remember which). Android treats this as it's own SD card. The second should be ext2 or ext3 and that is what gets mounted as /data.

On Wed, 20 May 2009, Nicolas MORA wrote:

Marcus Stong a ?crit :
Hi Michael,
Glad you're back. Should qi or u-boot be installed for freerunner-cupcake-snapshot-v4.jffs2?
Also what kernel?
I am unable to get past the flashing android logo on boot using qi and uImage-v17.bin.

I have the same problem, and when I mounted the .jffs2 image file, I found that the /data directory is empty, so there seems to be some problems.

Should we use a data filesystem that can be found elsewhere ?
_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org

_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org


_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org

_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org

Reply via email to