I created a LinuxforTegra directory and packaged it as a tar file. When I extract the L4T and flash it on the same host PC, everything works fine. However, if I use the same package and extract it on a different PC, it gets stuck during the process. I can log into the system using UART and complete the initial setup, but when I plug in the HDMI, it hangs.
I checked the permissions of the OEM configuration files, and there seems to be no issue there. Here are the commands I used to create and extract the package:
sudo tar -jcvpf quick_start.tar.bz2 Linux_for_Tegra/
sudo tar -jxvpf quick_start.tar.bz2
Could this be related to permission issues, or is there something else I should investigate? Any insights would be greatly appreciated!
Hi there @abisheak.p and welcome to the NVIDIA developer forums.
Which Jetson platform are you using? We have dedicated forum categories for Jetson and with that information I could refer you to the best fitting one.
For first point the issue is recreating in both the development kit and the custom board for the AGX Orin.
The issue is not limited to a single host PC; when I share the L4T tarball created on one PC (running Ubuntu 22.04) to another PC (running Ubuntu 20.04), it also gets stuck. I only copy the images and device tree binaries (DTBs) to the L4T and modules, and I’ve confirmed that the problem persists even when the binaries are excluded. The HDMI drivers are working correctly.
Regarding the third point, we consistently use the same steps to set up our Board Support Package (BSP) and root filesystem (rootfs).
Will there be any changes to the tarball or L4T if the package is prepared on a different Ubuntu version and shared or copied to other ubuntu versions, such as from 22.04 to 20.04?
logs from the stuck PC taken from uart journalctl_log.txt (447.3 KB) dmesh_log.txt (138.6 KB)
I prepare my L4T tar file on an Ubuntu 22.04 host, but when I share it with another PC running Ubuntu 20.04 or a different version, I encounter issues. I’ll checked with the new command to compress/extract the BSP package, still the issue presisit when the package is used on other host pc with different ubuntu version.
Hi @oscar.fallas@KevinFFF
I checked the path and found that the nvidia.ko, nvidia-drm.ko, and nvidia-modeset.ko drivers are already loaded. Even after unloading them and using modprobe to reload the drivers, as well as restarting the displaymanager.service, the GUI still fails to start.
I noticed that the nv-oem-config-gui.service is failing, and this failure is caused by the nv-l4t-usb-device-mode.service.
Logs regarding the service:
nvidia-desktop nv-l4t-usb-device-mode-stop.sh[10337]: rmdir: faii
led to remove ‘l4t/functions/mass_storage.0/’: No such file or directory
Sep 30 18:26:49 nvidia-desktop nv-l4t-usb-device-mode-stop.sh[10339]: rmdir: faii
led to remove ‘l4t/functions/acm.GS0/’: No such file or directory
Sep 30 18:26:49 nvidia-desktop nv-l4t-usb-device-mode-stop.sh[10341]: rmdir: faii
led to remove ‘l4t/functions/rndis.usb0/’: No such file or directory
Sep 30 18:26:49 nvidia-desktop nv-l4t-usb-device-mode-stop.sh[10343]: rmdir: faii
led to remove ‘l4t/configs/c.1/’: No such file or directory
Sep 30 18:26:49 nvidia-desktop nv-l4t-usb-device-mode-stop.sh[10344]: rmdir: faii
led to remove ‘l4t/strings/0x409’: No such file or directory
Sep 30 18:26:49 nvidia-desktop nv-l4t-usb-device-mode-stop.sh[10345]: rmdir: faii
led to remove ‘l4t’: No such file or directory
I checked and found that by disabling the nv-l4t-usb-device-mode.service before flashing, I was able to get the GUI working when “Auto Login” is enabled. However, if I disable Auto Login, the GUI fails to start. However, when I flashed the same package on an Ubuntu 22.04 host PC, the services did not encounter any issues.
is the flash script depend on any Host PC ubuntu dependent ?
I think you could try installing Linux_for_Tegra using the sdkmanager from a x86 host to see if the problem repeats. Here you have a complete guide how to do it in a Jetson AGX Orin .
