Page 26 of 28

Re: Gargoyle 1.15.x BETA - 2024-11-13 - Based on OpenWrt 23.05

Posted: Sun Mar 23, 2025 5:43 pm
by Lantis
If it can be done in OpenWrt, yes.
By default Gargoyle should display basic thermal properties on the overview page.
If it doesn’t (or there are extra parameters) feel free to show me and I’ll change it.

The fan is controlled off defined set points. If there is manual control you will need to add a script.

Re: Gargoyle 1.15.x BETA - 2024-11-13 - Based on OpenWrt 23.05

Posted: Mon Mar 24, 2025 12:03 am
by pythonic
ViBE wrote:
Sun Mar 23, 2025 11:54 am
just realised that GL.iNet MT-3000 became supported. can Gargoyle read temperature and able to control the built in fan?
see fan control - while the info is nominally for 24.10 I think you should be able to adapt this for use with 23.05 based Gargoyle builds (at least the required kmod should be included in the Gargoyle image).

edit: maybe this might give you a lead on more sophisticated control...

Re: Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

Posted: Tue Apr 01, 2025 1:11 pm
by oliver44
@Lantis wrt1900acs v2 https://s.go.ro/sp0qt3ix

Code: Select all

Disable Bandwidth Monitor

/etc/init.d/bwmon_gargoyle stop
/etc/init.d/bwmon_gargoyle disable



First, just software flow offloading:

Code: Select all

uci set firewall.@defaults[0].flow_offloading='1'
uci commit
ubus call network reload

 hardware flow offloading:

Code: Select all

uci set firewall.@defaults[0].flow_offloading_hw='1'
uci commit
ubus call network reload



uci set network.globals.packet_steering='1'
uci commit
ubus call network reload



Re: Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

Posted: Tue Apr 01, 2025 6:14 pm
by Lantis
oliver44 wrote:
Tue Apr 01, 2025 1:11 pm
@Lantis wrt1900acs v2 https://s.go.ro/sp0qt3ix

Code: Select all

Disable Bandwidth Monitor

/etc/init.d/bwmon_gargoyle stop
/etc/init.d/bwmon_gargoyle disable



First, just software flow offloading:

Code: Select all

uci set firewall.@defaults[0].flow_offloading='1'
uci commit
ubus call network reload

 hardware flow offloading:

Code: Select all

uci set firewall.@defaults[0].flow_offloading_hw='1'
uci commit
ubus call network reload



uci set network.globals.packet_steering='1'
uci commit
ubus call network reload


bwmon can be stopped from the GUI as of several versions ago, if you prefer.

Re: Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

Posted: Wed Apr 02, 2025 9:45 am
by oliver44
Can all of this be included in the firmware:software flow offloading, hardware flow offloading?
https://jmp.sh/s/iPcx8UWEDaaiGj49dzMA
https://jmp.sh/s/pqWaE5tvLmm42P7lgpvI

Re: Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

Posted: Wed Apr 02, 2025 7:08 pm
by Lantis
oliver44 wrote:
Wed Apr 02, 2025 9:45 am
Can all of this be included in the firmware:software flow offloading, hardware flow offloading?
https://jmp.sh/s/iPcx8UWEDaaiGj49dzMA
https://jmp.sh/s/pqWaE5tvLmm42P7lgpvI
No, not in the short term.
The features will likely never be compatible.
I do not have time to add features that will just drive users to the forum saying
“Feature X doesn’t work because I turned on offloading”

viewtopic.php?t=17924

Re: Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

Posted: Thu Apr 03, 2025 11:04 am
by ektus
Downloading the latest beta for the gl-inet GL-MT6000 (gargoyle_1.15.x-mediatek-filogic-glinet_gl-mt6000) I noticed a huge size difference between the factory (43MB) and sysupgrade (15MB) files. Why is this?

Re: Gargoyle 1.15.x BETA - 2025-03-31 - Based on OpenWrt 23.05

Posted: Thu Apr 03, 2025 5:34 pm
by Lantis
In the factory image the kernel is always padded out to 32MB, then the rootfs is added.
It doesn’t matter as you will almost never need the factory image for this device.

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Thu Apr 10, 2025 11:09 am
by Lajkzy
Im using 1.15.X (Built 20241013-2237 git@347e0534) on my Asus rt-ac51u. I cant flash another firmware, its stuck, no matter what i try it wont flash anything else. I also tried using asus recovery tool but it wont accept the firmware.. I had same issue with WNR2200 but i was able to use recovery mode. Is this build broken? Can i delete the partitions or force flash it in putty?

Partitions look like this on 51u
/root$ cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "SBL1"
mtd1: 00020000 00010000 "MIBIB"
mtd2: 00060000 00010000 "QSEE"
mtd3: 00010000 00010000 "CDT"
mtd4: 00010000 00010000 "DDRPARAMS"
mtd5: 00010000 00010000 "APPSBLENV"
mtd6: 00080000 00010000 "APPSBL"
mtd7: 00010000 00010000 "ART"
mtd8: 08000000 00020000 "ubi"

Re: Version 1.14.0: Based on OpenWrt 22.03

Posted: Thu Apr 10, 2025 8:22 pm
by Lantis
Lajkzy wrote:
Thu Apr 10, 2025 11:09 am
Im using 1.15.X (Built 20241013-2237 git@347e0534) on my Asus rt-ac51u. I cant flash another firmware, its stuck, no matter what i try it wont flash anything else. I also tried using asus recovery tool but it wont accept the firmware.. I had same issue with WNR2200 but i was able to use recovery mode. Is this build broken? Can i delete the partitions or force flash it in putty?

Partitions look like this on 51u
/root$ cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "SBL1"
mtd1: 00020000 00010000 "MIBIB"
mtd2: 00060000 00010000 "QSEE"
mtd3: 00010000 00010000 "CDT"
mtd4: 00010000 00010000 "DDRPARAMS"
mtd5: 00010000 00010000 "APPSBLENV"
mtd6: 00080000 00010000 "APPSBL"
mtd7: 00010000 00010000 "ART"
mtd8: 08000000 00020000 "ubi"
Moderator: I’ve moved your post to the 1.15 discussion as it was not relevant to 1.14.

What new version are you trying to put on?

I would suggest trying to upload the firmware to /tmp/ and run
sysupgrade -v -n /tmp/filenamehere.bin

And look at what if any errors are reported.
Please note the above command will attempt to upgrade without preserving settings.