Hello everyone, I’m having some serious issues with my Jetson AGX Orin and I’m hoping you can help me out.
Here’s the situation: I initially tried to install CUDA to compile OpenCV, but I encountered a problem during the installation process. In an attempt to fix it, I removed CUDA and inadvertently deleted some essential NVIDIA packages that were dependencies of CUDA. After rebooting, the BIOS screen would display, but when it should have loaded the Ubuntu login screen, I lost the video signal completely.
To try and resolve this, I flashed the Jetson using SDK Manager. The installation was successful, but now I’m facing a different problem. When I connect the Jetson to a monitor, keyboard, and mouse, there is no display output at all—not even the BIOS screen. The monitor behaves as if no HDMI cable is connected, and there’s no response from the keyboard or mouse (e.g., the Caps Lock light doesn’t toggle on).
I’ve also tried connecting via SSH from the host PC, but I receive a “permission denied” error. When I connect via minicom, I can see some logs and commands during the reboot, but I’m unable to type anything.
You’ll need to attach the minicom boot log. Also, you should mention how you installed CUDA; installing it via JetPack/SDK Manager is the correct method. If you installed from some other package not intended for a Jetson, then it might have messed with the video driver (Jetsons have an integrated GPU, an iGPU, whereas other systems have a discrete GPU, or dGPU…the drivers differ, and so does CUDA at the lower levels).
The Jetson’s GPU is integrated directly to the memory controller (an iGPU). Most GPUs are discrete video cards on the PCI bus (a dGPU). Having both drivers is normally a conflict, although I think they are working on something for Orin (the IGX Orin is a very expensive commercial platform, and it definitely supports both an A6000 GPU and the Orin GPU, but this is special hardware). I don’t know of any current Jetsons which are capable of running both drivers simultaneously.
I don’t know what would have to be backed out to remove the wrong dGPU software and leave only the iGPU software, but since even the serial console is failing, I think you are going to have to flash the unit again and start from scratch.
It is possible to clone the rootfs partition if there is something valuable on it. The raw clone (there is also a sparse clone) can be loopback mounted on a host PC. From that you can examine, copy, or edit that clone, and so if you have something special on it, then you could recover it. Cloning takes a lot of time and disk space though. Let me know if you are interested in cloning; otherwise, I think flashing again is the next step due to the conflict in drivers.
I am not interested in cloning the information. My only interest is to have the Jetson working again, even if it is restored to factory settings. My problem is that when trying to flash the Jetson, everything seems to go fine, but when I connect a video input, I don’t receive any image, nor do I get a response from the keyboard or mouse. I am attaching images and the log of the process.
What is the carrier board you are using? I assume that since this is an industrial module that it is likely some third party carrier board. For a third party carrier board you will find most of the time there is a slightly different copper layout; some pins on the module can be assigned multiple functions, and this is done via device tree. Any third party carrier board would (at least most of the time) require either a patch to the NVIDIA flash software, or else a rebranded flash software to deal with that firmware customization. If you are using JetPack/SDKM without the proper firmware, then I would expect that parts of the Jetson do not function correctly.
Assuming this is a third party carrier board, then the flash software (or patch to NVIDIA flash software) will come from that third party.
