Page 7 of 8

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Sat Sep 09, 2023 6:37 am
by Lantis
So it gave you a warning and you ignored it?
Depending on device it may have required a factory flash anyway. The architecture has changed significantly for such devices.

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Sat Sep 09, 2023 11:54 am
by encro
Lantis wrote:
Sat Sep 09, 2023 6:37 am
So it gave you a warning and you ignored it?
Depending on device it may have required a factory flash anyway. The architecture has changed significantly for such devices.
Yep :D

But only after doing uninstalling plugins, checking mode specs again and confirming the RAM and Storage lol, then thinking the error must be an actual error lol

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Mon Sep 11, 2023 8:56 pm
by snake218
Works on Archer C7 v2, but if you enable QoS it caps download speed to about 60mb only.

I had the same problem with firmware 1.13.0, last stable fw that don't cap speed for me is 1.12.0.

Any fix or something besides QoS can't be disabled to get more performance?

Thanks for your work and time.

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Sat Jan 06, 2024 12:38 am
by angus
Lantis wrote:
Tue Jul 25, 2023 7:46 am
angus wrote:
Tue Jul 25, 2023 7:11 am
Awaiting 1.14.0 for Linksys WRT3200ACM/WRT32X. Thanks.
It won't happen, so you can stop waiting.
You can wait for 1.15 for the Linksys AC series to be supported again.
Happy new year and approaching 1.15!

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Sat Jan 06, 2024 1:31 pm
by alkhall
Is TP-Link model AX6000 supported?

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Sat Jan 06, 2024 7:00 pm
by Lantis
alkhall wrote:
Sat Jan 06, 2024 1:31 pm
Is TP-Link model AX6000 supported?
No, it is a Broadcom based device and therefore very unlikely to be worth supporting.

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Thu Feb 01, 2024 5:04 pm
by Lajkzy
1.14 seems broken on WNDR3700v1. Factory img gets into bootloop, sysupgrade works but telling the storage is full, cant reset to solve this issue, any fix for v1?

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Wed Feb 07, 2024 10:18 pm
by whataboutnow
I used to have a couple of those before moving to the v4 and then on to what I'm using now -

If I recall correctly, I had to telent into it with a usb serial cable connected to the internal jumpers, push the stock firmware to it and then you can reflash with the factory image.

if you're in the UK, I might have that v1 I could post to you, or possibly even a v4 if I can dig them out :)

the reflash is pretty simple though 👍

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Fri Feb 09, 2024 10:55 pm
by pythonic
Lajkzy wrote:
Thu Feb 01, 2024 5:04 pm
1.14 seems broken on WNDR3700v1. Factory img gets into bootloop, sysupgrade works but telling the storage is full, cant reset to solve this issue, any fix for v1?
Unfortunately images for some of the 8MB flash routers get past the size checks in the build process but when these images are installed don't have enough free flash space to accept configuration file updates - hence the "storage full" message. At this time I would suggest going back to 1.13 pending release of a new version based on OpenWrt 23.05, as I doubt that there will be any updated 1.14 release.

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Tue Mar 19, 2024 10:54 am
by Eric3K
wilsonhlacerda wrote:
Thu Jun 29, 2023 8:43 pm
Eric3K wrote:
Fri Jun 02, 2023 10:47 pm
It doesn't appear compatible with my WDR4300 v1.3, even with default settings. It wouldn't activate the wireless interfaces and seemed to only briefly activate DHCP on ethernet before becoming unresponsive, and I ended up having to use TFTP to revert to 1.13.
Has anyone successfully upgraded TP-LINK TL-WDR4300 (or TL-WDR3600) to v1.14 without problems? Working fine? Thanks for reporting!
Seeing that there's new builds from https://eko.one.pl/?p=gargoylepl-1.14 available, I used TFTP to install gargoyle-1.14.0.3-tplink_tl-wdr4300-v1-squashfs-sysupgrade.bin and what do you know, it worked fine. I suspect there was a bug fix in OpenWrt 22.03.06, which it's based on.