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#3552 - Linksys RE6500 bootloops with latest snapshots #8577
Comments
bjonglez: Ok, on the serial port, it goes up to:
U-Boot 1.1.3 (Jun 2 2015 - 15:52:13)
It spends several seconds here, and then reboots. According to the wiki, there should be kernel boot log just after this point. |
bjonglez: It works with a self-built image on r15386-c22b689cf8 Probably an issue with kernel size, my build: u-boot legacy uImage, MIPS OpenWrt Linux-5.4.85, Linux/MIPS, OS Kernel Image (lzma), 2407280 bytes, Fri Jan 1 12:22:58 2021, Load Address: 0x80001000, Entry Point: 0x80001000, Header CRC: 0xB38001C5, Data CRC: 0x402476AB vs snapshot build: u-boot legacy uImage, MIPS OpenWrt Linux-5.4.85, Linux/MIPS, OS Kernel Image (lzma), 2512013 bytes, Thu Dec 31 22:09:09 2020, Load Address: 0x80001000, Entry Point: 0x80001000, Header CRC: 0x43D6213D, Data CRC: 0x8CD79BE0 |
Borromini: Looks like 8 MiB flash, how big is the kernel 'partition'? Or does mt7621 use a dynamic splitter? |
bjonglez: Yes it's a 8 MB flash device. Good question. It looks dynamic to me: 0x000000000000-0x000000030000 : "u-boot" 0x24bbb0 = 2407344 (my kernel is 2407280) |
dsouza: (deleted) |
I can confirm this on my RE6500.
Please let me know if I can help to debug this issue. I don't have a serial connection set up, but I can attempt one if boot logs would help. I'm eager to try some of the recent mt7621 improvements from SNAPSHOT once it's in a working state 🤞 |
@vemek we could enable lzma compression for this device. I had the same issue on GB-PC1 & GB-PC2 which have 32MB flash. Are you able to compile an image yourself? I can send a patch for you to test. |
@arinc9 absolutely, I can test that 👍 |
I won't have time to properly put up a patch, let me explain so you can manually do it. Find re6500 section at target/linux/ramips/image/mt7621.mk Copy Compile and see if sysupgrade installation boots. |
Hey @arinc9 - that worked perfectly once I added LZMA compression! 🚀 Thanks for that and for the improvements to the mt7621 stuff! Do you have time to open a one-liner patch for that target config? I can do it otherwise - though I don't have context on what size limit is being hit without it. |
I'm still on an ongoing Eurotrip so I'm going to leave it to you to deal with patching. I don't know what to say about the size limit on the patch log but just saying that it would exceed size limit without lzma compression is good enough in my book. |
At some point after 21.02.3 and before 22.03.0, the size limits of the Linksys RE6500 were reached and prevent booting from the 22.03.0 release or builds of current SNAPSHOT. This patch allows builds of master to boot again and has been tested on my device. Closes openwrt#8577 Signed-off-by: Mark King <mark@vemek.co>
At some point after 21.02.3 and before 22.03.0, the size limits of the Linksys RE6500 were reached and prevent booting from the 22.03.0 release or builds of current SNAPSHOT. This patch allows builds of master to boot again and has been tested on my device. Fixes: openwrt#8577 Signed-off-by: Mark King <mark@vemek.co>
At some point after 21.02.3 and before 22.03.0, the size limits of the Linksys RE6500 were reached and prevent booting from the 22.03.0 release or builds of current SNAPSHOT. This patch allows builds of master to boot again and has been tested on my device. Fixes: #8577 Signed-off-by: Mark King <mark@vemek.co> (cherry picked from commit bf5b1a5)
bjonglez:
The RE6500 was working fine on an old 19.07 snapshot: OpenWrt 19.07-SNAPSHOT r10578-b3d70f628b
I sysupgraded to latest snapshot and it does not come up. Judging from the LEDs, it seems to bootloop.
Booting the latest snapshot initramfs through TFTP works. I sysupgraded again from the initramfs, and it still bootloops.
Possibly related to FS#3539. I will try to get a serial output to see what happens.
The text was updated successfully, but these errors were encountered: