My Orin AGX devkit was working fine, but is now unreachable via SSH or ping (both ethernet port and USB-C dev port). The problems are basically identical to this post:
i.e. connecting a monitor and keyboard I see the same exact output from the following commands:
dmesg:
[ 12.569313] mdio_bus 6810000.ethernet: MDIO device at address 0 is missing.
[ 12.569328] nvethernet 6810000.ethernet: failed to connect PHY
[ 12.569332] net eth0: ether_open: Cannot attach to PHY (error: -19)
nmcli:
eth0: unavailable
"eth0"
ethernet (nvethernet), 48:B0:2D:A4:D3:92, hw, mtu 1466
ip a:
5: eth0: <BROADCAST,MULTICAST> mtu 1466 qdisc noop state DOWN group default qlen 1000
link/ether 48:b0:2d:a4:d3:92 brd ff:ff:ff:ff:ff:ff
ip link set eth0 up :
RTNETLINK answers: No such device
I attempted to re-flash the device with SDKManager for a fresh install, with JetPack 5.1.1. The flash completes successfully but when attempting to connect to the device via USB to install SDK components it cannot detect the board even after full reset:
Want to clarify that because it seems you misunderstood something.
The problem on ethernet has nothing to do with USB type C. They are independent and won’t affect each other.
Your attempt on sdkmanger to install with sdk seems not related ethernet problem. This could be skipped first.
You could firstly put your board into recovery mode and do flash with manual command from terminal first.
To clarify, I saw the above ethernet service issues first and THEN tried to flash to fix it, the flash did not cause the issues. I have only used SDKManager to flash, not command line so apologies if any of this is incorrect:
I downloaded 36.5 (JetPack 6.2.2) along with its root file system and ran the commands:
Booting with a keyboard and monitor successfully gets to the login screen but the keyboard and mouse do not work so I cannot login. The keyboard works in the NVIDIA boot screen but not on the login screen. I tried hot plugging and got the same result.
Is the device supposed to be reachable via ssh at this point? Pinging/SSHing 192.168.55.1 I still cannot see it, and I also cannot connect serially (ls -al /dev/ttyACM* shows
ls: cannot access ‘/dev/ttyACM*’: No such file or directory).
From your latest update, it looks like the steps you followed to flash the Orin AGX devkit from the command line are correct. However, could you please make sure that you followed all the steps exactly as described in this guide?
Even though the guide uses JetPack 6.1 as an example, the same process applies to JetPack 6.2.2.
If you did follow the guide step by step and the issue still persists, I would suggest skipping the “Create a Default User” step. By omitting this step, the board should launch the initial setup wizard on first boot (connected to a monitor), allowing you to manually configure the system and create a user. This can help you bypass the login screen issue you’re currently experiencing.
If you are sure your board at least booting into Ubuntu login, then above console must provide you logs.
If you are able to operate serial console, share us the dmesg.
Is the device supposed to be reachable via ssh at this point? Pinging/SSHing 192.168.55.1 I still cannot see it, and I also cannot connect serially (ls -al /dev/ttyACM* shows
This is USB interface. We used type C USB as USB device mode and then provide you a ip 192.168.55.1 to ssh it. Now your USB seems to be broken, so it might lead to this interface now showing up.
That is why using UART console is the only way to access the board and check situation.
Please be aware that I am uncertain if it is a hardware defect or software problem without the logs.
Thank you, I followed the guide and got the same result. My first attempt was without using the default user script, but I had the same keyboard and mouse issue and was unable to manually create a user, so I ran with the default user script.
