# TX2, error when max out the clock frequencies: n command: -max, please try again or see --help

**URL:** <https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611>\
**Category:** Jetson TX2\
**Created:** [February 27, 2018, 6:59pm UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611 "2018-02-27T18:59:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![heyworld](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/heyworld/32/11375_2.png) [@heyworld](https://forums.developer.nvidia.com/u/heyworld)\
**Post date:** [February 27, 2018, 6:59pm UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611/1 "2018-02-27T18:59:00Z")

</div>

Below command is provided by nvidia l4t documents.

To max out the clock frequencies  
•On the target, execute the following command:  
sudo /home/ubuntu/tegrastats -max  
which forces all runtime-modifiable clock frequencies to their maximum values. When run this way, tegrastats quits immediately after setting the clocks.

However I failed to run it on my machine, the error message is:  
n command: -max, please try again or see --help

Any idea about this?

BTW, sudo /home/ubuntu/tegrastats is totally good, I can see correct status, just argument “-max” doesn’t work.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![dusty\_nv](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/dusty_nv/32/14043_2.png) [@dusty\_nv](https://forums.developer.nvidia.com/u/dusty_nv)\
**Post date:** [February 27, 2018, 8:29pm UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611/2 "2018-02-27T20:29:11Z")

</div>

Hi heyworld, to max out the clocks, please run jetson\_clocks script like so:

```auto
$ sudo ~/jetson_clocks.sh

```

Alternatively, you can use the [nvpmodel](http://www.jetsonhacks.com/2017/03/25/nvpmodel-nvidia-jetson-tx2-development-kit/) tool.

---

<div class="post-metadata">

**Author:** ![Honey\_Patouceul](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/honey_patouceul/32/389777_2.png) [@Honey\_Patouceul](https://forums.developer.nvidia.com/u/Honey_Patouceul)\
**Post date:** [February 27, 2018, 10:41pm UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611/3 "2018-02-27T22:41:06Z")

</div>

Additional note: it is not obvious how nvpmodel and jetson\_clocks interact.

jeston\_clocks.sh boosts the clocks for you current config, that depends on last nvpmodel selected.

nvpmodel tries to use a preset of online cores / clocks for optimizing performance/power on different profiles (you may check the details in /etc/nvpmodel.conf).

The bad thing (at least on R28.2-DP) is that if you are running high speed clocks and then select a low power mode with nvpmodel, it can fail. For example, if I select MAXN mode and boost clocks (max performance), then it fails to properly switch to MAXP\_CORE\_DENVER mode:

```auto
sudo nvpmodel -m0
sudo ./jetson_clocks.sh 

sudo nvpmodel -m4
NVPM WARN: write PARAM GPU: ARG MAX_FREQ: PATH: /sys/devices/17000000.gp10b/devfreq/17000000.gp10b/max_freq VAL: 1134750000
	- probably failed due to it is less than current min value 1300500000
NVPM ERROR: Error writing to /sys/devices/17000000.gp10b/devfreq/17000000.gp10b/max_freq: 22
NVPM ERROR: failed to write PARAM GPU: ARG MAX_FREQ: PATH: /sys/devices/17000000.gp10b/devfreq/17000000.gp10b/max_freq VAL: 1134750000
NVPM ERROR: failed to set power mode!
NVPM ERROR: Failed to exec option requests!

```

So it is better to store the default (slow) clocks after boot with:

```auto
sudo ./jetson_clocks.sh --store

```

that will save the current config into ~/l4t\_dfs.conf and you can restore later with:

```auto
sudo ./jetson_clocks.sh --restore

```

In a similar way, if you change the nvpmodel for a performance mode from low power mode, you may have to relaunch jetson\_clocks to get max boost.

---

<div class="post-metadata">

**Author:** ![shaorui](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shaorui](https://forums.developer.nvidia.com/u/shaorui)\
**Post date:** [August 26, 2021, 1:03am UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611/4 "2021-08-26T01:03:25Z")

</div>

> [@dusty\_nv](#):
>
> `jetson_clocks.sh`

Where is jetson\_clocks.sh directory？

```auto
$ sudo ./jetson_clocks.sh
sudo: ./jetson_clocks.sh: command not found

```

Thanks

---

<div class="post-metadata">

**Author:** ![Honey\_Patouceul](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/honey_patouceul/32/389777_2.png) [@Honey\_Patouceul](https://forums.developer.nvidia.com/u/Honey_Patouceul)\
**Post date:** [August 26, 2021, 11:18am UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611/5 "2021-08-26T11:18:45Z")

</div>

In recent releases, this script has moved from nvidia user home directory to /usr/bin and it has been renamed without sh extension:

```auto
/usr/bin/jetson_clocks

```

---

<div class="post-metadata">

**Author:** ![nadeemm](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/nadeemm/32/367020_2.png) [@nadeemm](https://forums.developer.nvidia.com/u/nadeemm)\
**Post date:** [October 18, 2021, 6:14pm UTC](https://forums.developer.nvidia.com/t/tx2-error-when-max-out-the-clock-frequencies-n-command-max-please-try-again-or-see-help/58611/6 "2021-10-18T18:14:27Z")

</div>


