ubuntu-phone team mailing list archive

[Dmitrijs Ledkovs <xnox@xxxxxxxxxx>]

On 8 October 2013 22:12, Patrick Seemann <patsee14@xxxxxxxxx> wrote:
> Good evening,
>
> I'm porting ubuntu touch to Samsung Galaxy Tab 10.1 wifi. Currently working
> on the flipped image.
>
> To make the tablet boot up correctly I changed
> /usr/share/initramfs-tools/scripts/touch to include "UA" in the partlist, as
> this is the name of the data partition of my tab. But when booting the
> kernel still panics with "initrd: Couldn't find data partition. Spawning
> adbd ...". I've had this issue before and also posted on the list, and it
> turned out adding datapart= ... to the cmdline sort of works (kernel does
> not panic anymore).
>
> ... But, to tackle the real issue, that is adding "UA" to the partlist does
> not work, I wanted to check if I'm editing the right files, so I completely
> removed the following lines from the touch script:
>
>> if [ -z "$path" ]; then
>> echo "initrd: Couldn't find data partition. Spawning adbd ..." >/dev/kmsg
>> || true
>> panic "Couldn't find data partition. Spawning adbd ..."
>> fi
>
>
> yet I get exactly that error message when booting. Why? I deleted these
> lines t o.O
>
> That must mean I'm editing the wrong file?! Any ideas?

that file is used by initramfs-tools to generate initramfs and that's
the copy that you actually boot.

cd $(mktemp -d)
gzip -dc /path/to/ramdisk.img | cpio -ivd
<edit touch/script>
find . | cpio -o -H newc | gzip > ../new-ramdisk.img

To update files inside your initramfs.

Alternatively you can boot with following cmdline arg:
datapart=/dev/mydevicename
(real device name, not symlink "persistent" / "logical" name)

Regards,

Dmitrijs.