This does sound quite old, yeah. Can you update your u-boot version to something more recent? There's a good chance Linux never gets to see
Hi Alex, Thanks again. You wrote: the dtb Basically I don't dare to install a new uboot and I'm not sure there is one from Globalscale. I tried a different approach, by compiling the kernel with: CONFIG_ARM_APPENDED_DTB=y # CONFIG_ARM_ATAG_DTB_COMPAT is not set According to serveral sources one should be able to take the generated zImage, add armada-370-mirabox.dtb to it (as in "cat zImage armada-370-mirabox.dtb > mynewzImage") and convert it to a uImage with mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n linux-3.9-rc5 -d mynewzImage uImage You might guess... still nothing after booting on the mirabox, still stops after Starting kernel: 3466263 bytes read ## Booting kernel from Legacy Image at 06400000 ... Image Name: linux-3.9-rc5 Created: 2013-04-08 17:31:00 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3466199 Bytes = 3.3 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Compared to my previous uImage it is a bit larger which is due to the armada-370-mirabox.dtb I think, but other than that I don't see anything that hints that it understands the dtb... I see quite some emails on the http://www.spinics.net/lists/arm-kernel email list discussing kernel things about the mirabox, supposedly some of the persons on there have a running mirabox with a new kernel (at least newer than I have). Do you know anyone over there which I can ask if I can use their kernel source & kernel image? I have uploaded my linux 3.9 rc 5 .config file here: http://pastebin.com/fswx9Q23. If you have more things I might try, that would be wonderful, if not, then thanks a lot for taking the time to think this over! Best regards, Ge -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org