sporto
May 8, 2025, 9:15pm
6586
After upgrading to 24.10.0 a few weeks ago, I today discovered that I can no longer access the web configuration page for my ONT/modem (Humax BGW320-500). I have tried re-booting the modem, re-starting the WAN interface on the E8450, re-booting the E8450, etc. I also tried adding a modem interface on the E8450, following the instructions at https://openwrt.org/docs/guide-user/network/wan/access.modem.through.nat but that did not work either.
I can ping the modem at it's local address of 192.168.1.254 from the Luci diagnostics page (and by ssh'ing into the router), but I cannot ping the modem from a PC on my local subnet, 192.168.11.x
I would appreciate any thoughts or suggestions on how to debug further.
Cosmo
May 9, 2025, 2:36am
6587
Thanks. I think you're onto something here. The owut is showing some errors and I just tried the Attended sysupgrade on another device and it failed the same way. I don't have time to dig into this tonight and I have a eye doc appointment in the morning. If I can't figure it out on my own, I'll post something back here on Saturday.
Rick
1 Like
You can contact me via PM, and then we can set up a video meeting to see what went wrong, if you prefer this way.
Do you have the fitblk package installed in Luci? If not, try installing it. This solved my issue with the 24.10.0 to 24.10.1 upgrade not succeeding. I previously did an upgrade from 23.05 to 24.10.0 while retaining config, using the instructions on the e8450 wiki page.
I discovered this fix in the following link. If this is a common issue it should perhaps be added to the wiki.
opened 02:18PM - 17 Apr 25 UTC
closed 10:12AM - 26 Apr 25 UTC
target/mediatek
bug
Official Image
release/24.10
### Describe the bug
I cannot update the Linksys E8450 (UBI) from version 24.10ā¦ .0 to 24.10.1. I tested it with a custom images (with custom packages) and the default images. The version stays on version 24.10.0.
### OpenWrt version
r28427-6df0e3d02a
### OpenWrt release
24.10.0
### OpenWrt target/subtarget
mediatek/mt7622
### Device
Linksys E8450 (UBI)
### Image kind
Official downloaded image
### Steps to reproduce
_No response_
### Actual behaviour
_No response_
### Expected behaviour
_No response_
### Additional info
_No response_
### Diffconfig
```text
```
### Terms
- [x] I am reporting an issue for OpenWrt, not an unsupported fork.
1 Like
Snuupy
May 11, 2025, 4:59am
6591
Sorry - just had time to reconnect everything via serial and take apart the router again. Which file am I flashing to the recovery via TFTP in u-boot?
it's not any of these files: fl31-uboot.fip, kernel, preloader.bin, sysupgrade
so which one is the recovery for 24.10.1?
Edit: Ah, probably https://github.com/dangowrt/owrt-ubi-installer/releases/tag/v1.1.4 // openwrt-24.10.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb
flashed recovery successfully, no need to reply unless you think I did something wrong, thanks again
Cosmo
May 13, 2025, 5:34pm
6592
I wasn't able to commit any time to this problem until this morning and was hoping this was the issue. Unfortunately all my devices have the "fitblk" version 2 installed.
Thanks for the info though!
Cosmo
May 13, 2025, 5:52pm
6593
el_charlie:
I suggest you to install owut (on Luci > System > Software) and then SSH to one of the routers and run owut upgrade -v to see what happens.
If you're already on 24.10.0, you should've flashed the 1.1.2 or 1.1.3 installer by now, so it's not a matter of wrong partition layout.
Finally had some time to pursue this. As per your suggestion, this is the output I get. It does seem to think there is a bootloader issue but I built all 5 of these devices with the cookbook in the wiki.
The "wpad" issue is OK, I do run the full wpad package as I have an issue with some IOT devices that need it... and I have plenty of space as I don't run any DNS, DHCP or firewall, just backhaul WAP.
The Attended Sysupgrade runs, I can select the image for 24.10.1, it builds and starts to install the fails and falls out to the Luci/Status/Overview page and still shows 24.10.0 as the installed version.
Thoughts?
towut output
root@Poolhouse_OpenWRT:~# owut upgrade -v
owut - OpenWrt Upgrade Tool 2025.04.08~ef2bfb4d-r1 (/usr/bin/owut)
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target mediatek/mt7622
Profile linksys_e8450-ubi
Package-arch aarch64_cortex-a53
Root-FS-type squashfs
Sys-type sysupgrade
Version-from 24.10.0 r28427-6df0e3d02a (kernel 6.6.73)
Version-to 24.10.1 r28597-0425664679 (kernel 6.6.86)
Build-FS-type squashfs
Build-at 2025-04-13T16:38:32Z (~721 hours ago)
Image-prefix openwrt-24.10.1-mediatek-mt7622-linksys_e8450-ubi
Image-URL https://downloads.openwrt.org/releases/24.10.1/targets/mediatek/mt7622
Image-file openwrt-24.10.1-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
Installed 166 packages
Top-level 82 packages
Default 33 packages
User-installed 56 packages (top-level only)
Package version changes:
base-files 1655~6df0e3d02a 1658~0425664679
ca-bundle 20240203-r1 20241223-r1
jsonfilter 2024.01.23~594cfa86-r1 2025.04.18~8a86fb78-r1
kmod-cfg80211 6.6.73.6.12.6-r1 6.6.86.6.12.6-r1
kmod-crypto-acompress 6.6.73-r1 6.6.86-r1
kmod-crypto-aead 6.6.73-r1 6.6.86-r1
kmod-crypto-ccm 6.6.73-r1 6.6.86-r1
kmod-crypto-cmac 6.6.73-r1 6.6.86-r1
kmod-crypto-crc32c 6.6.73-r1 6.6.86-r1
kmod-crypto-ctr 6.6.73-r1 6.6.86-r1
kmod-crypto-gcm 6.6.73-r1 6.6.86-r1
kmod-crypto-geniv 6.6.73-r1 6.6.86-r1
kmod-crypto-gf128 6.6.73-r1 6.6.86-r1
kmod-crypto-ghash 6.6.73-r1 6.6.86-r1
kmod-crypto-hash 6.6.73-r1 6.6.86-r1
kmod-crypto-hmac 6.6.73-r1 6.6.86-r1
kmod-crypto-manager 6.6.73-r1 6.6.86-r1
kmod-crypto-null 6.6.73-r1 6.6.86-r1
kmod-crypto-rng 6.6.73-r1 6.6.86-r1
kmod-crypto-seqiv 6.6.73-r1 6.6.86-r1
kmod-crypto-sha3 6.6.73-r1 6.6.86-r1
kmod-crypto-sha512 6.6.73-r1 6.6.86-r1
kmod-gpio-button-hotplug 6.6.73-r5 6.6.86-r5
kmod-hwmon-core 6.6.73-r1 6.6.86-r1
kmod-leds-gpio 6.6.73-r1 6.6.86-r1
kmod-lib-crc-ccitt 6.6.73-r1 6.6.86-r1
kmod-lib-crc32c 6.6.73-r1 6.6.86-r1
kmod-lib-lzo 6.6.73-r1 6.6.86-r1
kmod-mac80211 6.6.73.6.12.6-r1 6.6.86.6.12.6-r1
kmod-mt76-connac 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mt76-core 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mt7615-common 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mt7615e 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mt7622-firmware 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mt7915-firmware 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mt7915e 6.6.73.2025.01.14~8e4f72b6-r1 6.6.86.2025.02.14~e5fef138-r1
kmod-mtd-rw 6.6.73.2021.02.28~e8776739-r1 6.6.86.2021.02.28~e8776739-r1
kmod-nf-conntrack 6.6.73-r1 6.6.86-r1
kmod-nf-conntrack6 6.6.73-r1 6.6.86-r1
kmod-nf-flow 6.6.73-r1 6.6.86-r1
kmod-nf-log 6.6.73-r1 6.6.86-r1
kmod-nf-log6 6.6.73-r1 6.6.86-r1
kmod-nf-nat 6.6.73-r1 6.6.86-r1
kmod-nf-reject 6.6.73-r1 6.6.86-r1
kmod-nf-reject6 6.6.73-r1 6.6.86-r1
kmod-nfnetlink 6.6.73-r1 6.6.86-r1
kmod-nft-core 6.6.73-r1 6.6.86-r1
kmod-nft-fib 6.6.73-r1 6.6.86-r1
kmod-nft-nat 6.6.73-r1 6.6.86-r1
kmod-nft-offload 6.6.73-r1 6.6.86-r1
kmod-nls-base 6.6.73-r1 6.6.86-r1
kmod-ppp 6.6.73-r1 6.6.86-r1
kmod-pppoe 6.6.73-r1 6.6.86-r1
kmod-pppox 6.6.73-r1 6.6.86-r1
kmod-slhc 6.6.73-r1 6.6.86-r1
kmod-thermal 6.6.73-r1 6.6.86-r1
kmod-usb-core 6.6.73-r1 6.6.86-r1
kmod-usb-xhci-hcd 6.6.73-r1 6.6.86-r1
kmod-usb-xhci-mtk 6.6.73-r1 6.6.86-r1
kmod-usb3 6.6.73-r1 6.6.86-r1
libmbedtls 3.6.2-r1 3.6.3-r1
libnl-tiny 2023.12.05~965c4bf4-r1 2025.03.19~c0df580a-r1
libopenssl 3.0.15-r1 3.0.16-r1
libucode 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
luci 24.297.79519~bcd13b9 25.130.38691~48b6321
luci-app-attendedsysupgrade 25.044.01357~67d27ad 25.130.38691~48b6321
luci-app-firewall 25.014.06885~bd39c63 25.130.38691~48b6321
luci-app-package-manager 24.341.02353~276fef8 25.130.38691~48b6321
luci-base 25.014.55016~7046a1c 25.130.38691~48b6321
luci-light 23.024.33244~34dee82 25.130.38691~48b6321
luci-mod-admin-full 19.253.48496~3f93650 25.130.38691~48b6321
luci-mod-network 25.021.30718~36b6107 25.130.38691~48b6321
luci-mod-status 25.009.65022~20bf9a4 25.130.38691~48b6321
luci-mod-system 24.336.49068~ef16778 25.130.38691~48b6321
luci-proto-ipv6 24.350.69236~8d13ea4 25.130.38691~48b6321
luci-proto-ppp 25.009.71487~a88d4af 25.130.38691~48b6321
luci-ssl 24.328.43591~9e70c9a 25.130.38691~48b6321
luci-theme-bootstrap 24.357.59015~779ca14 25.130.38691~48b6321
nano-full 8.3-r1 8.4-r1
openssh-sftp-server 9.9_p1-r1 9.9_p2-r1
ucode 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-fs 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-math 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-nl80211 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-rtnl 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-ubus 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-uci 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
ucode-mod-uloop 2024.07.22~b610860d-r3 2025.02.10~a8a11aea-r1
wireless-regdb 2024.10.07-r1 2025.02.20-r1
89 packages are out-of-date
Default package analysis:
Default Provided-by
nftables nftables-json
wpad-basic-mbedtls not installed
There are currently package build failures for 24.10.1 aarch64_cortex-a53:
Feed: telephony
freetdm Mon May 12 13:40:25 2025 - not installed
Failures don't affect this device, details at
https://downloads.openwrt.org/releases/faillogs-24.10/aarch64_cortex-a53/
WARNING: There are 1 missing default packages, confirm this is expected before proceeding
Request:
Version 24.10.1 r28597-0425664679 (kernel 6.6.86)
Request hash:
e5286710053f54e3e114f7ebc73d69295e6cac03171d890c360c1b20c9d6b6f5
--
Status: queued - 0 ahead of you
Progress: 0s total = 0s in queue + 0s in build
--
Status: container_setup
Progress: 5s total = 0s in queue + 5s in build
--
Status: validate_manifest
Progress: 15s total = 0s in queue + 15s in build
--
Status: building_image
Progress: 30s total = 0s in queue + 30s in build
--
Status: done
Progress: 35s total = 0s in queue + 35s in build
Build succeeded in 35s total = 0s in queue + 35s to build:
version_number = 24.10.1
version_code = r28597-0425664679 (requested r28597-0425664679)
kernel_version = 6.6.86
rootfs_size_mb = default
init-script = no-init-script
Image source: https://sysupgrade.openwrt.org/store/e5286710053f54e3e114f7ebc73d69295e6cac03171d890c360c1b20c9d6b6f5/openwrt-24.10.1-e113f384b3a8-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
Image saved : /tmp/firmware.bin
Manifest : /tmp/firmware-manifest.json
Verifying : /tmp/firmware.bin (12727506 bytes) against /tmp/firmware.sha256sums
Saved sha256 matches
ERROR: sysupgrade validation failed:
stderr =
Tue May 13 10:39:44 PDT 2025 upgrade: The device is supported, but this image is incompatible for sysupgrade based on the image version (1.0->2.0).
Tue May 13 10:39:44 PDT 2025 upgrade: SPI-NAND flash layout changes require bootloader update. Please run the UBI installer version 1.1.0+ (unsigned) first.
Image check failed.
Cosmo
May 13, 2025, 5:54pm
6594
I'm going to see what I can do here first. If I can't get Attended Sysupgrade to work, I will take you up on your offer.
Thank you!
Aha!
If you're already running 24.10.0, you already have the correct NAND layout. But the problem is that on your current settings, you haven't set the compat version to 2.0. So you need to run this commands first:
uci set system.@system[0].compat_version=2.0
uci commit
Then proceed with owut or Luci Attended Sysupgrade.
Cheers!
EDIT: more info on that change here . There are other files that you should also check. It looks like you restored an old backup from 23.05.x era.
1 Like
Cosmo
May 13, 2025, 6:28pm
6596
el_charlie:
Aha!
If you're already running 24.10.0, you already have the correct NAND layout. But the problem is that on your current settings, you haven't set the compat version to 2.0. So you need to run this commands first:
Bingo! That was it.
I've also modified the other two files in the change you pointed me to. One down, 4 to go.
1 Like
Hi, its time since I visit this thread.
I am still using this router. It was rock solid for many time.
Now I need to upgrade openWRT since I need some newer package.
So I am planning to upgrade to 24.10, but I am afraid of having problems with the upgrade in this router, as it is not so new router.
Is there any problem with compatibility with the new version.
I have had previously problems upgrading a fritz box router.
May I just use lucy automated attended sysupgrade and keep configuration?
I will download current config previously, just in case.
So if I understand it well, I cannot use the attendent sysupgrade from luci.
I was previously using 25.05.2 and ubi (I had already upgraded to ubi previously).
I should download de generated firmware, the backup de config file and delete
/etc/config/ubootenv
/etc/fw_env.config
What I did not complete understand is the 1 step with uci instructions and 5 step abotu flashing unsigned installer
It seems you cannot directly flash the downloaded firmware generated by sysupgrade
Correct. You can, at least, use Luci Attended Sysupgrade to generate a sysupgrade image with all your installed packages up to date and download said firmware file to your PC. Or use the Firmware Selector.
Step 1 is to log into your router with SSH (Terminal on linux/macOS or Putty on Windows) and execute the commands.
The installer is on Daniel's GitHub and was linked on the Wiki above the instructions. The link is this one.
So, you need to do the following, in a nutshell:
Create and download your custom firmware image with Attended Sysupgrade (do NOT install it) or the Firmware Selector.
Download the UNsigned 1.1.4 installer from Github.
SSH in the router to input the commands to set compat_version to 2.0 and download the config backup. Details in the Wiki.
Edit said backup deleting the files, again, mentioned on the Wiki.
Flash the UNsigned installer without keeping settings. The router will reboot to a recovery environment (you need a LAN cable to access it) where you can do a Sysupgrade with the firmware downloaded in Step 1. Again, don't keep settings.
Restore your backup with the deleted files mentioned on the Wiki.
Profit.
This tedious procedure must be done ONCE. For all future updates, you can use Owut or Luci Attended sysupgrade without issues.
3 Likes
Thanks a lot, now I understand it much better.
What I did not understand previously was the part of flasshing the installer and where to get it. Now it is much more clear for me.
I will wait to do it in a moment were people at home is not using the internet, as it is error prone and may take a while.
1 Like
Thank you.
Thanks a lot.
2 Likes
hanaro
May 15, 2025, 2:41pm
6603
Title: Linksys E8450 (UBI) - Needs manual boot after flashing 24.10 sysupgrade
Post:
Hi everyone,
I'm running into an issue with my Linksys E8450 (UBI) after attempting to upgrade to OpenWrt 24.10 .
The device was originally running OpenWrt 23.03.1 .
I flashed OpenWrt 24.10 sysupgrade (UBI) via LuCI, but the device failed to boot afterward.
I connected via serial and used mtk_uartboot-v0.1.1-x86_64-pc-windows-msvc to enter recovery.
I installed openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb , and it booted successfully into OpenWrt.
I then attempted to flash 24.10 sysupgrade again from LuCI.
After flashing 24.10 sysupgrade:
The device does not automatically boot .
I get stuck at the U-Boot prompt (MT7622>).
If I manually type boot, the system boots normally into OpenWrt 24.10.
CPU: MediaTek MT7622
Model: mt7622-linksys-e8450-ubi
DRAM: 512 MiB
Core: 48 devices, 21 uclasses, devicetree: separate
MMC:
Loading Environment from UBI... SPI-NAND: FM35Q1GA (128MB)
ubi0 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 18, need 20
...
Net: eth0: ethernet@1b100000
MT7622>
Why is the boot process stopping at the U-Boot prompt?
Is this a known issue with 24.10 on E8450 UBI?
Do I need to set any bootcmd or U-Boot environment variable manually to fix this?
Any help would be appreciated ā Iād like the device to automatically boot without requiring serial access and manual boot each time.
Thanks!
If you had read 2 posts above, you should've seen the steps to upgrade from 23.05 to 24.10.
Did you flash the 1.1.4 installer?
hanaro
May 15, 2025, 3:11pm
6605
Are you installing it from u-boot? I'm sorry
The installer image that you should know about if you already where on 23.05.
There is a new installer to move all the partitions to UBI for 24.10 onwards that was meant to be flashed prior flashing 24.10 or recent SNAPSHOTs.
The good part is that you can use the serial console, so fixing the router should be easier, but I don't know how. Maybe @daniel can chime in.
