[how-to] Jetson nano, updating jetpack from 4.4.1 to 5.0.2

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

I’ve browsed the documentation and I’m confused still
I opwn a Jetson nano running Ubuntu 18.04 / jetpack 4.4.1

Blockquote
$ sudo apt show nvidia-jetpack
Package: nvidia-jetpack
Version: 4.4.1-b50
Priority: standard
Section: metapackages
Maintainer: NVIDIA Corporation
Installed-Size: 199 kB
Depends: nvidia-cuda (= 4.4.1-b50), nvidia-opencv (= 4.4.1-b50), nvidia-cudnn8 (= 4.4.1-b50), nvidia-tensorrt (= 4.4.1-b50), nvidia-visionworks (= 4.4.1-b50), nvidia-container (= 4.4.1-b50), nvidia-vpi (= 4.4.1-b50), nvidia-l4t-jetson-multimedia-api (>> 32.4-0), nvidia-l4t-jetson-multimedia-api (<< 32.5-0)
Homepage: http://developer.nvidia.com/jetson
Download-Size: 29,4 kB
APT-Manual-Installed: yes
APT-Sources: https://repo.download.nvidia.com/jetson/t210 r32.4/main arm64 Packages
Description: NVIDIA Jetpack Meta Package
N: There are 2 additional records. Please use the ‘-a’ switch to see them.

Is there a newer version ?
How do I get there ? Is there a tutorial somewhere ?

Thank you

2

ok, I found this:

  • first edit etc/apt/sources.list.d/nvidia-l4t-apt-source.list to point to the 35.1 repo (just change the version to r35.1 in both lines)
  • sudo apt update
  • sudo apt dist-upgrade
3

Package: nvidia-jetpack
Version: 5.0.2-b231
Priority: standard
Section: metapackages
Maintainer: NVIDIA Corporation
Installed-Size: 199 kB
Depends: nvidia-jetpack-runtime (= 5.0.2-b231), nvidia-jetpack-dev (= 5.0.2-b231)
Homepage: Autonomous Machines | NVIDIA Developer
Download-Size: 29,3 kB
APT-Sources: https://repo.download.nvidia.com/jetson/common r35.1/main arm64 Packages
Description: NVIDIA Jetpack Meta Package

4

Nanos are only supported through the 4.x series of JetPack/SDK Manager. Note that L4T is what is flashed, which in turn is just Ubuntu plus NVIDIA drivers. Here is a URL for L4T releases, which in turn goes to a URL which also includes the specific JetPack/SDKM release (one L4T release is tied to a JetPack/SDKM release):
https://developer.nvidia.com/linux-tegra

Sorry, Nano is in a maintenance phase and won’t get new features. This is why you won’t see it with the newer R34.x/R35.x+ L4T (JetPack5.x+ is not supported for Nano).

Xavier products and newer support R35.x+ L4T (JetPack5.x+). I think Xavier just announced that in 2023 it will also go to maintenance, which would that if you want new features you would be better off with Orin.

5

well I ran the above and it upgraded to 5.0.2

I’m still confused about L4T/jetpack.
After 20 years in IT I thought we had enough words/acronyms/expressions to name stuff, and yet they came up with yet new stuff.

Anyway… my nano is still working so whatever I have broken is not yet showing :D

6

I suppose it might work if the boot content remains with the older content, but I’ve not heard of anyone doing this before. What I’m mostly wondering though is if the GPU driver still works?

If you don’t have “glxinfo”, then you could install this with “sudo apt-get install mesa-utils”. What do you see from:
glxinfo | egrep -i '(nvidia|version|opengl)'

The above should tell you if the GPU driver is working for direct hardware access. If it is, then you found something a lot of people would like.

7

***@jetson:~$ glxinfo | egrep -i ‘(nvidia|version|opengl)’
Error: unable to open display

In any case, I’m using the nano for BOINC (distributed computing) and GPU is working/computing

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
10948 boinc     30  10 8837300 199424  47512 S  14,4  4,9   1:33.62 einsteinbinary_
 5097 root      20   0       0      0      0 S   4,9  0,0  17:04.80 nvgpu_channel_p
8

You have to be running in the GUI for this to work. Also, a forwarded GUI will incorrectly tell you what the remote host GUI has instead of the Jetson.

1 Like
9

I run it headless :)
I access it through SSH :D

10

Something to consider is that most CUDA-based programs use the context of a running display. Unless the display is running many will fail. If you use ssh port forwarding of the GUI, then those same programs will use the host PC’s CUDA libraries and GPU, and so this might not be what you want. Some programs do seem to work without a display context, e.g., if run from serial console or local console without GUI (or even ssh without forwarding). Is your GPU-based program able to run either on serial console or over ssh without forwarding?

11

it just runs without display or SSh forwarding.

I just use ssh to connect for updates or the occasional maintenance :)
I’m not a programmer, just a user :)

there’s some info here on how to build the app, but I’m just running a pre-made app :)
https://boinc.berkeley.edu/trac/wiki/GPUApp

12

I can think of one more test, and if this passes, you’re probably onto something good. If you monitor “tegrastats”, and monitor GPU load, does GPU load go up when your CUDA (or other GPU-based app) run?

13

maybe it’s going to be useful to you,

RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [22%@518,1%@518,5%@518,4%@518] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38C thermal@29.25C POM_5V_IN 5670/5634 POM_5V_GPU 2789/2792 POM_5V_CPU 205/174
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [20%@102,4%@102,3%@102,3%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38.5C thermal@29.25C POM_5V_IN 5432/5618 POM_5V_GPU 2793/2792 POM_5V_CPU 123/170
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [23%@102,6%@102,4%@102,3%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28.5C PMIC@100C GPU@30C AO@38C thermal@29.5C POM_5V_IN 5481/5609 POM_5V_GPU 2716/2787 POM_5V_CPU 123/167
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [13%@204,13%@204,4%@204,5%@204] EMC_FREQ 0% GR3D_FREQ 96% PLL@25C CPU@28.5C PMIC@100C GPU@29.5C AO@38.5C thermal@29.5C POM_5V_IN 5637/5610 POM_5V_GPU 2757/2785 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [10%@204,20%@204,5%@204,4%@307] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38C thermal@29.25C POM_5V_IN 5416/5598 POM_5V_GPU 2600/2773 POM_5V_CPU 165/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [7%@102,21%@102,3%@102,4%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38.5C thermal@29C POM_5V_IN 5670/5602 POM_5V_GPU 2953/2784 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [5%@102,22%@102,7%@102,4%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38C thermal@29C POM_5V_IN 5432/5593 POM_5V_GPU 2757/2782 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [6%@102,21%@102,5%@102,7%@102] EMC_FREQ 0% GR3D_FREQ 90% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38.5C thermal@29.25C POM_5V_IN 5564/5591 POM_5V_GPU 2757/2781 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [6%@102,23%@102,3%@102,3%@102] EMC_FREQ 0% GR3D_FREQ 54% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38.5C thermal@29C POM_5V_IN 5176/5571 POM_5V_GPU 2600/2772 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [7%@102,19%@102,4%@102,6%@102] EMC_FREQ 0% GR3D_FREQ 85% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38C thermal@29C POM_5V_IN 5711/5577 POM_5V_GPU 2953/2781 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [6%@102,19%@102,4%@102,4%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38C thermal@28.75C POM_5V_IN 5678/5582 POM_5V_GPU 2752/2779 POM_5V_CPU 164/166
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [10%@102,18%@102,7%@102,6%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38.5C thermal@28.75C POM_5V_IN 5440/5576 POM_5V_GPU 2752/2778 POM_5V_CPU 164/165
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [8%@102,19%@102,6%@102,3%@102] EMC_FREQ 0% GR3D_FREQ 91% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38C thermal@29C POM_5V_IN 5522/5573 POM_5V_GPU 2716/2775 POM_5V_CPU 123/164
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [5%@403,21%@403,2%@403,7%@403] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38C thermal@29C POM_5V_IN 5761/5581 POM_5V_GPU 2839/2778 POM_5V_CPU 164/164
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [5%@204,20%@204,7%@204,3%@204] EMC_FREQ 0% GR3D_FREQ 90% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38.5C thermal@29C POM_5V_IN 5514/5578 POM_5V_GPU 2757/2777 POM_5V_CPU 164/164
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [10%@204,18%@204,4%@204,5%@204] EMC_FREQ 0% GR3D_FREQ 90% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38.5C thermal@28.75C POM_5V_IN 5440/5573 POM_5V_GPU 2716/2775 POM_5V_CPU 164/164
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [9%@307,17%@307,5%@307,4%@307] EMC_FREQ 0% GR3D_FREQ 63% PLL@25C CPU@28C PMIC@100C GPU@30.5C AO@38.5C thermal@29C POM_5V_IN 5325/5564 POM_5V_GPU 2674/2771 POM_5V_CPU 164/164
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [7%@204,21%@204,4%@204,5%@204] EMC_FREQ 0% GR3D_FREQ 97% PLL@25C CPU@28.5C PMIC@100C GPU@30C AO@38.5C thermal@29C POM_5V_IN 5825/5573 POM_5V_GPU 2953/2777 POM_5V_CPU 164/164
RAM 1451/3964MB (lfb 337x4MB) SWAP 0/1982MB (cached 0MB) CPU [7%@102,21%@102,5%@102,5%@102] EMC_FREQ 0% GR3D_FREQ 99% PLL@25C CPU@28C PMIC@100C GPU@30C AO@38C thermal@29C POM_5V_IN 5522/5572 POM_5V_GPU 2716/2775 POM_5V_CPU 164/164

I suppose the high GR3D_FREQ is a good sign that it is busy

14

It looks like it. You might want to post the changes you made to update the apt source list, along with command. I’m sure other people would like to try this.

15

All I did was this:

edit etc/apt/sources.list.d/nvidia-l4t-apt-source.list to point to the 35.1 repo (just change the version to r35.1 in both lines)
sudo apt update
sudo apt dist-upgrade

*****@jetson:~$ cat /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
deb https://repo.download.nvidia.com/jetson/common r35.1 main
deb https://repo.download.nvidia.com/jetson/t210 r35.1 main
16

Thanks…I don’t know if this will always work, but it is worth making it available for people to try.

17

@Le_zOU This does not touch the Kernel or BUP packages, right? Could you please check the versions of all the nvidia-l4t-* packages after the Update? So the “jetpack update” only includes runtime-libraries, right?

Best and thank you,

Axel

19 
*****@jetson:~$ apt list nvidia-l4t-*
Listing... Done
nvidia-l4t-3d-core/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-apt-source/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-bootloader/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-camera/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-configs/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-core/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-cuda/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-firmware/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-graphics-demos/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-gstreamer/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-init/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-initrd/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-jetson-io/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-jetson-multimedia-api/stable 35.1.0-20220825113828 arm64 [upgradable from: 32.4.4-20201027211359]
nvidia-l4t-kernel/now 4.9.140-tegra-32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-kernel-dtbs/now 4.9.140-tegra-32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-kernel-headers/now 4.9.140-tegra-32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-multimedia/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-multimedia-utils/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-oem-config/now 32.4.4-20201016124427 arm64 [installed,local]
nvidia-l4t-tools/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-wayland/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-weston/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-x11/now 32.4.4-20201027211359 arm64 [installed,local]
nvidia-l4t-xusb-firmware/now 32.4.4-20201016124427 arm64 [installed,local]
20

Thank you, yes that is what I mean. Only the “nvidia-jetpack” meta package is updated but no “real” system update is performed.

21

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.