On Sep 9, 2010, at 02:32, ext [email protected] wrote: > I'm trying to run the latest Meego N900 image on QEMU, but I'm getting an > error. Image creation and qflash complete with no errors, but I get a problem > when I launch the image. Here's my command to build and launch the image: > > sudo mic-image-creator --run-mode=0 --use-comps --cache=mycachedir > --format=raw --arch=armv7l --save-kernel > --config=meego-core-armv7l-n900-1.0.90.1.20100907.1.ks > > ./qflasher -m rx51 -k > meego-core-armv7l-n900-1.0.90.1.20100907.1-1.0.90.20100908.1624-vmlinuz-2.6.35.3-6.2-n900 > -o meego_qemu_nand.img -yk > > sudo qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -sd empty -sd > meego-core-armv7l-n900-1.0.90.1.20100907.1-1.0.90.20100908.1624-mmcblk0p.raw > -serial stdio -clock unix > > > Here's the error I see when it is launched: > qemu: hardware error: no boot device found > CPU #0: > R00=00000000 R01=00000000 R02=00000000 R03=00000000 > R04=00000000 R05=00000000 R06=00000000 R07=00000000 > R08=00000000 R09=00000000 R10=00000000 R11=00000000 > R12=00000000 R13=00000000 R14=00000000 R15=400140a4 > PSR=400001d3 -Z-- A svc32 > Abort > > Has anyone else seen this? I believe I am running the latest QEMU, but is > there a way to verify this?
It works, I just tested with the prebuilt images. Check that you are running the latest QEMU and that your NAND image is not corrupted. I would guess the latter in which case fetching a known-good NAND image and rewriting your new kernel on it should fix the problem. Why do you run QEMU as root? Regards, Juha _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
