From d01e374074ef333aa14ae74628e52fa60f5b5ae5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Mork?= Date: Fri, 29 Apr 2022 16:38:27 +0200 Subject: ramips: force ZyXEL NR7101 to boot from "Kernel" partition MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Make sure BootingFlag points to the system partition we install to. The BootingFlag variable selects which system partition the system boots from (0 => "Kernel", 1 => "Kernel2"). OpenWrt does not yet have device specific support for this dual image scheme, and can therefore only boot from "Kernel". This has not been an issue until now, since all known OEM firmware versions have ignored "Kernel2" - leaving the BootingFlag fixed at 0. But the newest OEM firmware has a new upgrade procedure, installing to the "inactive" system partition and setting BootingFlag accordingly. This workaround is needed until the dual image scheme is fully supported. Signed-off-by: Bjørn Mork (cherry picked from commit 79112e7d4758cc79dea506ffebdf40e00d94fa06) --- target/linux/ramips/mt7621/base-files/lib/upgrade/platform.sh | 1 + 1 file changed, 1 insertion(+) (limited to 'target') diff --git a/target/linux/ramips/mt7621/base-files/lib/upgrade/platform.sh b/target/linux/ramips/mt7621/base-files/lib/upgrade/platform.sh index 407611a6a2..e12eb3ede9 100755 --- a/target/linux/ramips/mt7621/base-files/lib/upgrade/platform.sh +++ b/target/linux/ramips/mt7621/base-files/lib/upgrade/platform.sh @@ -113,6 +113,7 @@ platform_do_upgrade() { zyxel,nr7101) fw_setenv CheckBypass 0 fw_setenv Image1Stable 0 + [ "$(fw_printenv -n BootingFlag)" = "0" ] || fw_setenv BootingFlag 0 CI_KERNPART="Kernel" nand_do_upgrade "$1" ;; -- cgit v1.2.3