MeeGo on SD with FAT partition?

[xxxxts]

I would love to dual boot MeeGo (which I have) but I would also like to have a useable MMC... it should be possible, how is it done?

[Hurrian]

You'll need to edit MeeGo's boot.scr (wonder why the hell this isn't done in the first place: u-boot bootfiles in vfat p1, MeeGo in ext3/4/btrfs p2, and swap on p3, to make it play nice with Maemo)

If you want to make the vfat partition something other than what's on the downloadable image, just download the u-boot for n900 sources, change which partition it points to, build, append and flash.

[xxxxts]

Originally Posted by Hurrian

You'll need to edit MeeGo's boot.scr (wonder why the hell this isn't done in the first place: u-boot bootfiles in vfat p1, MeeGo in ext3/4/btrfs p2, and swap on p3, to make it play nice with Maemo)

If you want to make the vfat partition something other than what's on the downloadable image, just download the u-boot for n900 sources, change which partition it points to, build, append and flash.

Shucks, it doesn't look like I know how to do that...

[Hurrian]

Originally Posted by xxxxts

Shucks, it doesn't look like I know how to do that...

This file:

+#define CONFIG_EXTRA_ENV_SETTINGS \ +    "usbtty=cdc_acm\0" \ +    "stdin=vga\0stdout=vga\0stderr=vga\0" \ +    "setcon=setenv stdin ${con};" \ +        "setenv stdout ${con};" \ +        "setenv stderr ${con}\0" \ +    "sercon=setenv con serial; run setcon\0" \ +    "usbcon=setenv con usbtty; run setcon\0" \ +    "vgacon=setenv con vga; run setcon\0" \ +    "loadaddr=0x82000000\0" \ +    "meegoargs=setenv bootargs\0" \ +    "loadbootscript=fatload mmc 0 ${loadaddr} boot.scr\0" \ +    "bootscript=echo Running bootscript from mmc ...; " \ +        "source ${loadaddr}\0" \ +    "loaduimage=fatload mmc 0:3 ${loadaddr} uImage\0" \ +    "mmcboot=echo Booting from mmc ...; " \ +        "run meegoargs; " \ +        "bootm ${loadaddr}\0" \ +    "noloboot=echo Booting NOLO supplied kernel ...; " \ +        "setenv atags ${nolo_atagaddr};" \ +        "bootm ${nolo_kernaddr}\0" +

"loaduimage=fatload mmc 0:3 ${loadaddr} uImage\0" \

This is the interesting part.

Wait a bit, I'll get a u-boot image out.

[xxxxts]

Originally Posted by Hurrian

This file:

+#define CONFIG_EXTRA_ENV_SETTINGS \ +    "usbtty=cdc_acm\0" \ +    "stdin=vga\0stdout=vga\0stderr=vga\0" \ +    "setcon=setenv stdin ${con};" \ +        "setenv stdout ${con};" \ +        "setenv stderr ${con}\0" \ +    "sercon=setenv con serial; run setcon\0" \ +    "usbcon=setenv con usbtty; run setcon\0" \ +    "vgacon=setenv con vga; run setcon\0" \ +    "loadaddr=0x82000000\0" \ +    "meegoargs=setenv bootargs\0" \ +    "loadbootscript=fatload mmc 0 ${loadaddr} boot.scr\0" \ +    "bootscript=echo Running bootscript from mmc ...; " \ +        "source ${loadaddr}\0" \ +    "loaduimage=fatload mmc 0:3 ${loadaddr} uImage\0" \ +    "mmcboot=echo Booting from mmc ...; " \ +        "run meegoargs; " \ +        "bootm ${loadaddr}\0" \ +    "noloboot=echo Booting NOLO supplied kernel ...; " \ +        "setenv atags ${nolo_atagaddr};" \ +        "bootm ${nolo_kernaddr}\0" +

This is the interesting part.

Wait a bit, I'll get a u-boot image out.

I am so lost... what I am trying to do is create an image for my 16GB card with 2GB for NITDroid (U12), 6GB for MeeGo(CE 1.2.0.90.6.20110630.4.DE.2011-07-01.1), and the rest for storage (FAT32) so I can triboot. After I make this image I intend of uploading the image on here to make it easier for everyone else... this is going on an MMC not eMMC.

[ivyking]

that's fairly easy !
u-boot scripts are generated from simple command files, that are then converted to as appropriate script by using mkimage.

an example command file :

mmc init
fatload mmc1 0 0x82000000 /meegos-kernel
setenv bootargs 'root=/dev/mmcblkXpY rootwait console=tty0 omapfb.vram=0:2M,1:2M,2:2M mtdoops.mtddev=2 nosplash'
bootm 0x82000000

meegos-kernel is to be replaced by the actual meego kernel uImage name,
mmcblkXpY is to be replace by the partition where you installed meego, please note that

X=0 for sd
X=1 for emmc

yes they are the reverse of maemo's ordering.

Y is the number of the partition where meego is installed.

when you are done save the file, convert it to a u-boot script called boot.scr by :

mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "MeeGo" -d commandFileName boot.scr

[xxxxts]

Originally Posted by ivyking

that's fairly easy !
u-boot scripts are generated from simple command files, that are then converted to as appropriate script by using mkimage.

an example command file :

mmc init
fatload mmc1 0 0x82000000 /meegos-kernel
setenv bootargs 'root=/dev/mmcblkXpY rootwait console=tty0 omapfb.vram=0:2M,1:2M,2:2M mtdoops.mtddev=2 nosplash'
bootm 0x82000000

meegos-kernel is to be replaced by the actual meego kernel uImage name,
mmcblkXpY is to be replace by the partition where you installed meego, please note that

X=0 for sd
X=1 for emmc

yes they are the reverse of maemo's ordering.

Y is the number of the partition where meego is installed.

when you are done save the file, convert it to a u-boot script called boot.scr by :

mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "MeeGo" -d commandFileName boot.scr

Okay... I am still very confused - I flash my SD card using these instructions;

http://wiki.meego.com/ARM/N900/Install/MMC#Windows

With the exception of #11, put my SD card into my phone and boot into Maemo. However due to the way the image has partitioned my SD card I cannot access it as storage, thus also making it very difficult to install NITDroid on - I might be a little mixed up but I don't see how this so much has to do with u-boot...

[xxxxts]

I am not throuly frustrated, I cannot think of anything else to do...

[xxxxts]

Bump for desperation.

[Daneel]

It actually would be cool if they released flashable FAT images, my bet is more people would try out/test meego.