QEMU's OMAP ROM emulatopm would complain about lack of boot data.
Comparing the Ubuntu images with Angstrom images, I saw that the Ubuntu images had the same disk partition type and meta-data, but the filesystem would differ: FAT32 in the case of Angstrom and FAT16 for Ubuntu.
I've loop-mounted an image (with kpartx), copied over the files in the FAT partition, and reformated it with mkfs.msdos -F 32. This allowed QEMU to boot and start the kernel from the modified image.
Oliver compared with the jasper-initramfs code, which uses -F 32, so it would seem safe to force -F 32 in debian-cd as well (it currently is unspecified, so mkdosfs picks FAT16 according to the size of the partition), however I recommend this to be tested on target hardware configurations.
Hi
While testing the image Ubuntu Netbook pre-installed OMAP image (http:// cdimage. ubuntu. com/ubuntu- netbook/ ports/daily- preinstalled/ current/ maverick- preinstalled- netbook- armel+omap. img.gz) in QEMU, it wouldn't boot.
QEMU's OMAP ROM emulatopm would complain about lack of boot data.
Comparing the Ubuntu images with Angstrom images, I saw that the Ubuntu images had the same disk partition type and meta-data, but the filesystem would differ: FAT32 in the case of Angstrom and FAT16 for Ubuntu.
I've loop-mounted an image (with kpartx), copied over the files in the FAT partition, and reformated it with mkfs.msdos -F 32. This allowed QEMU to boot and start the kernel from the modified image.
Oliver compared with the jasper-initramfs code, which uses -F 32, so it would seem safe to force -F 32 in debian-cd as well (it currently is unspecified, so mkdosfs picks FAT16 according to the size of the partition), however I recommend this to be tested on target hardware configurations.
Thanks.