Remote control Jetson with a monitor connected

Hi Team,

We have Jetson Orin AGX Developer kit 64GB, We have installed JetPack 6.2.1.
We need to remotely control the GUI of jetson. Jetson will be connected to a monitor.

  1. We are using Gnome remote desktop to get GUI control remotely.
  2. We were facing issue that when screen is locked, we were not able to get the remote access,
    I resolved it by installing gnome extension : link.
  3. But when jetson is rebooted or loses power and start again, we are not able to take remote.

I would request you to help resolve this issue or suggest alternative.

Note:

  1. We have tried installing xrdp (remote crashes after entering username and password)
  2. We have tried GDM autologin, the remote doesn’t work.

*** Please note that this reply is generated by LLM automatically ***

I’d be happy to help you with your issue.

It sounds like you’re trying to remotely control the GUI of your Jetson Orin AGX Developer Kit, which is connected to a monitor. You’ve installed JetPack 6.2.1 and are using Gnome Remote Desktop to access the GUI remotely. However, you’re facing two issues:

  1. When the screen is locked, you’re not able to access the GUI remotely. You’ve resolved this by installing a Gnome extension.
  2. When the Jetson reboots or loses power and starts again, you’re not able to access the GUI remotely.

To address the second issue, I’ll provide some suggestions and alternatives.

Gnome Remote Desktop

It’s great that you’ve got Gnome Remote Desktop working, but it’s not surprising that it’s not working after a reboot or power loss. This is because Gnome Remote Desktop is a session-based remote desktop solution, which means it relies on an active user session to function. When the Jetson reboots or loses power, the user session is terminated, and Gnome Remote Desktop is no longer available.

Alternative Solutions

Here are a few alternative solutions you could consider:

  1. xrdp: You’ve already tried xrdp, but it’s crashing after entering the username and password. This might be due to a configuration issue or a compatibility problem with the Jetson’s graphics drivers. You could try troubleshooting xrdp or seeking help from the xrdp community.
  2. VNC: VNC (Virtual Network Computing) is another popular remote desktop solution. You can install a VNC server on your Jetson, such as TightVNC or TigerVNC, and use a VNC client on your remote machine to access the GUI. VNC is a more traditional remote desktop solution that doesn’t rely on user sessions, so it might be more suitable for your needs.
  3. NoMachine: NoMachine is a remote desktop solution that provides a more seamless and user-friendly experience. It’s designed for Linux and supports a wide range of distributions, including Ubuntu, which is the base OS for JetPack. NoMachine uses a proprietary protocol that provides better performance and security than traditional VNC solutions.
  4. GDM Autologin: You’ve tried GDM autologin, but it’s not working for you. This might be due to a configuration issue or a compatibility problem with the Jetson’s graphics drivers. You could try troubleshooting GDM autologin or seeking help from the GDM community.

Additional Suggestions

To improve the reliability of your remote desktop solution, you could consider the following:

  1. Use a static IP address: Assign a static IP address to your Jetson to ensure that it’s always accessible at the same IP address.
  2. Configure the firewall: Make sure that the firewall on your Jetson is configured to allow incoming connections on the port used by your remote desktop solution.
  3. Use a remote desktop gateway: Consider using a remote desktop gateway, such as Apache Guacamole, to provide an additional layer of security and reliability for your remote desktop connections.

I hope these suggestions and alternatives help you resolve your issue and find a reliable remote desktop solution for your Jetson Orin AGX Developer Kit.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Hi,

Please try the vino VNC instead.

Thanks

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