I recently purchased a brand-new Jetson Orin Nano Super Developer Kit (8GB) and installed JetPack 7.2 on an NVMe SSD using the official Jetson ISO installer.
The board boots and works normally, but I’m facing an issue with the power modes.
In the Power Mode GUI, I can only see:
7W
15W
I do not see 25W or MAXN SUPER.
However, MAXN SUPER is not completely unavailable on my system. I can manually enable MAXN SUPER from the terminal using nvpmodel commands, and the board successfully switches to MAXN SUPER mode and operates correctly. Performance increases as expected, which suggests that the hardware and MAXN SUPER profile are functioning properly.
The problem is that the setting is not persistent. After every reboot, the board automatically returns to 15W mode, and the GUI again shows only 7W and 15W as available options. I have to manually enable MAXN SUPER after each boot.
What I have checked:
Official 19V power supply
Fresh JetPack 7.2 installation on NVMe SSD
Board operates normally
MAXN SUPER can be enabled manually through the terminal
After reboot, system always returns to 15W
GUI continues to show only 7W and 15W
Because MAXN SUPER can be activated manually and works correctly, I suspect this may be a power-mode persistence issue, startup configuration issue, or a JetPack 7.2 software bug rather than a hardware problem.
I would appreciate guidance on the following:
Is this a known issue with JetPack 7.2 on the Orin Nano Super Developer Kit?
Should 25W and MAXN SUPER appear in the Power Mode GUI?
Is there a way to make MAXN SUPER persist across reboots?
Would reinstalling JetPack 7.2 be expected to resolve this issue, or is it likely a software/configuration problem?
— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —
To address the issue of the Jetson Orin Nano Super Developer Kit not showing 25W and MAXN SUPER power modes in the Power Mode GUI after installing JetPack 7.2, and the setting not being persistent across reboots, we need to consider the provided context and the specific details of the Jetson Orin Nano platform.
Understanding Power Modes: The Jetson Orin Nano supports various power modes, including 7W, 15W, 25W, and MAXN SUPER. These modes are designed to offer a balance between performance and power consumption. The MAXN SUPER mode, in particular, is an uncapped power mode that enables the highest number of cores and clock frequency for CPU, GPU, DLA, PVA, and SOC engines, making it ideal for demanding applications.
Persistence of Power Modes: Typically, the power mode settings should persist across reboots. However, the behavior described suggests a potential issue with how the power mode is being set or saved.
Manual Activation of MAXN SUPER: The fact that MAXN SUPER can be manually activated through the terminal using nvpmodel commands and works correctly indicates that the hardware and the MAXN SUPER profile are functioning properly. This suggests that the issue might be related to the software or configuration rather than a hardware problem.
JetPack Version and Compatibility: The issue is observed with JetPack 7.2, which is a specific software version for the Jetson platform. It’s essential to consider whether this is a known issue with JetPack 7.2 on the Orin Nano Super Developer Kit.
Given the information and the context provided:
Is this a known issue with JetPack 7.2 on the Orin Nano Super Developer Kit? The provided context does not explicitly mention this as a known issue. However, the behavior described could be related to configuration or software issues rather than a hardware problem.
Should 25W and MAXN SUPER appear in the Power Mode GUI? Yes, these power modes should be available for the Jetson Orin Nano Super Developer Kit, especially considering that MAXN SUPER can be manually enabled and works correctly.
Is there a way to make MAXN SUPER persist across reboots? Typically, settings like power modes should persist across reboots. The persistence issue might be related to how the setting is being saved or applied during the boot process. Checking the configuration files related to power management or the nvpmodel settings might provide insights.
Would reinstalling JetPack 7.2 be expected to resolve this issue, or is it likely a software/configuration problem? Reinstalling JetPack 7.2 might resolve the issue if it’s related to a software or configuration problem that occurred during the initial installation. However, if the issue persists after reinstallation, it could indicate a more specific problem with the device’s configuration or the JetPack version itself.
Recommendations:
Check the official NVIDIA documentation and forums for any known issues related to power modes in JetPack 7.2 on the Jetson Orin Nano Super Developer Kit.
Verify the nvpmodel configuration and ensure that the MAXN SUPER mode is correctly set and saved.
Consider reinstalling JetPack 7.2 to rule out any installation-related issues.
If the issue persists, it may be beneficial to seek further assistance from NVIDIA support or the developer community, as it could be a specific bug or configuration issue that requires more detailed troubleshooting.
Remember, the Jetson Orin Nano platform, like other embedded systems, can have version-specific issues or configuration nuances that affect its behavior. Always refer to the most current and relevant documentation for the specific hardware and software versions in use.
— We support team will also look into your issue to have further suggestions soon. please stay tuned. —
I installed JetPack 7.2 using the official Jetson ISO installer.
The ISO was written to a USB flash drive using Balena Etcher.
The Jetson Orin Nano Developer Kit was booted from the USB installer and Jetson Linux r39.2 / JetPack 7.2 was installed to the NVMe SSD.
No SDK Manager, flash.sh, or l4t_initrd_flash.sh commands were used.
sudo nvpmodel -q
NV Power Mode: 15W
0
Issue:
Only the 15W power mode is available. 25W mode and MAXN SUPER are missing. Any attempt to change the power mode reverts back to 15W after reboot.
Currently, the ISO image cannot upgrade a device from non-Super Mode to Super Mode.
Please use an x86 host to reflash the device with the Super Mode configuration.
I have this exact same issue (right down to the same command line outputs as pictured above).
So how are we supposed to flash the device when the ISO that we download to the laptop (the x86 host) to generate the USB doesn’t seem to contain the “Super Mode” configuration to begin with ? Or are we all missing some sort of step that’s not mentioned in the Quick Start Guide ?
I was able to unlock these modes by performing a proper Jetpack installation. I downloaded the Driver Package (BSP) and Sample Root Filesystem from JetPack SDK Downloads and Notes | NVIDIA Developer then I unzipped the Sample Root Filesystem into the Linux_for_Tegra/rootfs folder and ran the script ./apply_binaries.sh and then performed the installation with these script
#!/usr/bin/env bash
set -euo pipefail
BOARD="jetson-orin-nano-devkit-super"
EXT_DEV="nvme0n1p1"
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
cd "$SCRIPT_DIR"
if [[ "${EUID}" -ne 0 ]]; then
echo "Run this script with sudo"
exit 1
fi
echo "=================================================="
echo " Jetson Orin Nano Super flashing to NVMe"
echo "=================================================="
[[ -x ./tools/kernel_flash/l4t_initrd_flash.sh ]] || {
echo "Missing: ./tools/kernel_flash/l4t_initrd_flash.sh"
exit 1
}
[[ -f ./bootloader/generic/cfg/flash_t234_qspi.xml ]] || {
echo "Missing: ./bootloader/generic/cfg/flash_t234_qspi.xml"
exit 1
}
[[ -f ./tools/kernel_flash/flash_l4t_t234_nvme.xml ]] || {
echo "Missing: ./tools/kernel_flash/flash_l4t_t234_nvme.xml"
exit 1
}
./tools/kernel_flash/l4t_initrd_flash.sh
--showlogs
--network usb0
--external-device "${EXT_DEV}"
-p "-c ./bootloader/generic/cfg/flash_t234_qspi.xml"
-c ./tools/kernel_flash/flash_l4t_t234_nvme.xml
"${BOARD}" internal
echo "=================================================="
echo " DONE"
echo "=================================================="
Here is my result cat /etc/nv_boot_control.conf TNSPEC 3767-300-0005-T.1-1-1-jetson-orin-nano-devkit-super- COMPATIBLE_SPEC 3767--0005--1--jetson-orin-nano-devkit-super- TEGRA_BOOT_STORAGE nvme0n1 TEGRA_CHIPID 0x23 TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0 TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
and sudo nvpmodel -q NV Power Mode: MAXN_SUPER 2
Hellkin6, I think you mentioned that you got it to work using nvpmodel. How did you do this? Did you modify the .conf file?
I did not see a .conf file for the p3766. Even being able to do this from CLI is helpful.
Having the only option to install from old version Ubuntu laptop is pretty sad. I can install earlier Ubuntu version under Windows wsl2 but I think it may require actually installing Jetpack 6.x which I don’t know if that could be an installed distro under wsl2. Does anyone know?
@photomark I went into the same issue. There is super-conf here: /etc/nvpmodel/nvpmodel_p3767_0003_super.conf you can move the symlink: sudo ln -sf /etc/nvpmodel/nvpmodel_p3767_0003_super.conf /etc/nvpmodel.conf but this does not help. After reboot it is gone again. You can even move the symlink around and I was able to see the MAXN_SUPER power mode being switched on (in the UI)
sudo cp /etc/nvpmodel/nvpmodel_p3767_0003.conf /etc/nvpmodel/nvpmodel_p3767_0003.conf.original
sudo cp /etc/nvpmodel/nvpmodel_p3767_0003_super.conf /etc/nvpmodel/nvpmodel_p3767_0003.conf
# and doing a reboot
you fooled the software - Jetson Power GUI is still saying Freq 1510 MHz.
Since I do not have an Ubuntu Host, my idea is to use a live Ubuntu system from USB thumb drive, install the required SDK Manager and use the usb-c connection from ubuntu live system to flash it. As long as NVIDIA is not coming up with a better idea…
From what im gathering, NVIDIA gave us the wrong iso, while also not mentioning this issue anywhere in the quickstart guide. So we are stuck wth brand new boards at 60% ability unless you have another x86 host. Classic.
dpkg-reconfigure nvidia-14t-bootloader
dpkg-query: package ‘nvidia-14t-bootloader’ is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: nvidia-14t-bootloader is not installed
this is the output
