Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-16 Thread Per Andersson
tags 512589 + pending
thanks

I plan to assimilate the changes Luca made and the
package related with this bug.


On Thu, Feb 12, 2009 at 7:30 PM, Martin Michlmayr t...@cyrius.com wrote:
 * Luca Capello l...@pca.it [2009-02-12 17:07]:
 a) check that it works on other devices (QNAP, Kurobox, etc.); I cc:ed
Martin Michlmayr, who uploaded the last version and I guess still has
some U-Boot-capable devices

 I cannot test on the Kurobox right now and I haven't managed to create
 a proper config file for the QNAP devices yet (what's the best way to
 find out where the u-boot environment is stored?).  I hope Per can
 test the new package on the Kurobox.

Sorry, this is a no go. My Kurobox is offline and in a
different country than me. :(


-- Per



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-13 Thread Luca Capello
Hi Martin!

On Thu, 12 Feb 2009 20:30:09 +0100, Martin Michlmayr wrote:
 * Luca Capello l...@pca.it [2009-02-12 17:07]:
 a) check that it works on other devices (QNAP, Kurobox, etc.); I cc:ed
Martin Michlmayr, who uploaded the last version and I guess still has
some U-Boot-capable devices

 I cannot test on the Kurobox right now and I haven't managed to create
 a proper config file for the QNAP devices yet (what's the best way to
 find out where the u-boot environment is stored?).

I guess the proper location is /proc/mtd:
=
debian-gta02:~# cat /proc/mtd
dev:size   erasesize  name
mtd0: 0020 0001 physmap-flash.0
mtd1: 0004 0002 u-boot
mtd2: 0004 0002 u-boot_env
mtd3: 0080 0002 kernel
mtd4: 000a 0002 splash
mtd5: 0004 0002 factory
mtd6: 0f6a 0002 rootfs
debian-gta02:~#
=

Thx, bye,
Gismo / Luca


pgphdXOGikbDI.pgp
Description: PGP signature


Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-13 Thread Martin Michlmayr
* Luca Capello l...@pca.it [2009-02-13 14:04]:
 I guess the proper location is /proc/mtd:

Unfortunately there's no separate u-boot partition on the devices I
have.

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-12 Thread Timo Juhani Lindfors
Luca Capello l...@pca.it writes:
 # MTD device name Device offset   Env. size   Flash sector size   
 Number of sectors
 /dev/mtd2   0x  00040002  
   2

Aha, with this change it looks good:

$ sudo fw_printenv
boot_menu_timeout=300
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 
console=tty0 loglevel=8 regular_boot
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ext2 
root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M persistent_log=127M; mmcinit; 
ext2load mmc 1 0x3200 ${sd_image_name}; bootm 0x3200
bootdelay=1
menu_1=Boot from Flash: setenv bootargs ${bootargs_base} ${mtdparts}; nand 
read.e 0x3200 kernel 0x20; bootm 0x3200
menu_2=Reboot: reset
menu_3=Power off: neo1973 power-off
menu_4=Set console to USB: setenv stdin usbtty; setenv stdout usbtty; setenv 
stderr usbtty
menu_5=Set console to serial: setenv stdin serial; setenv stdout serial; setenv 
stderr serial
menu_6=SD/uImage2.bin: setenv bootargs ${bootargs_base} ${mtdparts} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 
1 0x3200 uImage2.bin; bootm 0x3200
menu_7=SD/uImage3.bin: setenv bootargs ${bootargs_base} ${mtdparts} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 
1 0x3200 uImage3.bin; bootm 0x3200
mtddevname=nor
mtddevnum=0
mtdids=nor0=physmap-flash,nand0=neo1973-nand
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)
partition=nor0,0
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0xfe
quiet=1
sd_image_name=uImage.bin
splashimage=nand read.e 0x3200 splash 0x5000; unzip 0x3200 0x880 
0x96000
stderr=usbtty
stdin=usbtty
stdout=usbtty
usbtty=cdc_acm

li...@ginger:~$ sudo fw_setenv bootcmd 'setenv bootargs ${bootargs_base} 
${mtdparts} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M; 
mmcinit; ext2load mmc 1 0x3200 ${sd_image_name}; bootm 0x3200'

li...@ginger:~$ sudo fw_printenv

 boot_menu_timeout=300
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 
console=tty0 loglevel=8 regular_boot
bootdelay=1
menu_1=Boot from Flash: setenv bootargs ${bootargs_base} ${mtdparts}; nand 
read.e 0x3200 kernel 0x20; bootm 0x3200
menu_2=Reboot: reset
menu_3=Power off: neo1973 power-off
menu_4=Set console to USB: setenv stdin usbtty; setenv stdout usbtty; setenv 
stderr usbtty
menu_5=Set console to serial: setenv stdin serial; setenv stdout serial; setenv 
stderr serial
menu_6=SD/uImage2.bin: setenv bootargs ${bootargs_base} ${mtdparts} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 
1 0x3200 uImage2.bin; bootm 0x3200
menu_7=SD/uImage3.bin: setenv bootargs ${bootargs_base} ${mtdparts} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 
1 0x3200 uImage3.bin; bootm 0x3200
mtddevname=nor
mtddevnum=0
mtdids=nor0=physmap-flash,nand0=neo1973-nand
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)
partition=nor0,0
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0xfe
quiet=1
sd_image_name=uImage.bin
splashimage=nand read.e 0x3200 splash 0x5000; unzip 0x3200 0x880 
0x96000
stderr=usbtty
stdin=usbtty
stdout=usbtty
usbtty=cdc_acm
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ext2 
root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M; mmcinit; ext2load mmc 1 
0x3200 ${sd_image_name}; bootm 0x3200

I did a test reboot and the system seemed to boot up nicely with updated kernel 
boot parameters:

$ cat /proc/cmdline
rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 
loglevel=8 regular_boot 
mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)
 rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M

Thanks a lot for packaking the fixed version!



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-12 Thread Luca Capello
tags 512589 + patch
thanks

Hi Timo!

On Thu, 12 Feb 2009 10:50:55 +0100, Timo Juhani Lindfors wrote:
 Luca Capello l...@pca.it writes:
 # MTD device nameDevice offset   Env. size   Flash sector size   
 Number of sectors
 /dev/mtd2   0x  00040002 
2

 Aha, with this change it looks good:
[...]
 I did a test reboot and the system seemed to boot up nicely with
 updated kernel boot parameters:
[...]
 Thanks a lot for packaking the fixed version!

I prepared another package:

1) set version to 20081215, the last commit to tools/env/ [1]

2) add a NEWS.Debian file, now fw_env.config requires a fifth parameter

3) add newline to EOF for qnap_ts101.config (this is mostly an aesthetic
   change, but it disturbed me...)

4) add openmoko_gta02.config, which I successfully tested [2]

5) imported the Debian package into a Git repository at [3]


Timo, can you confirm that the new package works as well, please?

Before uploading (I will *not* upload a source NMU), there are at least
the following two issues to be fixed:

a) check that it works on other devices (QNAP, Kurobox, etc.); I cc:ed
   Martin Michlmayr, who uploaded the last version and I guess still has
   some U-Boot-capable devices

b) finalize the debian/changelog and debian/NEWS entries


Per, Martin: I am not a boot loader expert, but uboot-envtools will be
used by the Debian-on-Openmoko installer, thus I can help in maintaining
the package as well as sponsoring, if needed.

Thx, bye,
Gismo / Luca

Footnotes: 
[1] 
http://git.denx.de/?p=u-boot.git;a=commit;h=22525779cb51f1bbe4e96fea7b778de1935a5a69
[2] http://people.debian.org/~gismo/tmp/uboot-envtools/
[3] http://git.debian.org/?p=users/gismo/uboot-envtools.git;a=summary


pgpWDjAY3QuSV.pgp
Description: PGP signature


Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-12 Thread Martin Michlmayr
* Luca Capello l...@pca.it [2009-02-12 17:07]:
 a) check that it works on other devices (QNAP, Kurobox, etc.); I cc:ed
Martin Michlmayr, who uploaded the last version and I guess still has
some U-Boot-capable devices

I cannot test on the Kurobox right now and I haven't managed to create
a proper config file for the QNAP devices yet (what's the best way to
find out where the u-boot environment is stored?).  I hope Per can
test the new package on the Kurobox.

 Per, Martin: I am not a boot loader expert, but uboot-envtools will be
 used by the Debian-on-Openmoko installer, thus I can help in maintaining
 the package as well as sponsoring, if needed.

I've sponsored Per's uploads so far, but I'm happy for you to take
over.  Please coordinate with Per.
-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-12 Thread Timo Juhani Lindfors
Luca Capello l...@pca.it writes:
 Timo, can you confirm that the new package works as well, please?

20081215-1~gismo.1 seems to let me change and print environment on
freerunner, thanks a lot.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-11 Thread Luca Capello
user pkg-fso-ma...@lists.alioth.debian.org
usertags 512589 + config-uboot
thanks

Hi there!

For Timo: it seems you forgot to cc: the pkg-fso-maint mailing list.
For everyone: please keep the pkg-fso-maing mailing list list cc:ed.

On Thu, 22 Jan 2009 01:29:04 +0100, Timo Juhani Lindfors wrote:
 I tried to add mem=127M boot option on openmoko neo freerunner but
 fw_setenv seems to fail mysteriously:

FWIW, the very same error happens on my FR as well:
=
debian-gta02:~# free
 total   used   free sharedbuffers cached
Mem:120808  90196  30612  0   3748  39068
-/+ buffers/cache:  47380  73428
Swap:0  0  0

debian-gta02:~# fw_printenv | grep quiet
quiet=1

debian-gta02:~# fw_setenv quiet 0
Unlocking flash...
Done
Cannot malloc -131072 bytes: Cannot allocate memory
Error: can't write fw_env to flash

debian-gta02:~# fw_printenv | grep quiet
quiet=1

debian-gta02:~#
=

It would be good to test if a more recent version still generates this.

Thx, bye,
Gismo / Luca


pgpDU8Nqj2NLi.pgp
Description: PGP signature


Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-11 Thread Luca Capello
tags 512589 + fixed-upstream
thanks

Hi there!

On Thu, 12 Feb 2009 00:38:41 +0100, Luca Capello wrote:
 On Thu, 22 Jan 2009 01:29:04 +0100, Timo Juhani Lindfors wrote:
 I tried to add mem=127M boot option on openmoko neo freerunner but
 fw_setenv seems to fail mysteriously:
[...]
 It would be good to test if a more recent version still generates
 this.

I am quite sure that this bug was an uptream one fixed by commit [1]:

  commit 5608692104efa8d56df803dc79ea41ac3607eee5
  Author: Guennadi Liakhovetski l...@denx.de
  Date:   Thu Sep 4 13:01:49 2008 +0200

  fw_env: add NAND support

  Add support for environment in NAND with automatic NOR / NAND
  recognition,
  including unaligned environment, bad-block skipping, redundant
  environment
  copy.

  Signed-off-by: Guennadi Liakhovetski l...@denx.de

I packaged that version (available at [2]) and indeed it works.  Timo,
can you confirm it, please?

Thx, bye,
Gismo / Luca

Footnotes: 
[1] 
http://git.denx.de/?p=u-boot.git;a=commit;h=5608692104efa8d56df803dc79ea41ac3607eee5
[2] http://people.debian.org/~gismo/tmp/uboot-envtools/


pgp35wCiETnvU.pgp
Description: PGP signature


Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-11 Thread Timo Juhani Lindfors
Luca Capello l...@pca.it writes:
 I packaged that version (available at [2]) and indeed it works.  Timo,
 can you confirm it, please?

$ sudo fw_printenv
Too few good blocks within range

$ cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.

# MTD device name   Device offset   Env. size   Flash sector size
/dev/mtd2   0x  00040002

$ dpkg -l uboot-envtools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version  
Description
+++---
ii  uboot-envtools   20080909-1~gismo.1   
read/modify the environment for the bootloader U-Boot




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-02-11 Thread Luca Capello
Hi Timo!

On Thu, 12 Feb 2009 01:44:57 +0100, Timo Juhani Lindfors wrote:
 Luca Capello l...@pca.it writes:
 I packaged that version (available at [2]) and indeed it works.  Timo,
 can you confirm it, please?

 $ sudo fw_printenv
 Too few good blocks within range

/usr/share/doc/uboot-envtools/README:

  DEVICEx_ENVSECTORS defines the number of sectors that may be used for
  this environment instance. On NAND this is used to limit the range
  within which bad blocks are skipped, on NOR it is not used.

This means that (/usr/share/doc/uboot-envtools/fw_env.config):

--8---cut here---start-8---
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# Notice, that the Number of sectors is ignored on NOR.

# MTD device name   Device offset   Env. size   Flash sector size   
Number of sectors
/dev/mtd2   0x  00040002
2
--8---cut here---end---8---

Thx, bye,
Gismo / Luca


pgpXr634loujV.pgp
Description: PGP signature


Bug#512589: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

2009-01-21 Thread Timo Juhani Lindfors
Package: uboot-envtools
Version: 20080520-4
Severity: normal

Hi,

I tried to add mem=127M boot option on openmoko neo freerunner but
fw_setenv seems to fail mysteriously:

li...@ginger:~$ sudo fw_setenv bootcmd 'setenv bootargs ${bootargs_base} 
${mtdparts} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M; 
mmcinit; ext2load mmc 1 0x3200 ${sd_image_name}; bootm 0x3200'
Unlocking flash...
Done
Cannot malloc -131072 bytes: Cannot allocate memory
Error: can't write fw_env to flash

li...@ginger:~$ free
 total   used   free sharedbuffers cached
Mem:118704  75956  42748  0   2260  47908
-/+ buffers/cache:  25788  92916
Swap:0  0  0


li...@ginger:~$ sudo fw_printenv
boot_menu_timeout=300
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 
console=tty0 loglevel=8 regular_boot
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ext2 
root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M; mmcinit; ext2load mmc 1 
0x3200 ${sd_image_name}; bootm 0x3200
bootdelay=1
menu_1=Boot from Flash: setenv bootargs ${bootargs_base} ${mtdparts}; nand 
read.e 0x3200 kernel 0x20; bootm 0x3200
menu_2=Reboot: reset
menu_3=Power off: neo1973 power-off
menu_4=Set console to USB: setenv stdin usbtty; setenv stdout usbtty; setenv 
stderr usbtty
menu_5=Set console to serial: setenv stdin serial; setenv stdout serial; setenv 
stderr serial
menu_6=SD/uImage2.bin: setenv bootargs ${bootargs_base} ${mtdparts} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 
1 0x3200 uImage2.bin; bootm 0x3200
menu_7=SD/uImage3.bin: setenv bootargs ${bootargs_base} ${mtdparts} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 
1 0x3200 uImage3.bin; bootm 0x3200
mtddevname=nor
mtddevnum=0
mtdids=nor0=physmap-flash,nand0=neo1973-nand
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)
partition=nor0,0
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0xfe
quiet=1
sd_image_name=uImage.bin
splashimage=nand read.e 0x3200 splash 0x5000; unzip 0x3200 0x880 
0x96000
stderr=usbtty
stdin=usbtty
stdout=usbtty
usbtty=cdc_acm


li...@ginger:~$ cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.

# MTD device name   Device offset   Env. size   Flash sector size
/dev/mtd2   0x  00040002

li...@ginger:~$ cat /proc/mtd
dev:size   erasesize  name
mtd0: 0020 0001 physmap-flash.0
mtd1: 0004 0002 u-boot
mtd2: 0004 0002 u-boot_env
mtd3: 0080 0002 kernel
mtd4: 000a 0002 splash
mtd5: 0004 0002 factory
mtd6: 0f6a 0002 rootfs





-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armel (armv4tl)

Kernel: Linux 2.6.28-GTA02_lindi-andy-tracking_b8b36e5ec3db71d5-mokodev 
(PREEMPT)
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages uboot-envtools depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries

uboot-envtools recommends no packages.

uboot-envtools suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org