This was previously working.
I click the button that says “25W” at the top of the screen and then select Power Mode→ “MAXN SUPER.” Immediately a dialog opens saying “Warning - System reboot is required to apply changes. Do you want to reboot now?’ with options for OK and Cancel. Even after I reboot, the system is still in 25W mode.
Same problem if I pick 15W or 7W mode.
Any ideas on how to fix?
Thank you.
*** Please note that this reply is generated by LLM automatically ***
The issue you’re experiencing with your Jetson Orin Nano seems to be related to the power mode not changing even after rebooting the system. Here are a few potential causes and solutions:
Power Mode Configuration: Ensure that you’re selecting the correct power mode from the dropdown menu. In your case, you’re trying to switch to MAXN_SUPER, which requires a minimum of 8.0V to the VDD_IN pins (as mentioned in the documentation). Verify that your power supply meets this requirement.
nvpmodel Configuration File: The power mode details for your device are stored in the /etc/nvpmodel.conf file. You can try editing this file manually to set the desired power mode. However, be cautious when making changes to system configuration files, as incorrect settings can cause system instability.
System Reboot: Although you’ve mentioned that you’ve rebooted the system, try performing a power cycle (turning off the power supply, waiting for a few seconds, and then turning it back on) to ensure that the system is fully reset.
Firmware or Software Issues: It’s possible that there’s a firmware or software issue preventing the power mode from changing. Check for any updates to the Jetson Orin Nano’s firmware or software, and apply them if available.
Hardware Issues: If none of the above solutions work, it’s possible that there’s a hardware issue with your Jetson Orin Nano. Try using a different power supply or checking the VDD_IN pins for any damage or corrosion.
In comparison to other Jetson models, the Jetson Orin Nano has similar power management features, but the specific power modes and requirements may vary. The MAXN_SUPER power mode, in particular, is mentioned in the documentation as requiring a minimum of 8.0V to the VDD_IN pins, which is specific to the Jetson Orin NX.
To troubleshoot the issue further, you can try checking the system logs for any error messages related to power mode changes. Additionally, you can try using the nvpmodel command-line tool to set the power mode manually and see if that resolves the issue.
Example usage of the nvpmodel command:
sudo nvpmodel -m <mode>
Replace <mode> with the desired power mode (e.g., MAXN_SUPER, 15W, or 7W).
If none of these solutions work, you may want to consider seeking further assistance from NVIDIA support or the Jetson Orin Nano community forums.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Hi barca,
What’s the Jetpack version in use?
Do you mean that there’s no issue before you perform this?
Could you share the result of the following command on your devkit?
# nvpmodel -q --verbose
And provide the /etc/nvmodel.conf on your board for further check.
FYI: I’ve managed to change the power mode using:
sudo nvpmodel -m 2 --force
System info:
Jetpack version appears to correspond to JetPack 6.1 Rev 1.
head -n 1 /etc/nv_tegra_release:
R36 (release), REVISION: 4.7, GCID: 42132812, BOARD: generic, EABI: aarch64,
jetson_release shows:
Model: NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super
When I say “this worked before,” I mean changing the power mode using the dropdown menu was working a couple months ago on the same system.
nvpmodel -q --verbose returns
NVPM VERB: Config file: /etc/nvpmodel.conf
NVPM VERB: parsing done for /etc/nvpmodel.conf
NVPM VERB: Current mode: NV Power Mode: 25W
1
NVPM VERB: PARAM CPU_ONLINE: ARG CORE_0: PATH /sys/devices/system/cpu/cpu0/online: REAL_VAL: 1 CONF_VAL: 1
NVPM VERB: PARAM CPU_ONLINE: ARG CORE_1: PATH /sys/devices/system/cpu/cpu1/online: REAL_VAL: 1 CONF_VAL: 1
NVPM VERB: PARAM CPU_ONLINE: ARG CORE_2: PATH /sys/devices/system/cpu/cpu2/online: REAL_VAL: 1 CONF_VAL: 1
NVPM VERB: PARAM CPU_ONLINE: ARG CORE_3: PATH /sys/devices/system/cpu/cpu3/online: REAL_VAL: 1 CONF_VAL: 1
NVPM VERB: PARAM CPU_ONLINE: ARG CORE_4: PATH /sys/devices/system/cpu/cpu4/online: REAL_VAL: 1 CONF_VAL: 1
NVPM VERB: PARAM CPU_ONLINE: ARG CORE_5: PATH /sys/devices/system/cpu/cpu5/online: REAL_VAL: 1 CONF_VAL: 1
NVPM VERB: PARAM FBP_POWER_GATING: ARG FBP_PG_MASK: PATH /sys/devices/platform/gpu.0/fbp_pg_mask: REAL_VAL: 0 CONF_VAL: 2
NVPM VERB: PARAM TPC_POWER_GATING: ARG TPC_PG_MASK: PATH /sys/devices/platform/gpu.0/tpc_pg_mask: REAL_VAL: 0 CONF_VAL: 240
NVPM VERB: PARAM GPU_POWER_CONTROL_ENABLE: ARG GPU_PWR_CNTL_EN: PATH /sys/devices/platform/gpu.0/power/control: REAL_VAL: auto CONF_VAL: on
NVPM VERB: PARAM CPU_A78_0: ARG MIN_FREQ: PATH /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq: REAL_VAL: 729600 CONF_VAL: 729600
NVPM VERB: PARAM CPU_A78_0: ARG MAX_FREQ: PATH /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: REAL_VAL: 1728000 CONF_VAL: 1344000
NVPM VERB: PARAM CPU_A78_1: ARG MIN_FREQ: PATH /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq: REAL_VAL: 729600 CONF_VAL: 729600
NVPM VERB: PARAM CPU_A78_1: ARG MAX_FREQ: PATH /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq: REAL_VAL: 1728000 CONF_VAL: 1344000
NVPM VERB: PARAM CPU_A78_2: ARG MIN_FREQ: PATH /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq: REAL_VAL: 729600 CONF_VAL: 729600
NVPM VERB: PARAM CPU_A78_2: ARG MAX_FREQ: PATH /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq: REAL_VAL: 1728000 CONF_VAL: 1344000
NVPM VERB: PARAM CPU_A78_3: ARG MIN_FREQ: PATH /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq: REAL_VAL: 729600 CONF_VAL: 729600
NVPM VERB: PARAM CPU_A78_3: ARG MAX_FREQ: PATH /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq: REAL_VAL: 1728000 CONF_VAL: 1344000
NVPM VERB: PARAM CPU_A78_4: ARG MIN_FREQ: PATH /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq: REAL_VAL: 729600 CONF_VAL: 729600
NVPM VERB: PARAM CPU_A78_4: ARG MAX_FREQ: PATH /sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq: REAL_VAL: 1728000 CONF_VAL: 1344000
NVPM VERB: PARAM CPU_A78_5: ARG MIN_FREQ: PATH /sys/devices/system/cpu/cpu5/cpufreq/scaling_min_freq: REAL_VAL: 729600 CONF_VAL: 729600
NVPM VERB: PARAM CPU_A78_5: ARG MAX_FREQ: PATH /sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq: REAL_VAL: 1728000 CONF_VAL: 1344000
NVPM VERB: PARAM GPU: ARG MIN_FREQ: PATH /sys/devices/platform/17000000.gpu/devfreq_dev/min_freq: REAL_VAL: 306000000 CONF_VAL: 0
NVPM VERB: PARAM GPU: ARG MAX_FREQ: PATH /sys/devices/platform/17000000.gpu/devfreq_dev/max_freq: REAL_VAL: 1020000000 CONF_VAL: 918000000
NVPM VERB: PARAM GPU_POWER_CONTROL_DISABLE: ARG GPU_PWR_CNTL_DIS: PATH /sys/devices/platform/gpu.0/power/control: REAL_VAL: auto CONF_VAL: auto
NVPM VERB: PARAM EMC: ARG MAX_FREQ: PATH /sys/kernel/nvpmodel_clk_cap/emc: REAL_VAL: 3199000000 CONF_VAL: 3199000000
Thank you.
I reinstalled l4t + jetpack using sdk mgr and everything is working normally now. Don’t have to reboot to change modes using the GUI.
Do you mean there’s no original issue after you use SDK manager to reflash the board?
The “original issue” was fixed by reinstalled JetPack/L4T using the SDK Manager.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.