Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

Don't overestimate priority levels in flyspray, no one classifies bugs that way. DSA for netifd is staging, but pending merging to master, afaik initial DSA support is also being tested and just waiting for the former.

1 Like

Hello folks

I have a WRT1900AC and have tried 18.06.1 and 19.07.4 with very unstable Wifi. The latency to the router's own IP is in the 2 digits milisecons mark. Very often it disconnects from either 2Ghz or 5 Ghz radios and takes a while to re-connect.

Using David's build (r13342) it seems better than 19.07.4, although not 100% still with some instability on the radios that disconnect every in a while and takes some time to be able to connect again.

Has anyone had any success with 19.07.4 ?
The current OpenWrt snapshot for some reasons doesn't seem to have the builds for WRT1900AC v1, only for v2. Does anyone know why ?

@davidc502 does your build use the same mwlwifi driver of OpenWrt Snapshot or does it use any modified version that makes it more stable ?

Hi! Iā€™m using 19.07.4 with this driver and stability is about 90%, meaning you can use it pretty well https://github.com/eduperez/mwlwifi_LEDE/releases

Partition size has been exceeded for two wrtpac targets (mamba, venom). See PR3205

i will repeat my plea to increase the size of the lernel partition to 6 MB for wrt1900v1 and for wrt32x. the rationale is clearly stated here:



1 Like

You need to check if the bootloader can really cope with larger kernels, afaik linksys sets a fixed size in ubootenv to load from flash - just changing the partitioning wouldn't help without changing ubootenv (and that's problematic for first time installers, upgraders and anyone wanting to revert to the OEM firmware); this wasn't an issue on the ipq806x devices covered by my patches.

1 Like

Those two targets still build successfully for individuals, but the size increase with each kernel push will bite eventually. For example two builds done today:

5.4.71

  3070498 Oct 19 12:41 linksys_wrt1900ac-v1-kernel.bin
  3065738 Oct 19 12:41 linksys_wrt32x-kernel.bin

5.4.72

  3070666 Oct 19 14:00 linksys_wrt1900ac-v1-kernel.bin
  3065906 Oct 19 14:00 linksys_wrt32x-kernel.bin

Thanks for the reply @anomeome
Strange because WRT1900ACv1 has 128MB of total flash, so even with 2 partitions there is a fair amount of space to have a much bigger partition, doesn't it ?

Seems the rationale behind @ghoffman make sense, what do you think ?

You need to check https://openwrt.org/toh/linksys/linksys_wrt1900ac#flash_layout for details, https://openwrt.org/toh/linksys/linksys_wrt1900ac#openwrt_bootlog (in particular NAND read: device 0 offset 0xa00000, size 0x400000) would also be relevant. So even with 6 MB flash being reserved for the kernel, the bootloader will only attempt to read the first 4 MB of that. In the best of all cases this size value it defined in uboot-env (see fw_printenv for hints) - changing this might work, or it might fail fatally <-- this would need testing (with an oversized kernel), in worse cases the bootloader would need rebuilding with different settings or the introduction of a second stage bootloader between u-boot and kernel+rootfs.

Hi @slh perhaps some stuff from the kernel can be moved to modules. But yes, second stage could be also an option in the worse case.

Hi @razor7 did you install 19.07.4 and then dowgraded it to eduperez/mwlwifi version with "opkg install --force-downgrade" ?

Yes, that's it!

@davidc502 : Can you help clarify this for me?

Just a quick question. I am getting ready to upgrade from kernel 4.14.103 r9506 to 5.4.41 r13342 of David's builds. Any gotcha's I need to know about (1900ACS)?

(I was advised download a backup of my config, remove /etc/config/ubootenv and /etc/fw_env, repack. Upgrade w/o keeping config, then restore the modified backup.)

I'm currently running r12235 / kernel 4.19.101 of David's build, but unfortunately I don't have time to follow the developments in this thread very often, so I usually just visit his site every few months and upgrade to the latest build (mainly just for security reasons).

I just went to his site after not upgrading for quite some time and read his notice advising that there won't be any new builds for the time being. So, I'm wondering what I should 'upgrade' to - the last Davidc builds are from May of this year - would it still be OK to use this version, several months on? Or are there any other community builds which would be preferable? I saw some mentions of a 'SuperWRT' build? Or would the latest official OpenWRT 19.07.4 release be the best choice?

Just run the final davidc502 build. Comes with Linux kernel 5.4.x and is rock solid for me. At least until OpenWrt does a 20.x build (if they actually do) then re-evaluate.

3 Likes

Nice build, no issues, but dragons living in update process - read thread about it and DO NOT keep configuration.

1 Like

Thanks for the warning - is there a guide anywhere on how to safely upgrade?

Check up this thread, we have a discussion about it close to firmware release date.

Basicaly, you should NOT keep the configuration.

If you made backup - you need to delete 2 hardware-related files from it before restore backup. Or set all options again manually.

1 Like

I tried the SuperWRT build dated October 11 on my WRT3200ACM and it was a disaster, with random loss of Internet connectivity (not wireless connectivity, just Internet) on multiple devices. I went back to the latest davidc502 build and it has been reliable. I haven't yet tried the latest 19.07.4 build.