Experimental Gargoyle 1.15.x (released as 1.14) beta 20230124

[pythonic]

Thanks @pythonic

You're welcome

[rg66]

Flashed Apr18/23 1.15.x recovery.bin on MR3420v5 and booted without issues. LED's are now working.

I haven't played around much yet but did notice that there is only 84KB free whereas Feb 1.15.x left me with 212KB to install a few plugins.

Cheers

[pythonic]

notice that there is only 84KB free whereas Feb 1.15.x left me with 212KB to install a few plugins.

Sadly more flash space got taken up by solving problems like the LEDs and it seems likely to get squeezed a bit more before the final release . You should still be able to configure extroot to a USB drive/stick to be able to install additional plugins. Depending on which plugins are involved, building a custom image might be the only way to avoid using extroot.

A fair bit of effort has gone into keeping 8MB flash devices viable on Gargoyle 1.15. OpenWrt have already flagged that the yet to be branched 23.xx release will be the last to support 8MB devices.

[rg66]

Sadly more flash space got taken up by solving problems like the LEDs and it seems likely to get squeezed a bit more before the final release . You should still be able to configure extroot to a USB drive/stick to be able to install additional plugins. Depending on which plugins are involved, building a custom image might be the only way to avoid using extroot.

I figured as much and have setup extroot but can live without the plugins if need be. I have thought about doing a custom build but it's been a few years since I've compiled anything. It's amazing how fast you forget everything.

A fair bit of effort has gone into keeping 8MB flash devices viable on Gargoyle 1.15. OpenWrt have already flagged that the yet to be branched 23.xx release will be the last to support 8MB devices.

And I appreciate the effort, Gargoyle is by far the best router firmware I've found and plan on using it as long as possible. Many thanks to everyone involved.

Cheers

[ektus]

I successfully installed the build from April 18th on my Archer C5 V1. It's running in gateway mode, WAN wireless static, OpenVPN Server and Access point for both 2.4GHz and 5GHz bands. Seems to be working just fine, but the logfile is being cluttered with entries:

Code: Select all

Fri Apr 21 04:16:41 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:16:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:16:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:16:55 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:10 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:16 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:16 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:25 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:29 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:38 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:40 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:17:54 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:01 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:09 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:16 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:17 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:17 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:17 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:17 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:17 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:24 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:39 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:53 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:54 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:18:54 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:19:01 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:19:02 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:19:19 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:19:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:19:50 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:03 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:07 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:20:08 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:08 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:08 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:08 2023 daemon.err uhttpd[5090]: sh: write error: Broken pipe
Fri Apr 21 04:20:16 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:20:19 2023 daemon.notice hostapd: handle_probe_req: send failed
Fri Apr 21 04:20:19 2023 daemon.notice hostapd: handle_probe_req: send failed

[Maniac]

@Lantis any chance you could add the Belkin F9K1115v2 to the ath79 builds? It's supported in OpenWRT. Thanks!

Building a test image overnight, will upload for you and if it tests fine happy to include it.

It is now available:
Factory
Sysupgrade

So sorry for the delay on this, I forgot about it

I've actually moved on from this router, but I do still have it so I ran some basic tests. I was able to connect to the internet. LAN works. 2.4Ghz and 5 Ghz wireless both work, only tested channels 5 and 36. I did only get 100 mbps on a speedtest over wifi, but I was only get 190 with openwrt when using it as an AP so maybe using it as a router too slowed it down even more.

Thanks for implementing this!

[rg66]

Instead of using extroot to install plugins I can just ssh into it and do everything the logread, webshell and diagnostics plugins do. I will miss Xeye theme though, it's really nice.

I did a fresh install of 1.15.x April build, did all my settings (WAN, wireless, static IP's, quotas, restrictions etc...) and was left with 54KB space in Root. It then jumped up to 80KB for some reason even though I didn't do any more settings. After a reboot it settled on 64KB free and I haven't updated the repos yet. Is this going to be enough for daily usage with bandwidth and quota monitoring?

I'm currently using a second MR3420v5 with the 1.13.x build pythonic posted and don't want to change to 1.15.x if I'm going to get the "Router storage full (read only) or is mounted in volatile storage (RAM)" error.

On a similar note, can Root usage/free space be shown in status instead of going to plugins every time?

Cheers

[rg66]

Noticed this error last night, it's also in Feb build.

Code: Select all

Gargoyle Version:1.15.X (Built 20230418-1112 git@acaaac1d)
Model:TP-Link TL-MR3420 v5

Code: Select all

Sat Apr 15 02:33:09 2023 kern.info kernel: [    0.348451] spi-mt7621 10000b00.spi: sys_freq: 193333333
Sat Apr 15 02:33:09 2023 kern.info kernel: [    0.366056] spi-nor spi0.0: gd25q64 (8192 Kbytes)
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.370971] 4 fixed-partitions partitions found on MTD device spi0.0
Sat Apr 15 02:33:09 2023 kern.err kernel: [    0.377461] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Sat Apr 15 02:33:09 2023 kern.err kernel: [    0.384933] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Sat Apr 15 02:33:09 2023 kern.err kernel: [    0.392785] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Sat Apr 15 02:33:09 2023 kern.err kernel: [    0.400286] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.408254] Creating 4 MTD partitions on "spi0.0":
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.413198] 0x000000000000-0x000000020000 : "boot"
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.421581] 0x000000020000-0x0000007c0000 : "firmware"
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.428464] 2 tplink-fw partitions found on MTD device firmware
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.434555] Creating 2 MTD partitions on "firmware":
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.439628] 0x000000000000-0x0000001d9021 : "kernel"
Sat Apr 15 02:33:09 2023 kern.warn kernel: [    0.444660] mtd: partition "kernel" doesn't end on an erase/write block -- force read-only
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.455675] 0x0000001d9024-0x0000007a0000 : "rootfs"
Sat Apr 15 02:33:09 2023 kern.warn kernel: [    0.460797] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
Sat Apr 15 02:33:09 2023 kern.info kernel: [    0.471242] mtd: setting mtd3 (rootfs) as root device
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.477269] 1 squashfs-split partitions found on MTD device rootfs
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.483647] 0x000000750000-0x0000007a0000 : "rootfs_data"
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.490369] 0x0000007c0000-0x0000007d0000 : "config"
Sat Apr 15 02:33:09 2023 kern.notice kernel: [    0.497985] 0x0000007d0000-0x000000800000 : "factory"

[Lantis]

Bad cell count? It’s just a warning and reasonably benign.
It’s being discussed upstream but no fix yet. Root cause identified however.

[SirSWE]

Works great on my XR500, thank you. But will this support Linksys WRT32x?