Linksys EA6350v3: Periodic boot to stock

Installing and Using OpenWrt
1

Hi all!

This is a dual firmware device. I followed the wiki guide to install OpenWrt. The issue is that after 2 reboots the router boots the stock firmware and I have to use the 10/15seconds failed boots to boot to OpenWrt again.
Someone has already similar issue and they decided to install OpenWrt on both partitions. I don't want to do that.
Instead, I was wondering if I could move the stock firmware to the alt_kernel sector instead.

Any ideas how to proceed for that? A sketch of the steps would be helpful.

Thanks

2

I'll make you a deal:

I'll tell you the fix (which is in the page for your router) if you promise to read the page just be familiar with your router.

Deal?

Sorry I lied: it is not in the V3 page; the fix is for V4.

Your version should not be doing that.

Are you sure you have the correct version (v3) and the correct firmware?

1 Like
3

Yes. I'm pretty sure.

I using OpenWrt 22.03.06 build.

I thought of playing with the fw_setenv to change boot commands to force alt_kernel. But I didn't want to do anything irreversible

Screenshot_20240228_173810_Firefox
Screenshot_20240228_173810_Firefox1080×1985 179 KB

4

This link goes to OpenWrt's firmware selector.

It is already set to your model (I have the V4, sorry I thought they were just different versions of the same thing). Choose 'Customize installed packages and/or first boot script'. and flash it with that.

It adds packages OpenWrt has determined should be on your router.
Then, let's see if it does it again.

I'll do some searching because most dual partition routers are warned against writing OpenWrt to both partitions.

Well, .06 is not official yet, so lets go with known stable .05 in the link

1 Like
5

Thanks a lot. I didn't know I could build it online, I was too lazy to set a VM for the build.

I'll try it and see. I guess I'll just use the trick from v4 if things don't work out.

6

Not advised.

Set everything to defaults before you flash. We don't want anything corrupting the install.

1 Like
7

Then what if I get to install OpenWrt on the kernel sector then install OEM firmware on the alt_kernel sector... Then I don't have to tweak the setenv?

8

Well, I've never tried that so I don't know.

Did it again revert to OEM on the third reboot after you flashed it with current firmware, confirmed good (22.03.5 according to the firmware selector).

I try not to get ahead of myself and out think things; I tend to do things as told and if I have an issue duck duck go it.

1 Like
9

Did you do this step?

OpenWrt 23.05 (at least 23.05.2) works also in this device but you can not install or upgrade to it without first doing bootloader variable fw_setenv kernsize 500000 change . Thus the supported version in above table is 22.03 series which is the last version which works out of the box without kernsize change. See more from below Installation of 23.05 or newer.

Not saying to do it, just need to know.

10

Yes, I've followed the guide.
I didn't go for the 23.x build. I only used 22.03.06, the kernel resizing was not necessary in my case.

I've went ahead and read v4 guide. It seems it's describing the same issue I'm having now with v3 in relation to periodic reverting to stock.

Have you tried installing OpenWrt via serial connection before? I just want to make sure that I can always use uboot tftp if I screw up :nerd_face:

11

Nope, but I'm not afraid of it.

That is what the backup partition is for.

13

Have you verified that you are using the exact right kernel for your hardware/revision? Are there errors in syslog during startup? Have you considered doing the u-boot configuration which will allow you to run the more current kernel instead of the older smaller one?

https://openwrt.org/docs/techref/bootloader/uboot.config

14

Linksys' firmware page says to set the flash to default values after flashing with their firmware and before you reboot. Did you do that?

IOW:
Flash OEM
reboot
set linksys to default values.
flash to OpenWrt.

But this is all with V3.