# Jetson Orin NX stuck at NVIDIA logo after custom kernel flash

**URL:** <https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909>\
**Category:** Jetson Orin NX\
**Tags:** boot, kernel, jetson\
**Created:** [February 27, 2026, 12:16pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909 "2026-02-27T12:16:57Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [February 27, 2026, 12:16pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/1 "2026-02-27T12:16:57Z")

</div>

Hi,

I’m facing an issue while flashing a custom kernel on a Jetson Orin NX and wanted to ask if someone has seen this before.

I am using the standard Orin Nano developer kit baseboard and simply replaced the Orin Nano Super module with an Orin NX 16GB module on the same carrier board. The board, with NX, works fine when flashed using SDK Manager, so hardware setup looks correct.

My goal is only to enable SLCAN support and RT kernel, so I built a custom kernel. The exact same kernel and workflow work perfectly on an Orin Nano Super(on SD card, no tried on NVME), but on the Orin NX the system gets stuck during boot(on NVME).

We also tried multiple flashing approaches, not only `flash.sh`. We tried flashing using SDK Manager (which works normally), manual flashing using `flash.sh`, and the initrd flashing method for NVMe flashing, but the result is the same… flashing completes successfully but the Orin NX stops at the NVIDIA logo during boot.

I am currently using the jetson-orin-nano-devkit (and -nvme config as well) configuration because I couldn’t find a separate config for Orin NX on this devkit carrier in Linux-For-Tegra. From what I understand, flashing depends on the correct board configuration and DTB selection, so I’m wondering if this is the reason it hangs. NVIDIA docs mention that flashing uses the board `.conf` file and device tree tied to the module + carrier combination, so maybe I’m using the wrong target configuration but I could be wrong.

Could it be on custom kernel flash, it’s not able to boot from NVME though standard firmware from SDKmanager works fine

System details:

- Orin NX 16GB module

- Orin Nano devkit carrier

- NVMe boot

- JetPack 6.2.1 / L4T 36.4.7

- Kernel 5.15.148-tegra

- Host PC Ubuntu 22.04

SDK Manager flash boots normally, only custom flashing causes the hang.

Need help with this

Thanks.

---

<div class="post-metadata">

**Author:** ![carolyuu](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/carolyuu/32/14043_2.png) [@carolyuu](https://forums.developer.nvidia.com/u/carolyuu)\
**Post date:** [February 27, 2026, 12:39pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/2 "2026-02-27T12:39:54Z")

</div>

\*\*\* Please note that this reply is generated by LLM automatically \*\*\*

I’d be happy to help you troubleshoot the issue with flashing a custom kernel on your Jetson Orin NX module.

Firstly, it’s great that you’ve tried multiple flashing approaches, including SDK Manager, manual flashing, and initrd flashing, but unfortunately, the result is the same - the system gets stuck during boot.

Based on your description, it seems that the issue might be related to the board configuration and DTB (Device Tree Binary) selection. As you mentioned, NVIDIA docs state that flashing uses the board file and device tree tied to the module-carrier combination.

Since you’re using the Orin Nano developer kit baseboard with an Orin NX 16GB module, you might need to use a different configuration file. Although you couldn’t find a separate config for Orin NX on this devkit carrier, you can try using the `jetson-orin-nx-devkit.conf` file instead of `jetson-orin-nano-devkit.conf`.

Additionally, you can try using the `flash.sh` command with the `--board` option to specify the correct board configuration. For example:

```bash
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 --board jetson-orin-nx-devkit

```

If you’re still facing issues, you can try comparing the device tree files used by SDK Manager and your custom flashing approach. You can extract the device tree file from the SDK Manager flash package and compare it with the one used in your custom flashing approach.

To extract the device tree file from the SDK Manager flash package, you can use the following command:

```bash
sudo ./tools/kernel_flash/l4t_generate_soc_bup.sh --board jetson-orin-nx-devkit --output-dir /path/to/output/dir

```

This will generate the device tree file and other necessary files in the specified output directory.

By comparing the device tree files, you might be able to identify any differences that could be causing the issue.

Lastly, since you’re using a custom kernel, you can try booting the system with the standard firmware from SDK Manager and then switching to your custom kernel to see if the issue persists.

I hope these suggestions help you troubleshoot the issue and successfully flash your custom kernel on the Jetson Orin NX module.

**Comparison with Orin Nano Super**

Since you mentioned that the exact same kernel and workflow work perfectly on an Orin Nano Super, it’s possible that the issue is specific to the Orin NX module or the devkit carrier.

One key difference between the Orin Nano Super and Orin NX is the module type and the corresponding device tree files. The Orin Nano Super uses the `jetson-orin-nano-devkit.conf` file, while the Orin NX might require a different configuration file, as mentioned earlier.

Additionally, the Orin NX module has different power modes and configurations compared to the Orin Nano Super. You can try checking the power mode configuration in your custom kernel and ensure that it’s compatible with the Orin NX module.

By comparing the device tree files and power mode configurations between the Orin Nano Super and Orin NX, you might be able to identify any differences that could be causing the issue.

\*\*\* Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. \*\*\*

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [February 27, 2026, 1:10pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/3 "2026-02-27T13:10:11Z")

</div>

Hey! So there is no `jetson-orin-nx-devkit.conf` available. Am I missing something?

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [February 27, 2026, 4:13pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/4 "2026-02-27T16:13:07Z")

</div>

please ignore previous answer generated by LLM. Some items are not correct.

I can guess some possible reasons that lead to your problem but you better getting the serial log by using USB ttl cable first.

> **[Jetson Nano & NX Style - Serial Debug Console - JetsonHacks](https://jetsonhacks.com/2019/04/19/jetson-nano-serial-console/)**
>
> The Serial Debug Console is the most basic way to be able to interface with your Jetson Nano & NX Style Developer Kit. All it takes is a magic wire!

The log would provide the precise reaon.

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [February 27, 2026, 6:51pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/5 "2026-02-27T18:51:55Z")

</div>

Thanks @WayneWWW I tried this and problem is jetson never reaches up till the point it can be detected over USB ttl for serial debug. I tried and was not getting any data.

But I’ll try it today / tomorrow again and update here if I get something.

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [February 28, 2026, 7:49pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/6 "2026-02-28T19:49:32Z")

</div>

@WayneWWW So I tried and getting no data on serial console. Could it be the kernel is not being loaded?

I tried flashing using this command as well though, but not luck (using 1TB ssd and modified `flash_l4t_t234_nvme.xml` for updated num\_sectors:  
`sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml -S 966367641600 --showlogs --erase-all jetson-orin-nano-devkit-super-maxn-nvme external`

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 1, 2026, 6:02pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/7 "2026-03-01T18:02:54Z")

</div>

Hi @WayneWWW , finally got the log:

Seems like it’s UEFI closing to boot in recovery only. But ya, let me know where I am going wrong?

Thanks

[jeson\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/idHeeKbTTNuyjQW2A5aLhjWpOVT.txt) (73.4 KB)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 2, 2026, 2:19am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/9 "2026-03-02T02:19:28Z")

</div>

> Jetson System firmware version 36.4.4-gcid-41062509 date 2025-06-16T15:25:51+00:  
> 00  
> ESC to enter Setup.  
> F11 to enter Boot Manager Menu.  
> Enter to continue boot.  
> L4TLauncher: Attempting Recovery Boot  
> EFI stub: Booting Linux Kernel…

Device is stuck in recovery boot. Please get the status back to normal boot and dump log again.

Follow this to make it back:

> [@Jetson AGX Orin FAQ](https://forums.developer.nvidia.com/t/jetson-agx-orin-faq/237459#p-1101540-q-my-device-got-stuck-in-recovery-boot-how-to-recover-without-reflashing-34):
>
> Q: How to apply PCN210100 overlay patch? PCN210100 is supported from Jetpack 5.1.3. If you are using 5.1.1 or 5.1.2, there are overlay packages in: [Jetson Linux 35.3.1 | NVIDIA Developer](https://developer.nvidia.com/embedded/jetson-linux-r3531)[Jetson Linux 35.4.1 | NVIDIA Developer](https://developer.nvidia.com/embedded/jetson-linux-r3541) If your device is AGX Orin 64GB, please also add the patch mentioned in below link: [AGX orin 64GB flash fail - #3 by DaveYYY](https://forums.developer.nvidia.com/t/agx-orin-64gb-flash-fail/293127/3) Without this patch, Orin AGX 64GB with PCN update may not get flashed Q: I cannot control GPIO in Jetpack 6.0, 6.1 and 6.2, but it works with…

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 2, 2026, 11:21am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/10 "2026-03-02T11:21:23Z")

</div>

Hi @WayneWWW ! New logs:  
Mount is failing

[jeson\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/pggyciNpwqkDlnGKBoI55JXYO5j.txt) (127.7 KB)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 2, 2026, 1:32pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/11 "2026-03-02T13:32:12Z")

</div>

The mounting is failing because pcie driver fails to load.

After your kernel customization, you need to upload kernel modules (.ko) files too.

And pcie driver is part of initrd driver too so you need to put new pcie-tegra194.ko into initrd too.

> **[sudo nv-update-initrd - Kernel Customization — NVIDIA Jetson Linux Developer...](https://docs.nvidia.com/jetson/archives/r36.4.4/DeveloperGuide/SD/Kernel/KernelCustomization.html#building-the-nvidia-out-of-tree-modules)**
>
> You can manually rebuild the kernel used for the NVIDIA® Jetson™ Linux. You must have Internet access for this.

→ To update the initramfs, run the following commands

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 2, 2026, 5:06pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/12 "2026-03-02T17:06:16Z")

</div>

@WayneWWW Thanks, though I got past the issue of getting stuck at nvidia screen, I got stuck at initial desktop GUI without any icons. I got ubuntu system config setup, I entered a username and password and it boots to the initial desktop window but no icons and this log:

[jeson\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/1kWfdULECToMFAcsyXK5klMIn6M.txt) (75.9 KB)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 3, 2026, 3:55am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/13 "2026-03-03T03:55:12Z")

</div>

Please bypass the configuration first by using l4t-create-default-users.sh script in Linux\_for\_Tegra/tools.

I don’t think this is related to original problems you hit.

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 3, 2026, 8:04am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/14 "2026-03-03T08:04:51Z")

</div>

Hi @WayneWWW ! Did that and over serial console, I can login but on display, stuck at “exiting boot services“. Also noticed under home, there is only Desktop folder. None of the other folders liek Documents, etc, are not available.

Here’s the log:

[jetson\_log.txt](https://forums.developer.nvidia.com/secure-uploads/nvidia/original/4X/7/d/e/7de38ee47815661455061cf620dae9f3178a3341.txt) (78.7 KB)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 3, 2026, 9:10am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/15 "2026-03-03T09:10:04Z")

</div>

This seems not related to the kernel customization but more related to BSP preparation.

Is this issue happened after your kernel customization?

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 3, 2026, 9:44am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/16 "2026-03-03T09:44:27Z")

</div>

Yes @WayneWWW ! I simple added slcan in defconf. Not sure what’s going wrong for Orin NX though same kernel works fine on Jetson orin Nano Super.

Last command I used to flash: `sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --erase-all jetson-orin-nano-devkit-super-maxn-nvme internal`

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 3, 2026, 12:38pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/17 "2026-03-03T12:38:25Z")

</div>

@WayneWWW Probably am i missing some packages specific to jetson orin NX, causing this issue?

---

<div class="post-metadata">

**Author:** ![cristian.hidalgo](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/cristian.hidalgo/32/450067_2.png) [@cristian.hidalgo](https://forums.developer.nvidia.com/u/cristian.hidalgo)\
**Post date:** [March 3, 2026, 3:46pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/18 "2026-03-03T15:46:47Z")

</div>

Hi @sharma.sanket272, hope you are doing great.

This wiki on Orin NX might help you out: [NVIDIA Jetson Orin NX - JetPack 6.1 - Flashing Board](https://developer.ridgerun.com/wiki/index.php/NVIDIA_Jetson_Orin_NX/JetPack_6.1/Flashing_Board)

Regards,

Embedded Software Engineer  
RidgeRun | [https://www.ridgerun.com/](https://www.ridgerun.com/)

Contact us: [support@ridgerun.com](mailto:support@ridgerun.com)  
Developers wiki: [https://developer.ridgerun.com/](https://developer.ridgerun.com/)

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 5, 2026, 10:50am UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/19 "2026-03-05T10:50:50Z")

</div>

Hi @cristian.hidalgo ! Thanks a lot. I tried it but still no luck.

I am wondering because my main requirement is having slcan support, probably should build module natively? Any suggestions? @WayneWWW @cristian.hidalgo

---

<div class="post-metadata">

**Author:** ![sharma.sanket272](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sharma.sanket272](https://forums.developer.nvidia.com/u/sharma.sanket272)\
**Post date:** [March 6, 2026, 6:16pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/20 "2026-03-06T18:16:58Z")

</div>

Hi! The issue is solved. Since building and flashing the kernel for the NX was giving me a hard time, and my main requirement was to just get slcan and some other modules, I built those as an oot module for the same kernel build that is on my Jetson (flashed using SDK Manager).

Then I installed the module at `/lib/modules/$(uname -r)/updates`. After that, I ran `sudo depmod -a` to update the module index, and it worked. Thanks for the help.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [March 20, 2026, 6:17pm UTC](https://forums.developer.nvidia.com/t/jetson-orin-nx-stuck-at-nvidia-logo-after-custom-kernel-flash/361909/21 "2026-03-20T18:17:53Z")

</div>

Closed on March 20, 2026, 6:17pm UTC

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