adminX:
My real bootcmd is
bootcmd=i2c dev 1; i2c read 0x2a 0x9 1 0x00FFFFF0; setexpr.b rescue *0x00FFFFF0 ; if test $rescue -ge 1 ; then setexpr rescue $rescue - 1 ; if test $rescue -ge 1 ; then echo BOOT RESCUE ; run rescueboot ; else echo BOOT eMMC FS ; run mmcboot ; fi ; else echo BOOT SSD FS ; run ssdboot ; fi
It supports mmcboot as first rescue mode with all other rescue modes shifted upwards. I didn’t publish it back then as i was concerned someone will forget it and wonder why rescue modes not work like they should.
Does this mean there will be now 5 resue modes instead of 4? And rescue mode ‘1’ is boot to emmc, ‘2’ is reboot, etc.?
Does this command need any special setup if I already can switch between ssd & emmc with the fw_printenv stuff?
PS: I do have an old TO (so pre-2019), do this instructions apply to this hardware version?
adminX
January 24, 2021, 10:17am
44
Yes, my bootcmd shifts all rescue modes and allows to boot the plain eMMC system as “rescue mode”.
fw_* has the better support if there is the correct version of rescue in the flash. It should have a working rollback on the SSD. Mine does not as this was simply not needed.
The doc as it is right now only applies to the old hardware versions but not to the newer ones.
@drhm
Found a bit of time and used a debian container to get it to compile. It works and the patches are sent.
1 Like
kixorz
January 16, 2023, 3:08am
45
I’m printing and framing this great post!
It works perfectly here. If someone knows how to pass mount options for the boot disk, I can enable compress=ztds. It would be a shame not to.