dan/liminix
1
0
Fork 5
Code

rt3200: replace bootcmd variable

Browse Source 
the default is to boot to recovery if there's anything in pstore, but
this doesn't interact well with persstent logging
This commit is contained in:
Daniel Barlow 2025-01-01 11:56:54 +00:00
parent 28d39cd66d
commit 3af9e86624
1 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
devices/belkin-rt3200/default.nix
View File

@ -86,16 +86,25 @@
Name: liminix Name: liminix
Character device major/minor: 250:8 Character device major/minor: 250:8
root@OpenWrt:~# ubiupdatevol /dev/ubi0_7 /tmp/rootfs root@OpenWrt:~# ubiupdatevol /dev/ubi0_7 /tmp/rootfs
root@OpenWrt:~# fw_setenv orig_boot_production $(fw_printenv boot_production | sed -E 's/.+?=//')
To make the new system bootable we also need to change some U-Boot variables.
``boot_production`` needs to mount the filesystem and boot the FIT image
found there, and :code:`bootcmd` needs to be told _not_ to boot the rescue
image if there are records in pstore, because that interferes with
``config.log.persistent``
root@OpenWrt:~# fw_setenv orig_boot_production $(fw_printenv -n boot_production)
root@OpenWrt:~# fw_setenv orig_bootcmd $(fw_printenv -n bootcmd)
root@OpenWrt:~# fw_setenv boot_production 'led $bootled_pwr on ; ubifsmount ubi0:liminix && ubifsload ''${loadaddr} boot/fit && bootm ''${loadaddr}' root@OpenWrt:~# fw_setenv boot_production 'led $bootled_pwr on ; ubifsmount ubi0:liminix && ubifsload ''${loadaddr} boot/fit && bootm ''${loadaddr}'
root@OpenWrt:~# fw_setenv bootcmd 'run boot_ubi'
For subsequent Liminix reinstalls, just run the
For subsequent Liminix reinstalls, you don't need to repeat the :command:`ubiupdatevol` command again. You don't need to repeat
"Preparation" step and in fact should seek to avoid it if the "Preparation" step and in fact should seek to avoid it if
possible. Updating volumes with :command:`ubiupdatevol` will possible, as it will reset the erase counters used for write
preserve the erase counters used for write levelling, so is levelling. Using UBI-aware tools is therefore preferred over any
preferred over any kind of "factory" wipe which will reset them. kind of "factory" wipe which will reset them.
''; '';
system = { system = {
crossSystem = { crossSystem = {