You're welcome
![Cool 8-)](./images/smilies/icon_cool.gif)
Moderator: Moderators
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
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.pythonic wrote: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.
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.pythonic wrote: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.
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
So sorry for the delay on this, I forgot about it
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"