The `factory-reset` command provides a way to completely wipe the data partition, thus erasing any local configuration and state. The command itself simply enables a special systemd service unit that is activated during the shutdown process. This unit runs a script, after all filesystems, except rootfs, have been unmmounted. It then erases the signature of the filesystem on the data partition, so it will appear blank the next time the system boots. This will trigger the `init-storage` process, to create a new filesystem on the partition. |
||
---|---|---|
overlay | ||
patches/ebuilds/sys-boot/grub | ||
portage | ||
.gitignore | ||
.gitmodules | ||
Makefile | ||
README.md | ||
build-all.sh | ||
build-grub.sh | ||
build-host-tools.sh | ||
build-kernel.sh | ||
build-rootfs.sh | ||
build-squashfs.sh | ||
build-uboot.sh | ||
build-update.sh | ||
build.packages | ||
build.sh | ||
busybox.symlinks | ||
config | ||
config.txt | ||
genimage.cfg | ||
genimage.sh | ||
grub.cfg | ||
host-tools.packages | ||
install-update.sh | ||
install.packages | ||
installonly.packages | ||
linux.config | ||
ocivm.sh | ||
patch-uboot.sh | ||
podman-build.sh | ||
post-build.sh | ||
prepare.sh | ||
rebuild-pkg.sh | ||
setup-local-repo.sh | ||
squashfs.exclude | ||
start-container.sh | ||
vm-build.sh |
README.md
Errors
SWIOTLB Buffer
OF: reserved mem: failed to allocate memory for node … Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer
Ensure start_x=1
is in config.txt
and start_file
/fixup_file
are not
specified.
U-Boot: Overwrite Reserved Memory
** Reading file would overwrite reserved memory **
Set CONFIG_LMB_MAX_REGIONS=16
in u-boot/.config