Upgraded DRIVE Software 9.0 to 10.0 successfully but OS not configured and is broken

We have a NVIDIA DRIVE AGX Developer Kit.

We had Drive Software 8.0 working fine. Then yesterday we upgraded it to 9.0 first. It seemed fine. Then we upgraded it to 10.0 and SDK Manager finished saying INSTALLATION COMPLETED SUCCESSFULLY with no visible errors on the GUI or the GUI terminal.

But when we logged into the Xavier A or B devices, the OS installation is too incomplete. Icons are broken, half the software is not installed, no browsers, not even a screenshot tool.
We then retried flashing to see if it works this time but no avail, same results.

AGX Developer Kit was connected to the internet via an ethernet cable in the first flashing session to the HSD Ethernet port, in the second run to the first of two 10 GbE ports.
Nothing else was connected to the device.

““Success””

Xavier B Desktop

Xavier B Home Directory

Xavier B Installed Programs

Xavier A looks somewhat same, both don’t respond to even basic ping google.com command no matter which port we connect ethernet cable to.

We also have included the log files available from the Host pc ~/.nvsdkm folder.

Edit: And we didn’t get Auto-Run Vibrante-Setup Scripts window on the Nvidia device during the flashing process. Which screenshots from others have.
logs.tar.gz (969 KB)
pdkinstaller.log.zip (54 KB)

Dear faith.cirit,
It seems the flashing is successful.

Icons are broken, half the software is not installed, no browsers, not even a screenshot tool.

Just to clarify, The DRIVE SW 10.0 is shipped with minimal OS which does not have tools like earlier to reduce file system size. You can install whatever you need using apt-get.

Could you check connecting to internet using the Ethernet dongle?

And ethernet cable has internet, yes.

There is minimal and there is incomplete. If you look at the screenshots carefully you will see how different it is compared to a complete system. If you have ever had chance to install it yourself, you would’ve noticed the difference.

Examples don’t work, samples don’t work, there isn’t even a browser and you are telling me everything is fine and i should install them by myself?

This is not the first time I’m using a Drive platform and clearly there is something wrong.

Also those files in target_deb look like unfinished post-installation artifacts:

And we didn’t get Auto-Run Vibrante-Setup Scripts window during the flashing process. Which screenshots from others have.

Dear fatih.cirit,
I looked at your screenshots and I see the same on my machine after flashing DRIVE SW 10.0.
As per the sdkm.log and pdkinstaller.log output, the flashing seems to be successful.

*** End of Download Summary ***
                    
2020-01-08 13:14:17.184 - info: 
Install summary of 35 components:

        Install started on: 12:29:26 GMT+0300 (+03).

        Install ended on: 13:14:17 GMT+0300 (+03).

        Install duration:  00:44:50 .

        Install idle time: 0.000s .

        Real install duration (duration - idle time): 00:44:50 .

        Install 35 components.

            - Up-to-date 34 components.

        Install failed 0 files.

        Install skipped 0 files.

        Install details:

        - NV_CUDA_HOST_COMP@host: Up-to-date.
- NV_CUDA_HOST_CROSS_LINUX_COMP@host: Up-to-date.
- NV_CUDNN_HOST_CROSS_LINUX_COMP@host: Up-to-date.
- NV_TENSORRT_HOST_COMP@host: Up-to-date.
- NV_TENSORRT_HOST_CROSS_LINUX_COMP@host: Up-to-date.
- NV_DRIVE_AV_HOST_COMP@host: Up-to-date.
- NV_DRIVE_AV_HOST_CROSS_COMPILE_LINUX_COMP@host: Up-to-date.
- NV_DRIVE_WORKS_DOCUMENTATION_HOST_COMP@host: Up-to-date.
- NV_DRIVE_AV_APP_DOCUMENTATION_HOST_COMP@host: Up-to-date.
- NV_DRIVE_AR_HOST_COMP@host: Up-to-date.
- NV_DRIVE_AR_HOST_CROSS_COMPILE_LINUX_COMP@host: Up-to-date.
- NV_NVIDIA_NSIGHT_GRAPHICS_LINUX_COMP@host: Up-to-date.
- NV_NVIDIA_NSIGHT_SYSTEMS_LINUX_COMP@host: Up-to-date.
- NV_GNU_TOOLCHAINS_COMP@DDPX: Up-to-date.
- NV_DRIVE_FOUNDATION_PACKAGES_SDK_COMP@DDPX: Up-to-date.
- NV_DRIVE_FOUNDATION_OSS_COMP@DDPX: Up-to-date.
- NV_P3479_SPECIFIC_PACKAGE_COMP@DDPX: Up-to-date.
- NV_E3550_SPECIFIC_PACKAGE_COMP@DDPX: Up-to-date.
- NV_DRIVE_FOUNDATION_PDKINSTALLER@DDPX: Up-to-date.
- NV_OSS_AND_NV_PACKAGES_SDK_COMP@DDPX: Up-to-date.
- NV_DPX_PACKAGES_COMP@DDPX: Up-to-date.
- NV_AURIX_UPDATER_COMP@DDPX: Up-to-date.
- NV_DDS_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_LINUX_RELEASE_NOTES@DDPX: Up-to-date.
- NV_CUDA_TARGET_LINUX_COMP@DDPX: Up-to-date.
- NV_TENSORRT_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_AV_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_IX_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_AR_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_UX_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_PLATFORM_RFS_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_HYPERION_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_SERVICEFRAMEWORK_TARGET_COMP@DDPX: Up-to-date.
- NV_DRIVE_OTA_TARGET_COMP@DDPX: Up-to-date.
- NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Installed - 00:44:49 -start: 12:29:26 GMT+0300 (+03) - end: 13:14:16 GMT+0300 (+03).

Note that, web browser, CUDA samples and tensorRT samples are not included in package.

We recommend Xavier A for DRIVE AV development and testing and Xavier B for DRIVE IX development and testing(for more details check DRIVE SW 10.0 release notes at https://developer.download.nvidia.com/driveworks/secure/docs/DRIVE_10.0_Release_Docs/NVIDIA_DRIVE_Software_Release_Notes_10.0.pdf?f3cukQINevrX6sYsg4lBEC6PDYyy7Ing33pxsLONIwEuzr1h-aOF2mC5e2v12LB1vIqHiNj5prmxeiKd5X4bkBpPshucpiPwSVzQ3dEr0ef4KnDMVfItoBiLd6Q4BTIFk_Gr08f9_UfqyGY_Qs0zEjg6ooAWq6-JmFWVymPzvq7DfvpQTNThdlC5lgQn6YllSps6G9rlZR2IfA)

Could you share you connection details on DRIVE AGX to connect to internet. I have connected Dual GBE Dongle to front panel’s 3|4 port labelled with 1GbE or 100MbE to use internet. Could you check the same?

Also, Could you share details about the sample you failed to run?

If you really see the same things on your machine too then there is something wrong with your setup as well.

Here are lines starting from 23147 in sdkm.log file I have attached in the first post:

2020-01-07 19:07:25.061 - info: Preparing to unpack .../21-humanity-icon-theme_0.6.15_all.deb ...
2020-01-07 19:07:25.061 - info: Unpacking humanity-icon-theme (0.6.15) ...
2020-01-07 19:07:25.061 - info: dpkg: error processing archive /tmp/apt-dpkg-install-ZaXyjD/21-humanity-icon-theme_0.6.15_all.deb (--unpack):
2020-01-07 19:07:25.061 - info: corrupted filesystem tarfile - corrupted package archive
2020-01-07 19:07:25.061 - info: Selecting previously unselected package ubuntu-mono.
2020-01-07 19:07:25.061 - info: Preparing to unpack .../22-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb ...
2020-01-07 19:07:25.061 - info: Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) ...
2020-01-07 19:07:25.061 - info: Selecting previously unselected package adwaita-icon-theme.
2020-01-07 19:07:25.061 - info: Preparing to unpack .../23-adwaita-icon-theme_3.28.0-1ubuntu1_all.deb ...
2020-01-07 19:07:25.061 - info: Unpacking adwaita-icon-theme (3.28.0-1ubuntu1) ...
2020-01-07 19:07:25.061 - info: Errors were encountered while processing:
2020-01-07 19:07:25.061 - info: /tmp/apt-dpkg-install-ZaXyjD/21-humanity-icon-theme_0.6.15_all.deb
2020-01-07 19:07:25.061 - info: stderr:
2020-01-07 19:07:25.061 - info: debconf: delaying package configuration, since apt-utils is not installed
2020-01-07 19:07:25.061 - info: E: Sub-process /usr/bin/dpkg returned an error code (1)
2020-01-07 19:07:25.061 - info:  
2020-01-07 19:07:25.061 - info: ERROR:linux.targetfstool_linux:Failure running command: apt-get --yes install --no-install-recommends humanity-icon-theme

Some things are corrupted and it cannot install them. And as I’ve stated we didn’t get Auto-Run Vibrante-Setup Scripts window during the flashing process. Which screenshots from others have.

Also same file from line 26489:

2020-01-07 19:12:12.952 - info: * Reloading system message bus config...
2020-01-07 19:12:12.952 - info: Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
2020-01-07 19:12:12.952 - info: invoke-rc.d: initscript dbus, action "force-reload" failed.
2020-01-07 19:12:12.952 - info: Failed to preset unit, unit /etc/systemd/system/NetworkManager-dispatcher.service is masked.
2020-01-07 19:12:12.952 - info: /usr/bin/deb-systemd-helper: error: systemctl preset failed on NetworkManager-dispatcher.service: No such file or directory
2020-01-07 19:12:12.952 - info: Failed to preset unit, unit /etc/systemd/system/NetworkManager-wait-online.service is masked.
2020-01-07 19:12:12.953 - info: /usr/bin/deb-systemd-helper: error: systemctl preset failed on NetworkManager-wait-online.service: No such file or directory
2020-01-07 19:12:12.953 - info: Failed to preset unit, unit /etc/systemd/system/NetworkManager.service is masked.
2020-01-07 19:12:12.953 - info: /usr/bin/deb-systemd-helper: error: systemctl preset failed on NetworkManager.service: No such file or directory

Indicates it couldn’t install or configure network related things too.

And could you please explain what these are for in ~/target_deb folder? I don’t think others in this forum had that folder or had these issues.

Also If there is any doubt left on the broken installation, The driveworks samples are not installed.

The driveworks sdk docs state that I should be able to find precompiled samples under /usr/local/driveworks/bin :

But there is no bin folder under /usr/local/driveworks folder

Hi fatih.cirit,

As SivaRamaKrishna mentioned in #5, we recommend Xavier A for DRIVE AV development so the driveworks files installed at Xavier A & B may be different. You should be able to see /usr/local/driveworks/bin folder at Xavier A, right?

For humanity-icon-theme package installation, there is no problem on my side. We will check how to clariy further.

And as I’ve stated we didn’t get Auto-Run Vibrante-Setup Scripts window during the flashing process. Which screenshots from others have.
Could you show me the screenshots? We would like to know what “Auto-Run Vibrante-Setup Scripts window” is missing on your side.

This part is same on my side. I’ll check and then get back to you.

Besides, any crucial functional issues for your development on your system now? Thanks!

Hi VickNV and SivaRamaKrishna,

I’m in the same team with fatih.cirit.

–> Yes, we found the directory at Xavier A. Then I tried camera_gmsl sample,but I had an error that was “cannot connect to camera”.I checked the connection, it was connected then I decided to reboot. After I reboot the system, it worked somehow without the error.

–> I tried to install humanity-icon-them with “sudo apt install humanity-icon-theme”, but it was already installed. I just applied the theme, now we have icons as well.

–> https://devtalk.nvidia.com/default/topic/1056661/general/flash-drive-software-failed-on-xavier-e3550/post/5357559/#5357559 we meant the scripts window shown in the attachment of this post.

–> Currently we have internet connection as well. We are going to get in touch with you if we experience any problems related to the system after the flashing. Thank you so much for the collaboration.

Best regards

Dear mert.colak,
Regarding internet connection, I have connected Dual GBE Dongle to front panel’s 3|4 port labelled with 1GbE or 100MbE to use internet. Could you check the same and confirm?

Dear SivaRamaKrishna,

Yes, Dual GBE Dongle is connected to front panel’s 3|4 port labelled with 1GbE or 100MbE. But I made a connection test. When I connected the cable to Channel-A of Dual GBE Dongle, I couldn’t connected to the internet at both Xavier A&B. However, when the cable is connected to Channel-B, I connected to the internet. Moreover, I connected a GigE Camera to Channel-A of Dual GBE Dongle to check if there is a connection problem from Channel-A. But I received packages from the camera. I’m really confused right now. Why can’t I connect to the internet from Channel-A?

Dear mert.colak,
Why can’t I connect to the internet from Channel-A?

I could connect to internet using both channel A&B of Dual GBE Dongle on both Xavier A and B. Can you check the status after restarting network manager or rebooting machine.

sudo /etc/init.d/network-manager restart

Those are unneeded after flashing, they are preinstalled. Next release won’t have the issue. Thansk!