Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Justin Madru <justin.jdm64@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 3.10.38-1 sysupgrade not working
Date: Tue, 29 Apr 2014 02:59:36 -0400	[thread overview]
Message-ID: <16255.1398754776@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 28 Apr 2014 20:56:45 -0700." <CAJ5gi5KQQK21=U-T0RFgGgbFEKTaSuwPZhK=-haYU7mXLb8N7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3155 bytes --]

On Mon, 28 Apr 2014 20:56:45 -0700, Justin Madru said:

> I'm trying to flash the new version (3.10.38-1) using the
> openwrt-ar71xx-generic-wndr3800-squashfs-sysupgrade.bin image, but I'm
> getting the following error in the web ui.
>
> "The uploaded image file does not contain a supported format. Make sure
> that you choose the generic image format for your platform."

Ah.. somebody else with the problem :)

Following up on my previous testing - I was on 36-3, and 36-4 and 38-1 both
failed with that same error.  So as suggested by somebody, I scp'ed the 38-1
over to my 3800, and I got the following results from the command line:

First, try in 'test' mode - this returned *very* fast, as in sub-second:

root@bogon-gateway-1:~# sysupgrade -d 60 -v -T /tmp/openwrt-ar71xx-generic-wndr3800-squashfs-sysupgrade.bin

and no output.

So then try for real - and that worked and rebooted to 38-1 with all my config
settings preserved.  Not sure what the TRX header issue is - but it seemed to
come far too late in the process to explain my problems with Luci.

root@bogon-gateway-1:~# sysupgrade -d 60 -v  /tmp/openwrt-ar71xx-generic-wndr380
0-squashfs-sysupgrade.bin
Saving config files...
etc/xinetd.conf
etc/sysctl.conf
etc/shells
etc/shadow
etc/rc.local
etc/profile
etc/passwd
etc/opkg.conf
etc/lighttpd/lighttpd.conf
etc/inittab
etc/hosts
etc/group
etc/fw_env.config
etc/firewall.user
etc/dropbear/dropbear_rsa_host_key
etc/dropbear/dropbear_dss_host_key
etc/dropbear/authorized_keys
etc/dnsmasq.conf
etc/crontabs/root
etc/config/wol
etc/config/wireless
etc/config/upnpd
etc/config/ucitrack
etc/config/ubootenv
etc/config/transmission
etc/config/system
etc/config/sqm
etc/config/snmpd
etc/config/samba
etc/config/radvd
etc/config/qos
etc/config/polipo
etc/config/network
etc/config/natpmp
etc/config/minissdpd
etc/config/luci
etc/config/fstab
etc/config/firewall
etc/config/etherwake
etc/config/dropbear
etc/config/dhcp6c
etc/config/dhcp
etc/config/debloat
etc/config/ddns
etc/config/bcp38
etc/config/babeld
etc/config/aqm
etc/config/alttcp
etc/config/ahcpd
etc/config/6relayd
etc/babeld.conf
etc/avahi/avahi-daemon.conf
killall: watchdog: no process killed
Sending TERM to remaining processes ... lighttpd logd netifd odhcpd lighttpd cro
nd snmpd pimd xinetd dbus-daemon smbd nmbd avahi-daemon babeld ahcpd rngd ntpd d
nsmasq ubusd askfirst miniupnpd
Sending KILL to remaining processes ... askfirst
Switching to ramdisk...
Performing system upgrade...
Unlocking firmware ...

Writing from <stdin> to firmware ...
Appending jffs2 data from /tmp/sysupgrade.tgz to firmware...TRX header not found
Error fixing up TRX header

Upgrade completed
Rebooting system...

(And when it came back, it was on 38-1.

Pondering  /rom/usr/lib/lua/luci/view/admin_system/flashops.htm didn't
help much.  Down around line 83 we have this:

      <% if image_invalid then %>
             iv class="cbi-section-error"><%:The uploaded image file does not contain a supported format. Make sure that you choose the generic image format f
      <% end %>

but damned if I can figure out where/how image_invalid gets set on return
from the 'form method=post' above it....

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  reply	other threads:[~2014-04-29  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  3:56 Justin Madru
2014-04-29  6:59 ` Valdis.Kletnieks [this message]
2014-05-04 20:10   ` Chuck Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16255.1398754776@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=justin.jdm64@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox