Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
toh:meraki:mr24 [2018/06/19 17:37] – Datatables updated, cleanup tmomastoh:meraki:mr24 [2020/12/20 09:24] – [Tags] danitool
Line 49: Line 49:
 setenv owrt_boot run meraki_ubi owrt_bootargs\;run owrt_load meraki_checkpart owrt_bootkernel\;run owrt_recovery setenv owrt_boot run meraki_ubi owrt_bootargs\;run owrt_load meraki_checkpart owrt_bootkernel\;run owrt_recovery
 setenv bootcmd run owrt_boot setenv bootcmd run owrt_boot
 +setenv factory_boot_bak ${factory_boot}
 +setenv factory_boot run meraki_ubi\;run owrt_bootargs\;run owrt_recovery
 saveenv saveenv
 </code> </code>
Line 59: Line 61:
 </code> </code>
  
-4. Once OpenWrt boots and you are at a root prompt, you can Cleanup for maximum space. +4. Once OpenWrt boots and you are at a root prompt, you can Cleanup for maximum space. Find the UBI Volume ID of board-config. This is done with ''ubinfo /dev/ubi0 -N board-config''. Note that in this example, replace ''XX'' with the Volume ID for ''board-config'':
 <code> <code>
 ubirmvol /dev/ubi0 -N part1 ubirmvol /dev/ubi0 -N part1
 ubirmvol /dev/ubi0 -N part2 ubirmvol /dev/ubi0 -N part2
 ubirmvol /dev/ubi0 -N storage ubirmvol /dev/ubi0 -N storage
 +dd if=/dev/ubi0_XX of=/tmp/board-config.img
 +ubirmvol /dev/ubi0 -N board-config
 +ubimkvol /dev/ubi0 -s 24KiB -N board-config
 +ubiupdatevol /dev/ubi0_0 /tmp/board-config.img
 </code> </code>
  
-5. Create a recovery UBI partition. This will host an initramfs build so our board can have a failback image in case of a bad flash, or sysupgrade issue. Note you will first want to upload a copy of the initramfs image to the board (which can be done with SCP/HTTP Server). In the below tutorial note that the new partition is made to be just a bit larger than the initramfs image. You will want to do this as well.+5. Create a recovery UBI partition. This will host an initramfs build so our board can have a failback image in case of a bad flash, or sysupgrade issue. You can also manually boot to recovery by holding the reset button while powering on the device. The recovery ip will always be 192.168.1.1, no matter the changes made in the 'real' system. Note you will first want to upload a copy of the initramfs image to the board (which can be done with SCP/HTTP Server). In the below tutorial note that the new partition is made to be just a bit larger than the initramfs image. You will want to do this as well.
  
 <code> <code>
Line 849: Line 854:
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
-{{tag>APM82181 128RAM 32flash 2WNIC ppc44x mod router powerpc}}+{{tag>apm821xx APM82181 32flash 128RAM2WNIC ppc44x mod powerpc}}
  • Last modified: 2024/02/12 08:58
  • by 127.0.0.1