cd ~/nvidia/nvidia_sdk/JetPack_7.0_Linux_JETSON_AGX_THOR_TARGETS/Linux_for_Tegra/tools
./l4t_create_default_user.sh --help
Usage:
l4t_create_default_user.sh [-u <username>] [-p <password>] [-a] [-h]
-u | --username - If not specified then default will be set to 'nvidia'.
-p | --password - If not set then randomized password will be generated.
-a | --autologin - If specified autologin will be enabled. Default is disabled
-n | --hostname - If not specified then default will be set to 'tegra-ubuntu'.
-h | --help - print usage
--accept-license - Specified to accept the terms and conditions of EULA
Example:
l4t_create_default_user.sh -u nvidia -p NDZjMWM4
l4t_create_default_user.sh -u ubuntu -a
l4t_create_default_user.sh -n tegra
Got it.
Yeah, I am also not too familiar with the ISO method, I always use either SDK Manager or the flash script.
But yeah, if you wanna use the script I mentioned you will need to use SDK manager.
It will download all the required scripts and materials into ~/nvidia/..../Linux_for_Tegra.
That is where you will find the l4t_create_default_user script, inside a directory called tools to be more precise.
That being said.
If you use SDK manager for flashing you might be able to go through the regular setup process as you would with a new linux machine.
Please let me know if you need further support during flashing process.
Should be fairly simple, if you find yourself doing something weirdly complex, just let me know.
best regards,
Andrew
Embedded Software Engineer at ProventusNova
I don’t think the usb iso installation allows for pre-creating oemconfig.
usb iso stick is essentially a modified for Thor ubuntu 24.04 iso image. Oemconfig here is graphical.
You could attach a monitor, boot your Thor. run through oemconfig.
If you want to stick to that ISO image, then I would say you could download fresh image again and reinstall the ISO image again and see if you could bypass the error.
Actually, sdkmanager is a true method to reflash everything on a Jetson platform.
When some buggy situation happens, sdkmanager can always guarantee you back to normal situaiton. However, ISO image might not.
Just to let you know the procedure here.
If we cannot reproduce the error case, then I think the doc might not be wrong but more like a intermittent bug happened there.
Just thinking of when I flashed my Thor using the usb stick method I usb stick in Thor. I did not connect thor from Debug USB-C to my desktop. When flashing Thor was done, I removed the bootable usb stick when it wanted to reboot. Don’t know whether it matters but is is a difference.
After reboot I ran the Ubuntu oemconfig and setup userid/password/timezone/etc.
