ubuntu-phone team mailing list archive

[Ricardo Salveti de Araujo <ricardo.salveti@xxxxxxxxxxxxx>]

On Tue, Mar 18, 2014 at 1:19 PM, Corvus <lcuervo@xxxxxxxxx> wrote:
> I added this to the default cmdline using Boardconfig.mk:
>
> datapart=/dev/block/mmcblk0p9 boot=touch debug rw console=tty0,115200n8
> no_console_suspend=1
>
> I modify too the init scrip so now it does ln -s /dev/userdata
> /dev/block/mmcblk0p9
>
> Neither of this work. And it's supposed that if a data partition is not
> found it launch adbd so i can get a shell, and this doesnt happens.
>
> About creating the initrd... yes, i know it and this is the way that we do
> (integrated in the build scripts). We use a folder with all files extracted,
> made our modifications and the build Makefile create the ramdisk.img, but we
> extract the files from
> https://launchpad.net/ubuntu/trusty/+package/ubuntu-touch-generic-initrd,
> using i386 arch and i'm not really sure that this has been tested, because
> by example in this package the conf/arch.conf file has armhf inside it but
> the package is for i386. This is why i try to compile the sources of this
> package, to make sure that all files are for i386.

The emulator uses the x86 initrd, so it's consuming a valid i386 based initrd.

> Oh, and modify the init by hand doesnt work, because at every build the
> package is downloades and the ramdisk re-created using it, so if you create
> a ramdisk at hand will be deleted.

You can also edit your boot.img by hand as well (using abootimg), so
you can then just replace your custom initrd and use it to boot your
device.

Cheers,

-- 
Ricardo Salveti de Araujo