OpenWrt/LEDE Project

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report
  • Category Other
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Mirko Parthey - 08.02.2017
Last edited by Mathias Kresin - 27.02.2017

FS#484 - Image Builder generates broken image for ASUS WL500W

Software Revision

LEDE 17.01.0-rc2

Device

ASUS WL500W

Issue description

An image generated with the Image Builder can be booted only once after flashing it. On the second and further boot attempts, the device stays in the bootloader.

The OpenWrt 15.05.1 Image Builder is not affected. The official 17.01.0-rc2 image also works fine.

I wonder if the following Image Builder message hints at the problem:

WARNING: maxlen exceeds default maximum!  Beware of overwriting nvram!

The Image Builder result is actually smaller than the official image, 3608576 vs. 4001792 bytes.

Steps to reproduce

  • Use Debian Jessie amd64 or another suitable host system
  • Unpack lede-imagebuilder-17.01.0-rc2-brcm47xx-legacy.Linux-x86_64.tar.xz
  • Within the Image Builder directory: make image PROFILE=asus-wl-500w
  • Copy this resulting image to the device:
    bin/targets/brcm47xx/legacy/lede-17.01.0-rc2-r3131-42f3c1f-brcm47xx-legacy-asus-wl-500w-squashfs.trx
  • sysupgrade -n -v *.trx
  • Wait for automatic reboot, wait another 3 minutes
  • ssh root@192.168.1.1
  • Check dmesg for “jffs2 [...] complete” message, or wait until it appears
  • reboot

The device is now stuck in the bootloader, power-cycling does not help.

I can do further tests if necessary.

Regards,
Mirko

Closed by  Mathias Kresin
27.02.2017 11:48
Reason for closing:  Fixed
Mirko Parthey commented on 26.02.2017 19:27

The mtd fixtrx subcommand was previously missing in this package:

https://downloads.lede-project.org/releases/packages-17.01/mipsel_mips32/base/mtd_21_mipsel_mips32.ipk

which is used by the Image Builder.

However, the mtd binary built into the official firmware image was working OK, which explains the difference in behaviour.

Apparently the broken mtd package has now been replaced with a fixed version,
and this bug report can be closed.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing