mjptree
08/26/2023, 2:01 PMlsblk | grep nvme
).
5. Parition the drive as GPT.
6. Create the APP
parition for the root filesystem (naming the partition APP
correctly is important!).
7. Format partition as ext4.
8. Generate the rootfs on the host.
9. Mount the generate system image on the host, and the newly created nvme partition on the Jetson device.
10. Rsync the the system image with to the nvme drive.*
11. Unmount both the image on the host and the nvme partition on the device.
12. Reboot the device and open the uboot shell (requires a UART connection during boot).
13. Verify you can boot from the nvme drive and/or change the order of boot targets to move nvme drive to the top of the list.
\ In the docs the setup of the nvme drive is performed on the host. This is not necessary. It is enough to generate the system image on the host and then rsync the image and the device over network. However, this requires ssh root login to be enabled for the duration of the setup.*/etc/systemd/nvzramconfig.sh
. To disable swapping and have this setting persist across restarts, verify that swapping is currently active with
sudo systemctl status nvzramconfig.service
then disable this service via
sudo systemctl disable nvzramconfig.service
As you can verify with lsblk
and free -h
this setting will not become effective until you reboot the device.
To undo this change and reenable swapping, simple enable the service again via
sudo systemctl enable nvzramconfig.service
and reboot._dhanos_
08/26/2023, 2:39 PM/boot
partition must reside on the internal storage (eMMC or SD) and you have to remember to sync the changes there (like when you install kernel modules, recompile the kernel, set the settings, etc.). What I haven't tried, but might work, is to mount the /boot partition from the eMMC.SD as /root
(I do not recall why it is not)cnd747
08/26/2023, 2:53 PM_dhanos_
08/26/2023, 2:54 PM