Hi, I want to install JetsonPack on Jetson agx xavier following the document Install Jetson Software with SDK Manager :: NVIDIA SDK Manager Documentation, but SDKManager show install error on Jetson OS Image - File System and OS. How cound I fixed this problem. Thanks
Here is my install log
13:46:59 INFO : File System and OS : Installing BSP Debian packages in /home/joechen/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/rootfs
13:46:59 ERROR : File System and OS : qemu: uncaught target signal 4 (Illegal instruction) - core dumped
13:46:59 ERROR : File System and OS : /home/joechen/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/nv_tegra/nv-apply-debs.sh: line 194: 13034 Illegal instruction (core dumped) LC_ALL=C chroot . dpkg -i --path-include="/usr/share/doc/*" "${pre_deb_list[@]}"
13:46:59 ERROR : File System and OS : [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.sh; [error]: exit status 132
13:46:59 INFO : File System and OS : [ Package Install Finished with Error ]
13:46:59 INFO : File System and OS : [ 9.92 MB released. Disk Avail: 286.14 GB ]
13:46:59 INFO : File System and OS : [ NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP Install took 2m20s ]
13:46:59 ERROR : File System and OS : [error]: Run commands failed at step Install: command /tmp/tmp_NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.sh finished with error
13:46:59 INFO : File System and OS :
13:46:59 ERROR : File System and OS : command terminated with error
13:46:59 ERROR : File System and OS : Install 'File System and OS' failure, command < using adapter to install NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP@JETSON_AGX_XAVIER to /home/joechen/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER > terminated with error.
Is this being performed on a regular desktop Linux PC? That particular issue is probably from under QEMU, so this is not necessarily the case, but it seems like perhaps it is an issue with QEMU install (which should be done in the script, and then what works under QEMU would be arm64 instruction set). It just seems odd and I am wondering about the host PC specs.
Yes, host PC’s system is Ubuntu18.04.
Looks like an issue.
Could you directly go to
“/home/joechen/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/”
and run nv_tegra/nv-apply-debs.sh with sudo? Need your error message there.
or you could try a even more simple method as
cd Linux_for_Tegra/rootfs
sudo LC_ALL=C chroot
and see if any error.
Here is the error message
Root file system directory is /home/joechen/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/nv_tegra/../rootfs
Copying public debian packages to rootfs
Start L4T BSP package installation
QEMU binary is not available, looking for QEMU from host system
Found /usr/bin/qemu-aarch64-static
Installing QEMU binary in rootfs
~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/rootfs ~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/nv_tegra
Installing BSP Debian packages in /home/joechen/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/nv_tegra/../rootfs
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
./nv-apply-debs.sh: line 194: 18608 Illegal instruction (core dumped) LC_ALL=C chroot . dpkg -i --path-include="/usr/share/doc/*" "${pre_deb_list[@]}"
joechen@joechen:~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/rootfs$ sudo LC_ALL=C chroot
chroot: missing operand
Try 'chroot --help' for more information.
Hi,
Sorry that missing a “.” in previous command. Please try again.
sudo LC_ALL=C chroot .
Got the same error
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction
Hi,
Please check if you have this file in rootfs on your host.
JetPack_4.4_DP_Linux_DP_JETSON_XAVIER_NX/Linux_for_Tegra/rootfs$ ll usr/bin/qemu-aarch64-static
-rwxr-xr-x 1 root root 3126560 May 15 10:25 usr/bin/qemu-aarch64-static*
Also, is this host a x86 device?
Yes, it does
-rwxr-xr-x 1 root root 3143680 May 15 12:46 usr/bin/qemu-aarch64-static*
and uname -m returns x86-64, is this mean my host is a x64 device?
Could you share below info?
dpkg -s qemu-user-static;
uname -a
I’m sorry, there is something wrong with network currently so I upload the message via photo.
Hi joechenrh,
The qemu seems frmo ubuntu14.04… could you try to install the correct version for 18.04?
I installed the new version of qemu-user-static. And now sdkmanger create image succeed. Thank for your help and patience.
Package: qemu-user-static
Status: install ok installed
Priority: optional
Section: otherosfs
Installed-Size: 98806
Maintainer: Ubuntu Developers ubuntu-devel-discuss@lists.ubuntu.com
Architecture: amd64
Multi-Arch: foreign
Source: qemu
Version: 1:2.11+dfsg-1ubuntu7.23
Provides: qemu-user-binfmt
Recommends: binfmt-support
Suggests: sudo
Conflicts: qemu-user-binfmt
Description: QEMU user mode emulation binaries (static version)
QEMU is a fast processor emulator: currently the package supports
ARM, CRIS, i386, M68k (ColdFire), MicroBlaze, MIPS, PowerPC, SH4,
SPARC and x86-64 emulation. By using dynamic translation it achieves
reasonable speed while being easy to port on new host CPUs.
.
This package provides the user mode emulation binaries, built
statically. In this mode QEMU can launch Linux processes compiled for
one CPU on another CPU.
.
If binfmt-support package is installed, qemu-user-static package will
register binary formats which the provided emulators can handle, so
that it will be possible to run foreign binaries directly.
Built-Using: gcc-8 (= 8.3.0-6ubuntu1~18.04.1), glib2.0 (= 2.56.4-0ubuntu0.18.04.4), glibc (= 2.27-3ubuntu1.1), zlib (= 1:1.2.11.dfsg-0ubuntu2)
Homepage: http://www.qemu.org/
Original-Maintainer: Debian QEMU Team pkg-qemu-devel@lists.alioth.debian.org
I get the same error during file system and OS installation. " Fist I get installation is taking too long…" message and when I click yes, i get the error and it skips to step 4. Here is my log:
- 03:38:52 ERROR : File System and OS : [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.sh; [error]: exit status 1
- 03:38:52 INFO : File System and OS : [ Package Install Finished with Error ]
- 03:38:52 INFO : File System and OS : [ 1.10 MB used. Disk Avail: 23.73 GB ]
- 03:38:53 INFO : File System and OS : [ NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP Install took 12m45s ]
- 03:38:53 ERROR : File System and OS : [error]: Run commands failed at step Install: command /tmp/tmp_NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.sh finished with error
- 03:38:53 INFO : File System and OS :
- 03:38:53 ERROR : File System and OS : command terminated with error
- 03:38:54 ERROR : File System and OS : Install ‘File System and OS’ failure, command < using adapter to install NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP@JETSON_AGX_XAVIER to /media/yonatan/166AE8696AE846D9/jet2/JetPack_4.3_Linux_JETSON_AGX_XAVIER > terminated with error.
I am using linux 18.04. At first I thought it was my qemu, and I tried to update it, but it is already the new version.
Thanks,
Flash won’t work without a lot more disk space. The Xavier’s root filesystem will be about 30GB, and this needs to be generated on your host PC (it is an enormous file). Then a sparse version of this will be created, about 2 more GB. Other temp files are generated. I think the flash script wants you to have about 50GB of free space.
Incidentally, I normally use Fedora. I do have a tiny dual core Atom laptop I use when I must use JetPack/SDK Manager. It is quite slow, and the process takes a long time, especially with a very slow laptop disk. I see the “too slow” message many times and just tell it to keep going.
Actually, I have Ubuntu/windows dual boot. The disk containing ubuntu doesn’t have much space, so I downloaded the files there, and I chose the other disk containing windows as the install location since it has 300gb free space. So I don’t get why this is a space problem.
Thanks,
The files will be built somewhere under:
~/nvidia/nvidia_sdk/...a version.../Linux_for_Tegra/
If the space being used from Windows is not there, then it won’t help much. In particular, if the space is not formatted as a native Linux filesystem type (e.g., ext4), the even if flash works the boot will fail. NTFS, VFAT, and other Windows filesystem types are not capable of preserving Linux permissions even if you manage to mount the space within your home directory.
Useful to know: “df -H -T /whereever” will give both the available space and the filesystem type at “/whereever”.
