So I recently purchased a orin nano dev kit, and I am using a MicroSD card as storage. The issue I am facing is that neither jetpack 6 or 6.1 are working when I flash the MicroSD. I see the boot screen and then it says L4TLauncher is attempting direct boot, the fan stops then starts again, but the display never pops up, it’s just a black screen.
I have tried using the SDKManager to flash the OS, but it always fails on the file system and os step, and am unable to figure this out.
When I flash the MicroSD with any 5.X version it works completely fine, but I want to be able to run ros2 humble natively without using containers, so this is my issue.
The flash process does not even start and there is error log when installed package on your host
23:59:47.370 - Info:exec_command: /tmp/tmp_NV_L4T_FILE_SYSTEM_AND_OS_COMP.ubuntu.sh
00:06:46.962 - Error:tar: usr/share/help/sl/evince/figures: Directory renamed before its status could be extracted
I will try that tonight, for the error log I sent you, I was using 20.04. Although I have tried installing on both 18.04 and 20.04, both gave me the same error.
The file system where your download folder located. Is it ext4 or not? As you said your host is shared between a Windows and Ubuntu, it is possible that it is not Linux standard file system.
So I checked and my downloads folder was in a filesystem called “overlay” which I am unsure what that means, but there was an ext3 partition, should I download the files into a directory in that partition?
I’m not sure why it installed with ext3 and not ext4.
ext3 is a deprecated filesystem type, but generally speaking, if you have the ext4 driver, then you can also mount anything ext#. However, this is a bit concerning because nothing these days would use ext3. How did this get formatted as ext3?
The other question is also part of the answer: Overlay takes changes to the filesystem and writes them to RAM such that the RAM overlays the filesystem under it. Once you reboot, the overlay reverts back to empty (RAM is not persistent). A lot of kiosks would use this so that the actual filesystem cannot be modified and you always start with some reference, but during a session, one can write to files and edit just like any other filesystem. The overlay driver is not normally present and overlay takes extra configuration; booting straight to overlay without a proper initrd as an adapter will break boot.
If your thumb drive is formatted to ext4, and if no overlay is configured, then probably your odds of success go up dramatically. Please note that if the filesystem type is not capable of proper preservation of the environment, including permissions, then that too would cause a failure (this is likely not the case right now, but if for example you had a thumb drive formatted as VFAT or NTFS, then even if your kernel had those drivers, the system would still fail because various security systems break without full/correct permissions on files…some filesystem types cannot preserve Linux style permissions). I don’t know if the overlay filesystem preserves permissions or not, but if this adds further restrictions for security, then this too could be at fault even if you had the overlay drivers and had properly adapted an initrd.
Remove any overlay and run as ext4. If you really must have overlay, then it will work over ext4, and you could adapt to overlay once it runs correctly.
Hello, I finally got it to start flashing by flashing the usb drive with ext4 partition, except now I am getting an error when flashing. If you don’t mind could I get some help, here are the logs SDKM_logs_2024-10-06_18-34-46.zip (156.0 KB)
Yes, it is still /cow for changes made during the session but the base partition is now ext4 instead of ext3. Regardless, I am more curious about the errors that happened during the flashing: