Re: [ANNOUNCE] qi-bootmenu-0.2

2010-11-29 Thread David Garabana Barro
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:0x0004(qi),0x0004(depr-
ub-env),0x0080(kernel),0x000a(depr),0x0004(identity-
ext2),0x0f6a(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?


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-11-29 Thread David Garabana Barro
On Sábado 27 Noviembre 2010 15:46:03 Marc Andre Tanner escribió:

  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.

This is the output with qi-bootmenu 0.1

As said, it boots OS on any (2-3-5) partition:

~ # qi-bootmenu -d
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:
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'
kexec --append='loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init 
ro  mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(qi),0x0004(depr-
ub-env),0x0080(kernel),0x000a(depr),0x0004(identity-
ext2),0x0f6a(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 root=/dev/mtdblock6 
rootfstype=jffs2 loglevel=1 quiet splash' -l /mnt/mtdblock6/boot/uImage-
GTA02.bin
umount '/dev/mtdblock6'
kexec -e




signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-11-27 Thread Marc Andre Tanner
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?

 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.

Marc

-- 
 Marc Andre Tanner  http://www.brain-dump.org/  GPG key: CF7D56C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-11-23 Thread David Garabana Barro
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

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

This is my partition table:
/dev/mmcblk0p1   1  38   38896   83  Linux
/dev/mmcblk0p2  39 563  537600   83  Linux
/dev/mmcblk0p3 5642414 1895424   83  Linux
/dev/mmcblk0p42415   15326132218885  Extended
/dev/mmcblk0p524153041  642032   83  Linux
/dev/mmcblk0p63042   1508212329968   83  Linux
/dev/mmcblk0p7   15083   15326  249840   82  Linux swap / 
Solaris

Where:

/dev/mmcblk0p1 vfat partition, unused 
/dev/mmcblk0p2 ext3 Qtmoko
/dev/mmcblk0p3 ext3 Debian
/dev/mmcblk0p5 ext3 hackable:1
/dev/mmcblk0p6 reiserfs common data

Tried v0.1 again and it boots OS in partition you select.

Do you have any clue on what might be happening?

-- 
David Garabana Barro
jabber  google talk ID:da...@garabana.com
Clave pública PGP/GPG:  http://davide.garabana.com/pgp.html


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-08 Thread Treviño
Il giorno mer, 06/10/2010 alle 21.55 +0200, Marc Andre Tanner ha
scritto:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release 

Cool!
However, why not using this partition policy:
 - First partition used for both bootmenu kernel and rootfs
 - Other partitions and NAND for the other distros...




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-08 Thread Marc Andre Tanner
Marco Trevisan (Treviño) schrieb:
 Il giorno mer, 06/10/2010 alle 21.55 +0200, Marc Andre Tanner ha
 scritto:
 Hi,

 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release 
 
 Cool!
 However, why not using this partition policy:
  - First partition used for both bootmenu kernel and rootfs
  - Other partitions and NAND for the other distros...

The original idea was that it should be possible to swap the SD card
and the bootmenu should still be there and work as expected.
I therefore flash it into the NAND kernel partition. You can still
have a regular distro in the NAND rootfs partition. You just need
to place the distros kernel into the /boot folder as you would do
on a SD card.

Of course nothing prevents you from adding a bootmenu partition
to your SD card. The kernel doesn't care how it is started and
just runs its initramfs. The only 'problem' which I can think of
at the moment is, that it will present itself in the menu. So
you would have the possibility of a recursive bootmenu. This could
be taken care of by a parameter on the kernel command line which is
read by the initramfs.

Marc

-- 
  Marc Andre Tanner  http://www.brain-dump.org/  GPG key: CF7D56C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-08 Thread Marc Andre Tanner
Radek Polak schrieb:
 On Thursday 07 October 2010 16:25:03 Marc Andre Tanner wrote:
 
 No. It's the same as in the initial release (built sometime in February)
 I am not really up to date regarding the glamo timings, is it stable?
 What are the prefered settings? If you provide a patch I can add it.
 Or better yet someone should commit it to the openmoko git repository
 then I will pick it up 'automatically'.
 
 I am using it for 2 weeks now and it's stable. You can cherry pick commit 
 from 
 my repo:
 
 http://github.com/radekp/qi.git
 
 http://github.com/radekp/qi/commit/b214400c048857e0f2156028bcd7a16397094a7d

Thanks, I have queued it up.

Marc

-- 
  Marc Andre Tanner  http://www.brain-dump.org/  GPG key: CF7D56C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread Patryk Benderz
Dnia 2010-10-06, śro o godzinie 21:55 +0200, Marc Andre Tanner pisze:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release 
[cut]
Great! Shouldn't it also go to annou...@lists.openmoko.org
-- 
Patryk LeadMan Benderz
Linux Registered User #377521
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread giacomo 'giotti' mariani

 Hi,

 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release 

  http://www.brain-dump.org/projects/qi-bootmenu/

 with the following changes:

  - based on 2.6.34 this should hopefully fix some sd card
related problems

  - static NAND boot option in the menu, the NAND partition
is only mounted upon selection so there is no delay for
sd based boots.

To make NAND booting work out of the box it would be nice
if the distros (I tried SHR and QtMoko) could add their
kernels to the jffs2 images too.

At the moment you have to ssh into the device mount the
NAND partition, download their kernel and put it at the
right place. Something along the lines of: 

 ssh r...@$freerunner # the password is empty
 mkdir /mnt/mtdblock6
 mount -t jffs2 /dev/mtdblock6 /mnt/mtdblock6
 mkdir /mnt/mtdblock6/boot  cd /mnt/mtdblock6/boot
 wget $KERNEL
 mv $KERNEL uImage-GTA02.bin

Bonus points if the distros would place a bootlogo.png
alongside the kernel (current preferred dimension is
100x80)

  - visual feedback upon boot selection. There seems to be
a issue which ocassionally garbles parts of the 
font/text but I think it's better than before.

  - userspace updated to latest versions including EFL 1.0
beta release

  - integration of a cross toolchain into the build scripts.
this should make rebuilding everything a matter of
executing one shell script. Well at least in theory...

 Kernel and Qi ready to flash to your Freerunner can be found at:

  http://www.brain-dump.org/projects/qi-bootmenu/uImage-GTA02-bootmenu-0.2.bin
  http://www.brain-dump.org/projects/qi-bootmenu/qi-s3c2442-bootmenu-0.1.udfu

 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.

 The build scripts, in case anyone wants to rebuild the whole
 thing, can be found at:

  
 http://repo.or.cz/w/qi-bootmenu-system.git/snapshot/7c3a92f22e9498198212e4682b2fe078a676f1b5.tar.gz

 download and extract the tarball then run ./build.sh this will 
 download everything that is needed and then build the kernel +
 initramfs. See the README file for further information.

 What remains to be done is

  - add ubifs support

  - read partition labels? or some other way to display custom
text in the menu

  - gta01 support, this basically means kernel support in = 2.6.34
the kernel maximum size of 2MB including the initramfs
should be doable

  - ...

 Patches welcome.

 Have fun,
 Marc

   
Thanks.
__
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto 
spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread David Garabana Barro
On Miércoles, 6 de Octubre de 2010 21:55:44 Marc Andre Tanner escribió:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release
 
  http://www.brain-dump.org/projects/qi-bootmenu/


Only a question

Does the modified Qi includes 242 glamo timings patch?


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread David Garabana Barro
On Miércoles, 6 de Octubre de 2010 21:55:44 Marc Andre Tanner escribió:
 Hi,
 
 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release

Thanks a lot for the new release BTW :o)


signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread Marc Andre Tanner
David Garabana Barro schrieb:
 On Miércoles, 6 de Octubre de 2010 21:55:44 Marc Andre Tanner escribió:
 Hi,

 I finally had some time to hack on qi-bootmenu the result is
 a new 0.2 release

  http://www.brain-dump.org/projects/qi-bootmenu/
 
 
 Only a question
 
 Does the modified Qi includes 242 glamo timings patch?

No. It's the same as in the initial release (built sometime in February)
I am not really up to date regarding the glamo timings, is it stable?
What are the prefered settings? If you provide a patch I can add it.
Or better yet someone should commit it to the openmoko git repository
then I will pick it up 'automatically'.

I only found:

  http://dos.openmoko.pl/overclock/

but it seems you can change the timings at runtime too.

  ./memwrite $((0x4808)) $((0x1380))

Marc

-- 
  Marc Andre Tanner  http://www.brain-dump.org/  GPG key: CF7D56C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread David Garabana Barro
On Jueves, 7 de Octubre de 2010 16:25:03 Marc Andre Tanner escribió:
 David Garabana Barro schrieb:

  Does the modified Qi includes 242 glamo timings patch?
 
 No. It's the same as in the initial release (built sometime in February)
 I am not really up to date regarding the glamo timings, is it stable?
 What are the prefered settings? If you provide a patch I can add it.
 Or better yet someone should commit it to the openmoko git repository
 then I will pick it up 'automatically'.
 
 I only found:
 
   http://dos.openmoko.pl/overclock/
 
 but it seems you can change the timings at runtime too.
 
   ./memwrite $((0x4808)) $((0x1380))
 

Nop, it's no related with overclock (which is not stable for everyone).

Glamo timings are totally stable, because they are simply put at the values the 
glamo documentation says they should be.

More info:
http://www.mail-archive.com/community@lists.openmoko.org/msg60256.html

Here you have uboot patch:

http://www.bsdmn.com/openmoko/glamo/242/

And patched Qi:

http://www.mail-archive.com/community@lists.openmoko.org/msg60284.html

As it's not overclocking, and speedup is noticeable, it would be great if you 
put it by default on your Qi.

Thank you



signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [ANNOUNCE] qi-bootmenu-0.2

2010-10-07 Thread Radek Polak
On Thursday 07 October 2010 16:25:03 Marc Andre Tanner wrote:

 No. It's the same as in the initial release (built sometime in February)
 I am not really up to date regarding the glamo timings, is it stable?
 What are the prefered settings? If you provide a patch I can add it.
 Or better yet someone should commit it to the openmoko git repository
 then I will pick it up 'automatically'.

I am using it for 2 weeks now and it's stable. You can cherry pick commit from 
my repo:

http://github.com/radekp/qi.git

http://github.com/radekp/qi/commit/b214400c048857e0f2156028bcd7a16397094a7d

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[ANNOUNCE] qi-bootmenu-0.2

2010-10-06 Thread Marc Andre Tanner
Hi,

I finally had some time to hack on qi-bootmenu the result is
a new 0.2 release 

 http://www.brain-dump.org/projects/qi-bootmenu/

with the following changes:

 - based on 2.6.34 this should hopefully fix some sd card
   related problems

 - static NAND boot option in the menu, the NAND partition
   is only mounted upon selection so there is no delay for
   sd based boots.

   To make NAND booting work out of the box it would be nice
   if the distros (I tried SHR and QtMoko) could add their
   kernels to the jffs2 images too.

   At the moment you have to ssh into the device mount the
   NAND partition, download their kernel and put it at the
   right place. Something along the lines of: 

ssh r...@$freerunner # the password is empty
mkdir /mnt/mtdblock6
mount -t jffs2 /dev/mtdblock6 /mnt/mtdblock6
mkdir /mnt/mtdblock6/boot  cd /mnt/mtdblock6/boot
wget $KERNEL
mv $KERNEL uImage-GTA02.bin

   Bonus points if the distros would place a bootlogo.png
   alongside the kernel (current preferred dimension is
   100x80)

 - visual feedback upon boot selection. There seems to be
   a issue which ocassionally garbles parts of the 
   font/text but I think it's better than before.

 - userspace updated to latest versions including EFL 1.0
   beta release

 - integration of a cross toolchain into the build scripts.
   this should make rebuilding everything a matter of
   executing one shell script. Well at least in theory...

Kernel and Qi ready to flash to your Freerunner can be found at:

 http://www.brain-dump.org/projects/qi-bootmenu/uImage-GTA02-bootmenu-0.2.bin
 http://www.brain-dump.org/projects/qi-bootmenu/qi-s3c2442-bootmenu-0.1.udfu

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.

The build scripts, in case anyone wants to rebuild the whole
thing, can be found at:

 
http://repo.or.cz/w/qi-bootmenu-system.git/snapshot/7c3a92f22e9498198212e4682b2fe078a676f1b5.tar.gz

download and extract the tarball then run ./build.sh this will 
download everything that is needed and then build the kernel +
initramfs. See the README file for further information.

What remains to be done is

 - add ubifs support

 - read partition labels? or some other way to display custom
   text in the menu

 - gta01 support, this basically means kernel support in = 2.6.34
   the kernel maximum size of 2MB including the initramfs
   should be doable

 - ...

Patches welcome.

Have fun,
Marc

-- 
 Marc Andre Tanner  http://www.brain-dump.org/  GPG key: CF7D56C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community