Re: [OpenWrt-Devel] build: sysupgrade: kernel: mtd: Image too SMALL to Restore Config

2019-07-01 Thread Hannu Nyman
The smaller, "failing" image contains in /dev/mtd2: 003eebd0 00 01 59 5a be e7 20 00  00 00 00 00 04 80 00 00  |..YZ.. .| 003eebe0  00 00 dc eb 20 00 00 00  00 00 ff ff ff ff ff ff  | ...| 003eebf0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff || *

Re: [OpenWrt-Devel] build: sysupgrade: kernel: mtd: Image too SMALL to Restore Config

2019-07-01 Thread Hannu Nyman
The smaller, "failing" image contains in /dev/mtd2: 003eebd0 00 01 59 5a be e7 20 00  00 00 00 00 04 80 00 00  |..YZ.. .| 003eebe0  00 00 dc eb 20 00 00 00  00 00 ff ff ff ff ff ff  | ...| 003eebf0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff || *

[OpenWrt-Devel] build: sysupgrade: kernel: mtd: Image too SMALL to Restore Config

2019-07-01 Thread Jeff Kletsky
I've run across some seemingly "wrong" behavior related to sysupgrade where if the image is "too small" the contents of /sysupgrade.tgz are not properly recovered on reboot. It seems as if the various pieces are functioning as expected, but that they do not work in concert under certain