Forum / NoMachine for ARM / How can I get a local HDMI signal if headless?
Tagged: Jetson
- This topic has 5 replies, 2 voices, and was last updated 7 months, 1 week ago by Tboonstl.
-
AuthorPosts
-
February 27, 2024 at 14:24 #47184TboonstlParticipant
I’m a newbie and have a Jetson Orin Nano with Ubuntu 22.04 on it. I installed the NoMachine software with the help of a video.
After installing the NoMachine software, the video said to type these commands to go headless:
sudo systemctl set-default multi-user.target
sudo /usr/NX/bin/nxserver --restart
The problem is that I was not able to log into the Jetson with the Windows box and now the Jetson is headless and I’m not able to get a screen.
How can I fix this?
February 27, 2024 at 18:06 #47188BritgirlKeymasterTo restore the GUI you just removed, you can run
sudo systemctl set-default graphical.target
.You should still be able to connect with NoMachine 🙂 When you say “not able to get a screen”, what do you mean exactly? Did you install NoMachine on Windows, NoMachine on your Jetson and then tried connecting with NoMachine using the Jetson’s IP address? Can you tell us what happens exactly?
What desktop environment is running in Ubuntu? We have an article here with some tips about how to set up your Jetson. Take a look: https://kb.nomachine.com/AR02R01074 and follow the tips there and let us know how you get on.
February 27, 2024 at 18:33 #47189TboonstlParticipantSomeone suggested I get NoMachine to remote into a Jetson Orin Nano. I watched the video at https://www.youtube.com/watch?v=OYrSADrtSag and followed the directions. It seems to follow the same info in the link you had provided.
I also installed NoMachine on a Windows 10 box (and port forwarded the Jetson on the router). But, I must have done something wrong as I cannot remote into the Jetson (with Ubuntu 22.04).
I should NOT have done the headless option until I successfully tested the Windows remote capability. Kind of a bone-headed thing to do, but now I can’t get into the Jetson to run “sudo systemctl set-default graphical.target” to get GUI back.
If I can get the Windows to remote in, that would be ideal, but I’m pretty stymied.
February 27, 2024 at 22:03 #47192TboonstlParticipantOne more smaller item, the sound on my Windows machine is very muffled after installing NoMachine. What might be the workaround for that?
February 28, 2024 at 12:10 #47204BritgirlKeymasterWith regards to the sound issue, check what is indicated in your Windows sound settings. Are you able to change to another audio output? With regards to the no access on Jetson issue, are you not even able to SSH into it? Have you tried rebooting? Rebooting with a monitor attached or HDMI dongle (if you don’t have a monitor)?
February 28, 2024 at 17:34 #47212TboonstlParticipantWhen I rebooted after installing NoMachine, Windows did an automatic update (contrary to my settings). I think that update is what messed up my sound.
I’m rebuilding the Jetson from the last backup.
I appreciate all your help though.
Thank you.
-
AuthorPosts
This topic was marked as solved, you can't post.