need help in order to make a proper boot.img for liquid

[Guest the tman]

hello ,

i try to make a boot.img for liquid.

so far i use

http://gitorious.com/liquide/kernel

or

http://gitorious.com/~roggin/liquide/roggins-kernel

in order to make the zimage by using the command

make ARCH=arm CROSS_COMPILE=~/arm-2010q1/bin/arm-none-linux-gnueabi-

to compile the kernel in order to have the ramdisk i take the boot.img that come from roggin CM6 rom an split it with command

split_bootimg.pl boot.img

it create two file: boot.img-kernel boot.img-ramdisk.gz so far i understand that boot.img-kernel is the zimage that roggin have made and boot.img-ramdisk.gz is the ramdisk Yet, when i try to recreate the boot.img without modify anything with:

liquidmkbootimg  --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --deploy 1 -o newboot.img

and booting it with

fastboot-linux -i 0x0502 boot newboot.img

the bootloader is stuck on 'loading boot'... when i flash it with

fastboot-linux -i 0x0502 flash  boot newboot.img

it don't boot at all!

booting the initial boot.img of roggin work with the same command work and the boot.img load

so i would like some help in order to make proper boot.img for liquid for either froyo , gingerbread CM or aosp

because i don't know if the way i use for make a ramdisk, kernel and boot.img is good

there is a way to make myself the ramdisk or i need to take it from other boot.img?

what is the difference between the ramdisk made by cyanogenMOd 7 (or6) compilation and the ramdisk taken out of other boot.img?

thanks for your help

(thanks disco, pphuson and roggins for the kernel)

(thanks xian and cleaton / liquidCM_devicetree for the device tree)

(thanks malez for the wonderfull recovery)

Edited February 6, 2011 by the tman

[Guest fear_factory84]

your post is very interesting, and if you get the missing part could be a base to build a step by step tutorial about liquid kernel compilation...

[Guest the tman]

nobody have any suggestion?

[Guest koudelka]

nobody have any suggestion?

I have had problem with using boot.img-ramdisk.gz file before, try using repackboot.pl I have had best experience with that (just modify it to use liquidmkbootimg and add deploy option) http://android-dls.com/files/apps/repack-bootimg.zip

also i recommend you joining us at IRC if you want to talk :P #acer-liquid @freenode

Edited February 6, 2011 by koudelka

[Guest the tman]

thanks for your help koudelka ,i will try

[Guest Borkata]

There are two things that you should consider:

1) First set vm_split 2G if you gonna use your boot.img on stock acer rom or based on stock. Otherwise use 3G split option for CM, MIUI or any ports from other devices.

2) If you have problems with deploy 1 try 0 or 2.