Agx orin ssh无法登录

agx orin
jp5.1.7 客户自定义板子

升级软件版本,从5.1.2升级到jp5.1.7,jp5.1.2的能ssh能远程登录,jp5.1.7发现ssh没办法登录

  1. 网口设置静态ip,能ping通,但是无法ssh;
  2. 虚拟网口ifconfig无法找到对应网口192.168.55.1

发现sudo systemctl status ssh会有报错,能知道这是什么原因吗,谢谢。

sudo systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2026-09-15 16:54:03 CST; 9min ago
       Docs: man:sshd(8)
             man:sshd_config(5)

9月 15 16:54:03 ubuntu-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
9月 15 16:54:03 ubuntu-desktop systemd[1]: Stopped OpenBSD Secure Shell server.
9月 15 16:54:03 ubuntu-desktop systemd[1]: ssh.service: Start request repeated too quickly.
9月 15 16:54:03 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 16:54:03 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.



eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 48:b0:2d:95:6c:82  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 48:b0:2d:95:6c:7f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether fc:5c:ee:04:36:1e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 92  base 0x5000  

eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.20.1  netmask 255.255.255.0  broadcast 192.168.20.255
        inet6 fe80::c340:2248:84db:5be9  prefixlen 64  scopeid 0x20<link>
        ether fc:5c:ee:04:36:1f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 38  bytes 4310 (4.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 93  base 0x1000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 192  bytes 14174 (14.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 192  bytes 14174 (14.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f2:d8:8a:df:35:99  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether f2:d8:8a:df:35:9b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::d9ea:5d0b:289b:fad6  prefixlen 64  scopeid 0x20<link>
        ether a0:2c:36:5f:a6:2d  txqueuelen 1000  (Ethernet)
        RX packets 3  bytes 455 (455.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 25  bytes 5027 (5.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Hi,

the log shows that the SSH service failed to start, but it does not show the underlying error.

Please run the following command from the Jetson’s local or serial console and share the full output:

sudo journalctl -b -u ssh.service --no-pager

Thanks.

ubuntu@ubuntu-desktop:~$ sudo journalctl -b -u ssh.service --no-pager
[sudo] password for ubuntu: 
-- Logs begin at Tue 2026-09-15 17:28:36 CST, end at Wed 2026-09-16 13:52:44 CST. --
9月 15 17:28:43 ubuntu-desktop systemd[1]: Starting OpenBSD Secure Shell server...
9月 15 17:28:45 ubuntu-desktop sshd[1070]: sshd: no hostkeys available -- exiting.
9月 15 17:28:45 ubuntu-desktop systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
9月 15 17:28:45 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 17:28:45 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.
9月 15 17:28:45 ubuntu-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
9月 15 17:28:45 ubuntu-desktop systemd[1]: Stopped OpenBSD Secure Shell server.
9月 15 17:28:45 ubuntu-desktop systemd[1]: Starting OpenBSD Secure Shell server...
9月 15 17:28:45 ubuntu-desktop sshd[1694]: sshd: no hostkeys available -- exiting.
9月 15 17:28:45 ubuntu-desktop systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
9月 15 17:28:45 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 17:28:45 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.
9月 15 17:28:46 ubuntu-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2.
9月 15 17:28:46 ubuntu-desktop systemd[1]: Stopped OpenBSD Secure Shell server.
9月 15 17:28:46 ubuntu-desktop systemd[1]: Starting OpenBSD Secure Shell server...
9月 15 17:28:47 ubuntu-desktop sshd[1730]: sshd: no hostkeys available -- exiting.
9月 15 17:28:47 ubuntu-desktop systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
9月 15 17:28:47 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 17:28:47 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.
9月 15 17:28:47 ubuntu-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3.
9月 15 17:28:47 ubuntu-desktop systemd[1]: Stopped OpenBSD Secure Shell server.
9月 15 17:28:47 ubuntu-desktop systemd[1]: Starting OpenBSD Secure Shell server...
9月 15 17:28:47 ubuntu-desktop sshd[1747]: sshd: no hostkeys available -- exiting.
9月 15 17:28:47 ubuntu-desktop systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
9月 15 17:28:47 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 17:28:47 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.
9月 15 17:28:48 ubuntu-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4.
9月 15 17:28:48 ubuntu-desktop systemd[1]: Stopped OpenBSD Secure Shell server.
9月 15 17:28:48 ubuntu-desktop systemd[1]: Starting OpenBSD Secure Shell server...
9月 15 17:28:48 ubuntu-desktop sshd[1772]: sshd: no hostkeys available -- exiting.
9月 15 17:28:48 ubuntu-desktop systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
9月 15 17:28:48 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 17:28:48 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.
9月 15 17:28:48 ubuntu-desktop systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
9月 15 17:28:48 ubuntu-desktop systemd[1]: Stopped OpenBSD Secure Shell server.
9月 15 17:28:48 ubuntu-desktop systemd[1]: ssh.service: Start request repeated too quickly.
9月 15 17:28:48 ubuntu-desktop systemd[1]: ssh.service: Failed with result 'exit-code'.
9月 15 17:28:48 ubuntu-desktop systemd[1]: Failed to start OpenBSD Secure Shell server.

Hi,

The error sshd: no hostkeys available -- exiting means SSH has no usable server host keys.

Please run the following commands from the Jetson’s local or serial console to generate any missing default host keys and restart SSH:

sudo ssh-keygen -A
sudo systemctl reset-failed ssh.service
sudo systemctl restart ssh.service
sudo systemctl status ssh.service --no-pager -l

If the service shows active (running), try connecting over Ethernet again. If it still fails, please share the command output and any SSH client error.

Thanks.

按照如上方法,静态网线已经能正常ssh登录,但是typeC口虚拟网口192.168.55.1依然不存在,且无法登录。能修复这个问题吗

type C issue sounds like totally different item.

Are you sure the usb device mode is already detected from your host side?

jp5.1.2和jp5.1.1相同的硬件能通过typeC接口,ssh ubuntu@192.168.55.1登录,但是升级到最新jp5.1.7就不行了,不确定是那个原因导致的

jp5.1.7没办法ping通,并且在设备ifconfig也找不到对应的虚拟网口

請問你的usb host那端在"lsusb" command底下能看到你的Jetson嗎?

lsusb也找不到,是不是我们设备树没有配置到还是什么原因导致的

但是jp5.1.2能找到,硬件都相同

Jetson端的dmesg給出來給我們確認一下.

dmesg.log (102.3 KB)
log如下

給出來的dmesg顯示usb device mode沒有反應.

你們嘗試一下usb type C 正反面都插一下測試看看dmesg有沒有新log.

插拔也没有log,一点log都没有,感觉像是usb type C 没有被enable起来

那還是得問你們device tree怎麼設定的了. 建議開個新ticket. 跟原本的已經離題了

嗯嗯已经重提了一个: Agx orin typeC口无法识别到设备 - Jetson Systems / Jetson AGX Orin - NVIDIA Developer Forums