Jetson orion nano developer kit unable to boot - shows black screen with white keyboard cursor flashing

Hi Community,

I purchased Jetson Orion nano developer kit recently and was able to set it up by running the install via MicroSD and then also attached SSD card to it. For some reason, this week it failed to boot, suspecting it might be a corrupted SD I then went on to flash the SD card with the Jetpack 6.2 from this website https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v4.3/jp62-orin-nano-sd-card-image.zip

When I tried to install again with the newly flashed SD card it showed the normal NVDIA screen > I pressed ESC > picked SD card to boot > it then showed the following messages and then followed by the black screen with the flashing cusor, it then got stucked in the cursor black screen forever:
/LTILauncher: Attempting Recovery Boot

E2I status: Booting Linux Kernel…

E2I status: Using MTF from configuration table

E2I status: Loaded initrd from LIMBO_EFI_INITRD_MEDIA_SHIM device path

E2I status: Exiting boot services…

Here’s a video:

I thought it’s a defective SD card so I purchased a brand new SD card, flashed the jetpack6.2 , ran the install but getting the exact same outcome (black screen)…

My firmware per boot up ESC key check is: 36.4.3.

I am really puzzled why it cannot boot up as it was all good when I first received the tool and I did exactly what I did originally. Can anyone please help, it’s really frustrating as this is merely a 1 month old device, I don’t believe it would be a damaged hardware or something…

Thanks community..

Regards,
Jerry

NVM. Resolved by sdk manager.

But what is the solution, I have a very similar problem, just that my firmware is 36.4.4.
It was working jetpack 6.2, in a sd, i tried to copy it and to run it from a solid state drive of 2 tb, it was recognized by the booard, so i though that there was no problem, i moved some the configuration, i followed this instructions:
Make sure the NVMe is detected:
*lsblk

Partition & Format the NVMe This will erase everything on the NVMe!
*sudo parted /dev/nvme0n1

Inside parted:
*mklabel gpt
*mkpart primary ext4 1MiB 100%
*quit

Then format:
*sudo mkfs.ext4 /dev/nvme0n1p1

Mount it:
*sudo mkdir /mnt/nvme
*sudo mount /dev/nvme0n1p1 /mnt/nvme

……………………………………………..
Clone the current root filesystem, You can copy everything from / to the NVMe:
*sudo rsync -axv --progress / /mnt/nvme

You may want to exclude /mnt/nvme itself and /proc, /sys, /dev and other virtual filesystems — a safer version:
sudo rsync -axv --exclude='/mnt/nvme/’ --exclude=‘/proc/’ --exclude='/sys/’ --exclude=‘/dev/*’ / /mnt/nvme

………………………………
Update the Bootloader to boot from NVMe
On JetPack 5.x/6.x, the Orin bootloader supports NVMe by default.
You simply need to modify the rootfs location.
Edit /boot/extlinux/extlinux.conf:
*sudo nano /boot/extlinux/extlinux.conf

Find the line starting with APPEND and change the root= to point to the NVMe, for example:
*APPEND … root=/dev/nvme0n1p1 rw rootwait …

Save & exit.

After all of these i retired the ssd and i am just trying to boot with the sd card, also i am trying to reset the bios to default but it is also not working. When i start the jetson i get:

jetson system firmware version 36.4.4 gcid …
then
ESC to enter setup
F11 to enter the boot manager menu
Enter to cotinue boot
L4T launcher: Attempting Recovering boot
EFI stub Booting linux kernel
efi stub using dbt from configurtation table
efi stub loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
efi stub exiting boot services…

And after that, a black screen with a cursor in the top right appears, and nothing else happens, it has the operative system saved in the sd

Hi there,

My solution was to install Jetson 6.2 via the SDK manager instead of flashing the OS to SD card via Balena Ethecher.

This is the youtube guide I followed: https://www.youtube.com/watch?v=CmDaXah4l5g&ab_channel=CytronTechnologies

This is the official written guide: 🛸 Initial Setup (SDK Manager method) - NVIDIA Jetson AI Lab

If you check out past cases, someone from NVDIA often point to SDK manager as the method when dealing with blank screen.

Take note the process was quite painful and long, as the SDK manager kept reporting dependencies failure, network authentication failure but after 4 hours of persist attempts, mine managed to completed the SDK flash,

With regards to the instructions you tried to followed, I believe that’s the one to move your OS from SD to your SSD, if you do the SDK manager method, it will give you the option to pick whether you want to flash it to SD card or your SSD, since yours is already black out, might as well utilize the SDK manager and flash it on the SSD.

I am curious though to find out why did the jetson failed despite that I did not do any modification.
At this time I presume the SD card as OS is susceptible to such failure?

1 Like

It worked, thank you so much, just that i needed a computer with the corresponding ubuntu, also it took a while as you said, but thank you, it is done!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.