Can't wake up monitor

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

Have a Jetson Nano Orin running the latest JetPack 6.1. For some odd reason it does not wake up the monitor after inactivity (after moving mouse or pressing a key). The device is still on as I can still SSH in and all just fine. How do I fix this issue (monitor not waking up)?

2 
$pstree

$sytemctl gdm3 status

If gdm3 is still running it might be your monitor went in energy save mode or ??

3

Please share the result of /var/log/Xorg.0.log when this situation happened.

Is it a pure DP monitor or you are using a adapter?

6

Please directly attach the log.

7

If I understand you correctly, yes, it’s a pure DP monitor - no adapters are used. Attached is the content of Xorg.0.log.

monitorwontwake-Xorg.0.log (26.1 KB)

9

Hi,

At what situation did you dump this log out? Is gdm3 running when you dumped this log?

10

Is it correct to assume it has a display port connector on it and you are connecting directly to nano board without an hdmi to display port adapter?

11

Yes, gdm3 was running when this was dumped.

12

It’s a DP monitor and DP cable. No HDMI port or DP to HDMI adapter are involved.

13

But your log indicates xorg is already disabled. This shall not happen if gdm3 is truly running there.

[    48.998] (II) systemd-logind: not releasing fd for 13:66, still in use
[    48.998] (II) UnloadModule: "libinput"
[    48.998] (II) systemd-logind: releasing fd for 13:64
[    49.023] (II) UnloadModule: "libinput"
[    49.023] (II) systemd-logind: releasing fd for 13:68
[    49.060] (II) UnloadModule: "libinput"
[    49.060] (II) systemd-logind: releasing fd for 13:67
[    49.089] (II) UnloadModule: "libinput"
[    49.089] (II) systemd-logind: releasing fd for 13:66
[    49.117] (II) UnloadModule: "libinput"
[    49.117] (II) systemd-logind: releasing fd for 13:65
[    49.180] (II) NVIDIA(GPU-0): Deleting GPU-0
[    49.182] (II) Server terminated successfully (0). Closing log file.

Just to clarify. GDM3 will trigger xorg so xorg log shall be enabled.

14

At this point, its unknown what broke. If you don’t have any important files on the drive it would be best to just do fresh install. Problems like this are hard and nearly impossible to find and the amount of time you spend will greatly exceed the time to reinstall. Keep in mind when you do reinstall everything will be wiped out.

15

Looks like you’re right, gdm3 is not running even though systemctl says it is. Out of curiosity I ran “systemctl restart gdm3” (from SSH) and the monitor woke up and the login screen appears! Downside is it’s a new desktop session so whatever was active when the monitor went to sleep is gone. This is an improvement, but still a bummer.

Very weird considering this is a fresh install.

16

Will the monitor still go into sleep and make the same situation happened again after this gdm3 restart?

17

Solved. I think. It looks like the monitor (Dell P2414H) just does something weird in terms of sleeping. I tried a different monitor (Samsung F27T450FQN) and it wakes up consistently, no matter how long of in-activity. The desktop session stays intact, too. So yeah, I’d say it’s the monitor that’s causing the issue. Indeed, a very strange problem with a relatively critical effect (a basic device like a monitor crashing GDM3 and losing your desktop session).

19

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.