From: Sebastian Moeller <moeller0@gmx.de>
To: Joel Stanley <joel@jms.id.au>
Cc: Frits Riep <riep@riepnet.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Having issue upgrading to latest image 3.10.36-4
Date: Mon, 14 Apr 2014 15:17:39 +0200 [thread overview]
Message-ID: <90A7D447-F54D-4493-A9A7-89CEF5DE0FBC@gmx.de> (raw)
In-Reply-To: <CACPK8Xego8UsKQG36LUiB6h8JsZ0bLbLNtjxS9a-2kdMeWQNbA@mail.gmail.com>
Hi Joel,
On Apr 13, 2014, at 15:57 , Joel Stanley <joel@jms.id.au> wrote:
> On Sun, Apr 13, 2014 at 5:58 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> I think Valdis Kletnieks reported the same for a 3800. Please try the "manual" route described below and report back your results to the list:
>
> I attempted an upgrade using the web interface from -3 to -4 and it
> also failed. I tried from the shell:
>
> root@cerowrt:/tmp# sysupgrade -c -v
> openwrt-ar71xx-generic-wndr3800-squashfs-sysupgrade_new.bin
> Saving config files...
> etc/lighttpd/lighttpd.pem
> etc/passwd-
> etc/fw_env.config
> etc/shadow
> etc/passwd
> etc/group-
> etc/ethers
> etc/config/wireless
> etc/config/system
> etc/config/polipo
> etc/config/ucitrack
> etc/config/network
> etc/config/ubootenv
> etc/config/dropbear
> etc/config/firewall
> etc/config/upnpd
> etc/config/fstab
> etc/config/luci
> etc/config/dhcp
> etc/config/sqm
> etc/dropbear/dropbear_rsa_host_key
> etc/dropbear/authorized_keys
> etc/dropbear/dropbear_dss_host_key
> etc/sudoers
> etc/shadow-
> etc/samba/secrets.tdb
> etc/samba/smbpasswd
> etc/group
> etc/firewall.user
> killall: watchdog: no process killed
> Sending TERM to remaining processes ... logd netifd odhcpd lighttpd
> crond lighttpd snmpd pimd xinetd dbus-daemon smbd nmbd avahi-daemon
> miniupnpd polipo babeld natpmp ahcpd rngd ntpd dnsmasq ubusd askfirst
> 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
I would not be amazed if this issue would throw off the GUI method. Have you tried the GUI without keeping the configuration, and does that also fail? (When I update on the command line with the "-n" switch (do not keep old configuration) I do not see any of the two lines containing information about TRX)
Best Regards
Sebastian
>
> Upgrade completed
> Rebooting system...
>
> After reboot:
>
> root@cerowrt:~# cat /etc/openwrt_release
> DISTRIB_ID="CeroWrt"
> DISTRIB_RELEASE="3.10.36-4"
> DISTRIB_REVISION="r40438"
>
> The system appears to be working okay, except my 2.4GHz interface is
> missing - I haven't spent any real time looking into that.
>
> Regards,
>
> Joel
next prev parent reply other threads:[~2014-04-14 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 18:46 Frits Riep
2014-04-12 20:28 ` Sebastian Moeller
2014-04-12 20:42 ` Valdis.Kletnieks
2014-04-13 13:57 ` Joel Stanley
2014-04-14 11:48 ` Frits Riep
2014-04-14 13:17 ` Sebastian Moeller [this message]
2014-04-15 0:29 ` Joel Stanley
2014-04-19 19:12 ` Dave Taht
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=90A7D447-F54D-4493-A9A7-89CEF5DE0FBC@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=joel@jms.id.au \
--cc=riep@riepnet.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