I just used the SDKManager to update my AGX Nano 64gb dev-kit machine to JetPack 6.1. It flashed the new OS version, and it boots up, but neither the mouse nor the keyboard work. As a result, I am unable to complete the Ubuntu setup, Nor am I able to do anything with the device – SSH is not enabled (so please don’t ask me to post copies of the logs – I cannot get them.)
During boot, I can see the log messages on the screen in the few seconds before the Ubuntu start-up screen appears, and everything mostly looks fine, except for a number things (like OpenBSD_SSH or something) could not start, and a couple other things. I don’t know if that is normal or not. Ubuntu seems happy enough, just waiting for me to click “Start”, which I would love to do, but for the keyboard and mouse not working.
And, yes, the keyboard and mouse work fine – they worked with the Nano before I attempted the upgrade.
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!
Better clarifying what are you trying to asking here first.
There is nothing called “AGX Nano”. Only AGX Orin, Orin NX and Orin Nano.
Orin Nano has not 64GB to use either. This forum is for Orin AGX but not Orin Nano.
Are you using a NV devkit or custom board? Or you are not sure what I am talking about here?
The behavior is actually not like a devkit. Many users cannot tell whether they are using NV devkit or custom board. So if you are uncertain, please just tell you are not sure.
It would seem that there have been a number of unrelated problems, some of which I have gotten past.
(First, I am using WSL.)
I flashed the upgrade from Ubuntu 24, instead of Ubuntu 18 or 22. (I am unclear on why this should matter)
Attempting to flash from Ubuntu 22 resulted, many times, in the SDKManager completely freezing at various points – at 33%, 77%, and at 94% complete. This left the Ubuntu instance either frozen as well, or in a state where the simplest command (e.g. ps -aux) would seg fault.
At this point I began downloading an ISO for Ubuntu 22 to install on a laptop I have available. 2 gigs into that, I was informed that I am out of disk space. Surely that might explain the behavior with the WSL Ubuntu locking up. I freed up 70 GB of space and started the process over. It completed the download successfully.
The Jetson then dropped the USB connection, and booted up in regular, non-recovery, mode. Whereas before I had some red error lines in the dmsg log on startup (which I was able to see for about all of 2 seconds), now there are no red error lines (that is the best I can tell you, as again, I see the last ~100 lines out of about 10,000 for about 2 seconds). The Jetson then goes to a blue screen and sits there. Not quite the same shade of blue as a Windows BSOD (it’s a little darker, closer to a royal blue, if anyone cares), but equally discouraging.
The USB connection reverts to one where it exposes files and a few directories on the Jetson.
The SDKManager complains that “no board detected”, and I cannot proceed.
If I reboot the Jetson back into recovery mode, SDKManager is happy to see a “board” is connected, and lets me proceed, whereupon after a few seconds it fails, and highlights the IP address, and complains that it could not make an SSH connection.
Do I need the original packaging to return this thing? Because I am about 3 days away from doing that, and I no longer have the original box. In summary, my experience with this device has been extraordinarily frustrating and disappointing.
Actually it is always better to use native Ubuntu host. We don’t suggest to use WSL.
The board could be detected on lsusb by sdkmanager with 2 method. First one is putting the board into recovery mode. And the second one is if the board is able to boot into kernel and enable usb device mode.
The current situation here is 2nd way is not available (reason unknown) so you could only enable recovery mode to make your host detect your Jetson.
Just to clarify, entering recovery mode is a very basic operation on any Jetson boards. It is the first thing you should learn when you get this board.
Please forget about ssh connection, enable the serial console log by connecting the micro usb cable and follow this website to dump boot log. NVIDIA Jetson Orin AGX - In Board - Getting in Board - Serial Console
Share us the boot log so that I can check why usb does not work on your side.
BTW, if you don’t have micro usb port on your board, please let us know too.
We are engineer team here so we don’t involve with any return policy. I don’t see any points here that could say your board has hardware problem. Better dumping the log so that we can check what is going on. The whole situation looks like a software issue so far.
I have installed Ubuntu 22 on a laptop I have available. Ultimately, I am still in the same situation as before, but I feel like this will go better.
I have attached the microUSB cable, and gotten the boot log, which I will attempt to attach to the reply.
I can see that Ubuntu is showing a second ethernet adapter, configured for IPv4 192.168.55.1, as expected. It is unable to use it however, and it repeatedly complains that it cannot activate the connection.
When the Jetson is in either mode, lsusb shows a device called “NVIDIA Corp. Tegra On-Platform Operator”, which I don’t think I saw in WSL. In recovery mode, it shows “NVIDIA Corp. APX”
Just one reminder. Your boot_log.txt got truncated in each line. What I am telling is each line from your log is not completed. Please resize the terminal and dump the log again.
Also, one question here, does your board have type C port on it?
The ssh connection will only work after you complete the system configuration (user name/pwd), but as usb has some problem which makes you not able to do that now.
I don’t see usb driver enabled in your log. That could be the cause of this problem, but as the log is not completed, need you to share full one first.
I have now, apparently, been able to properly flash the device. I tried again with no monitor, keyboard, or mouse attached.
I am able to ssh into the device, and in that respect it seems to operate as expected.
However, the monitor does not work when connected. More accurately, it works initially, during the boot sequence, but it seems once the OS starts, it either goes completely blank (with no signal going to the monitor), or I get the previously mentioned blue screen.
run manual flash command (remember to put the board into recovery mode before running command)
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
After this method, check your UART serial console log. It shall not get stuck in the “Please complete system configuration setup on desktop to proceed…”. If so, please share me the result of “sudo dmesg” and “lsmod” commands.
I have now done the manual flashing. There was no difference: the device seems to work fine, except the display does not work. It works fine during UEFI boot, then blanks. Then maybe depending on whether a mouse/keyboard is connected ¯_(ツ)_/¯ , either stops sending any signal to the monitor, OR shows only a blue screen.
I could not get the UART log; for some reason it is finicky about connecting, and today it wouldn’t find ttyACM0.
What exactly is in the image that gets flashed? Is it a complete disk image, or a differential image which depends on something else already being on the disk?
Just to clarify. What I am doing here will not fix your usb problem. What I an trying to do here is let you bypass the “Please complete system configuration setup on desktop to proceed…”.
The SSH/dmesg/lsmod commands would only work after you bypass this. And I need the dmesg and lsmod to check usb situation.
Also, this image is same as what sdkmanger flashed to your Jetson before. So if UART was alive, then it should be alive here too. As I told, this package is previsouly installed by sdkmanager to your host. It is just sdkmanager won’t run “l4t_create_default_user.sh”. What we’ve done here is just running this script.
