Hello Loic, Am 03.10.2016 um 12:54 schrieb LOIC DEVULDER:
I saw that Andreas has a WIP on GeekBox (https://en.opensuse.org/HCL:GeekBox) and, as I understand, it’s possible to boot openSUSE with both the vendor U-Boot or the mainline U-Boot.
That is likely not correct. It only works with the vendor U-Boot so far. It is possible to boot into U-Boot with mainline-based patches of mine, but not yet from U-Boot into openSUSE for lack of drivers.
Here my question (finally!): what openSUSE image do I use? And where to find the initrd? I found a kernel in the generic JeOS image but no initrd...
Short answer is: Use the JeOS-rootfs for any new boards. Yes, it does not contain an initrd, because it's not for a specific board. Theoretically you could use dracut to create a "no-host" initrd, but then you might run into size limitations for the initrd flash partition. The easiest way for new board enablements is to (cross-)compile an upstream defconfig kernel yourself locally (make CROSS_COMPILE=aarch64-suse-linux- CC=aarch64-suse-linux-gcc-6 ARCH=arm64 ...), boot it and then update/reinstall kernel-default. On the GeekBox I have not yet tried that step, since I would rather have the kernel+initrd loaded from SSD than flashing it to eMMC. Chances are there's no .dts for your device yet, which means you'll need to hack on the kernel yourself anyway, which is quickest with a non-OBS kernel setup and may require you to use linux-next.git. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org