[ANNOUNCE] qi-bootmenu-0.2

David Garabana Barro david at garabana.com
Mon Nov 29 11:42:43 CET 2010


On Sábado 27 Noviembre 2010 15:46:03 Marc Andre Tanner escribió:
> On Tue, Nov 23, 2010 at 11:41:10PM +0100, David Garabana Barro wrote:
> > O Mércores, 6 de Outubro de 2010, Marc Andre Tanner escribiu:
> > > If you flash the above Qi version, pressing AUX should boot from
> > > NAND and thus present the bootmenu independently of the content
> > > of your sd card. If you don't want to use my patched Qi then
> > > get it to boot from NAND in some other way, for example by putting
> > > noboot-GTA02 files into your sd partitions. Let me know how it
> > > works for you.
> > 
> > For me your Qi it's allways booting first uSD partition unless I add
> > "noboot- GTA02" to /boot directories
> 
> Do you feel the vibration when you press AUX?

I feel vibration when I initially press power. Pressing AUX anytime between 
pressing power and bootmenu is shown does nothing, or at least I feel nothing 
is done.

> > If I create noboot-GTA02 on every uSD partition, menu is booted, but if I
> > select any uSD partition from bootmenu, it allways boot the distro on
> > /dev/mmcblk0p5
> 
> Don't know what the problem could be, you could try to ssh into the phone
> and run "qi-bootmenu -d".

~ # qi-bootmenu -d
Couldn't identify filesystem on '/dev/mmcblk0'
No kernel found at '/mnt/mmcblk0p1/boot/zImage-GTA02.bin'
mount: Device or resource busy
mount: Device or resource busy
mount: Device or resource busy
Unsupported filesystem 'reiserfs' on '/dev/mmcblk0p6'
Unsupported filesystem 'swap' on '/dev/mmcblk0p7'
Partitions:
/dev/mtdblock6
/dev/mmcblk0
/dev/mmcblk0p1
/dev/mmcblk0p2
/dev/mmcblk0p3
/dev/mmcblk0p5
/dev/mmcblk0p6
/dev/mmcblk0p7
Built in filesystems:
sysfs
rootfs
bdev
proc
tmpfs
devtmpfs
sockfs
pipefs
anon_inodefs
devpts
ext3
ext2
ramfs
jffs2
Bootable images:
mount -t jffs2 /dev/mtdblock6 /mnt/mtdblock6
kexec --append='loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init 
ro  mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(depr-
ub-env),0x00800000(kernel),0x000a0000(depr),0x00040000(identity-
ext2),0x0f6a0000(rootfs)  g_ether.dev_addr=00:1F:11:01:3D:E1 
g_ether.host_addr=00:1F:11:01:3D:E2 rootfstype=jffs2 root=/dev/mtdblock6 qi-
bootmenu-args="-i /dev/mtdblock6" lpj=498688 rootwait root=/dev/mtdblock6 
rootfstype=jffs2 loglevel=1 quiet splash' -l /mnt/mtdblock6/boot/uImage-
GTA02.bin
umount /dev/mtdblock6
kexec -e


/dev/mmcblk0p1 has no OS on it, and /dev/mmcblk0p6 is a data partition.
I have OS in /dev/mmcblk0p2, /dev/mmcblk0p3 and /dev/mmcblk0p5

Does this give you any clue about what is happening?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/community/attachments/20101129/c0275e9d/attachment-0001.pgp 


More information about the community mailing list