Hi All,
Is there any specific process that need to follow to update from 23.05 to 24.10 for Linksys EA8100? I try to do sysupgrade but it seems like does not work. The router is no longer accessible and give bogon network, 169.254.159.201. Any guide on how to fix it?
https://openwrt.org/toh/linksys/ea8100_v1
It's a dual partition device, failing a boot three times, should make it boot the other partition.
FYI I have one and it's working find on 24.10.0
can't remember doing anything special while upgrading
have not had to recover this model yet tho
It is odd that it does not working for me. Does the file size is correct? for openwrt-24.10.0-ramips-mt7621-linksys_ea8100-v1-squashfs-sysupgrade.bin, the file size is 7601KB. For openwrt-24.10.0-ramips-mt7621-linksys_ea8100-v1-squashfs-factory.bin, the file size is 9730KB.
It looks about right but unless you do this in bytes
the correct way is to get a sha256sum of your file and compare to the
OpenWrt one listed where you download the file from
Did you have any luck booting into the linksys firmware from multiple resets ?
No luck so far. It getting rejected and boot into the original linksys firmware. Was thinking to try to upload 23.05 and see how does it work. Initially it was running 23.05 just fine and I try to upgrade to 24.10 and it seems like stuck in the process and force me to hard reset. Luckily I am able to and now it is running on original linksys firmware again. But since then I am not able to update to 24.10. Haven't try on 23.05 yet.
It's good, not bricked
there maybe a fault with the V24 factory file
if V24 didn't work then I'd try V23 and V22
you should at lest be able to sysupgrade from the earlier version
When you do sysupgrade, did you do from the luci web portal or are you using SSH or telnet? I did that from the web portal earlier.
I used sysupgrade via the luci web interface
I did test most of the rc versions, so I did go thought them tho
So what happen when you use the linksys update page
with the V24 factory file ?
is it accepted but won't boot after ?
"is it accepted but won't boot after ?". Yes, that is correct.
Do I need to reset the configuration/setting when doing the update from 23.05 to 24.10? or keep the setting? I did select keep the setting that later it won't boot.
While having trouble, best to not keep settings
if it is a keeping setting problem, then a factory reset
should fix it while on and booted, hold down reset button Until lights change
maybe light on this one and it should erase openwrt setting anyway
it seems like keeping the setting that cause the issue. I try to do sysupgrade one more time after successfully update to 24.10 and it goes back to the original problem. It has been more than 15 minutes already and it still flashing.
1 Like
I have a new issue with my linksys ea8100 v1. I have successfully upgrade to 24.10. However the router seems like stuck during power on or rebooting. It become unreachable. If I take a look at the network port, only left led that is light up. The right one does not. I switch off and on couple of time the power switch then only it works again. I check the system log but I don't see any error. What could be the issue? I have not experienced this on other routers that are running openwrt. This is a unique use case for me.
I've linked the system and kernel log in case if I overlooked something
https://www.mediafire.com/folder/ljloggq95cp4j/EA8100v1
Any assistants would be much appreciate it. Thanks, in advance.
I'm little confused
if your router is unreachable, how did you get the logs ?
In the logs I see "lease of 192.168.1.61 obtained from 192.168.1.1, lease time 43200"
is the wan on the same IP subnet, "192.168.1.*" ?
And that's LAN so it looks like the LAN is getting DHCP I must be reading this wrong
is it protecting itself ?
did you try to boot it up without wan connected ?
@Lucky1, I restart the router multiple times (by power off/on the power switch) until it is reachable, that is how I am able to connect to the router and extract the logs. I am using this as AP right now. Not as router. The lan interface is setup as DHCP client.
Ok so when you can get to it, it's working so the logs reflect that
mine is also setup as an access point
what about erased, can you get to it ?
What do you mean by erased? That is all the logs that I can see. Perhaps, it does not even logged, I assumed
The default OpenWrt setting as just a plan router
same as the "Preform reset button" in OpenWrt or not keep setting in sysupgrade
if you are having trouble connecting
the 1st thing you do is get the basic setup to work
Yup. That is what I did. Once the original firmware is stable. I install factory.bin. Once it has been successfully installed. I configure the interface and wifi. Each changes before I reboot, I check on the log if there is any error. So far, none is captured. But the symptom is the same. It seems like stuck with only left led that light up and it works fine after I try to restart a couple of times.
In Kernel log, I did see these lines, Not sure if it is related or not
mtdblock: MTD device 'devinfo' is NAND, please consider using UBI block devices instead.
[ 1.124702] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 1.132691] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 1.260727] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
[ 1.267277] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
[ 1.274162] pci 0000:00:01.0: BAR 0: no space for [mem size 0x80000000]
[ 1.280754] pci 0000:00:01.0: BAR 0: failed to assign [mem size 0x80000000]