New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#1810 - broken sysupgrade in 18.06.1 for EA3500 #7058
Comments
tibyke: I can confirm the report. kirkwood/audi (Linksys EA3500) 18.06.1 upgrade wont get applied, while 18.06.0 is totally fine, I can flash snapshots (even newer than revision of 18.06.1) but 18.06.1 just wont get installed. tried it both from CLI and LUCI with no success. any idea on that? |
jogo: As a comparison, kirkwood/viper (Linksys EA4500) seems to work fine, I successfully upgraded from 18.06.0 to 18.06.1. |
zz0rk: Model Linksys EA3500 I've previously tried to directly upgrade from version 17.01.4 to 18.06.1. This failed, but I was able to successfully upgrade from 17.01.4 > 17.01.5 > 18.06.0. When I tried to upgrade from 18.06.0 to 18.06.1 it failed. I am also concerned that this upgrade somewhere along the way broke my extroot configuration, since all my installed packages are gone and Software shows only ~9MB of available disk space down from ~14GB. This behavior is repeatable and I have been able to reproduce it on two identical configured EA3500 devices. Some advice regarding both issues would be appreciated. Cheers Model |
mike: Just adding another confirmation, going from 18.06.0 to 18.06.1 failed on my ea3500, I also tried going form one of my own builds to 18.06.1 and it failed as well. |
tapper82: Forum post here: |
Robby: Another confirmation here that version 18.06.1 does not boot on the EA3500. However, I have also tried today's (Sat Sep 29 22:50:53 2018) snapshot, and this does successfully boot on the EA3500. So, hopefully when version 18.06.2 is released, it will also have the fix that the current snapshot has. I have also tried searching git for the exact commit that fixes the issue, but have not been able to find it. Oh well. |
Dantekazuma: Same here cannot upgrade from 18.06.0 to 18.06.1 , system reboots into flashed partiton goes into a panic and reboots to previous working partition . tried 7 times same outcome . Also as a side note regarding this device has the THS DVFS and the mwl8k modifications have been merged to this device to enable all the 5Ghz Channels ? commit is linked |
por: Is this the contents of /etc/fw_env.config ? |
tibyke: well, thats not much of progress during the last 4 months.... |
ynezz: It would be nice if someone could build image from this branch https://git.openwrt.org/?p=openwrt/staging/jow.git;a=shortlog;h=refs/heads/backport-18.06 which is going to be 18.06.2 release soon. If building of such images is problem, then please let me know and I'll try to build one for you, please just specify for which devices are the images needed. |
timoleon: I built an image from this branch (jow snapshot if I'm not wrong) cloned yesterday. The upgrade by itself was straightforward, but I have the following issue:
Solution: Unplug the wire 30 seconds.
I also built that image for D-Link DIR-825; I have the same pppoe/Ethernet port issue. Unfortunately, I could not try installing this image from Linksys original FW. |
Robby: I have tested the newly released version 18.06.2 and can hereby confirm this issue has now been fixed with the release of this new version, although its not explicitly mentioned as such in the changelog. So, this issue can be closed now. |
tibyke: I hereby confirm that 18.06.2 upgrade is successful from 18.06.0 on kirkwood/audi (linksys ea3500) thank you for the contribution! |
tapper82:
sysupgrade is not doing the upgrade on the ea3500. User tibyke on irc says that they cant flash from 18.06.0 to 18.06.1
The sysupgrade seems to work but after a reboot firmware is still on 18.06.0.
I all so have a friend Frank who tryed to flash his ea3500 from stock with openwrt 18.0.6.1 and after a reboot it was still on stock. I will get him to try flashing 18.06.0.
The text was updated successfully, but these errors were encountered: