Avahi-daemon, utils issues

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
[O] DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
[O] Linux
QNX
other

Hardware Platform
[O] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
[O] 1.8.1.10392
other

Host Machine Version
[O] native Ubuntu 18.04
other

After we download minicom to use, 3 errors are popped up on our Host screen.

Errors were encountered while processing:

Processing triggers for initramfs-tools (0.130ubuntu3.13) …
Processing triggers for libc-bin (2.27-3ubuntu1.2) …
Errors were encountered while processing:
avahi-daemon
avahi-utils
libnss-mdns:arm64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Like that…

We’ve tried to update to the newest version of software.

keeping current version.

either way did not work properly, same error occurs.

Thank you.

Dear @rlfxogud961,
How did you install minicom?
Do you see this issue while installing DRIVE OS 5.2.6 on host? If so, could you share the sdkm logs(~/.nvsdkm/ folder )

Hello Krishna :)
To answer your questions,

  • How did you install minicom?
    → I connected xavier and host pc with usb (serial communication) and connected to xavier through minicom from the host pc.

  • Do you see this issue while installing DRIVE OS 5.2.6 on host?
    → No… I had a perfect install with no errors.

  • If so, could you share the sdkm logs(~/.nvsdkm/ folder )
    → Since it was installed with no errors on the host pc, so I upload xavier’s sdkm logs…

How I solved that problem?
logs.zip (294.5 KB)

Dear @rlfxogud961,
If the installation is successful and you can connect to Tegra using minicom. What is the issue here?

Thank you for reply quickly.

I connected xavier using minicom and then I started to install GUI on target.
And I followed below link [step by Installing GUI on target]
https://docs.nvidia.com/drive/drive-os-5.2.0.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_Development_Guide/Interfaces/sys_components_file_ubuntu.html

After running ‘apt-get install gdm3 ubuntu-unity-desktop’ command, I got the below errors.

Errors were encountered while processing:
avahi-daemon
avahi-utils
libnss-mdns:arm64
E: Sub-process /usr/bin/dpkg returned an error code (1)

The following error occurred, but the display is connected. However, when rebooting, the display connection is cut off…

Why occured this happens…?

Dear @rlfxogud961,
You can ignore avahi related errors. Could you test using lightdm instead of gdm3 when installing GUI on fresh installation.
Please see the discussion on below topics if it helps

I’ve installed lightbm, but it still didn’t work.

At this time, the display was not turned on.
The first trial with gdm3, the monitor was turned on, but an error occurs after we rebooted.

Moreover, we got another error message, which is “/var/lib/dpkg/lock-frontend”, we have no idea what it is, is this issue related to authorization?

I appreciate your support.

Dear @rlfxogud961,
Could you please reflash the target and check installing GUI again. Please make a note of steps and input values you have provided on terminal and share with us for verification. The steps I have followed is at Error trying to connect monitor - #17 by SivaRamaKrishnaNV