Empty /etc/apt/sources.list on clean DRIVE OS 5.1.6.1 image

I used the NVIDIA sdkmanager GUI to flash a DRIVE AGX target with DRIVE OS 5.1.6.1.

With Xavier A connected to the internet, I found that all my apt-get installs were failing (note: technically, I was running “apt install”, but I understand that this is equivalent to “apt-get install”). Eventually I discovered that /etc/apt/sources.list was an empty file.

The same was true in the cross-compilation environment (~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs_a).

Since this was a clean install, I’m wondering whether this is expected behavior. Should /etc/apt/sources.list be empty?

I populated it so I could proceed with other tutorials, but I’m worried that I may be installing the wrong packages and setting myself up for failure.

Could someone else check their target’s /etc/apt/sources.list and share the contents here? Thanks!

Hi evanmt03s,

Below is my ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs_a/etc/apt/sources.list.
Are you sure your installation was completed?

# Copyright (c) 2018, NVIDIA CORPORATION.  All rights reserved.
#
# NVIDIA CORPORATION and its licensors retain all intellectual property
# and proprietary rights in and to this software, related documentation
# and any modifications thereto.  Any use, reproduction, disclosure or
# distribution of this software and related documentation without an express
# license agreement from NVIDIA CORPORATION is strictly prohibited.

# Recommended mirrors default, -updates, -security, Components main restricted & universe enabled
deb http://ports.ubuntu.com/ubuntu-ports/ bionic main universe restricted
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-updates main universe restricted
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-security main universe restricted

# Backports https://wiki.ubuntu.com/UbuntuBackports not recommended
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-backports main universe restricted

# Proposed https://wiki.ubuntu.com/Testing/EnableProposed not recommended
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-proposed main universe restricted

# Multiverse components have copyright or legal issues use with (legal) care
# https://help.ubuntu.com/community/Repositories/Ubuntu
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic multiverse
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-updates multiverse
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-security multiverse

Hi VickNV, thanks for your reply.

I’m sure the installation completed — at least, the GUI indicated that it had completed. Is there another way for me to verify the integrity of my installation? If the installation didn’t complete, I’m concerned that there might be other files missing from my image that could cause other problems. Thanks.

Please provide ~/.nvsdkm/logs directory (installation logs) for our investigation. Thanks!

Here are the logs:

https://drive.google.com/open?id=1hj036lErRqSliRo-TjS9jFqBR0gs_qz3

Thanks for looking into this!

I checked your logs and have no idea why you meet the issue.

This is how I checked them:

Below messages decribes sources.list in ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs-pkgs/filesystem.tar.bz2 was installed into ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs.

$ grep -rn 'filesystem\.tar'
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log:141:Now installing ./drive-t186ref-linux/targetfs-pkgs/filesystem.tar.bz2 to ./drive-t186ref-linux/targetfs

Below messages decribes things under ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs were copied/moved into ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs_a and ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs_b respectively.

$ grep -rn 'Total time to install targetfs_a and _b' -B 5
...
logs/DRIVE_Software_10.0_Linux_OS/NV_DRIVE_PLATFORM_RFS_TARGET_COMP.log-19601-Time to install the base components: 86
logs/DRIVE_Software_10.0_Linux_OS/NV_DRIVE_PLATFORM_RFS_TARGET_COMP.log-19602-Time to install all the components: 105
logs/DRIVE_Software_10.0_Linux_OS/NV_DRIVE_PLATFORM_RFS_TARGET_COMP.log:19603:Total time to install targetfs_a and _b: 233

You can check below code snippet of ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform/tools/full_install_setup.sh for the details:

component_install() {

...
    if [[ $dual_targetfs == 0 ]]; then
...
    else
...
        install_for_dual_targetfs || failure "Installing components for dual targetfs failed"
        print_time "Total time to install targetfs_a and _b" $time_snapshot2
    fi
...
}
...
install_for_dual_targetfs() {
...
    print_time "Time to install the base components" $time_snapshot
    sudo rm "$targetfs_dir/targetfs/etc/build*info.txt"
    sudo cp -rp "$targetfs_dir/targetfs" "$targetfs_dir/targetfs_b"
    sudo mv "$targetfs_dir/targetfs" "$targetfs_dir/targetfs_a"
...
    print_time "Time to install all the components" $time_snapshot
}

Thanks for the detailed explanation.

I decided to try to untar that image file (filesystem.tar.bz2) myself to make sure it contained the correct /etc/apt/sources.list. To untar, I copied the archive to ~/Desktop/test and ran this command:

$ tar xvjf filesystem.tar.bz2

And the resulting /etc/apt/sources.list did match the contents you posted. So I’m not sure why it ended up empty for me.

But I did see some errors during the untar process. These went away when I ran the command again (in a new, empty directory) with sudo. Errors below:

./dev/
./dev/zero
tar: ./dev/zero: Cannot mknod: Operation not permitted
./dev/fd
./dev/full
tar: ./dev/full: Cannot mknod: Operation not permitted
./dev/urandom
tar: ./dev/urandom: Cannot mknod: Operation not permitted
./dev/ptmx
tar: ./dev/ptmx: Cannot mknod: Operation not permitted
./dev/stderr
./dev/pts/
./dev/stdout
./dev/random
tar: ./dev/random: Cannot mknod: Operation not permitted
./dev/stdin
./dev/tty
tar: ./dev/tty: Cannot mknod: Operation not permitted
./dev/null
tar: ./dev/null: Cannot mknod: Operation not permitted
./dev/shm/
./home/
./home/nvidia/
./home/nvidia/.profile
./home/nvidia/examples.desktop
./home/nvidia/.bash_logout
./home/nvidia/.bashrc

I’m wondering whether sdkmanager untars this file using sudo, and whether these errors could be causing problems if it doesn’t. Thanks.

According to your log below:

$ grep -rn 'filesystem\.tar' -B 10
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-131-Info: change working directory to /home/perceptive/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-132-Info: [ Package Install Started ]
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-133-Info: runfile installer start to install NV_OSS_AND_NV_PACKAGES_SDK_COMP
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-134-Info: change working directory to /home/perceptive/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-135-Info: .install/ folder from previously installed component exists and is being removed
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-136-Info: exec_command: /home/perceptive/Downloads/nvidia/sdkm_downloads/drive-t186ref-linux-5.1.6.1-16902563-nv-core-rfs.run --nox11
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-137-Verifying archive integrity... All good.
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-138-Uncompressing drive-t186ref-linux-5.1.6.1-16902563........
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-139-Installing drive-t186ref-linux root filesystem
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log-140-
logs/DRIVE_Software_10.0_Linux_OS/NV_OSS_AND_NV_PACKAGES_SDK_COMP.log:141:Now installing ./drive-t186ref-linux/targetfs-pkgs/filesystem.tar.bz2 to ./drive-t186ref-linux/targetfs

You can run below commands:

cd ~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS
~/Downloads/nvidia/sdkm_downloads/drive-t186ref-linux-5.1.6.1-16902563-nv-core-rfs.run --nox11

I decided to delete ~/.nvsdkm and rebuild all the target images + reflash my AGX.

I checked targetfs_a after the flashing step started, and now /etc/apt/sources.list has the expected contents.

Maybe this is because I enabled passwordless sudo. I also disabled secure boot and resolved some other NVIDIA driver issues.

Anyway, thanks for your help.

Just for completeness, in the end my /etc/apt/sources.list was still empty on the target (and in the chroot mirror) after flashing.

So I expanded filesystem.tar.bz2 on my host and manually copied the resulting etc/apt/sources.list over to my target so I could install packages.

I’m still concerned about the overall integrity of my install given this persistent issue.

Contents below:

# Copyright (c) 2018, NVIDIA CORPORATION.  All rights reserved.
#
# NVIDIA CORPORATION and its licensors retain all intellectual property
# and proprietary rights in and to this software, related documentation
# and any modifications thereto.  Any use, reproduction, disclosure or
# distribution of this software and related documentation without an express
# license agreement from NVIDIA CORPORATION is strictly prohibited.

# Recommended mirrors default, -updates, -security, Components main restricted & universe enabled
deb http://ports.ubuntu.com/ubuntu-ports/ bionic main universe restricted
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-updates main universe restricted
deb http://ports.ubuntu.com/ubuntu-ports/ bionic-security main universe restricted

# Backports https://wiki.ubuntu.com/UbuntuBackports not recommended
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-backports main universe restricted

# Proposed https://wiki.ubuntu.com/Testing/EnableProposed not recommended
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-proposed main universe restricted

# Multiverse components have copyright or legal issues use with (legal) care
# https://help.ubuntu.com/community/Repositories/Ubuntu
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic multiverse
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-updates multiverse
# deb http://ports.ubuntu.com/ubuntu-ports/ bionic-security multiverse

I just tried to install DRIVE Software 10.0 from scratch on new installed ubuntu 18.04.3. Right before Flash Xavier A+B stage, I checked both sources.list files and both look good. FYI.

~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs_a/etc/apt/sources.list
~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DRIVEOS/drive-t186ref-linux/targetfs_b/etc/apt/sources.list

I faced exactly same issue. According to following post, there is at least another person who faced this issue.

I looked around files and scripts, and there are a file etc/sources.list_default in both of targetfs_a/b next to empty sources.list. It seems have correct lines.
I also found a following script which generate the file.

nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_E3550/DriveSW_Components/DrivePlatform/tools/linux/targetfstool_linux.py

Would you check the script? In functions prepare_apt_sources() and cleanup_apt_sources(), it moves sources.list (and _default). I suppose this functions didn’t work properly.

1 Like

I’ve also encountered this issue before.
I manually edited in a rudimentary sources.list, so I could download and run Puppet, which sets up the rest.

Same here.

Hi all,

We can reproduce the issue and are checking it with internally. Will get back to you here. Thank!

5 Likes

Hello VickNV,

I can also confirm for our system the described issue (flashed the unit online & offline with cleaning the download folders inbetween). I just was wondering if you have an update for us (we have slight consernces that some other configs might be as well not in a correct state)?

1 Like

Hello VickNV,
has there been any advance in fixing this bug? Your last post is from 2 weeks ago and there is no new information yet.

Before we fix and update DRIVE Software, please use sources.list_default manually by below commands:

sudo cp /etc/apt/sources.list_default /etc/apt/sources.list sudo apt update
$ sudo apt install

Sorry for any inconvenience!

1 Like

The fix is in DRIVE Software 10.0 revision 2 so target systems flashed with revision 2 (~/Downloads/nvidia/sdkm_downloads/sdkml3_drive_linux_5161_r2_sdk_os.json seen in your host system) won’t need the WAR. Thanks!