[    0.000000] Linux version 4.4.61 (shawn@stinky.workgroups.win) (gcc version 5.4.0 (LEDE GCC 5.4.0 r4132-f7fd2abf25) ) #0 SMP Mon May 15 02:39:15 2017
[    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
[    0.000000] MIPS: machine is ZBT-WE1326
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 1c000000  00000000 (usable)
[    0.000000]  memory: 04000000  20000000 (usable)
[...]
[    2.270000] MediaTek Nand driver init, version v2.1 Fix AHB virt2phys error
[    2.270000] spi-mt7621 1e000b00.spi: sys_freq: 50000000
[    2.280000] m25p80 spi32766.0: using chunked io (size=32)
[    2.290000] m25p80 spi32766.0: w25q128 (16384 Kbytes)
[    2.290000] 4 ofpart partitions found on MTD device spi32766.0
[    2.300000] Creating 4 MTD partitions on "spi32766.0":
[    2.300000] 0x000000000000-0x000000030000 : "u-boot"
[    2.310000] 0x000000030000-0x000000040000 : "u-boot-env"
[    2.310000] 0x000000040000-0x000000050000 : "factory"
[    2.320000] 0x000000050000-0x000001000000 : "firmware"
[    2.360000] 2 uimage-fw partitions found on MTD device firmware
[    2.360000] 0x000000050000-0x0000001c77ae : "kernel"
[    2.370000] 0x0000001c77ae-0x000001000000 : "rootfs"
[    2.380000] mtd: device 5 (rootfs) set to be root filesystem
[    2.380000] 1 squashfs-split partitions found on MTD device rootfs
[    2.390000] 0x0000006f0000-0x000001000000 : "rootfs_data"
[    2.400000] netif_napi_add() called with weight 128 on device eth%d
[    2.420000] libphy: mdio: probed
[    3.820000] mtk_soc_eth 1e100000.ethernet: loaded mt7530 driver
[    3.820000] mtk_soc_eth 1e100000.ethernet eth0: mediatek frame engine at 0xbe100000, irq 10
[    3.830000] mt7621_wdt 1e000100.wdt: Initialized

The Domino Team (GL-Inet) LEDE 17.01.1 release.

I’ve been a big fan of GL-Inet’s skinning and additions to OpenWRT, and after asking them a bit over a month ago about their progress with LEDE, well- here it is.

It’s been a spell between 17.01.1, and support for the ZBT WE1326. I’m hoping that the mt76 driver will be fairly trivial to mesh would take longer to type this than to update, even though it didn’t..

Having 802.11ac hardware, a stronger processor, and double RAM with the Domino interface? I’d but it!

Why is it “crabrouter”? It is not very happy taking non-Ralink SDK built kernels, among other, more obvious reasons. Sadly, the 2.4Ghz spectrum on this is still fairly unreliable when using the mt76 open source driver. It was sitting here on my kitchen table non-office transient workplace, and I had just been listening to Chicane (I have been looking to replace this CD for years- and find it at a thrift shop in rural Nevada of all places).. then frustpiration hit (frustration+inspiration): CRABROUTER CRUSH PUNY CASE- NO SEE SALTWATER HERE.

Thanks to a couple good resources, I was able to obtain a build of mt76 which isn’t in LEDE, and is behind a handful of revisions, but has many more features than it. I’ll probably merge the two and see how difficult it would be to get docs for the freakin’ chipset- but I have more pressing tasks, first!

I’m back to working on my WG3526-similar device, as it’s too cold to work on the cars, and the last HP 4100 was (re)built before lunch. It’s nice to have a functional panel on it.

I’ve found someone else who received a device which was based on the ZBT WE1326, and has a slightly different design than mine internally. Of course, his works with the stock LEDE DTS for the WE1326. Naturally!

I really like the default design of the hnyman WNDR3×00 builds which have dyndns, luci-ssl, et al- so I started working on one of my own now that, indeed, the 5Ghz is stable with a standard WE1326, even if the 2.4Ghz radios are still pretty useless (which is bad for my needs- I’m still primarily 2.4Ghz- one of the perils of not upgrading every couple years for the sake of upgrading).

Anyhow, onto the “Well duh” moments (some I’ve discovered though trial and error, yet others, I was aware of due to others’ trial and error):

• Don’t install openssh server by default- it has wisely disabled root by default, whereas dropbear will let you login, which is useful for a clean flash (which has no password). dropbear also uses fewer resources. Don’t be wasteful on embedded targets!
• Don’t forget to not only update your packages, but to install them. luci-ssl isn’t all that useful when your docroot is empty.
• Always sysupgrade from /tmp – I’ve never not done so, but I can’t imagine it being great to try to do so from a bit-banged MMC.
• Always be aware of your umask. Anything except umask 022 is going to cause pain!

Since my same-but-not device is a different revision than that of the only other person I know who owns one- I really have to question how we’re going to get this supported in LEDE since we don’t have a real definitive platform for this device, or revision history.

It looks like this device I am trying to get mainline support into LEDE was done in a greymarket way. It has an older kernel, but is built against a version of OpenWRT that is 2 years old (15.05). It looks like they may have used DreamBox Binary Modules. I don’t want to lock myself down, especially to a Dirty COW (if not patched) kernel, but this may be a way to get a semi-recent LEDE working, and stable.

I thought I should write a little cautionary note for anyone considering the not-as-well know Teleflora.com.

Two years ago, I used them to deliver roses on Mothers’ Day, and they arrived wilted and half dead. When I contacted them about my dissatisfaction, they did not offer a replacement or refund- they offered me 10% off my subsequent order. I told them that this was not sufficient, and they offered no further solution, despite asking to have them replaced.

Needless to say, there was no second order. Stick to FTD, 1-800-FLOWERS, or your trusted local florist.