Hi Marcus, Thanks for your efforts of getting us a building JeOS image at all. :) Am 05.01.2014 19:14, schrieb Marcus Schäfer:
All my attempts were based on
- berryboot and kernel-raspberry
Sorry, I have no idea what berryboot is. That's something we're neither using in the JeOS image nor have packaged in Factory:Contrib, it seems?
I think you tried with
- u-boot and kernel-default + dtb
Is that correct ?
I left the bootcode.bin etc. in place and based upon that I tried booting different binaries via Config.txt: kernel=zImage (JeOS-raspberrypi defaults) => OK, but no way to specify initrd in Config.txt kernel=zImage, device_tree=bcm2835-rpi-b.dtb, device_tree_address=0x100 => no boot (arguments no longer valid?) kernel=u-boot.bin (u-boot-rpib patched to load our boot.scr) boot/linux.vmx + boot/initrd.uboot boot/linux.vmx + boot/initrd.uboot + bcm2835-rpi-b.dtb boot/linux.vmx + bcm2835-rpi-b.dtb boot/linux.vmx zImage-3.12.2-2-default + bcm2835-rpi-b.dtb zImage-3.12.2-2-default + boot/initrd.uboot + bcm2835-rpi-b.dtb => U-Boot on HDMI, but no output after "Starting kernel ..." Alex told me the preferred way to boot were to use U-Boot everywhere, thus my efforts to get a working setup. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org