Jetpack 4.6.3 is upgraded to jetpack 4.6.6 online

The system I am using is jetpack4.6.3, and I want to upgrade it to jetpack4.6.6. Can I use online upgrade? What is the specific method?

Please refer to NVIDIA Jetson Linux Developer Guide : Over-the-Air Update | NVIDIA Docs

Thank you!
But I have a problem. Currently I have installed the following in my system:
CUDA10.2, CUDNNv8, tensorRT, opencv4.1.1, python2, python3, tensorflow2.3,
jetpack4.6.1, yolov5, jetson-inference package (including related models), jetson-gpio library, installed pytorch1.8 and
torchvesion0.9, ​​installed node v15.0.1, npm7.2.3, jupyter, enabled VNC service, installed Ros2 docker, Ros1 visual processing

I just ran sudo apt upgrade, and it showed:
Errors were encountered while processing:
nvidia-l4t-bootloader
nvidia-l4t-xusb-firmware
nvidia-l4t-initrd
E: Sub-process /usr/bin/dpkg returned an error code(1)

Is this related to the software I installed?

Do you have any suggestions for my previous question?

Hi

Could your dump the result and share with us?

cat /etc/apt/sources.list.d/nvidia-l4t-apt-source.list

Thanks

Hi, here is the information I got:

cat /etc/apt/sources.list.d/nvidia-l4t-apt-source.list

# SPDX-FileCopyrightText: Copyright (c) 2019-2021 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# SPDX-License-Identifier: LicenseRef-NvidiaProprietary
#
# NVIDIA CORPORATION, its affiliates and licensors retain all intellectual
# property and proprietary rights in and to this material, related
# documentation and any modifications thereto. Any use, reproduction,
# disclosure or distribution of this material and related documentation
# without an express license agreement from NVIDIA CORPORATION or
# its affiliates is strictly prohibited.

deb https://repo.download.nvidia.com/jetson/common r32.7 main
deb https://repo.download.nvidia.com/jetson/t210 r32.7 main

Hi,

Have you executed sudo apt update before the sudo apt upgrade?

Thanks

Yes, I ran sudo apt update. The result is this:

Get:1 file:/var/cuda-repo-l4t-10-2-local  InRelease
Ign:1 file:/var/cuda-repo-l4t-10-2-local  InRelease
Get:2 file:/var/visionworks-repo  InRelease
Ign:2 file:/var/visionworks-repo  InRelease
Get:3 file:/var/visionworks-sfm-repo  InRelease
Ign:3 file:/var/visionworks-sfm-repo  InRelease
Get:4 file:/var/visionworks-tracking-repo  InRelease
Ign:4 file:/var/visionworks-tracking-repo  InRelease
Get:5 file:/var/cuda-repo-l4t-10-2-local  Release [564 B]
Get:5 file:/var/cuda-repo-l4t-10-2-local  Release [564 B]
Get:6 file:/var/visionworks-repo  Release [2,001 B]                            
Get:6 file:/var/visionworks-repo  Release [2,001 B]                            
Get:7 file:/var/visionworks-sfm-repo  Release [2,005 B]                        
Get:7 file:/var/visionworks-sfm-repo  Release [2,005 B]                        
Get:8 file:/var/visionworks-tracking-repo  Release [2,010 B]                   
Get:8 file:/var/visionworks-tracking-repo  Release [2,010 B]                   
Ign:9 http://mirrors.ustc.edu.cn/ros/ubuntu bionic InRelease                   
Hit:10 http://mirrors.ustc.edu.cn/ros/ubuntu bionic Release                    
Hit:13 https://repo.download.nvidia.cn/jetson/common r32.7 InRelease           
Hit:15 https://repo.download.nvidia.cn/jetson/t210 r32.7 InRelease             
Hit:16 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic InRelease       
Get:18 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-security InRelease [102 kB]
Get:20 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-updates InRelease [102 kB]
Get:21 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-backports InRelease [102 kB]
Get:22 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-security/main arm64 DEP-11 Metadata [70.9 kB]
Get:23 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-security/multiverse arm64 DEP-11 Metadata [212 B]
Get:24 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-security/restricted arm64 DEP-11 Metadata [212 B]
Get:25 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-security/universe arm64 DEP-11 Metadata [56.9 kB]
Get:26 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-updates/main arm64 DEP-11 Metadata [290 kB]
Get:27 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-updates/multiverse arm64 DEP-11 Metadata [212 B]
Get:28 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-updates/restricted arm64 DEP-11 Metadata [212 B]
Get:29 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-updates/universe arm64 DEP-11 Metadata [297 kB]
Get:30 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-backports/main arm64 DEP-11 Metadata [5,376 B]
Get:31 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-backports/multiverse arm64 DEP-11 Metadata [216 B]
Get:32 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-backports/restricted arm64 DEP-11 Metadata [216 B]
Get:33 http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports bionic-backports/universe arm64 DEP-11 Metadata [10.0 kB]
Fetched 1,038 kB in 2h 28min 47s (116 B/s)                                     
Reading package lists... Done
Building dependency tree       
Reading state information... Done
337 packages can be upgraded. Run 'apt list --upgradable' to see them.

This seems normal, right?

Yes.
Is your Jetson Nano disk space enough to install?

I’m using a 64GB SD card, and there really isn’t much space left. How much space does the update require? Will it work if I replace it with a 128GB one?

Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1   59G   46G   11G  81% /
none            1.8G     0  1.8G   0% /dev
tmpfs           2.0G   88K  2.0G   1% /dev/shm
tmpfs           2.0G   29M  2.0G   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
tmpfs           397M  132K  397M   1% /run/user/1000

Hi,

It appears that a similar topic (Also Jetpack 4.6.3) discussed in

The above workaround might solve your issue.

It seems enough to install.

It’s better to get bigger size as rootfs.

Thanks

Thanks for your help!
I just re-ran sudo apt update and sudo apt upgrade with my new image and it worked without any errors. That was a surprise.
Maybe it’s just a fluke. I’ll keep watching this project.

1 Like

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