Maybe Qi is not looking in where we think it was $ strings qi-s3c2442-andy_8b773038524299aa.udfu mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(cmdline),0x00800000(backupkernel),0x000a0000(extra),0x00040000(identity),0x0f6a0000(backuprootfs) console=ttySAC2,115200 init=/sbin/init ro console=tty0 loglevel=8 SD Card EXT2 P1 Kernel boot/uImage-GTA02.bin root=/dev/mmcblk0p1 SD Card EXT2 P2 Kernel root=/dev/mmcblk0p2
I get it, Qi expects the kernel to be on the same partition as the root file system, unlike that created by the Debian install.sh script. [EMAIL PROTECTED]:~# mount /dev/mmcblk0p1 on /media/card type ext3 (rw,data=ordered) /dev/mmcblk0p2 on /media/mmcblk0p2 type ext2 (rw,sync) so I # mv /media/mmcblk0p1/uImage-GTA02.bin /media/mmcblk0p2/uImage-GTA02.bin and edited out /dev/mmcblk0p1 from /media/mmcblk0p2/etc/fstab . And low an behold, after a whole minute of starting at a dark purple screen (as if you were already in production mode with not a single message about what is taking so long, from pressing power till now,) a X appears, and it's Debian's nodm! Conclusions: Debian team: notice that you'll have to ln or cp to uImage-GTA02.bin and not just uImage.bin to match Qi, and of course it should all be on the same partition... root and boot. As for booting into Debian from NOR, hmmm, well if Qi skips vfat partitions, then we can still have that too. Several misconceptions on http://wiki.openmoko.org/wiki/Qi , "I'll try to clear them up". And Qi team: please turn on the verbosity, starting at the purple screen can come after you've sold your first gold or platinum record album of a telephone. I don't suppose Qi is flexible like grub2 or whatever, so we will just have to cater to where it puts things.
