Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

I did a clean build from git master branch, and only selected test kernel under "global build settings" in "make menuconfig" in order to build 5.10 kernel. Everything else is left at default.

But my wrt1900ACv2 router wont boot with my build. After I flash it, the power led keeps flashing every 0.5 second.

Is there anything I missed in order to build with a 5.10 kernel? I've verified my router can boot with Divested-WRT 5.10 kernel builds though...

I believe you need to resize the partition as seen in the divested patch for 5.10, or else the kernel is too big

thanks for the info, but wrt1900ACv2(cobra) should has 6MB kernel partition.

ahh, my mistake. Not sure since I only have a 32x

Yea I have a WRT32X too. The good news for us is the kernel resizes are committed to master now, so we should start seeing official 21.02 snapshots soon for our routers. They've previously only been on WRT32000ACM. Linking the commits below for those that might have missed them:

Summary

https://github.com/openwrt/openwrt/commit/15309f5133d55e92bec3ed91dfb3ac9d124f6a96
https://github.com/openwrt/openwrt/commit/b4f76d9f0d61779b5e04228d1eb3f2ba412ffd26

iif it gets picked to that branch.

Good point. It’s up on snapshot now though (based off master branch I assume?). I’m probably going to try one later this week. Still running the final Davidc502 and it’s been awesome but itching for an update and to mess with DSA.

I switched to DSA a long time ago, never looked back.

nitroshift

1 Like

PR4307 (Introduce support for managing config device and config bridge-vlan sections) was also merged and available in snapshot about a week ago. https://github.com/openwrt/luci/pull/4307

Kernel size change on the master are excellent news, I don't have to deal with customized size anymore :smiley:
Didn't have much sense nor future that huge effort to reduce kernel size, the gain was minimal and it was a matter of time.

Can anyone define for me what snspshot means in the openwrt release cycle? Is it equivalent to a beta?

'from the head of the branch'

master -> snapshot = based on current master code ( bleeding edge - everything is the latest )
21.02 -> snapshot = based on current 21.02 code ( since branching... latest only for that branch )

or more simply... the 'taken from the running state'

I would try DSA, if there was an easy way to convert a VLAN setup from switch to DSA.

WRT32X build is now up on 21.02-snapshot branch :slight_smile:

2 Likes

I've been looking in this thread if it is safe to get back to the official stable OpenWRT build from a Davidc502 build while keeping the settings, but it is not clear to me yet if settings will be kept in a sysupgrade to a different build (from Davidc's to Official, I mean).

Anyone has tried this before?

Of course, the beauty of the mvebu platform is it dual boots firmware. Just read the doc page carefully on flashing and you can keep everything on the main partition while it flashes to the alternate.

1 Like

Thanks phinn. I've read the Wiki and, if I'm not mistaken, since I already have Davidc's build, I want to "upgrade" to the official stable 19.07, what means, the .bin file. (because the .img file is what I used when moving from the LinkSys firmware to Davidc's), correct?

PD: Always so scared when updating the router firmware... :smiley:

Yes it sounds like you have it right. Definitely read the page carefully. You can use the firmware selector to make sure you use "sysupgrade" to update your current build, or "factory" to install from the OEM partition.

For example, I've kept the OEM Linksys firmware on mine for years because every time I update OpenWrt I always reboot into the OEM firmware and do the update from there so it flashes to the other partition. Then reboot back into OpenWrt and it's updated. I just first SSH in and choose the active/boot partition which is described on the wiki. I'll link below.

Summary

https://openwrt.org/toh/linksys/wrt_ac_series

https://firmware-selector.openwrt.org/

I can use the advanced_reboot to switch partitions or

SSH

  1. Determine current partition:

/usr/sbin/fw_printenv -n boot_part

  1. Boot

  2. Primary Partition:

/usr/sbin/fw_setenv boot_part 1 && reboot

  1. Alternate Partition:

/usr/sbin/fw_setenv boot_part 2 && reboot

Im using this:

Can i for example upgrade to last david502c build using the "sysupgrade" file ?

I would sysupgrade if you're staying within davidc502 builds. I wouldn't sysupgrade from davidc502 to OpenWrt 19.07.7 or 21.02, I would do a clean install for that. It might work I'm just not sure.