Update: Yes, it’s using the big.LITTLE switcher. Look at the dmesg output below closely.
I finally got the ODROID-XU to boot, using the official Fedora 19 image.
I can’t get any display output on anything, and I’ve tried HDMI and DP in various configurations. So I had to do everything blind.
Firstly I wrote the official image to the SD card, put that into the ODROID-XU, and booted it. The blue flashing light indicates that something is happening. By examining my DHCP server’s logs I could guess that an IP was being assigned, but there was no ssh or other port open.
So I pulled the SD card, mounted it up in virt-rescue and was able to at least confirm that the ODROID had booted, by looking at /var/log/messages on /dev/sda3 on the card.
My guess was that firewalld was the problem. Since the card has an ARM guest and the virt-rescue host I was using is x86-64, I was not able to just chroot into the disk image and start using systemctl commands. Instead, I masked firewalld by linking this file:
Putting the SD card back into the ODROID and booting .. it worked!
Unfortunately I cannot recommend the ODROID-XU, because there’s just far too much trouble getting the display to work (or rather, I have gone through a lot of different cables, and not got anything to work, and that is not good).
The other reason I cannot recommend this is that this is running some ancient Android kernel (3.4.5), hence no KVM. But also I suspect this must be running the ARM big.LITTLE switcher underneath (search for hypervisor on this page and see this page). For whatever reason, only 4 CPU cores are visible:
Here is dmesg from the machine:
