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#735 - LEDE 17.01.1 boot loop on Asus RT-N56U ramips, rt3883 #5886
Comments
jow-: Are you able to capture a serial console log? |
tinde: I'm afraid that I'm not. AFAIK it requires opening the router case and using some kind of cable to connect it to a computer, so beyond my skills. |
tinde: Hi I made some testing yesterday. Flashed latest Asus' official firmware in, then tried with different lede firmwares. Results were so, that neither rt-n56u-squashfs-factory.bin nor rt-n56u-squashfs-sysupgrade.bin v17.01.1 was booting up. Also, older v17.01.0 rt-n56u-squashfs-factory.bin never booted up. Only way to recover is to use Asus' firmware restoration utility for flashing v.17.01.0 sysupgrade version. Also tried builds from Image generator, same results. One thing to note, I never managed to get in to a failsafe mode. Well, router itself was in failsafe mode according to PWR led flashing cycle, but no SSH or telnet connections could be established. Guides used in this phase: https://lede-project.org/docs/user-guide/failsafe_and_factory_reset https://wiki.openwrt.org/doc/howto/generic.failsafe Leds were acting pretty much like it was described in the latter. |
tinde: Git bisected this to 649e766 |
aczlan: Timo, you need to use the TFTP or ASUS Firmware Restoration utility, telnet and SSH will not work. Attached are my bootlogs from 17.01.1 (and 17.01.2 which seems : Aaron Z |
mkresin: Aaron, would you please try an image from https://downloads.lede-project.org/snapshots/targets/ramips/rt3883/. As already bisected by Timo it is an update of the wireless drivers which causes the crash. But the release images are build without debug informations and do not print the really important informations in the stacktrace. |
aczlan: Here is a boot log with the nightly from 26 Jun: Aaron Z |
mkresin: Would you please try an image from https://www.kresin.me/files/lede-17.01.2/ and reported back whether the issue is fixed. |
aczlan: I will try that tonight. Aaron Z |
vk496: Hello. Same thing in HG556a ver. C [[https://forum.lede-project.org/t/hg556a-ver-c-boot-loop/4811|Forum report]]. Tried with snapshot of 04/07/2017 (also stable versions have the same problem). My bootlog: https://pastebin.com/mBnsKkgQ Salu2 |
vk496: Also tried [[https://www.kresin.me/files/lede-17.01.2/|https://www.kresin.me/files/lede-17.01.2/]], and the bootloop persist. Salu2 |
mkresin: Valentin, would you please try [[www.kresin.me/files/lede-brcm63xx-generic-HG556a-C-squashfs-cfe.bin|this image]] and provide a serial console bootlog. |
mkresin: Anyone? |
aczlan: Sorry, didn't make it home till after 11PM the last two nights so I haven't had time to try installing it. I will try to get it installed tonight. Aaron Z |
aczlan: That image works for me (it boots, I can enable wifi and connect to the internet through it). Bootlog attached: FS#735 -MKresin5JulBootl.log Aaron Z |
hvegh: Hey all.... There's a two line fix for this see Btw the method of communication can be improved imho...
|
tinde:
After upgrading 17.01.0=>17.01.1 router won't boot up at all. After image is flashed and router reboots, power light flashes, then it lits up, followed by LAN light. Then they both go down and it starts all over again. PWR light flashes, then stays on, LAN follows, and reboot.
Tested both downloaded lede-17.01.1-ramips-rt3883-rt-n56u-squashfs-sysupgrade.bin and lede-17.01.1-ramips-rt3883-rt-n56u-squashfs-factory.bin, as well as builded image using lede-imagebuilder-17.01.1-ramips-rt3883.Linux-x86_64.tar.xz. SHA256 sums verified. All fails.
Problem occurs every time, no matter whether I flash it using Luci, sysupgrade via SSH or Asus native firmware restoration utility.
Recovery is done by flashing any other FW, padawan, openwrt or lede 17.01.0 using Asus FW restoration utility. It is only way to connect to router when bootlooping, no SSH or telnet connection.
Sounds identical to #733:
https://bugs.lede-project.org/index.php?do=details&task_id=733
BR,
tinde
The text was updated successfully, but these errors were encountered: