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

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Timo Juhani Lindfors <timo.lindfors@iki.fi>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 22 Jan 2009 02:29:04 +0200

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:

lindi@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 0x32000000 ${sd_image_name}; bootm 0x32000000'
Unlocking flash...
Done
Cannot malloc -131072 bytes: Cannot allocate memory
Error: can't write fw_env to flash

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


lindi@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 0x32000000 ${sd_image_name}; bootm 0x32000000
bootdelay=1
menu_1=Boot from Flash: setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel 0x200000; bootm 0x32000000
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 0x32000000 uImage2.bin; bootm 0x32000000
menu_7=SD/uImage3.bin: setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 1 0x32000000 uImage3.bin; bootm 0x32000000
mtddevname=nor
mtddevnum=0
mtdids=nor0=physmap-flash,nand0=neo1973-nand
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
partition=nor0,0
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0xfe
quiet=1
sd_image_name=uImage.bin
splashimage=nand read.e 0x32000000 splash 0x5000; unzip 0x32000000 0x8800000 0x96000
stderr=usbtty
stdin=usbtty
stdout=usbtty
usbtty=cdc_acm


lindi@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               0x0000          00040000        00020000

lindi@ginger:~$ cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00010000 "physmap-flash.0"
mtd1: 00040000 00020000 "u-boot"
mtd2: 00040000 00020000 "u-boot_env"
mtd3: 00800000 00020000 "kernel"
mtd4: 000a0000 00020000 "splash"
mtd5: 00040000 00020000 "factory"
mtd6: 0f6a0000 00020000 "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

Message #10 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Luca Capello <luca@pca.it>

To: Timo Juhani Lindfors <timo.lindfors@iki.fi>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 00:38:41 +0100

[Message part 1 (text/plain, inline)]

user pkg-fso-maint@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     shared    buffers     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

[Message part 2 (application/pgp-signature, inline)]

Message #15 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Luca Capello <luca@pca.it>

To: Timo Juhani Lindfors <timo.lindfors@iki.fi>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 01:27:52 +0100

[Message part 1 (text/plain, inline)]

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 <lg@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 <lg@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/

[Message part 2 (application/pgp-signature, inline)]

Message #22 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Timo Juhani Lindfors <timo.lindfors@iki.fi>

To: Luca Capello <luca@pca.it>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 02:44:57 +0200

Luca Capello <luca@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               0x0000          00040000        00020000

$ 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

Message #27 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Luca Capello <luca@pca.it>

To: Timo Juhani Lindfors <timo.lindfors@iki.fi>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 01:58:36 +0100

[Message part 1 (text/plain, inline)]

Hi Timo!

On Thu, 12 Feb 2009 01:44:57 +0100, Timo Juhani Lindfors wrote:
> Luca Capello <luca@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               0x0000          00040000        00020000                2
--8<---------------cut here---------------end--------------->8---

Thx, bye,
Gismo / Luca

[Message part 2 (application/pgp-signature, inline)]

Message #32 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Timo Juhani Lindfors <timo.lindfors@iki.fi>

To: Luca Capello <luca@pca.it>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 11:50:55 +0200

Luca Capello <luca@pca.it> writes:
> # MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
> /dev/mtd2               0x0000          00040000        00020000                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 0x32000000 ${sd_image_name}; bootm 0x32000000
bootdelay=1
menu_1=Boot from Flash: setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel 0x200000; bootm 0x32000000
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 0x32000000 uImage2.bin; bootm 0x32000000
menu_7=SD/uImage3.bin: setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 1 0x32000000 uImage3.bin; bootm 0x32000000
mtddevname=nor
mtddevnum=0
mtdids=nor0=physmap-flash,nand0=neo1973-nand
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
partition=nor0,0
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0xfe
quiet=1
sd_image_name=uImage.bin
splashimage=nand read.e 0x32000000 splash 0x5000; unzip 0x32000000 0x8800000 0x96000
stderr=usbtty
stdin=usbtty
stdout=usbtty
usbtty=cdc_acm

lindi@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 0x32000000 ${sd_image_name}; bootm 0x32000000'

lindi@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 0x32000000 kernel 0x200000; bootm 0x32000000
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 0x32000000 uImage2.bin; bootm 0x32000000
menu_7=SD/uImage3.bin: setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load mmc 1 0x32000000 uImage3.bin; bootm 0x32000000
mtddevname=nor
mtddevnum=0
mtdids=nor0=physmap-flash,nand0=neo1973-nand
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
partition=nor0,0
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0xfe
quiet=1
sd_image_name=uImage.bin
splashimage=nand read.e 0x32000000 splash 0x5000; unzip 0x32000000 0x8800000 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 0x32000000 ${sd_image_name}; bootm 0x32000000

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:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs) rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10 mem=127M

Thanks a lot for packaking the fixed version!

Message #37 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Luca Capello <luca@pca.it>

To: Timo Juhani Lindfors <timo.lindfors@iki.fi>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org, Martin Michlmayr <tbm@debian.org>

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 17:07:17 +0100

[Message part 1 (text/plain, inline)]

tags 512589 + patch
thanks

Hi Timo!

On Thu, 12 Feb 2009 10:50:55 +0100, Timo Juhani Lindfors wrote:
> Luca Capello <luca@pca.it> writes:
>> # MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
>> /dev/mtd2               0x0000          00040000        00020000                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

[Message part 2 (application/pgp-signature, inline)]

Message #44 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>

To: Luca Capello <luca@pca.it>

Cc: Timo Juhani Lindfors <timo.lindfors@iki.fi>, "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 20:30:09 +0100

* Luca Capello <luca@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/

Message #49 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Timo Juhani Lindfors <timo.lindfors@iki.fi>

To: Luca Capello <luca@pca.it>

Cc: "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org, Martin Michlmayr <tbm@debian.org>

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Thu, 12 Feb 2009 22:47:25 +0200

Luca Capello <luca@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.

Message #54 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Luca Capello <luca@pca.it>

To: Martin Michlmayr <tbm@cyrius.com>

Cc: Timo Juhani Lindfors <timo.lindfors@iki.fi>, "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Fri, 13 Feb 2009 14:04:27 +0100

[Message part 1 (text/plain, inline)]

Hi Martin!

On Thu, 12 Feb 2009 20:30:09 +0100, Martin Michlmayr wrote:
> * Luca Capello <luca@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: 00200000 00010000 "physmap-flash.0"
mtd1: 00040000 00020000 "u-boot"
mtd2: 00040000 00020000 "u-boot_env"
mtd3: 00800000 00020000 "kernel"
mtd4: 000a0000 00020000 "splash"
mtd5: 00040000 00020000 "factory"
mtd6: 0f6a0000 00020000 "rootfs"
debian-gta02:~#
=====

Thx, bye,
Gismo / Luca

[Message part 2 (application/pgp-signature, inline)]

Message #59 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>

To: Luca Capello <luca@pca.it>

Cc: Timo Juhani Lindfors <timo.lindfors@iki.fi>, "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>, 512589@bugs.debian.org

Subject: Re: fw_setenv: Cannot malloc -131072 bytes: Cannot allocate memory

Date: Fri, 13 Feb 2009 14:36:31 +0100

* Luca Capello <luca@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/

Message #64 received at 512589@bugs.debian.org (full text, mbox, reply):

From: Per Andersson <avtobiff@gmail.com>

To: Martin Michlmayr <tbm@cyrius.com>, 512589@bugs.debian.org

Cc: Luca Capello <luca@pca.it>, Timo Juhani Lindfors <timo.lindfors@iki.fi>, "ML Debian FreeSmartphone.Org Team" <pkg-fso-maint@lists.alioth.debian.org>

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

Date: Tue, 17 Feb 2009 01:33:11 +0000

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 <tbm@cyrius.com> wrote:
> * Luca Capello <luca@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

Message #69 received at 512589-close@bugs.debian.org (full text, mbox, reply):

From: Per Andersson <avtobiff@gmail.com>

To: 512589-close@bugs.debian.org

Subject: Bug#512589: fixed in uboot-envtools 20081215-1

Date: Fri, 13 Mar 2009 17:47:07 +0000

Source: uboot-envtools
Source-Version: 20081215-1

We believe that the bug you reported is fixed in the latest version of
uboot-envtools, which is due to be installed in the Debian FTP archive:

uboot-envtools_20081215-1.diff.gz
  to pool/main/u/uboot-envtools/uboot-envtools_20081215-1.diff.gz
uboot-envtools_20081215-1.dsc
  to pool/main/u/uboot-envtools/uboot-envtools_20081215-1.dsc
uboot-envtools_20081215-1_armel.deb
  to pool/main/u/uboot-envtools/uboot-envtools_20081215-1_armel.deb
uboot-envtools_20081215.orig.tar.gz
  to pool/main/u/uboot-envtools/uboot-envtools_20081215.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 512589@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Per Andersson <avtobiff@gmail.com> (supplier of updated uboot-envtools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 07 Mar 2009 02:41:15 +0000
Source: uboot-envtools
Binary: uboot-envtools
Architecture: source armel
Version: 20081215-1
Distribution: unstable
Urgency: low
Maintainer: Per Andersson <avtobiff@gmail.com>
Changed-By: Per Andersson <avtobiff@gmail.com>
Description: 
 uboot-envtools - read/modify the environment for the bootloader U-Boot
Closes: 512589
Changes: 
 uboot-envtools (20081215-1) unstable; urgency=low
 .
   [ Luca Capello ]
   * New Git checkout (22525779cb51f1bbe4e96fea7b778de1935a5a69):
     + add NAND support (Closes: #512589).
   * debian/NEWS:
     + explain the new parameter in /etc/fw_env.config.
   * debian/uboot-envtools-examples/openmoko_gta01.config: new file.
   * debian/uboot-envtools-examples/openmoko_gta02.config: new file.
   * debian/uboot-envtools-examples/qnap_ts101.config:
     + add newline at EOF.
Checksums-Sha1: 
 a6a9afe3a04f925f0d7d71f84c521b9d232623fe 1202 uboot-envtools_20081215-1.dsc
 35f9da46d31e7f65c68dd7cdd5ca200dd6693bd6 13566 uboot-envtools_20081215.orig.tar.gz
 2901b5129061e40cc7992bd9f9bf6f4d01983ecd 4540 uboot-envtools_20081215-1.diff.gz
 274649bdaeef0b7e2d53a0d9d4c2ec61371b51de 14818 uboot-envtools_20081215-1_armel.deb
Checksums-Sha256: 
 c29c292e53d3c175ccbb6e9ff231fc04e933c256880539fb5a6950635a39b384 1202 uboot-envtools_20081215-1.dsc
 69f540e23344c2eed23e33094b05eba24e9b7b1283c8f70c0540303480695833 13566 uboot-envtools_20081215.orig.tar.gz
 a9364036813a8e06c67792b707e008871a9245af18a1a9411f01b1cfb7938234 4540 uboot-envtools_20081215-1.diff.gz
 e579913b038854705cb1d088ed320d5e2201c77dc132aaed5f91eed7e8359795 14818 uboot-envtools_20081215-1_armel.deb
Files: 
 0226cb801c3c9f2236f7b4a6471aa47a 1202 utils optional uboot-envtools_20081215-1.dsc
 21191178f21da802754063069a882b5b 13566 utils optional uboot-envtools_20081215.orig.tar.gz
 ae6c0bb5f699fd05ff8bedb60e7b0406 4540 utils optional uboot-envtools_20081215-1.diff.gz
 9ad8fb34f3095f9563e8eb86b885d8b2 14818 utils optional uboot-envtools_20081215-1_armel.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iJwEAQECAAYFAkm6moEACgkQZwOMsWhEDTP15wQAxJVYIUyqYaU2s+pR9JBVS2uJ
UNdquHdeJiiPGtm2z1Me0IoaahlSTZMfBgbVssTt4cdVUfW9SM5rXf6Dm2Wojy98
E6gpYyWmrF6Uci9xYUoyTLtj5RKq7UVaZCMxNZwSXgmqXLE+s1mZZosmwc4v3ufx
YZUGhIfRZWIC81PEhZw=
=5x45
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.