I use Jetson AGX Orin in Academy.
I use it for ROS learning.
Also, it is connected to a ROS robot (TOYOTA HSR) in wired, and I often use ssh to the Jetson via wifi.
However, sometimes I cannot connect (broken pipe etc.).
It seems ok the wifi I use.
first image shows speedtest of jetson,
second image shows speedtest of another pc(same wifi).
By the way, I use it in group, so the host environment is wide variety (powershell, wsl, linux etc.) but all members are facing the problem.
I use Jetpack5.1.2 (to use isaac ros)
Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!
Thank you for your reply.
I am able to boot and use Jetson AGX Orin on its own. The problem I am facing is that I frequently experience the inability to ssh connect to Jetson AGX Orin, even though the network is not unstable. In the worst case, I cannot ssh at all for about 2 hours.
Pursuant to man sshd_config.5 you could try editing with vi or nano:
sudo nano /etc/ssh/sshd_config
and uncomment #MaxSessions 10 (10 is the default but increase the number from 10 to 15 or 20).
MaxSessions 15
and save the file and then maybe have everyone save their work logout of their ssh connections; then run:
sudo systemctl daemon-reload
sudo systemctl restart ssh
and log back on via ssh and see if it helped. If you got more than 20 concurrent ssh connections to the Orin then increase the number some more, understanding that eventually it may affect the devices perfomance.
Thank for your advice, and sorry to late reply.
It’s better than before.
But even now, sometimes we cannot use ssh for 30~60 min per day.
You could try the following if people are leaving ssh connections open and not doing anything over ssh.
To terminate inactive SSH connections after 5 minutes (300 seconds) or 10 minutes (600 seconds) or any time limit you need, open the sshd server configuration file
in a text editor:
sudo nano /etc/ssh/sshd_config
Modify the following two lines, removing #:
ClientAliveInterval 300
ClientAliveCountMax 0
Save and exit. Then restart the SSH service:
sudo systemctl restart sshd
ClientAliveInterval 300: Sends a keepalive message to inactive ssh client connections every 300 seconds (5 minutes).
ClientAliveCountMax 0: Terminates the connection if the client does not respond to a keepalive message.
