21:48 <gordan> Greetings.

21:49 <gordan> I'm trying to get a kernel with initramfs to boot on my peach pi, and I am having no success even though I have tried 3 different approaches.

21:49 <gordan> I can boot a kernel+dtb itb image using vboot without problems.

21:50 <gordan> If I add a ramdisk section to the its, mkimage, vbutil_kernel ... the resulting itb no longer boots.

21:50 <gordan> I tried various load/entry addresses (0x50000000 works on snow, not on peach pi), I tried addresses in various other ranges with no success.

21:51 <gordan> I also tried several nv u-boot images, including the one from here: http://linux-exynos.org/dist/chromebook/nv_uboot/nv_uboot-peach-pi.kpart

21:52 <gordan> The one mentioned here: https://gist.github.com/EmbeddedAndroid/54d6a7f8a8f13e8fdf71

21:52 <gordan> And one I built myself from mainline u-boot today.

21:52 <gordan> The two I downloaded end with a blank screen and a locked up machine.

21:52 <gordan> The one I built myself hangs forever at "Starting kernel ..." message.

21:53 <gordan> This happens even if I use the exact same itb image that boots just fine using vboot if I pack it up using vbutil_kernel.

21:54 <gordan> The load address in u-boot I am using is 0x42000000, again, because that works on snow.

21:55 <gordan> I also building the initramfs (raw cpio) into the kernel itself using the relevant option, and tried booting that using vboot, but that also causes vboot to fail to boot (beeps, returns back to the boot screen waiting for Ctrl-D or Ctrl-U to be pressed).

21:56 <gordan> The kernel I am using is the ChromeOS one with the 3 patches from arch to get fbdev and wifi to work.

21:58 <gordan> Is there some magic load/entry address for the initrd I need? Past experience with various other devices implies that more or less anywere in the memory should be fine as long as the various components don't end up overlapping and clobbering each other, but maybe the memory map on the peach is boobytrapped.

21:58 <gordan> Any ideas welcome.