Issue while Installing JetPack 4.4 DP

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

Hi,

I am facing issue while installing the Jetpack 4.4 DP with the L4T version r32.4.2 DP.

The HDMI display is having the issue as mentioned in the topic : HDMI Display is not showing after installing JetPack 4.4

Could you please suggest some ways to install the JetPack 4.4 DP.

I am using the following commands to install the Jetpack:-

sudo apt update

apt depends nvidia-jetpack | awk ‘{print $2}’ | xargs -I {} sudo apt install -y {}

I doubt that while doing the apt update, all the packages are updating to the latest version. So the version mismatch is coming and the HDMI is having the issue.
Could you please help me figure out how to install the Jetpack 4.4 DP

Regards,
Ann Rose Antony

2

It is difficult to work with multiple forum threads for one topic, so I’d recommend asking in the original thread. However, you should know that the JetPack/SDKM release is tightly bound to the flashed software. You would be correct that a system flashed with one version of JetPack/SDKM is not compatible with optional packages like CUDA from another release. If you need the software of one release, then you must flash that release. Any software available in a given JetPack/SDKM is correct for what it will flash.

Also, HDMI issues are common and very likely a configuration issue or failing to use a true HDMI cable (for example, a VGA adapter will cause failure). The GPU drivers on embedded systems are not the same as on a PC because the GPU is not PCI. On the Jetson the GPU is directly integrated to the memory controller. That driver has more restrictions on things like extension modes and custom modes (the integrated GPU driver does not accept those, but a PCI driver does).

3

Thanks for the response.

Actually HDMI is working without the JetPack Installation. Once the JetPack is installed then only we are facing the issue.

We were working with the L4T version R32.4.2 and installed the Jetpack 4.4 DP and after one reboot, It will show the error logs and HDMI will not be up.
According to me since the cuda libraries and the related packages are updated, the Jetpack is having the version mismatch. Hence the HDMI is not working.

So from the information, I can understand that only Jetpack Version depends on respective package versions only.

4

It should be noted that the “DP” of that release is a beta release (“Developer Preview”), and so you might expect extra problems with this which would not be found in a full release.

5

Okay

6

Installed Jetpack 4.4 on L4T version R32.4.3, still facing the same problem which means the HDMI is not up.

For now we have installed Jetpack 4.4.1 over L4t Version R32.4.4 and we are not facing any issues.

  • But what are the possibilities that ,I wont face this issue every time there is a new release of L4T/Jetpack?
7

Is there a way to install the compatible versions of these optional packages.?

8

JetPack/SDK Manager will offer to install only compatible releases. If you flashed with that release of JetPack/SDKM, then it will be a match. If you flashed with a different JetPack/SDKM release, then any installed packages would be incompatible.

Newer releases tend to also allow installation of optional packages using the “apt-get” mechanism, and those would be compatible.

If you still have a failure of the video, then you will probably want to include both the full serial console boot log, and the “/var/log/Xorg.0.log” (in some cases it might be “Xorg.1.log”). Before looking at the Xorg.0.log file you will want to add some configuration to the “/etc/X11/xorg.conf” file for increased logging. In that file there will be a 'Section "Device"', and somewhere in that you would add this line:
Option "ModeDebug"

What this will do is cause the driver to explicitly say what each possible mode is and why the mode is accepted or rejected. You could save a copy of the Xorg.0.log renamed with a “.txt” file name suffix, and then attach to the forum thread.