sh_bad_flash_2.log (39.8 KB)
History: cuda did not work on jetson orin AGX and LTS 20.02
Nvidia recommended using later version!
Tried to flash the target with sdkmanager was a nightmare with proxy settings that never finished authentication and the attempting to download with apt, even though material is downloaded as sdk manager showe. (sdkmanager proxy settings are not tested as usual).
Tried to flash using flash_jetson.sh R36.4.3
this ends up with failures:
gzip: /jp6-flash-jetson-linux/R36.4.3/Linux_for_Tegra/kernel/Image: not in gzip format
_BASE_KERNEL_VERSION=5.15.148-tegra
many of:
cp: cannot stat
‘/jp6-flash-jetson-linux/R36.4.3/Linux_for_Tegra/rootfs/usr/lib/modules/5.15.148-tegra/kernel/drivers/phy/tegra/phy-tegra194-p2u.ko’:
No such file or directory
ending:
jp6-flash-jetson-linux/R36.4.3/Linux_for_Tegra/rootfs/boot/extlinux/extlinux.conf
It is amazing what low quality and unorganized , untested tools/software is offered by Nvidia.
i have attached a shot of sdkmanager and it behavior with proxy.
also a logfile when using flash script.
sh_bad_flash_2.log (39.8 KB)
Hi,
Parts of the installation process use the apt-get command to install external libraries directly or from a Docker container. Consequently, your apt and Docker configurations must be set to access through the proxy to the Ubuntu repositories.
Some questions to confirm:
- Is your
apt and Docker set the proxy setting?
Thanks
Hi,
I am not using a docker , and the system and sdkmanager setting for proxy are set.
If you are refering to sdkmanager, it became clear that the proxy settings of sdkmanager
never let even the authentication to finish. It was a mere coincidense that I used -cli option
and mgically it popped a qr code in the linux terminal!. The proxy settings are set in the sdkmanager.
Although the sdkmanager splash showes apt repository check failure, the sdk log file shows
error details:
Err:9 https://repo.download.nvidia.com/jetson/common r36.4 InRelease <—??
error: Err:4 ubuntu jammy-updates InRelease
12:02:25.234 - warn: Failed to get component from group data map for undefined
12:02:25.234 - info: Connection failed [IP: 10.20.28.20 8080]
and more
most are from httpc://repo/download.nvidia.com
In any case I have abandoned the use of sdkmanager when behind a proxy.
When using the flashing script,
Does the script also needs to use apt?
The log file shows that it is looking for files like “phy-tegra194-p2u.ko” in the local dir where
the jp6-flash-jetson-linux is installed.
Thanks
Hi @jojo_19,
Please upgrade the sdk manager to 2.4.1 since the proxy issue is fixed in the latest version.
Thanks
I installed the sdkmanager 2.4.1 but I am not seeing any change.
with or without sdk manager the errors a when pre checking before flashin happens to do with apt-keys
ex :
E: The repository ‘https://repo.download.nvidia.com/jetson/common r36.4 InRelease’ is not signed.
W: GPG error: https://repo.download.nvidia.com/jetson/t234 r36.4 InRelease:
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 0D296FFB880FB004
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: Index of /ubuntu jammy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
I tried:
sudo apt-key adv --fetch-key https://repo.download.nvidia.com/jetson/jetson-ota-public.asc
How do I find and get the keys needed?
So many references to this problem but no one in nvidia seems to bother/care amazing
Hi,
Please try to use another method:
- Download the Driver Package (BSP) and Sample Root Filesystem from Jetson Linux Release 36.5 | NVIDIA Developer
- Follow the Quick Start — NVIDIA Jetson Linux Developer Guide to do below steps
$ tar xf ${L4T_RELEASE_PACKAGE}
$ sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./tools/l4t_flash_prerequisites.sh
$ sudo ./apply_binaries.sh
$ sudo ./flash.sh jetson-agx-orin-devkit internal
Thanks
