Created attachment 895 [details] screen shot! When building a core-image-minimal with poky-tiny distribution, booting it will result in a hang with last message: "Booting from ROM...". Also you can get an image from here: http://autobuilder.yoctoproject.org/pub/nightly-tiny/ Tested in master: commit ee8d3fb19fb0132812dec2bde1dfb7026deb642d Date: Fri Oct 19 13:03:32 2012 +0000
How are you trying to boot it? I suspect you may be just running with runqemu. If so, the problem is that runqemu isn't particularly aware of poky-tiny images. By default poky-tiny doesn't support VGA consoles and only writes to the serial console. The other thing is the kernel doesn't have block or filesystem support (hrm... I don't think, we may have broadened support a bit) but by default it expects that you are using an initramfs. Try booting with: $ qemu -kernel /path/to/kernel -initrd /path/to/core-image-minimal-qemux86.cpio.gz -append "root=/dev/ram0 console=ttyS0" -nographic
poky-tiny is in meta-yocto, recategorize as appropriate.
Thank you for your response. Indeed I was using runqemu. I tried to follow your suggestion and use "qemu" instead of "runqemu" but even after sourcing the environment from the apropiate toolchain for my machine, I get the folowing message: "qemu: command not found" I tried to use full path to binary (./sysroots/x86_64-pokysdk-linux/usr/bin/qemu) but I get: "-bash: ./sysroots/x86_64-pokysdk-linux/usr/bin/qemu: No such file or directory" If runqemu does not work for poky-tiny images, please suggest me another method with which to test this. /Cornel
Try using qemu-system-i386 rather than "qemu".
Stoicescu, any update here? Have you been able to boot a poky-tiny minimal image?
It worked with qemu-system-i386 -kernel /path/to/kernel -initrd /path/to/core-image-minimal-qemux86.cpio.gz -append "root=/dev/ram0 console=ttyS0" -nographic branch: master commit: 93c04c16e45a3c8f60f8ffc0b26a78c24bda71da
This bug is really about support for poky-tiny with runqemu. Updating the title and categorization accordingly.
Actually, turns out this is then a dup of Bug 2612. *** This bug has been marked as a duplicate of bug 2612 ***