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#3686 - Belkin F9K1115 v2 - boot loop with 21.02 snapshot #8763
Comments
nerzakt: Mine does the same thing I have a f9k1109v1, I am stuck on 19.0.7 |
Same problem here with 21.02.2 on F9K1115 V2 after upgrade from 19.07.9 Kernel log:
|
Seems like sysupgrade issue to me:
So in order to find out what is going on, we would need to see the console output during sysupgrade process from 19.07. Maybe @xdarklight would have some clue? @mrtnmtth Can you please try flashing openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-factory.bin via the U-Boot HTTP upgrade page (which is by default listening on 192.168.2.1) and report back? |
I think I did test sysupgrade from ar71xx to ath79 back then but it's been a while.
I am sure that I tried this approach as I found some issue with the image generation process and had to tackle that. |
Flashing openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-factory.bin via the recovery web-if does indeed work. For other devices, sysupgrades from ar71xx to ath79 also worked without any problems back on 19.07, when I applied them a year or two ago. I guess there might be something missing from the sysupgrade image for this device. Old images used to be around 16MB whereas the 21.02 ath79 ones are only 6MB. Image comparison using binwalk:
|
great, thanks for reporting back!
On my own device I run master. The image size there is similar to 21.02. sysupgrade (from one ath79 image to another) works fine for me. I suspect that the ar71xx -> ath79 sysupgrade problem comes from the LZMA loader because original u-boot has some kernel size restrictions (which I think is why in ar71xx the device was moved to the tiny sub-target, while there's plenty of space in flash). I have been re-using this part from F9J1108v2 which was added by @dmascord |
To be fair, I needed to force the sysupgrade from 19.07.
But I anyway assumed this to be a valid upgrade path and proceeded. Maybe it should just be documented somewhere that the sysupgrade 19.07 -> 21.02 is not supported for this device (and maybe other affected Belkin devices too). Another issue I noticed is that the eth interfaces are now enumerated the other way around. Therefore, my network config needed some manual fixing as well. |
I found this documentation in the wiki: https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79 The release notes for 21.02.0 are linking to above wiki page as well: https://openwrt.org/releases/21.02/notes-21.02.0#dropped_hardware_targets
Above mentioned wiki page even has a section with "incompatible changes". It states that there are changes to Ethernet interfaces, LEDs and wifi device paths. |
Oh well... 😅. Shame on me for not rtfm. Sorry for bothering you then. But thanks very much for the support anyway. |
It's not that this was the first thing on my mind - so don't worry! In this ticket there's now three different reports:
I suggest closing this issue for two reasons:
I am not an OpenWrt developer so I don't have permission to close this issue myself. |
@xdarklight Thanks! |
siturf:
Boot loop, no communication with the router after upgrade to 21.02 snapshot (tested r15866).
Upgrade from Belkin web UI (factory image) is not working.
Probably migration to the new ath79 architecture is not correct:
The text was updated successfully, but these errors were encountered: