Jetpack 4.6 running on NVMe ssd

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

HELP!!!

I have been running jetpack 4.5 on NVMe ssd on my xavier NX every thing worked fine.
I tried to upgrade from 4.5 to 4.6 as a small upgrade.
I don’t have another machine running Unix so it seams there is no way I can upgrade properly.
Although some new features are working on the “UPGRADE” most are not,

ALL I WANT IS THE SYSTEM RUNNING ON XAVIER NX AS BEFORE USING JETPACK 4.6.
I have tried sd card seems to have loads of error.

~$ apt depends nvidia-jetpack | awk '{print $2}' | xargs -I {} sudo apt install -y {}

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

[sudo] password for paul: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nvidia-cuda is already the newest version (4.6-b199).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nvidia-opencv is already the newest version (4.6-b199).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nvidia-cudnn8 is already the newest version (4.6-b199).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nvidia-tensorrt is already the newest version (4.6-b199).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nvidia-visionworks is already the newest version (4.6-b199).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  docker-ce docker-ce-rootless-extras nvidia-docker2 pigz
Suggested packages:
  cgroupfs-mount | cgroup-lite
Recommended packages:
  slirp4netns
The following NEW packages will be installed
  docker-ce docker-ce-rootless-extras nvidia-container nvidia-docker2 pigz
0 to upgrade, 5 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/21.2 MB of archives.
After this operation, 95.5 MB of additional disk space will be used.
debconf: Delaying package configuration, since apt-utils is not installed.
Selecting previously unselected package pigz.
(Reading database ... 158686 files and directories currently installed.)
Preparing to unpack .../archives/pigz_2.4-1_arm64.deb ...
Unpacking pigz (2.4-1) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a20.10.8~3-0~ubuntu-bionic_arm64.deb ...
Unpacking docker-ce (5:20.10.8~3-0~ubuntu-bionic) ...
Selecting previously unselected package nvidia-docker2.
Preparing to unpack .../nvidia-docker2_2.2.0-1_all.deb ...
Unpacking nvidia-docker2 (2.2.0-1) ...
Selecting previously unselected package nvidia-container.
Preparing to unpack .../nvidia-container_4.6-b199_arm64.deb ...
Unpacking nvidia-container (4.6-b199) ...
Selecting previously unselected package docker-ce-rootless-extras.
Preparing to unpack .../docker-ce-rootless-extras_5%3a20.10.8~3-0~ubuntu-bionic_arm64.deb ...
Unpacking docker-ce-rootless-extras (5:20.10.8~3-0~ubuntu-bionic) ...
Setting up docker-ce (5:20.10.8~3-0~ubuntu-bionic) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Thu 2021-09-02 12:18:55 BST; 15ms ago
     Docs: https://docs.docker.com
  Process: 12497 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 12497 (code=exited, status=1/FAILURE)

Sep 02 12:18:55 xavier systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Setting up docker-ce-rootless-extras (5:20.10.8~3-0~ubuntu-bionic) ...
Setting up pigz (2.4-1) ...
dpkg: dependency problems prevent configuration of nvidia-docker2:
 nvidia-docker2 depends on docker-ce (>= 18.06.0~ce~3-0~ubuntu) | docker-ee (>= 18.06.0~ce~3-0~ubuntu) | docker.io (>= 18.06.0); however:
  Package docker-ce is not configured yet.
  Package docker-ee is not installed.
  Package docker.io is not installed.

dpkg: error processing package nvidia-docker2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-container:
 nvidia-container depends on nvidia-docker2 (= 2.2.0-1); however:
  Package nvidia-docker2 is not configured yet.

dpkg: error processing package nvidia-container (--configure):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
No apport report written because the error message indicates it's a follow-up error from a previous failure.
No apport report written because the error message indicates it's a follow-up error from a previous failure.
Processing triggers for systemd (237-3ubuntu10.51) ...
Errors were encountered while processing:
 docker-ce
 nvidia-docker2
 nvidia-container
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nvidia-vpi is already the newest version (4.6-b199).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up docker-ce (5:20.10.8~3-0~ubuntu-bionic) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Thu 2021-09-02 12:19:05 BST; 19ms ago
     Docs: https://docs.docker.com
  Process: 13229 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 13229 (code=exited, status=1/FAILURE)

Sep 02 12:19:05 xavier systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of nvidia-docker2:
 nvidia-docker2 depends on docker-ce (>= 18.06.0~ce~3-0~ubuntu) | docker-ee (>= 18.06.0~ce~3-0~ubuntu) | docker.io (>= 18.06.0); however:
  Package docker-ce is not configured yet.
  Package docker-ee is not installed.
  Package docker.io is not installed.

dpkg: error processing package nvidia-docker2 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-container:
 nvidia-container depends on nvidia-docker2 (= 2.2.0-1); however:
  Package nvidia-docker2 is not configured yet.

dpkg: error processing package nvidia-container (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up error from a previous failure.
No apport report written because the error message indicates it's a follow-up error from a previous failure.
Errors were encountered while processing:
 docker-ce
 nvidia-docker2
 nvidia-container
^C
3

You should run dist-upgrade first.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/updating_jetson_and_host.html#wwpID0E0AL0HA

4

thanks for the reply
I followed the instructions including dist-upgrade I have spent over a day trying to rectify my situation, It was in desperation I posted this SOS.
Is there any way I can clear the error messages like too many attempts etc so that i can start again.

5

What is your current result of “cat /etc/nv_tegra_release”?

6

cat /etc/nv_tegra_release

R32 (release), REVISION: 6.1, GCID: 27863751, BOARD: t186ref, EABI: aarch64, DATE: Mon Jul 26 19:36:31 UTC 2021

7

What is the exact error now? Looks like your device is already upgrade to rel-32.6.1.

8

1st Example

docker images
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
No wi-fi
Power icon seems to have disapeared . It did have the latest option 20w etc
Not being able to boot without sd card in place

9

The NVMe SSD boot supported is actually added from rel-32.6.1.

Thus, actually what you’ve done in previous release was not a real “boot from” NVMe case.
For such case, the apt get upgrade/dist-upgrade may not able to know such customization. And it just fallback to normal boot flow as the sdcard boot.

Actually, I am wondering if you are really willing to dump the log and resolve this issue one by one. Honestly, I think reflash the board will be faster than debugging this. Especially when checking wifi issue requires some knowledge in linux kernel.

10

Whats the best way to reflash the board. I don’t have another unix computer.
I have jetson nano ,the xavier nx which using now, Raspberry pi 4., windows surface pro 4 using a ubuntu 18.04 app (Unfortunately running windows 11) I have followed the jetsonhacks instructions downloaded onto the surface but it does not recognise the usb devices (lsusb)
I don’t just ask for help I have tried my best but have now hit a brick wall
thanks very much for your help so far

11

sudo vi /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
deb https://repo.download.nvidia.com/jetson/common r32.6 main
deb https://repo.download.nvidia.com/jetson/t194 r32.6 main
This is where it all started!!!

12

Sorry Wayne are you still there?

13

You can try to use virtual box to run Ubuntu and expose usb to the virtual OS. I was able to flash using virtual box before. I use windows 10 though

14

Thanks for the tip I’ll give it try. I have now got 4.6 booting on nvme the same way as before but sd card has to be present.
Cheers for the help
Regards

15

I have tried virtual box not got the flashing to to work. Does not recognise xavier. The was one point when it did so I took out 9:10 pin connection then the connection was lost. I have tried n number of times to no avial.
The windows machine recognises the xavier nx as APX device.
Thanks for the tip
Cheers