Unable to add conservative default mode "nvidia-auto-select"

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

I am currently running Orin NX on the Orin Nano board. I am experiencing an issue where the X server crashes when a specific device is connected to the DisplayPort at startup (the device I have confirmed the issue with is a DP hub device with nothing connected on the Tx side).

$ sudo cat /var/log/Xorg.0.log | grep EE

[    29.766] Current Operating System: Linux eizo-desktop 5.15.136-tegra #1 SMP PREEMPT Mon May 6 09:56:39 PDT 2024 aarch64
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    30.254] (EE) NVIDIA(GPU-0): Unable to add conservative default mode "nvidia-auto-select".
[    30.254] (EE) NVIDIA(GPU-0): Unable to add "nvidia-auto-select" mode to ModePool.
[    30.255] (EE) NVIDIA(0): Unable to use default mode "nvidia-auto-select".
[    30.255] (EE) NVIDIA(0): Failing initialization of X screen
[    30.537] (EE) Screen(s) found, but none have a usable configuration.
[    30.537] (EE)
[    30.537] (EE) no screens found(EE)
[    30.537] (EE)
[    30.537] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    30.537] (EE)
[    30.543] (EE) Server terminated with error (1). Closing log file.

I am unable to determine the following regarding this issue:

  • Under what conditions does the DisplayPort device cause this abnormal behavior?
  • Can this issue be prevented through X server configuration or other settings?
  • If resolving this is difficult, is there a guarantee that this issue only occurs with this specific device?

What should I check to resolve this issue? I appreciate your assistance with this matter.

2

Sounds an issue to check. Could you flash your BSP back to rel-35.5 and see if such issue is there too?

Also, provide us model ID of the device you are using.

3

Hello, Wayne. Thank you for your response.

Sounds an issue to check. Could you flash your BSP back to rel-35.5 and see if such issue is there too?

It seems that the same issue occurs with R35.5.0 as well.

ubuntu@ubuntu-desktop:~$ sudo cat /var/log/Xorg.0.log | grep EE

[    17.913] Current Operating System: Linux ubuntu-desktop 5.10.192-tegra #1 SMP PREEMPT Mon Feb 19 20:19:53 PST 2024 aarch64
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    18.849] (EE) NVIDIA(GPU-0): Unable to add conservative default mode "nvidia-auto-select".
[    18.849] (EE) NVIDIA(GPU-0): Unable to add "nvidia-auto-select" mode to ModePool.
[    18.850] (EE) NVIDIA(0): Unable to use default mode "nvidia-auto-select".
[    18.850] (EE) NVIDIA(0): Failing initialization of X screen
[    18.888] (EE) Screen(s) found, but none have a usable configuration.
[    18.888] (EE)
[    18.888] (EE) no screens found(EE)
[    18.888] (EE)
[    18.888] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    18.888] (EE)
[    18.895] (EE) Server terminated with error (1). Closing log file.

Also, provide us model ID of the device you are using.

The device where I confirmed the issue is the Synaptics VMM6220 (with nothing connected on the Tx side).

Thank you.

4

Could you share your full xorg log but not just this partial one?

1 Like
5

I am attaching the complete syslog and Xorg.0.log.

Thank you.

r35_5_syslog.log (541.9 KB)
r35_5_Xorg.0.log (9.1 KB)

6

Do you have other hub there that can check if all the hub would hit such issue or only VMM6220?

8

I only have hubs from the same manufacturer.
It seems that these hubs also experience the same issue.

Synaptics VMM5320
Synaptics VMM6210

Also, I have not yet confirmed the same issue with monitors. However, I have not tested with special monitors that lack EDID or have incomplete EDID information.

9

I still haven’t found a good solution to this problem.
Is there any additional information I should provide here to help resolve this issue?