Error trying to connect monitor

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX General
,
#1

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
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
Linux
QNX
other

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

SDK Manager Version
1.6.0.8170
other

Host Machine Version
native Ubuntu 18.04
other

After flashing and installing ubuntu desktop following this instructions: Install DRIVE with SDK Manager :: DRIVE Platform Installation Guide with NVIDIA SDK Manager
I’m still unable to see anything on the monitor, but I get this message in the terminal when the pegasus reboots, and every time i disconnect and connect the monitor.

[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
��verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000
fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000
fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
��[  OK  ] Started Session c2 of user lightdm.
��verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000
fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
��[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
**��verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000**
**fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000**
**verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000**
**fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000**

What’s the meaning of this error and how to fix it?

DRIVE OS 5.2.6 Target display GUI issues
Drive OS 5.2.6 Monitor İssues
DRIVE OS 5.2.6 SDK Target (Pegasus) monitor display Issue
Error trying to enable HDMI
How to flash factory default?
#4

Dear @jber4282,
May I know the monitor details? Is the same monitor has no issue on DRIVE OS 5.2.0

#5

Hi @SivaRamaKrishnaNV
It’s a dell monitor model 1908fp, yes no issues with Drive OS 5.2.0

#7

Dear @jber4282,
Could you confirm If you have followed the steps in https://docs.nvidia.com/drive/drive-os-5.2.6.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_NGC_Development_Guide/Interfaces/sys_components_file_ubuntu.html#wwpID0E0FB0HA
Also, is it possible to try with another monitor. Please check the discussion on No Monitor Display for DriveOS 5.2.6.0 if it helps.

#8

Hi @SivaRamaKrishnaNV

I presume that this document is outdated as the queries are different. I have flashed the pegasus to have a clean start. I have attached the full log while trying to install GUI on the target, I can see some errors related to the network configuration (which is different from the standard network manager)

Network manager error (545.5 KB)

To pass the last error I remove avahi-daemon
sudo apt-get remove avahi-daemon

Then I’m able to see the installation succeed:

nvidia@tegra-ubuntu:~$ sudo apt-get install gdm3 ubuntu-unity-desktop           
Reading package lists... Done                                                   
Building dependency tree                                                        
Reading state information... Done                                               
ubuntu-unity-desktop is already the newest version (0.1).                       
gdm3 is already the newest version (3.28.3-0ubuntu18.04.6).                     
The following packages were automatically installed and are no longer required: 
  bind9-host geoip-database libavahi-core7 libbind9-160 libdns1100 libgeoip1    
  libisc169 libisccc160 libisccfg160 liblwres160                                
Use 'sudo apt autoremove' to remove them.                                       
0 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.

I’ve also set the AutomaticLoginEnable to true.

![image|258x57](upload://624DJbNrPXhMrG6lsYZEk5AEXCR.png

After rebooting I’m unable to see anything on the screen yet, but I can see the following messages:

tegra-ubuntu login: [   35.141401] bash[1309]: Switch did not repospond to MAC 1
[   35.144440] bash[1309]: Get firmware version will be attempted using 02-00-01
[   45.309693] bash[1309]: Unable to get the current switch firmware version    
[   45.310280] bash[1309]: Please also check the ethernet interface provided.   
[   45.310737] bash[1309]: Current ethernet interface used is : eth0.200        
[   45.311096] bash[1309]: Try running with sudo if not already                 
[   45.311451] bash[1309]: Could not get the current firware version.           
[   45.311809] bash[1309]: Updation failed                                      
[   45.312700] bash[1309]: ----------------------- Error log start -------------
[   45.313992] bash[1309]: /lib/firmware/marvell_ethernet//tools/linux/prebuilt0
[   45.314611] bash[1309]: Marvell 88Q5050 Image Download Tool v0.00.0014 (loca)
[   45.315094] bash[1309]: Result = 0                                           
[   45.315355] bash[1309]: Start: 5580, current: 10006581, diff: 10001001, diff1
[   45.315928] bash[1309]: Timeout 10000 elapsed, RX tries: 5560141             
[   45.316555] bash[1309]: TIMEOUT!                                             
[   45.316952] bash[1309]: Failed to Get the response for firmware version get .
[   45.317336] bash[1309]: GetFwVersion failed with error:9                     
[   45.317668] bash[1309]: Image Download Tool exiting with result 2.           
[   45.318441] bash[1309]: /lib/firmware/marvell_ethernet//tools/linux/prebuilt0
[   45.318844] bash[1309]: Marvell 88Q5050 Image Download Tool v0.00.0014 (loca)
[   45.319207] bash[1309]: Result = 0                                           
[   45.319527] bash[1309]: Start: 5008, current: 10006009, diff: 10001001, diff1
[   45.319893] bash[1309]: Timeout 10000 elapsed, RX tries: 5594357             
[   45.320257] bash[1309]: TIMEOUT!                                             
[   45.320567] bash[1309]: Failed to Get the response for firmware version get .
[   45.321034] bash[1309]: GetFwVersion failed with error:9                     
[   45.321289] bash[1309]: Image Download Tool exiting with result 2.           
[   45.321997] bash[1309]: ----------------------- Error log end ---------------
[   45.322641] bash[1309]: Failed to update the Marvell switch firmware.. Scrip1

which seems to be a network issue ? below the log after rebooting
reboot (95.3 KB)

I have followed the suggested link but still I’m unable to see anything on the screen.

#9

Dear @jber4282,
This is strange. Is the flashing successful? Is it possible to check re-flashing and check installing GUI as given Error trying to connect monitor - #7 by SivaRamaKrishnaNV . If it does not fix, Please attach the fresh logs to file bug.

#10

Hi @SivaRamaKrishnaNV

I re-flashed the pegasus successfully, here the logs:
last_log_14_sept.zip (389.4 KB)

In this query:

image
image700×280 26.3 KB

I left it as it was (No), keeping the current version as suggested in the guide. For the rest of the queries I also kept the current versions.
The rest of the GUI installation process happened just as described before. Logs below:
nvidia_gui_installation (513.3 KB)

The monitor doesn’t have any signal.

.

#11

Dear @jber4282,
Could you share the Aurix FW version?

#13

Hi @SivaRamaKrishnaNV

Here it is:
image

#14

Hi @SivaRamaKrishnaNV

Just an update: I re-flashed the pegasus downgrading it to the Drive OS 5.2.0; after installing the GUI, everything works, and I’m able to see the screen.
Then, re-flash it again with Drive OS 5.2.6 and follow all the instructions without any success the Switch did not resposnd to MAC 1 remains after rebooting and the monitor has no signal.

#15

Dear @jber4282,
Thanks for the update. It looks like issue could be with few monitors. I don’t think switch issue has any connection to display
I am checking internally on switch issue. Do you see gdm is running?

#16

Hi @SivaRamaKrishnaNV

This is the output:

nvidia@tegra-ubuntu:~$ systemctl status display-manager
��● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabl
   Active: active (running) since Thu 2021-09-16 16:40:04 AEST; 3h 7min ago
  Process: 1169 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status
 Main PID: 1192 (gdm3)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/gdm.service
           ��└��─1192 /usr/sbin/gdm3

Sep 16 19:48:00 tegra-ubuntu gdm3[1192]: GdmDisplay: display lasted 0.491382 sec
Sep 16 19:48:01 tegra-ubuntu gdm3[1192]: Child process -8287 was already dead.
Sep 16 19:48:01 tegra-ubuntu gdm3[1192]: Child process 8269 was already dead.
Sep 16 19:48:01 tegra-ubuntu gdm3[1192]: Unable to kill session worker process
Sep 16 19:48:01 tegra-ubuntu gdm-launch-environment][8306]: pam_unix(gdm-launch-
Sep 16 19:48:01 tegra-ubuntu gdm-launch-environment][8306]: pam_unix(gdm-launch-
Sep 16 19:48:01 tegra-ubuntu gdm3[1192]: Child process -8324 was already dead.
Sep 16 19:48:01 tegra-ubuntu gdm3[1192]: Child process 8306 was already dead.
Sep 16 19:48:01 tegra-ubuntu gdm3[1192]: Unable to kill session worker process
Sep 16 19:48:01 tegra-ubuntu gdm-launch-environment][8339]: pam_unix(gdm-launch-
Ubunutu GUI not showing after installation with sudo apt-get install gdm3 ubuntu-unity-desktop
#17

Dear @jber4282,
I have flashed DRIVE OS 5.2.6 on target again and at first I see no GUI on the display.

I see errors related to avahi in the end like you. Please check the log at install_GUI.txt (485.5 KB). Also,I see below messages on serial console similar to you whenever I turn on display using power button on monitor.

fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000

But I could get the display . I increased brightness of the screen for on safe side.

nvidia@tegra-ubuntu:~$  systemctl status display-manager
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2021-09-21 03:51:33 -05; 17min ago
  Process: 1109 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
 Main PID: 1126 (gdm3)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gdm.service
           └─1126 /usr/sbin/gdm3

Sep 21 03:51:33 tegra-ubuntu systemd[1]: Starting GNOME Display Manager...
Sep 21 03:51:33 tegra-ubuntu systemd[1]: Started GNOME Display Manager.
Sep 21 03:51:33 tegra-ubuntu gdm-autologin][1162]: gkr-pam: no password is available for user
Sep 21 03:51:34 tegra-ubuntu gdm-autologin][1162]: pam_unix(gdm-autologin:session): session opened for user nvidia by (uid=0)

Do you see the same issue with both Tegras? I had checked flashing only Tegra B as it has DRIVE OS 5.2.0 earlier.

Could not have HDMI signals in monitor
#18

Hi @SivaRamaKrishnaNV

I just followed all the steps for Tegra B and I was able to get the display. I wonder why isn’t working for Tegra A.

S.

#19

Dear @jber4282,
This is strange. Do you see the network switch error on Tegra B also? Earlier, I had ran the GUI commands remotely and notice no display when I saw the machine in office. So, I had reflashed it again and I could see the display now.
Could you check flashing only Tegra A and confirm if you still see the issue.

DRIVE OS 5.2.6 SDK Target (Pegasus) monitor display Issue
#20

Hi @SivaRamaKrishnaNV

I flashed only Tegra A, and I was able to see the display now, thanks!

#21

Dear @jber4282,
Good to hear that display issue is fixed now. Do you still see the marvel switch issue?

#22

Hi @SivaRamaKrishnaNV

yes, it’s still there.

#23