Am 16.10.2016 um 00:00 schrieb Andreas Färber:
Note that there is no .dts file for the Pi Zero in the v4.7 kernel: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm... Only v4.9 will have it. Not sure how our U-Boot version handles that. Can you press a key to get a U-Boot prompt, then enter "printenv fdtfile" and share the output?
U-Boot> printenv fdtfile fdtfile=bcm2835-rpi-zero.dtb bcm2835-rpi-zero.dtb doesn't exist in dtb-bcm2835 4.7, leading to: libfdt fdt_check_header(): FDT_ERR_BADMAGIC before it enters GRUB with my modified image or runs our boot.scr with the official image. The workaround then is very easy: a) Interrupt U-Boot and manually load an existing .dtb file: load mmc 0:2 $fdt_addr_r dtb/bcm2835-rpi-b-plus.dtb or with my experimental GRUB based image boot/dtb/bcm2835-rpi-b-plus.dtb b) Create a bcm2835-rpi-zero.dtb symlink to that file: cd /boot/dtb ln -s bcm2835-rpi-b-plus.dtb bcm2835-rpi-zero.dtb This step may need to be repeated after zypper up/dup installs new dtb-bcm2835 packages. If you create the symlink on your host, you can skip step a). Eh voilà, you get a booting Tumbleweed system. 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