Hi everyone,
I would like to ensure that the CPU and GPU frequencies remain in Jetson clock mode every time the system boots up. I’ve come across some articles mentioning potential issues with achieving this through automatic startup, such as unsuccessful configuration or the need to set a sleep delay, which seems a bit unreliable.
Therefore, I would like to ask, what is your recommended and most reliable method to maintain Jetson clock mode on every boot?
If these suggestions don’t help and you want to report an issue to us, please attach the model, command/step, and the customized app (if any) with us to reproduce locally.
Hi @WayneWWW
My current setup is as follows: I have chosen multi-user.target as the base, and then jetson_clocks is executed afterward. I would like to know if this target might cause any resource conflicts or if it is appropriate for this purpose. Alternatively, do you have any other recommended targets to suggest?
[Unit]
Description=Jetson Clocks Service
After=multi-user.target