didnt see that.
data.zip (220.8 KB)
Hi.
Will you hit any error if you just type sudo apt-get update on your terminal over your host?
oh… yes.
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/trusty-updates/main/binary-amd64/Packages 404 Not Found [IP: 2001:67c:1562::18 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/trusty-security/main/binary-amd64/Packages 404 Not Found [IP: 2001:67c:1562::18 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/binary-amd64/Packages 404 Not Found [IP: 2001:67c:1562::18 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Please get this fixed first. Or directly find other host that can run apt-get without problem.
Hi again @WayneWWW
now sdk manager downloaded the installation package. but it didn’t installed. no errors shows in apt-get update in ubuntu 16.04
these are the error logs
SDKM_logs_JetPack_4.5.1_Linux_for_Jetson_TX2_2021-06-15_16-24-13.zip (158.2 KB)
I checked the log again. It is similar to the early log.
Info: exec_command: /tmp/tmp_NV_L4T_FILE_SYSTEM_AND_OS_T186_COMP.sh
Using rootfs directory of: /media/gayan/New_Volume/sdk_new/target/JetPack_4.5.1_Linux_JETSON_TX2/Linux_for_Tegra/rootfs
||||||||||||||||||||||| ERROR |||||||||||||||||||||||
-----------------------------------------------------
1. The root filesystem, provided with this package,
has to be extracted to this directory:
/media/gayan/New_Volume/sdk_new/target/JetPack_4.5.1_Linux_JETSON_TX2/Linux_for_Tegra/rootfs
-----------------------------------------------------
2. The root filesystem, provided with this package,
has to be extracted with 'sudo' to this directory:
/media/gayan/New_Volume/sdk_new/target/JetPack_4.5.1_Linux_JETSON_TX2/Linux_for_Tegra/rootf
What is the file system of this disk partition - /media/gayan/New_Volume/sdk_new/target/? Is this a ext4?
NTFS is not supported.
Failed to fetch of an Ubuntu URL is just telling you that this particular Ubuntu server does not provide packages for that architecture. This isn’t something NVIDIA controls. It also is not necessarily a fatal error since there are mirrors, and even if no server provides certain packages it is is possible the packages are unrelated to boot.
SDK components run on NVIDIA servers, not Ubuntu servers, so an Ubuntu address failure is different than an NVIDIA address failure (and I see only non-NVIDIA servers saying no arm64 found).
And you mentioned something about a router, and of course no package would be found if the router is not functioning correctly, but if that were the case then no package would be retrieved, so that is unlikely the problem.
If you use a proxy or if you go through a firewall it is quite possible that the failed components are due to selective network blocking, but I’ve seen a number of Ubunt servers which don’t provide the arm64 packages. Seeing a message about a “404” not found implies the server was reached, and this is not a firewall/router/network issue. It goes back to being an issue of that particular server.
If servers have changed what they provide, then it might be possible to update “/etc/sources.list” to look at different servers.
If you just flash, and don’t try to install any optional packages, does the issue change? E.g., flash only of the Jetson and no other operation. Prior to flash, on the Ubuntu host PC side, you might want to first:
sudo apt update
sudo apt --fix-broken install
(then see if it flashes)
Thanks for the help.
I have fixed this with manual build. Need to extract files on /Home/ folder.
then it gains root access correctly.
“New_Volume/sdk_new/target/” yeah this is NTFS file system. I think that’s the problem
Thanks!
So it usb working or not?
yes. working
1 Like
NTFS would appear to flash correctly, but you are correct that this is a problem (once the system is up and running most of the file permissions would then be incorrect since NTFS does not support Linux permissions).
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.