Why orin nano 8G with R36.4.3 doing apt upgrade will setup 36.4.4 packages

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi

Our German customer ( time zone is “Berlin”) is working on Orin nano 8G with our custom board using R36.4.3.
When running "sudo apt update && sudo apt upgrade ",
It attempts to install some nvidia-l4t-… 36.4.4 packages, but our current version is R36.4.3.

image
image1255×737 37.5 KB

However, we cannot replicate the same issue in Taiwan.
Any ideas why?

Thx
Yen

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I’ll attempt to provide a comprehensive answer to the question.

The issue described involves a Jetson Orin Nano 8GB module (P3767-0003) with a custom board, where running sudo apt update && sudo apt upgrade attempts to install some packages, but the current version is already up-to-date (image 1255737, 375 KB). The customer in Germany is experiencing this issue, but it cannot be replicated in Taiwan.

To address this issue, let’s consider the following points:

  1. Geographical location: The fact that the issue is specific to Germany and cannot be replicated in Taiwan suggests that there might be a regional or network-related factor at play. It’s possible that the package repositories or update servers are different or have varying levels of access in different regions.
  2. Custom board: The use of a custom board might imply that there are specific hardware or software configurations that could be contributing to the issue. It’s essential to verify that the custom board is properly configured and compatible with the Jetson Orin Nano 8GB module.
  3. Package repositories: The sudo apt update && sudo apt upgrade command relies on the package repositories configured on the system. It’s possible that the repositories used in Germany are different from those used in Taiwan, which could lead to discrepancies in package availability or versions.
  4. Network connectivity: Network connectivity issues or firewall restrictions might prevent the system from accessing the required package repositories or update servers. This could be specific to the German location or the custom board’s network configuration.
  5. Image version: The image version (1255737, 375 KB) seems to be up-to-date, but it’s essential to verify that this version is compatible with the custom board and the Jetson Orin Nano 8GB module.

To troubleshoot this issue, I recommend the following steps:

  1. Verify package repositories: Check the package repositories configured on the system in Germany and compare them with those used in Taiwan. Ensure that the repositories are correct and accessible.
  2. Check network connectivity: Verify that the network connectivity is stable and not restricted by firewalls or other network policies.
  3. Verify custom board configuration: Double-check the custom board’s configuration and ensure that it is compatible with the Jetson Orin Nano 8GB module.
  4. Check image version compatibility: Verify that the image version (1255737, 375 KB) is compatible with the custom board and the Jetson Orin Nano 8GB module.
  5. Try a different update method: Instead of using sudo apt update && sudo apt upgrade, try using the sudo apt-get update && sudo apt-get upgrade command or the sudo aptitude update && sudo aptitude upgrade command to see if the issue persists.

By following these steps, you should be able to identify and potentially resolve the issue affecting the Jetson Orin Nano 8GB module with the custom board in Germany.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hi,
Please apply this solution:

Jetson/L4T/r36.4.x patches - eLinux.org
[Jetpack 6.1/r36.4.0] Self-built kernel is overwritten after sudo apt update && sudo apt upgrade

1 Like
System stuck at transition from L4T 36.4.3 to L4T 36.4.4
5

Hi,

If I don’t modify the kernel but only recompile it, will this issue still occur?

Thx
Yen

6

Hi,
Yes, it will be updated to r36.4.4. Please do apt-mark hold to hold the packages.

7

Hi,

We would like to how why blocking the following packages and nvidia-l4t-bootloader won’t be upgraded.
nvidia-l4t-display-kernel
nvidia-l4t-kernel
nvidia-l4t-kernel-dtbs
nvidia-l4t-kernel-headers
nvidia-l4t-kernel-oot-headers
nvidia-l4t-kernel-oot-modules

Thx
Yen

10

Hi,
Do you mean in your custom board, you need to hold nvidia-l4t-bootloader? We think it should be fine to hold the kernel packages.

11

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