couldn't install jetpack 2.0 on tx1

wbergerson · November 25, 2015, 1:51pm

I’m on a intel i7 machine with ubuntu 14.04 and the jetpack couldn’t make it through install for a tx1. If I do a ./JetPack_ver_.run I get a error of
“the manifest file is broken”

if I do a sudo ./JetPack_ver.run, the install just hangs. I’m going to see if I can flash with the l4t .tbz2 and file system directly.l

-wb

wbergerson · November 25, 2015, 6:46pm

I was able to flash the x1 with the l4t os / filesystem and get the cuda-repo-l4t-r23.1-7-0-local_7.0-71_armhf.deb package installed.

sorta annoyingly, the make on the samples only builds a partial set, but the device passes the deviceQuery executable.

kayccc · November 30, 2015, 8:22am

Is there any change you made?

Would you please provide more clear information for this issue?

Cheers

wbergerson · November 30, 2015, 3:12pm

The only change I made was skip the jetpack route for installation and flash the os from a laptop with the cuda linux for tegra image. From there, on the actual tx1, post flash, I could do the install with the cuda toolkit for the L4T image.

on the make issue, Once the took kit is installed, simply going to the example folder and doing a ‘make all’ did not actually allow all of the samples to be turned into executables in a batch run.

wb

dusty_nv · November 30, 2015, 4:01pm

Are you going into to the samples folder at /usr/local/cuda/samples or /home/ubuntu/NVIDIA_CUDA_7.0_Samples?
The copy located in /usr/local might give permission problems unless you are building with sudo.

Were there any errors in particular from the make that you can share?
On Jetson TX1 I normally make the samples with make SMS=53.

Some of the samples are for dGPU and not meant for Tegra, these are skipped during compilation (e.g. simpleP2P, cudaDecodeGL, nvrtc).
In the past, the samples with OpenGL interop wouldn’t link out-of-the-box because of missing (GLEW, GLUT, ect), but it seems that JetPack installs these packages automatically.

EdwardZhou · December 1, 2015, 2:53am

JetPack will set up cross-compilation environment on host to compile CUDA samples. However, you will need install the missing packages by yourself if you want to compile CUDA samples directly on TX1 device.

wbergerson · December 4, 2015, 7:37pm

my install of cuda didn’t put a copy of the samples in the /home/ubuntu but the sudo make, with the ‘SMS=53’ additions took care of the makes. -thanks dusty.

wb

seeky15 · December 17, 2015, 7:13am

Is there any solution to the initial problem “The manifest file is broken”?
Getting the same on Ubuntu 14.04 64bit.

EdwardZhou · December 18, 2015, 9:54am

Hi seeky15,

Can you please clean up the JetPack directory and retry? Please make sure you can access the Internet before starting JetPack.

phill-EuL · January 15, 2016, 6:57am

Hello everyone,

I have the same problem with JetPack-L4T-2.0-linux-x64.run. After typing in my sudo password during the startup of the Component Manager, a error message box pops up stating “The manifest file is broken”. Clicking on ok ends the installation process. My college has the same problem with his development kit…

I tied several things with and without sudo, restarting the PC (as if we were on Windows :-)) always cleaning up the installation folder prior to the next try.

Is there any solution to this problem, besides the posibity of flashing the tx1 “by hand”.

EdwardZhou · January 18, 2016, 2:23am

After typing your sudo password during the startup of the Component Manager, JetPack will download <JetPack_Dir>/manifest.json file first. Can you please paste the content of this file?

Another question: is there any special setting on your machine to the Internet? Like special proxy, etc.

phill-EuL · January 18, 2016, 11:39am

Hi Edward, thanks for the answer. Below is the content of the manifest file:

{
  "manifest": {
    "name": "JetPack L4T",
    "portfolio": [
      {
        "name": "JetPack L4T",
{
  "manifest": {
    "name": "JetPack L4T",
    "portfolio": [
      {
        "name": "JetPack L4T",
{
  "manifest": {
    "name": "JetPack L4T",
    "portfolio": [
      {
        "name": "JetPack L4T",

I am in a company network and we do have a proxy, but what do you mean with “special”? Usually all connections to the internet work seamlessly. I am clarifying with our IT department if the file got screwed up somewhere through the servers…
In the meantime: Is it possible to obtain the file from elsewhere, download it manually and add it by hand?

I don’t know if this is a useful hint but jetpack 1.1 for the tk1 worked without problems.

EdwardZhou · January 19, 2016, 5:13am

Hi Phill,

The manifest.json file is downloaded from http://developer.download.nvidia.com/devzone/devcenter/mobile/jetpack_l4t/json/linux-x64/manifest.json

Can you check if you are able to open it directly in browser?

The content of this file looks like the following:

{
  "manifest": {
    "name": "JetPack L4T",
    "portfolio": [
      {
	    "name": "JetPack L4T",
        "version": "2.0",
        "url": "http://developer.download.nvidia.com/devzone/devcenter/mobile/jetpack_l4t/001/json/jetpack-l4t-devzone.json",
        "installerMin": "1.0"
      }
    ]
  }
}

I’ll write in another comment on how to workaround the issue.

EdwardZhou · January 19, 2016, 6:04am

To use manually downloaded files, please use following steps:

Create <JetPack_Dir>/_installer/local.manifest file, with following content:

{
  "manifest": {
    "name": "JetPack L4T",
    "portfolio": [
      {
	    "name": "JetPack L4T",
        "version": "2.0",
        "url": "file:///repository.json",
        "installerMin": "1.0"
      }
    ]
  }
}

phill-EuL · January 20, 2016, 7:20am

Thanks for the support so far. It helped a lot.

It is no problem for me to download the files via web browser or wget, but with the Component Manager I get a download error for every single file listed in the post.

Thanks to the instructions above I was still able to install the jetpack.

I cleaned up the install folder and created the manifest and repository file as described above. With a little bash script I downloaded all the listed files to the folder <JetPack_Dir>/jetpack_download/, ran the Jetpack again and installation and flashing the device was finished without problems.

EdwardZhou · January 20, 2016, 8:20am

Thanks to update further information.

With more investigation, I think the broken files might be caused by optimized proxy: Range field in http header will be ignored and cached content will be used instead when downloading from the same url. Thus the multi-thread download mechanism in Component Manager doesn’t work. We’ll add support to download with single thread in future JetPack releases.

EdwardZhou · April 8, 2016, 5:59am

In JetPack 2.1, the command to force JetPack to use single-thread downloading is as following:

NV_DEVTOOLS_FORBID_MULTIPLE_DOWNLOAD_THREADS=1 ./JetPack-L4T-2.1-linux-x64.run

vshaban · April 18, 2016, 1:50pm

I’m trying to run JetPack L4T installer from JetPack-L4T-2.1-linux-x64.run
When Component manager window appears it has no list of packages.
All its lists and combo boxes are empty. What’s wrong with the installer?

I tried to do this with VirtualBox and real ubuntu host. The same result.
How can I make JetPack installer to download packages?

EdwardZhou · April 19, 2016, 2:46am

Hi vshaban,

Can you please check the previous discussions under the same topic and see if they solve your issue?

vshaban · April 19, 2016, 6:00am

Hi Edward, thanks for your answer.
I’ve found desc how to workaround this issue.
The way is to download manually all files
and rerun Jetson installer.
For me it’s interesting how to make installer
to download and set files according to its scenario.

Thanks any way for your answer.